August 26, 2026AIExplore

How to Use Runway Video to Video Editing

Edit existing footage in Runway Edit Studio with Aleph, write clear change deltas, preserve timing, and avoid retired Gen-3 workflows.

Runway

Runway Video to Video transforms existing footage instead of inventing a shot from scratch. Official help states older Gen-3 Alpha and Gen-3 Alpha Turbo Video to Video features were retired, with Video to Video directed to Edit Studio Aleph 2.0. Academy model listings show Aleph 2.0 at 28 credits per second for video editing and stylization, and Gen-4 Aleph at 15 credits per second. Confirm which Aleph option your workspace shows before budgeting. Overview: /explore/runway.

This guide shows how to write edit deltas, preserve motion, and avoid asking for a brand new scene. Pair with Image to Video at /blog/how-to-use-runway-image-to-video-generation and Custom style exploration via stills at /blog/how-to-use-runway-image-generation.

When Video to Video fits

Use it to restyle, regrade atmosphere, or change specific elements while keeping path, timing, and camera intent. If you need a wholly new composition, switch to Text to Video or Image to Video.

Step by step Video to Video workflow

1. Trim to the story beat

Shorter source clips are easier to evaluate. Remove dead space before you spend credits per second of output.

Scenario:
A realistic runway workflow is being prepared for Use Runway Text to Video Generation using runway. The starting requirement is: Source prep [ ] Trim to the action [ ] Stabilize only if shake is unintentional [ ] Note what must stay identical [ ] Export a clean intermediate. 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 "Source prep [ ] Trim to the action [ ] Stabilize only if shake is unintentional [ ] Note what must stay identical [ ] Export a clean intermediate" 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 "Source prep [ ] Trim to the action [ ] Stabilize only if shake is unintentional [ ] Note what must stay identical [ ] Export a clean intermediate" 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. Describe the delta

Say what changes and what remains. Style, weather, time of day, or object swaps work better one at a time.

Scenario:
A realistic runway workflow is being prepared for Use Runway Text to Video Generation using runway. The starting requirement is: Edit prompt Convert to animated watercolor style. Preserve walking pace and camera angle. Keep the same path through the frame. No added characters.. 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 "Edit prompt Convert to animated watercolor style. Preserve walking pace and camera angle. Keep the same path through the frame. No added characters." 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 "Edit prompt Convert to animated watercolor style. Preserve walking pace and camera angle. Keep the same path through the frame. No added characters." 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. Generate, compare, tighten

Play source and output side by side. If identity or timing slips, reduce the size of the change. Confirm credit rate for Aleph 2.0 or Gen-4 Aleph in the current UI.

Scenario:
A realistic runway workflow is being prepared for Use Runway Text to Video Generation using runway. The starting requirement is: Compare checklist [ ] Timing still matches [ ] Subject path intact [ ] Style change landed [ ] No unwanted new props [ ] Flicker acceptable. 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 "Compare checklist [ ] Timing still matches [ ] Subject path intact [ ] Style change landed [ ] No unwanted new props [ ] Flicker acceptable" 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 "Compare checklist [ ] Timing still matches [ ] Subject path intact [ ] Style change landed [ ] No unwanted new props [ ] Flicker acceptable" 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 Video to Video use cases

Watercolor street

Scenario:
A realistic runway workflow is being prepared for Use Runway Text to Video Generation using runway. The starting requirement is: [upload walking clip] Animated watercolor style. Preserve pace and framing. No new 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 "[upload walking clip] Animated watercolor style. Preserve pace and framing. No new 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 "[upload walking clip] Animated watercolor style. Preserve pace and framing. No new 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.

Night to dusk regrade

Scenario:
A realistic runway workflow is being prepared for Use Runway Text to Video Generation using runway. The starting requirement is: [upload city clip] Shift to blue hour atmosphere. Keep traffic motion. Do not redesign buildings.. 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 "[upload city clip] Shift to blue hour atmosphere. Keep traffic motion. Do not redesign buildings." 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 "[upload city clip] Shift to blue hour atmosphere. Keep traffic motion. Do not redesign buildings." 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.

Snow atmosphere

Scenario:
A realistic runway workflow is being prepared for Use Runway Text to Video Generation using runway. The starting requirement is: [upload park path clip] Add light falling snow. Preserve camera move. Keep subject clothing colors.. 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 "[upload park path clip] Add light falling snow. Preserve camera move. Keep subject clothing colors." 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 "[upload park path clip] Add light falling snow. Preserve camera move. Keep subject clothing colors." 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.

Anime style pass

