Video Deliverable Formats: A Professional Workflow Guide
A professional deliverables pipeline runs in four stages: camera originals (RAW, BRAW, R3D, or native H.264/H.265) > low-res proxies (ProRes Proxy or H.264) > mezzanine edit masters (ProRes 422 HQ, DNxHR, or MXF) > compressed delivery masters (H.264/H.265 for web, IMF/MXF or ProRes for broadcast and major streamers). Getting that stack right from day one prevents platform rejections, speeds editorial throughput, and gives clients a clean, complete handoff.
Every professional job should produce at minimum:
- Camera originals backed up to at least two locations before any transcoding
- Proxy files for offline editing (H.264 MOV/MP4 or ProRes Proxy)
- Mezzanine/edit master for color, VFX, and archiving
- Compressed delivery master matched to the platform's ingest spec
- Audio stems (DX, MX, FX, M&E) at PCM 48kHz/24-bit
- Captions/subtitles as sidecar files or embedded per platform requirement
- QC report confirming loudness, frame rate, timecode, and spec compliance
Platform ingest docs from Netflix, Roku, and U.S. broadcasters can mandate IMF/MXF containers or specific ProRes profiles. Submitting the wrong format triggers outright rejection, not a correction request.
Key Takeaways
Choosing the right video deliverable formats at each stage, from camera originals through compressed delivery masters, is the single most effective way to prevent platform rejections and reduce post-production turnaround time.
| Point | Details |
|---|---|
| Four-stage format stack | Camera originals > proxies > mezzanine masters > delivery masters covers every professional workflow stage. |
| Intraframe for editing | ProRes 422 HQ and DNxHR provide frame-accurate scrubbing; never edit natively in H.264 on long-form projects. |
| Platform specs are mandatory | Netflix, Roku, and U.S. broadcasters require specific containers and codecs; noncompliance causes ingest rejection. |
| Loudness target for U.S. broadcast | ATSC A/85 sets -24 LKFS integrated loudness; confirm true peak does not exceed -2 dBTP before delivery. |
| Kinter for full-service delivery | Kinter Media manages the complete pipeline from on-set media management through IMF/MXF packaging and QC. |
Table of Contents
- What are the four role-based video deliverable format categories?
- Which codecs and containers should you use, and when?
- How should your workflow map formats from capture through archive?
- What do U.S. platform and broadcast delivery specs actually require?
- What are the right export settings for YouTube, social, and broadcast?
- How should you handle archival and handoff to prevent re-delivery?
- How do you fix the most common delivery and workflow problems?
- Why these recommendations: Kinter Media's post-production approach
- Kinter Media handles your full deliverables pipeline
- What the format decisions look like from inside a production
- Sources
What are the four role-based video deliverable format categories?
Video file types map to four workflow roles
, and studios routinely exchange multiple copies per asset during production. Understanding each role prevents the common mistake of treating every file as interchangeable.
Raw media is the camera's original output: sensor-native codecs like BRAW (Blackmagic RAW), R3D (RED Digital Cinema), ARRIRAW, or the H.264/H.265 files that consumer and mirrorless cameras record internally. These files carry maximum color headroom and dynamic range. Never re-encode originals before backing them up to at least two separate drives.
Proxy files exist for one reason: edit speed and file mobility. A ProRes Proxy or low-bitrate H.264 file is small enough to cut on a laptop, share over a network, or upload to a cloud review platform. Proxies are always relinked to the full-resolution masters before finishing.
Mezzanine files sit between the camera original and the final delivery. ProRes 422, ProRes 422 HQ, Avid DNxHR, and MXF mezzanine files offer edit-quality resolution with manageable file sizes. These are the formats your colorist and VFX team work from, and they become your archival master.
Delivery masters are the compressed, platform-optimized output: H.264 or H.265 for web and social, IMF or MXF for broadcast and major streaming ingest, and ProRes for high-end platform masters. Each destination may require a different variant.
Pro Tip: Create a textless master (no lower thirds, no titles) during the finishing session while the timeline is still open. Producing it later costs a full re-render and risks version mismatches.
Which codecs and containers should you use, and when?
. A practical workflow uses different codecs at different stages, not one codec throughout.
Intraframe vs. interframe is the core distinction. Intraframe codecs (ProRes, DNxHR) compress each frame independently, so the timeline can scrub to any frame instantly without decoding a GOP sequence. Interframe codecs (H.264, H.265) reference surrounding frames to reduce file size, which is ideal for delivery but creates CPU overhead during editing.
- H.264 (AVC): Universal delivery codec. Small files, broad playback support across every platform and device. Avoid editing natively in H.264 on long-form projects.
- H.265 (HEVC): Roughly half the file size of H.264 at comparable quality. Growing platform support, but heavier CPU decode. Useful for social delivery and client review links where bandwidth matters.
- Apple ProRes family: ProRes Proxy for offline editing; ProRes 422 and 422 HQ for editing and finishing; ProRes 4444 when you need an alpha channel for compositing. ProRes is intraframe and faster for editing; H.264 is interframe and better for compressed delivery, so many workflows transcode to ProRes for editing and export H.264 for distribution.
- Avid DNxHR / DNxHD: The cross-platform equivalent of ProRes. DNxHR is preferred for UHD projects; DNxHD covers HD. Both are intraframe and work natively in Avid Media Composer and DaVinci Resolve.
- RAW codecs (BRAW, R3D, ARRIRAW): Maximum latitude for color grading. Camera-specific and require the manufacturer's SDK or a compatible NLE. Archive originals; transcode to ProRes or DNxHR for the edit.
- MP4 container: Wraps H.264 or H.265 for web delivery. Broadly compatible, smaller overhead than MOV for streaming.
- MOV container: Apple's QuickTime wrapper. Preferred for ProRes masters and professional post workflows on macOS.
- MXF container: The broadcast and post-production standard. Required by many broadcasters and streaming platforms for ingest.
- IMF (Interoperable Master Format): The studio-grade package format used by Netflix and major distributors. Contains a composition playlist, timed text, audio tracks, and video essence in a single, versioned package.
| Role in Workflow | Codec/Container | Editing Performance | File Size | Platform Compatibility | Color Depth |
|---|---|---|---|---|---|
| Capture/Archive | RAW (BRAW, R3D) | Requires debayer | Very large | Camera-specific | bit raw |
| Proxy/Offline | ProRes Proxy, H.264 | Good (Proxy), limited (H.264) | Small | NLE, review tools | 10 bit |
| Edit/Mezzanine | ProRes 422 HQ, DNxHR | Excellent (intraframe) | Large | NLE, broadcast | 10 bit, 4:2:2 |
| Delivery/Web | H.264 (MP4/MOV) | Not for editing | Small–medium | Universal | 10 bit |
| Broadcast/Streaming | ProRes 4444, MXF, IMF | N/A (delivery) | Large | Platform-specific | 10 bit, 4:4:4 |
Pro Tip: Standardize on one editing codec across your team, ProRes 422 HQ on macOS or DNxHR on cross-platform Avid pipelines, rather than editing in whatever codec the camera recorded. Consistency cuts troubleshooting time significantly.
How should your workflow map formats from capture through archive?
Understanding the digital video workflow process helps you assign the right format to each stage before the shoot begins, not after problems surface in post.
- Capture: Record in the camera's best available codec (BRAW, R3D, ProRes RAW, or H.264/H.265 native). Back up to two drives on set via a DIT before any other step.
- Proxy generation: Transcode camera originals to ProRes Proxy or low-bitrate H.264 MOV/MP4 immediately after backup. Keep visible timecode burned into proxies for QC.
- Offline edit: Cut with proxies in Premiere Pro, Final Cut Pro, or Avid. Keep the project file linked to proxies throughout the assembly and rough cut stages.
- Relink to masters: Before color and finishing, relink the timeline to full-resolution camera originals or mezzanine transcodes. Confirm every clip relinks cleanly before the colorist begins.
- Grade and finish: Work in ProRes 422 HQ or DNxHR at 10-bit 4:2:2 minimum. Deliver a graded mezzanine master as the archival file.
- Deliver compressed masters: Export H.264 or H.265 for web, social, and client review. Export ProRes or IMF/MXF for broadcast and streaming platform ingest.
- Archive: Store camera originals, mezzanine masters, project files, and stems together. Run checksums (MD5 or SHA-256) on all archived files.
- Generate proxies on set or same day as the shoot.
- Confirm proxy-to-original timecode match before editorial begins.
- Lock picture before relinking to masters.
- Deliver graded mezzanine to colorist and VFX simultaneously.
- Run QC on the finished master before exporting delivery variants.
- Package stems, captions, and QC report with the master before handoff.
Pro Tip: For remote collaboration, upload H.264 proxies to a cloud review platform like Frame.io or Vimeo Review. Ship hard drives containing mezzanine masters only when the edit is locked and the client has approved the cut.
What do U.S. platform and broadcast delivery specs actually require?
High-end streaming platforms require IMF or MXF containers with strict metadata, stem, and loudness rules. Failing to meet those ingest specifications leads to outright rejection of the master, not a revision request.
specifies ProRes 4444XQ as the preferred master profile, with ProRes 422 HQ listed as acceptable. Audio must be PCM 48kHz/24-bit, and proxy deliverables require H.264 MOV or MP4 files with visible timecode burned in, following Roku's naming conventions precisely.
Professional HD deliverable specifications for North American broadcast include explicit codec, raster, chroma sampling, and data rate requirements. Audio for professional deliverables is typically PCM 48kHz/24-bit across broadcast and agency workflows.
Audio deliverables differ by destination: U.S. broadcast follows ATSC A/85 at -24 LKFS integrated loudness, while European platforms follow EBU R 128 at -23 LUFS. Streaming platforms each publish their own targets. True peak ceiling for broadcast is typically -2 dBTP. Stems must be labeled and delivered as discrete files: DX (dialogue), MX (music), FX (effects), and M&E (music and effects combined).
Minimum platform handoff checklist:
- Picture master (correct container, codec, bit depth, frame rate)
- Textless master
- Proxies with visible timecode
- Full stem set (DX, MX, FX, M&E) at PCM 48kHz/24-bit
- Closed caption sidecar file (.SRT or .TTML per platform)
- QC report with loudness measurements
- Delivery manifest listing every file and its checksum
What are the right export settings for YouTube, social, and broadcast?
Following platform-recommended export settings yields better final quality than delivering an oversized high-bitrate file the platform will heavily recompress.
- YouTube/Vimeo: H.264 or H.265, 1920x1080 or 3840x2160, Rec.709 or HDR10 color space, audio PCM or AAC 48kHz/24-bit. YouTube recommends a high-quality H.264 master for 4K so its encoder has clean source material.
- Social (Instagram, LinkedIn, TikTok): H.264 MP4, 1080x1080 (square) or 1080x1920 (vertical), maximum 3.5 Gbps for Instagram. Keep files under platform size limits.
- Client review proxies: H.264 MOV or MP4 at 5–10 Mbps with burned-in timecode and watermark. Keep these clearly labeled as "REVIEW ONLY."
- Broadcast/major streaming masters: ProRes 422 HQ or 4444 in MOV, or IMF/MXF package per platform spec.
Final QC numbered checklist before any export:
- Confirm frame-accurate in and out points with no black frames at head or tail.
- Verify slate information matches the delivery manifest.
- Check timecode continuity from start to finish.
- Confirm captions are frame-accurate and either embedded or packaged as a sidecar.
- Run a loudness measurement and confirm integrated LUFS and true peak values meet spec.
- Spot-check audio stems for phase and sync against the picture master.
How should you handle archival and handoff to prevent re-delivery?
Building the deliverables package during production rather than assembling it at the end reduces the risk of missing a single asset that triggers a rejection or re-delivery request.
Naming convention example (based on Roku and broadcast conventions):
- SHOWCODE_EP101_EN_MASTER_v01_20260115.mov
- SHOWCODE_EP101_EN_PROXY_TC_v01_20260115.mp4
- SHOWCODE_EP101_DX_STEM_v01_20260115.wav
Handoff asset checklist:
- Camera originals (labeled by card/drive and shoot date)
- Mezzanine masters (graded, with and without titles)
- Proxies (with visible timecode)
- Audio stems (DX, MX, FX, M&E)
- Captions/subtitles (sidecar .SRT, .TTML, or .VTT per platform)
- Graphics package (layered files and rendered versions)
- QC report
- Delivery manifest with file names, checksums, and version notes
Platforms including Netflix require sidecar caption files rather than embedded captions. Confirm the required format before delivery, as embedded captions in the video stream are often rejected.
Final handoff verification steps:
- Run MD5 or SHA-256 checksums on every file and log them in the manifest.
- Confirm file names match the delivery manifest exactly, including version and date suffixes.
- Play back the master on a calibrated monitor and verify audio sync on the first and last scenes.
- Store one archival copy offsite or in cold cloud storage (AWS Glacier or equivalent).
How do you fix the most common delivery and workflow problems?
- Timeline stutter during editing: Transcode camera originals to ProRes 422 or DNxHR, or generate proxies and link the NLE to them. Never edit natively in H.264 or H.265 on a long-form project.
- Upload failures or oversized files: Export a delivery proxy in H.264 or H.265 at the platform's recommended bitrate. Oversized masters trigger platform recompression that can reduce perceived quality.
- Loudness mismatch at delivery: Run an integrated LUFS measurement in your DAW or NLE before export. Adjust gain and confirm true peak does not exceed -2 dBTP for broadcast.
- Missing textless master: Create it during the finishing session before closing the timeline. Producing it after the fact requires a full re-render and risks version drift.
- Wrong container for platform ingest: Confirm whether the platform requires MOV, MP4, MXF, or an IMF package before starting the export. Container errors are among the most common ingest rejection causes.
Pro Tip: Before submitting to any platform, run a lightweight pre-QC pass: confirm the slate frame is present, timecode starts at 01:00:00:00 (or per spec), and a stereo mixdown plays back cleanly on consumer headphones. Catching these in five minutes prevents a multi-day rejection cycle.
Why these recommendations: Kinter Media's post-production approach
Kinter Media, led by director and cinematographer Alex Kinter, applies these conventions across commercial, corporate, and broadcast productions for clients including AT&T, Marriott, and the Dallas Cowboys. The rules here reflect what actually prevents rejections and speeds delivery, not theoretical best practices.
Following platform delivery docs has prevented ingest rejections on broadcast and streaming submissions. Proxy-first workflows, where editors cut offline and relink before color, consistently reduce finishing time on projects with large media volumes. When a client requests a format outside the standard stack, such as a specific MXF profile or a proprietary codec. Kinter builds that requirement into the production schedule rather than treating it as a post-delivery afterthought.
The DIT and media management services Kinter provides on set are where this pipeline begins: cards are offloaded, checksummed, and proxies are generated before the crew wraps for the day.
Kinter Media handles your full deliverables pipeline
Producing compliant post production deliverables across multiple platforms, from YouTube to broadcast MXF, requires a coordinated pipeline that most marketing teams and agencies do not have in-house. Kinter Media offers full-service video production and post-production from pre-production planning through final delivery, including:
- Proxy generation and media management on set
- Mezzanine master creation, color grading, and sound design
- IMF/MXF packaging and broadcast delivery
- Audio stem production and loudness compliance
- Caption and subtitle preparation
Kinter's post-production team handles QC, naming, and delivery manifest preparation so your team receives a complete, compliant package. View completed projects in the Kinter portfolio or reach out directly to discuss your next production's deliverable requirements.
What the format decisions look like from inside a production
Planning deliverables at Kinter starts during pre-production, when the delivery destination determines the camera codec, proxy resolution, and audio layout before a single frame is shot. On a typical corporate or commercial production, the DIT owns proxies and camera originals on set. The editor owns the offline cut. The colorist and sound designer receive the relinked mezzanine master. Kinter's post supervisor runs QC and assembles the final package.
The resource allocation lesson is straightforward: budget storage for ProRes 422 HQ mezzanine masters require significant storage at 1080p and time for a proper QC pass. Skipping either to save cost almost always costs more in re-delivery time than the savings were worth.
Sources
Always verify the current version of each platform's delivery spec before submitting, as values change without notice.
- From Raw Video to Proxy to Mezzanine to Final Delivery | Signiant
- Understanding Video Codecs: H.264, ProRes, and Beyond - GrabFootage Blog
- ProRes vs H.264: Differences and What Should You Use
- Developer