August 26, 2026AIExplore

How to Use Runway Text to Video Generation

Write Gen-4.5 Text to Video prompts with clear visuals and motion, set duration and ratio, and iterate one variable at a time without wasting credits.

Runway

Runway Text to Video turns a written shot description into a short clip without an input image. On current official Gen-4.5 help, Gen-4.5 is Runway’s most advanced model for Text to Video and Image to Video. It costs 12 credits per second, supports durations from 2 to 10 seconds, outputs 720p, and is available on web for Standard and higher plans. Confirm live plan access and rates in Runway help and runwayml.com/pricing. Product map: /explore/runway.

This guide shows how to write prompts that include both visuals and motion, how to choose duration, and how to iterate without wasting credits. Pair it with Image to Video at /blog/how-to-use-runway-image-to-video-generation when you already have a strong still, and with image generation at /blog/how-to-use-runway-image-generation when you want to design the first frame first.

When Text to Video is the right mode

Use Text to Video when you do not have a locked first frame and you need to invent the whole shot: subject, environment, lighting, and motion. Prefer Image to Video when brand composition is already approved as a still. Prefer Video to Video when you are transforming footage you already shot.

Step by step Text to Video workflow

1. Write a one shot brief

Name subject, environment, camera move, action, lighting, and style. One primary action per clip. If you need a sequence of events, lengthen duration toward the top of the Gen-4.5 range instead of stuffing three scenes into two seconds.

Scenario:
A realistic runway workflow is being prepared for Use Runway Text to Video Generation using runway. The starting requirement is: Shot brief Subject: pour over coffee maker on wood counter Environment: quiet kitchen, soft afternoon side light Camera: slow orbit Action: steam rises; no people Style: cinematic product hero Locks: no logos, no on screen text Duration: 5s | Ratio: 16:9 | Model: Gen-4.5. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Shot brief Subject: pour over coffee maker on wood counter Environment: quiet kitchen, soft afternoon side light Camera: slow orbit Action: steam rises; no people Style: cinematic product hero Locks: no logos, no on screen text Duration: 5s | Ratio: 16:9 | Model: Gen-4.5" that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Inputs:
Use the actual source material required for this task, together with the intended audience, destination, format, and quality requirements. Specify relevant files, text, URLs, structured data, reference assets, dimensions, language, tone, timing, model or generation settings, credentials, field mappings, or integration values when they apply. Keep secrets out of the example and use the product's supported credential or configuration mechanism.

Workflow:
1. Start with one representative input that contains the important characteristics of the real workload.
2. Configure runway specifically for the requested task and make the important settings explicit.
3. Run the first pass and inspect the result against the objective.
4. Correct only the settings or source material responsible for a failed requirement instead of changing everything at once.
5. Validate the intermediate result before passing it to the next step.
6. When the result meets the requirements, save the successful configuration so the same process can be repeated consistently.
7. If this is a multi-step workflow, verify each handoff and keep a clear fallback or review path for failures.

Requirements:
The example must use supported functionality only. Do not invent product features, pricing, limits, integrations, model names, API behavior, or unavailable settings. Preserve important source data and formatting. Validate required fields before processing, handle empty or invalid input explicitly, prevent accidental duplicate processing where relevant, and stop or route the item for review when a required step fails. For credentials, use the supported secure configuration rather than placing secrets directly in the content.

Expected output:
The final result should directly satisfy the "Shot brief Subject: pour over coffee maker on wood counter Environment: quiet kitchen, soft afternoon side light Camera: slow orbit Action: steam rises; no people Style: cinematic product hero Locks: no logos, no on screen text Duration: 5s | Ratio: 16:9 | Model: Gen-4.5" requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

2. Draft the prompt in full sentences

Official guidance says Text to Video prompts should describe both visual and motion elements in clear, direct language. Keyword stacks alone increase ambiguity.

Scenario:
A realistic runway workflow is being prepared for Use Runway Text to Video Generation using runway. The starting requirement is: Prompt draft Slow orbit around a ceramic pour over coffee maker on a wooden counter. Warm afternoon side light. Soft steam rises from the carafe. Background stays blurred and uncluttered. No logos, no on screen text.. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Prompt draft Slow orbit around a ceramic pour over coffee maker on a wooden counter. Warm afternoon side light. Soft steam rises from the carafe. Background stays blurred and uncluttered. No logos, no on screen text." that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Prompt draft Slow orbit around a ceramic pour over coffee maker on a wooden counter. Warm afternoon side light. Soft steam rises from the carafe. Background stays blurred and uncluttered. No logos, no on screen text." requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

