FIELD GUIDE

Runway ProRes and PNG Sequence Exports: When to Spend More Than MP4

An MP4 clip may be perfectly adequate for quick previews and most web publishing. An effects-heavy production may instead need a higher-fidelity handoff with an editorial-friendly codec or individual frames for compositing. Runway explicitly documents ProRes and PNG sequence options for Gen-4.5 in Tool Mode and Aleph 2.0 in Edit Studio, but these are plan- and workflow-specific choices rather than generic downloads.

The supported formats

Runway describes three outputs: MP4 as the normal viewing file; Apple ProRes inside MOV for editorial use; and a ZIP of PNG frames for VFX and compositing. The ProRes profiles listed include 422 Proxy, LT, 422, HQ, 4444 and 4444 XQ. The help page says ProRes MOV exports include uncompressed PCM audio. A frame sequence, by contrast, requires a conform process in an editor and is not automatically a ready-to-play video.

The format choice is available on Max, Unlimited (Legacy) and Enterprise plans as documented. Runway’s Gen-4.5 documentation also states a surcharge of five Runway credits per second for ProRes or PNG sequence beyond base generation cost. A ten-second Gen-4.5 shot therefore has a documented twelve-credit-per-second base and a five-credit-per-second output-format add-on, for 170 Runway credits in that mode. Verify the invoice and the selected format before generation.

Decide before pressing Generate

Runway’s help documentation warns that format selection occurs at generation time. Existing MP4 assets cannot simply be converted to a true original-generation ProRes or PNG sequence inside the platform; a different export request requires running generation again. This distinction is more than a file extension. Transcoding a compressed MP4 to ProRes cannot restore information already discarded by the original encoder.

For an ad that needs color grading and effects, select the profile supported by the editor and storage budget, then check the audio sample rate, sequence FPS, color assumptions and filename order. A PNG sequence is useful when artists must paint or key individual frames; it is expensive in disk space and needs a reliable frame-numbering strategy. For a social-media quick turn, MP4 may be the more efficient option.

Workflow pitfalls

The provider distinguishes Edit Studio edits applied to an entire clip from edits on a limited timeline range: range-only Aleph edits return MP4 even when high-end outputs are otherwise available. It also says Workflows and Agent generations deliver MP4 rather than offering the same manual format selector. Avoid telling automation engineers that a feature visible in Tool Mode is a universal API option.

Rights do not change merely because the container changed. Keep approved source frames and likeness permissions with the exported files. Record each generation’s model, account tier, output codec, credits, FPS and content hash so a finishing artist can trace exactly which asset was graded.

Worked production example

A finishing house needs a ten-second hero shot as ProRes 4444, but the creative team only generated a compressed MP4. Converting that MP4 after the fact cannot recreate a native ProRes generation. Before spending again, confirm whether the extra quality matters to its effects workflow, whether the account tier can select the output and whether the editing range permits it. Test one full-length export, verify frame count and audio in the target editor and record the surcharge. Do not order PNG frames for a fast social cut that will never enter a VFX pipeline.

Relevant alternatives and trade-offs

For native-audio generation assess Gemini Omni Flash; for sophisticated HDR/VFX handoff inspect Ray3.2; for exact on-screen graphics use a conventional compositor.

Sources & Further Reading

CONTINUE EXPLORINGExplore related files ↗