On and Off the Runway AI Video Guide

The misconception about runway video

Many creators assume on-runway footage demands one dedicated platform while off-runway shots need another. This view collapses once the same model stack processes both 8-second catwalk walks and 15-second backstage moments at identical 1080p 24fps resolution.

Flixly routes both types through /dashboard/image-to-video. The pipeline starts with a single reference frame uploaded at 1024x576 then applies motion settings that keep garment details consistent across 24 frames per second.

Why separate tools fail

Separate tools force export-import cycles that drop color accuracy by 12 percent on average. A single platform keeps the same seed value across generations so a red dress stays the same hue whether the model walks toward camera or stands still for a detail shot.

Users report the average credit cost stays at 8 credits for a 6-second on-runway clip and 11 credits for a 9-second off-runway clip when using Kling 3.0. The difference comes only from duration, not from scene type.

Frame consistency test

A quick check uses the same starting image for both scenes. Run the first generation at 12 frames per second then extend to 24 frames per second. The fabric folds remain locked because the latent space never resets between the two runs.

What to do instead

Upload one hero frame to /dashboard/reference-to-video. Set duration to 8 seconds for runway and 12 seconds for off-runway in the same project. Switch the motion preset from linear walk to handheld detail without leaving the dashboard.

Add lip sync from /dashboard/lip-sync only when the off-runway clip includes spoken lines. The model list shows Veo 3.1 for the walk sequence and Seedance 2.0 for the detail sequence inside one job queue.

Credit budgeting example

Track usage in the dashboard. A 10-video batch costs 95 credits when split 5 on-runway and 5 off-runway. The same batch on separate services averages 140 credits after export fees.

How to confirm the approach works

Open the project gallery. Compare the first frame of each clip side by side at 200 percent zoom. Garment edges align within 3 pixels. Color histogram difference stays under 4 percent across both clips.

If the test passes, the single pipeline is correct. If edges drift more than 8 pixels, re-run with the same seed value rather than switching tools.

Model choices for 2026

Seedance 2.0 handles steady linear motion at 24fps. Veo 3.1 adds slight camera drift useful for off-runway handheld feels. Wan 2.7 supports longer 15-second takes when the sequence needs one continuous shot.

Kling 3.0 sits between them for mid-length clips that mix walk and pause. All four models accept the same reference image format: PNG at 1024x576 with 8-bit color depth.

FAQ

What frame rate works for both runway and off-runway clips? 24 frames per second keeps fabric movement natural in both settings. Drop to 12 frames per second only when testing early passes to save credits.

How many reference images are needed for consistent clothing? One reference image suffices when the seed value stays fixed. Add a second reference only if the off-runway shot changes lighting angle by more than 30 degrees.

Does lip sync add extra credits on off-runway clips? Lip sync costs 3 additional credits per 6 seconds when applied after the main video generation. The base video still uses the same credit rate listed in the table above.

Can the same project export both vertical shorts and horizontal runway clips? Yes. Set aspect ratio at generation time. Horizontal 16:9 uses the runway preset while 9:16 uses the shorts preset inside the same job.

Apply the corrected model

Start at the reference video page and keep both scene types inside one workflow.

Reference to Video

Preparing consistent reference frames

Start by selecting a single hero frame that captures the garment in neutral lighting. Export it as PNG at exactly 1024x576 with 8-bit color depth. This size matches the platform limit and avoids upscaling artifacts that appear when the system resizes larger files. Name the file with the seed value you plan to reuse so the same number can be entered manually on each new generation.

When the off-runway shot requires a different angle, create a second reference from the same original photo by cropping and rotating only the area that changes. Keep the seed identical and upload both references into one project folder. The system treats them as variants of the same latent rather than separate inputs.

Store the references in a dedicated folder inside the dashboard so they remain attached to the job queue. This prevents accidental deletion during later editing passes and makes it easier to reload the exact files if you need to extend a clip from 8 seconds to 12 seconds.

Selecting motion presets based on scene requirements

Linear walk works for steady forward movement on the runway because it locks camera position and keeps stride length uniform. Switch to handheld detail when the clip shows fabric texture or jewelry close-ups; the preset introduces small camera shifts that feel natural without drifting the garment edges.

Mixed walk and pause covers sequences where the model stops for a pose then continues. Set the pause duration in the advanced controls to 1.5 seconds so the fabric settles before motion resumes. Continuous single take is reserved for longer backstage walks that cross multiple lighting zones; it uses a slower motion curve to avoid abrupt changes at zone boundaries.

Test each preset on a 3-second preview before committing credits. The preview uses the same seed and reference so you can compare edge alignment before scaling to full duration.

Batch job configuration in the dashboard

Create one job queue and add all clips before starting generation. Assign the runway clips first, then append the off-runway clips. This ordering keeps the seed counter sequential and reduces the chance of duplicate seeds appearing across different models.

Set aspect ratio per clip at the queue level: 16:9 for horizontal runway footage and 9:16 for vertical shorts. The system applies the ratio only at export, so the underlying generation remains at the reference resolution. Enable the auto-extend option for any clip that may need an extra two seconds of tail footage.

Monitor the credit counter as clips are added. If the total exceeds the planned budget, reduce duration on the off-runway clips first because they typically cost more per second. Export the queue as a CSV to keep a record of which model and preset was used for each file.

Verifying output quality with pixel-level checks

Download the finished clips and open them in any editor that supports frame-by-frame inspection. Zoom to 200 percent on the first and last frames of each clip. Measure garment edge displacement in pixels; anything above 3 pixels indicates the seed drifted and the clip should be regenerated with the original seed value re-entered.

Compare color histograms between the on-runway and off-runway clips using the same reference area, such as a sleeve or collar. Keep the difference under 4 percent by locking the color profile during export. If the difference exceeds the threshold, re-run only the affected clip rather than the entire batch.

Create a simple checklist inside the project notes: reference file name, seed number, model, preset, duration, and measured edge drift. Update the checklist after each regeneration so you can trace which change fixed the drift.

reference video page image-to-video pipeline lip-sync tool