3. Set duration, ratio, and generate

Gen-4.5 Text to Video lists 16:9 at 1280x720. Choose 24 or 25 fps in advanced settings when offered. At 12 credits per second, a 5 second clip costs 60 credits and a 10 second clip costs 120 credits.

Scenario:
A realistic runway workflow is being prepared for Use Runway Text to Video Generation using runway. The starting requirement is: Preflight [ ] Model Gen-4.5 [ ] Duration matches action count [ ] Aspect ratio matches delivery [ ] Credit cost estimated [ ] Prompt has visuals AND motion. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Preflight [ ] Model Gen-4.5 [ ] Duration matches action count [ ] Aspect ratio matches delivery [ ] Credit cost estimated [ ] Prompt has visuals AND motion" that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Preflight [ ] Model Gen-4.5 [ ] Duration matches action count [ ] Aspect ratio matches delivery [ ] Credit cost estimated [ ] Prompt has visuals AND motion" requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

4. Iterate one variable

Change only camera, or only subject action, or only lighting. Keep the rest identical so you can learn what fixed the failure.

Scenario:
A realistic runway workflow is being prepared for Use Runway Text to Video Generation using runway. The starting requirement is: Iteration log V1: slow orbit, steam, 5s V2: same, add subtle handheld shake V3: remove shake; lengthen steam only Keep: V2 framing, V3 motion cleanliness. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Iteration log V1: slow orbit, steam, 5s V2: same, add subtle handheld shake V3: remove shake; lengthen steam only Keep: V2 framing, V3 motion cleanliness" that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Iteration log V1: slow orbit, steam, 5s V2: same, add subtle handheld shake V3: remove shake; lengthen steam only Keep: V2 framing, V3 motion cleanliness" requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

Practical Text to Video use cases

Cinematic kitchen hero

Scenario:
A realistic runway workflow is being prepared for Use Runway Text to Video Generation using runway. The starting requirement is: Slow tracking shot through a sunlit kitchen. Steam rises from a mug on the counter. Soft morning light through sheer curtains. Gentle camera push in. Natural motion only. No dialogue, no logos.. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Slow tracking shot through a sunlit kitchen. Steam rises from a mug on the counter. Soft morning light through sheer curtains. Gentle camera push in. Natural motion only. No dialogue, no logos." that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Slow tracking shot through a sunlit kitchen. Steam rises from a mug on the counter. Soft morning light through sheer curtains. Gentle camera push in. Natural motion only. No dialogue, no logos." requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

Social vertical rain street

Scenario:
A realistic runway workflow is being prepared for Use Runway Text to Video Generation using runway. The starting requirement is: Vertical night street in the rain. Neon reflections on wet asphalt. A cyclist rides toward camera through shallow puddles. Handheld feel with subtle shake. Moody teal and amber light. No logos.. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Vertical night street in the rain. Neon reflections on wet asphalt. A cyclist rides toward camera through shallow puddles. Handheld feel with subtle shake. Moody teal and amber light. No logos." that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Vertical night street in the rain. Neon reflections on wet asphalt. A cyclist rides toward camera through shallow puddles. Handheld feel with subtle shake. Moody teal and amber light. No logos." requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

Wildlife story beat

Scenario:
A realistic runway workflow is being prepared for Use Runway Text to Video Generation using runway. The starting requirement is: Wide shot of a fox in fresh snow at dawn. The fox lifts its head and exhales visible breath. Camera holds steady. Soft pink morning light. Quiet cinematic mood. No text.. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Wide shot of a fox in fresh snow at dawn. The fox lifts its head and exhales visible breath. Camera holds steady. Soft pink morning light. Quiet cinematic mood. No text." that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Wide shot of a fox in fresh snow at dawn. The fox lifts its head and exhales visible breath. Camera holds steady. Soft pink morning light. Quiet cinematic mood. No text." requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

Fashion runway glance