Scenario:
A realistic runway workflow is being prepared for Use Runway Text to Video Generation using runway. The starting requirement is: [upload dialogue scene] Stylize toward clean anime shading. Preserve lip motion timing as much as possible. No new characters.. 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 "[upload dialogue scene] Stylize toward clean anime shading. Preserve lip motion timing as much as possible. No new characters." 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 "[upload dialogue scene] Stylize toward clean anime shading. Preserve lip motion timing as much as possible. No new characters." 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.

Product footage polish

Scenario:
A realistic runway workflow is being prepared for Use Runway Text to Video Generation using runway. The starting requirement is: [upload handheld product clip] Cleaner studio look, softer shadows. Keep product shape and labels readable. No logo invention.. 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 "[upload handheld product clip] Cleaner studio look, softer shadows. Keep product shape and labels readable. No logo invention." 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 "[upload handheld product clip] Cleaner studio look, softer shadows. Keep product shape and labels readable. No logo invention." 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.

Vintage film look

Scenario:
A realistic runway workflow is being prepared for Use Runway Text to Video Generation using runway. The starting requirement is: [upload documentary clip] Subtle 16mm grain and warmer highlights. Preserve documentary framing. No scene redesign.. 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 "[upload documentary clip] Subtle 16mm grain and warmer highlights. Preserve documentary framing. No scene redesign." 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 "[upload documentary clip] Subtle 16mm grain and warmer highlights. Preserve documentary framing. No scene redesign." 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.

Remove distraction ask carefully

Scenario:
A realistic runway workflow is being prepared for Use Runway Text to Video Generation using runway. The starting requirement is: [upload interview] Simplify busy background toward soft bokeh. Keep subject face and gesture timing. Do not change wardrobe.. 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 "[upload interview] Simplify busy background toward soft bokeh. Keep subject face and gesture timing. Do not change wardrobe." 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 "[upload interview] Simplify busy background toward soft bokeh. Keep subject face and gesture timing. Do not change wardrobe." 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.

Season swap

Scenario:
A realistic runway workflow is being prepared for Use Runway Text to Video Generation using runway. The starting requirement is: [upload tree lined road] Autumn foliage colors. Keep camera speed. Do not add vehicles.. 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 "[upload tree lined road] Autumn foliage colors. Keep camera speed. Do not add vehicles." 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 "[upload tree lined road] Autumn foliage colors. Keep camera speed. Do not add vehicles." 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.

Illustration hybrid

Scenario:
A realistic runway workflow is being prepared for Use Runway Text to Video Generation using runway. The starting requirement is: [upload dance clip] Graphic novel ink wash style. Preserve choreography. No costume redesign.. 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 "[upload dance clip] Graphic novel ink wash style. Preserve choreography. No costume redesign." 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 "[upload dance clip] Graphic novel ink wash style. Preserve choreography. No costume redesign." 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.

Weather intensity

Scenario:
A realistic runway workflow is being prepared for Use Runway Text to Video Generation using runway. The starting requirement is: [upload rainy window clip] Increase rain density on glass. Keep interior exposure. Camera locked behavior unchanged.. 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 "[upload rainy window clip] Increase rain density on glass. Keep interior exposure. Camera locked behavior unchanged." 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 "[upload rainy window clip] Increase rain density on glass. Keep interior exposure. Camera locked behavior unchanged." 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 prompts

Scenario:
A realistic runway workflow is being prepared for Use Runway Text to Video Generation using runway. The starting requirement is: Prompt: sky only Keep motion. Change only the sky to overcast. Buildings and people unchanged.. 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: sky only Keep motion. Change only the sky to overcast. Buildings and people unchanged." 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: sky only Keep motion. Change only the sky to overcast. Buildings and people unchanged." 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: reduce flicker Style is right. Reduce texture flicker on walls. Preserve timing.. 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: reduce flicker Style is right. Reduce texture flicker on walls. Preserve timing." 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: reduce flicker Style is right. Reduce texture flicker on walls. Preserve timing." 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: color pop Keep realism. Increase saturation on the red jacket only. Everything else restrained.. 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: color pop Keep realism. Increase saturation on the red jacket only. Everything else restrained." 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: color pop Keep realism. Increase saturation on the red jacket only. Everything else restrained." 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: soft dream Add gentle bloom and softer contrast. Preserve blocking and pace.. 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: soft dream Add gentle bloom and softer contrast. Preserve blocking and pace." 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: soft dream Add gentle bloom and softer contrast. Preserve blocking and pace." 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: reject full reshoot Do not invent a new camera path. Edit the uploaded motion only.. 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: reject full reshoot Do not invent a new camera path. Edit the uploaded motion only." 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: reject full reshoot Do not invent a new camera path. Edit the uploaded motion only." 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.

Tips and verification

Do not follow retired Gen-3 Video to Video tutorials as current product truth. Official retirement notices point to Edit Studio Aleph 2.0. Credit figures on the academy page can change; verify in your account before large jobs.

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.