Skip to content
Kling 4.0 is on Runway Dev 20% off Through November 30 Get started

Professional film and video work typically specifies a resolution, frame rate, and/or color grade beyond what a generated clip already has. The pipeline often also needs a container it can open directly, such as ProRes or a PNG sequence.

Runway Dev covers both: Gen-4.5 and Aleph 2.0 generate these formats natively. Additionally, we have post-production models that can upscale, change the frame rate, or convert SDR to HDR on a video you already have.

Gen-4.5 and Aleph 2.0 can deliver ProRes, a PNG sequence, or the default H.264 .mp4 on the generation request. These files stay in standard dynamic range. HDR is a separate delivery.

To generate outputs in these formats, simply specify an outputFormat in your request:

outputFormatDelivery
mp4 (default)H.264 .mp4
proresProRes .mov
png_sequence.zip of PNG frames (plus a separate .wav when the output has audio)

For prores, optionally set proresProfile (422 Proxy, 422 LT, 422, 422 HQ, 4444, or 4444 XQ; default 4444).

The same two models can also deliver 10-bit Rec.709 SDR when a grade needs more precision than 8-bit H.264. That file is still SDR.

outputFormatDeliveryModels
sdr_rec709_10bitHEVC Main 10, Rec.709 .mp4Gen-4.5, Aleph 2.0

prores and png_sequence add 5 credits per second. 10-bit SDR uses the higher per-second surcharge. See pricing.

Seedance 2.5 can deliver a .mov instead of the default .mp4: set outputFormat: "mov" on text to video, image to video, or video to video. It keeps higher color precision for grading and compositing, and costs the same as mp4. Draft previews are .mp4 only.

Seedance 2.0, Seedance 2.0 Fast, and Seedance 2.0 Mini render at standard bitrate by default. Set bitrate: "high" to keep more detail with fewer compression artifacts, at a larger file size. Both settings cost the same.

HDR (high dynamic range) stores a wider span of brightness than standard dynamic range (SDR). Highlights keep detail that an SDR file would clip, which is what HDR playback, broadcast, and theatrical specs ask for. A default H.264 .mp4 is SDR and cannot carry that range.

Gen-4.5 can generate HDR natively. Set outputFormat to one of the HDR values below.

Ruby converts any SDR video, including an Aleph edit, to HDR on POST /v1/video_to_hdr. Inputs must be SDR, at most 30 seconds, and up to 4K.

Gen-4.5 HDR outputs are true HDR renders, graded into BT.2020 with measured HDR10 metadata.

outputFormatDelivery
hdr10HEVC Main 10, BT.2020 + PQ .mp4
hlgHEVC Main 10, BT.2020 + HLG .mp4
hdr_pq_12bit_master12-bit 4:4:4 BT.2020 + PQ .mov (lossless)
hdr_proresBT.2020 + PQ ProRes .mov
hdr_png_sequence.zip of 16-bit PNG frames + colorimetry sidecar (plus a separate .wav when the output has audio)
hdr_exr_sequence.zip of half-float OpenEXR frames as linear BT.2020 light (1.0 = 100 nits) + colorimetry sidecar (plus a separate .wav when the output has audio)
hdr_exr_acescg_sequence_1_3The EXR delivery as scene-referred ACEScg for ACES 1.3 pipelines — reads with the stock ACES - ACEScg input transform
hdr_exr_acescg_sequence_2_0The same scene-referred ACEScg delivery for ACES 2.0 pipelines (inverted through the ACES 2.0 Output Transform)

For hdr_prores, proresProfile accepts 422, 422 HQ, or 4444 (default 422 HQ). On /v1/video_to_hdr, sources with an alpha channel are delivered as 4444 regardless of proresProfile.

The ACEScg EXRs are scene-referred: the delivered picture is inverted through the ACES 1.3 Output Transform (Rec.2100 PQ, 1000-nit), so reading the frames with the stock ACES - ACEScg input transform and viewing through your ACES pipeline reproduces the delivered picture — no Read-node changes needed. The colorimetry.json sidecar names the ACES version and the inverted transform.

These formats use the higher per-second surcharge — see pricing.

A clip you already have can still fall short of the resolution or frame rate a timeline, broadcast spec, or playback target asks for.