Scenario:
A realistic runway workflow is being prepared for Use Runway Text to Video Generation using runway. The starting requirement is: Medium shot of a model walking toward camera on a minimal white set. Soft overhead studio light. Camera dollies backward to keep framing. Fabric moves with each step. No logos.. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Medium shot of a model walking toward camera on a minimal white set. Soft overhead studio light. Camera dollies backward to keep framing. Fabric moves with each step. No logos." that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Medium shot of a model walking toward camera on a minimal white set. Soft overhead studio light. Camera dollies backward to keep framing. Fabric moves with each step. No logos." requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

Macro product texture

Scenario:
A realistic runway workflow is being prepared for Use Runway Text to Video Generation using runway. The starting requirement is: Extreme close up of brushed aluminum speaker grille. Soft side light reveals micro texture. Camera slowly drifts left. Specular highlights slide gently. No text.. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Extreme close up of brushed aluminum speaker grille. Soft side light reveals micro texture. Camera slowly drifts left. Specular highlights slide gently. No text." that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Extreme close up of brushed aluminum speaker grille. Soft side light reveals micro texture. Camera slowly drifts left. Specular highlights slide gently. No text." requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

Documentary city morning

Scenario:
A realistic runway workflow is being prepared for Use Runway Text to Video Generation using runway. The starting requirement is: Handheld wide of a quiet subway entrance at sunrise. Commuters walk through soft haze. Camera pans left following foot traffic. Natural color. No on screen titles.. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Handheld wide of a quiet subway entrance at sunrise. Commuters walk through soft haze. Camera pans left following foot traffic. Natural color. No on screen titles." that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Handheld wide of a quiet subway entrance at sunrise. Commuters walk through soft haze. Camera pans left following foot traffic. Natural color. No on screen titles." requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

Abstract motion graphic feel

Scenario:
A realistic runway workflow is being prepared for Use Runway Text to Video Generation using runway. The starting requirement is: Abstract ribbons of liquid chrome flowing through deep black space. Slow camera push in. Soft volumetric light shafts. Seamless loop friendly motion. No logos.. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Abstract ribbons of liquid chrome flowing through deep black space. Slow camera push in. Soft volumetric light shafts. Seamless loop friendly motion. No logos." that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Abstract ribbons of liquid chrome flowing through deep black space. Slow camera push in. Soft volumetric light shafts. Seamless loop friendly motion. No logos." requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

Food steam close up

Scenario:
A realistic runway workflow is being prepared for Use Runway Text to Video Generation using runway. The starting requirement is: Close up of a bowl of ramen on a wood table. Thick steam rises toward a soft backlight. Camera locked. Chopsticks rest still in frame. No text.. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Close up of a bowl of ramen on a wood table. Thick steam rises toward a soft backlight. Camera locked. Chopsticks rest still in frame. No text." that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Close up of a bowl of ramen on a wood table. Thick steam rises toward a soft backlight. Camera locked. Chopsticks rest still in frame. No text." requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

Architecture dusk orbit

Scenario:
A realistic runway workflow is being prepared for Use Runway Text to Video Generation using runway. The starting requirement is: Slow aerial orbit of a modern glass pavilion at dusk. Warm interior lights glow. Reflections ripple on a nearby pool. Smooth cinematic camera. No people.. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Slow aerial orbit of a modern glass pavilion at dusk. Warm interior lights glow. Reflections ripple on a nearby pool. Smooth cinematic camera. No people." that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Slow aerial orbit of a modern glass pavilion at dusk. Warm interior lights glow. Reflections ripple on a nearby pool. Smooth cinematic camera. No people." requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

Sports training grit

Scenario:
A realistic runway workflow is being prepared for Use Runway Text to Video Generation using runway. The starting requirement is: Side tracking shot of a runner on an empty wet track at night. Stadium lights cut through mist. Camera tracks beside the subject. Strong motion blur on background. No logos.. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Side tracking shot of a runner on an empty wet track at night. Stadium lights cut through mist. Camera tracks beside the subject. Strong motion blur on background. No logos." that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Side tracking shot of a runner on an empty wet track at night. Stadium lights cut through mist. Camera tracks beside the subject. Strong motion blur on background. No logos." requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

More copyable prompts

Scenario:
A realistic runway workflow is being prepared for Use Runway Text to Video Generation using runway. The starting requirement is: Prompt: office ambient Quiet open office at night. Only desk lamps glow. Camera slowly pushes down a corridor. Paper edges flutter from HVAC air. No people faces. No text.. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Prompt: office ambient Quiet open office at night. Only desk lamps glow. Camera slowly pushes down a corridor. Paper edges flutter from HVAC air. No people faces. No text." that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Prompt: office ambient Quiet open office at night. Only desk lamps glow. Camera slowly pushes down a corridor. Paper edges flutter from HVAC air. No people faces. No text." requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

Scenario:
A realistic runway workflow is being prepared for Use Runway Text to Video Generation using runway. The starting requirement is: Prompt: ocean cliff Wide cliffside path above the ocean. Wind moves tall grass. A lone hiker walks away from camera. Slow pan right. Golden hour. No logos.. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Prompt: ocean cliff Wide cliffside path above the ocean. Wind moves tall grass. A lone hiker walks away from camera. Slow pan right. Golden hour. No logos." that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Prompt: ocean cliff Wide cliffside path above the ocean. Wind moves tall grass. A lone hiker walks away from camera. Slow pan right. Golden hour. No logos." requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

Scenario:
A realistic runway workflow is being prepared for Use Runway Text to Video Generation using runway. The starting requirement is: Prompt: lab sci fi Clean laboratory bench with glassware. Soft cyan under glow. Camera locked. Liquid swirls slowly inside a flask. No readable labels.. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Prompt: lab sci fi Clean laboratory bench with glassware. Soft cyan under glow. Camera locked. Liquid swirls slowly inside a flask. No readable labels." that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Prompt: lab sci fi Clean laboratory bench with glassware. Soft cyan under glow. Camera locked. Liquid swirls slowly inside a flask. No readable labels." requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

Scenario:
A realistic runway workflow is being prepared for Use Runway Text to Video Generation using runway. The starting requirement is: Prompt: kids storybook tone Soft illustration style meadow at noon. A red kite dips and rises. Camera tilts up following the kite. Gentle clouds drift. No text.. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Prompt: kids storybook tone Soft illustration style meadow at noon. A red kite dips and rises. Camera tilts up following the kite. Gentle clouds drift. No text." that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Prompt: kids storybook tone Soft illustration style meadow at noon. A red kite dips and rises. Camera tilts up following the kite. Gentle clouds drift. No text." requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

Scenario:
A realistic runway workflow is being prepared for Use Runway Text to Video Generation using runway. The starting requirement is: Prompt: car teaser Night garage. A matte electric coupe sits centered. Camera orbits slowly. Cool overhead practicals. Reflections crawl across the body. No brand marks.. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Prompt: car teaser Night garage. A matte electric coupe sits centered. Camera orbits slowly. Cool overhead practicals. Reflections crawl across the body. No brand marks." that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Prompt: car teaser Night garage. A matte electric coupe sits centered. Camera orbits slowly. Cool overhead practicals. Reflections crawl across the body. No brand marks." requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

Prompt writing guidance

Lead with camera and subject action
Name lighting in concrete terms
Lock brand unsafe elements with positive phrasing
Prefer one motion idea per short duration
Lengthen duration when actions are sequenced
Avoid expecting precise dialogue or lip sync from text alone

Tips and verification

Verify model access on your plan. Official Gen-4.5 help lists Standard and higher for Text to Video. Free plan details describe a one time 125 credit deposit and watermarks. Credit costs and plan prices can change, so confirm on the credits help article and runwayml.com/pricing before promising deliverables.

Keep a short shot list beside your Runway session. Note model, duration, aspect ratio, and the one motion change you will try next. That habit saves credits when you iterate.

When a generation pauses or a plan limit appears, confirm your plan and remaining credits in the dashboard instead of guessing. Official Free plan help notes watermarks and a one time credit deposit.

Treat every clip as a draft until you review subject identity, flicker, and unwanted text. Export only after a full playback, not a frozen thumbnail.

If you collaborate, store winning prompts on a shared page with the seed when available. Reuse the prompt skeleton and change one variable at a time.

Match delivery early. A 9:16 social cut is harder to rescue from a 16:9 master than starting in the correct ratio.

Separate exploration from finals. Draft on lower cost models when they fit the mode, then spend Gen-4.5 credits once motion and framing are locked.

For client work, keep a verification note: no invented logos, no trademarked characters, and no claims the footage cannot support.

Close each session by archiving the best still or last frame for the next shot. Continuity across clips beats regenerating from memory.