Color, Frame Rate & Technical Specs
Codec and container are only half a spec. The other half — resolution, frame rate, aspect ratio, color space, and audio loudness — gets checked just as strictly, and a mismatch on any of them bounces your file. Here's what each one means and why it matters.
A delivery spec is a list of parameters, and codec and container are only two of them. The rest describe the actual shape and character of your picture and sound, and each one is checked — often automatically — when you deliver. The reason these matter so much is that a playback system or pipeline is built for a specific set of these values, and a mismatch doesn't just look slightly off; it can make the file unplayable, out of sync, wrong-colored, or too loud/quiet for their standard, any of which is a rejection. The good news is that most of these you set correctly once, early in the project, and then they take care of themselves — which is exactly why this chapter belongs in Foundations. Decide your resolution, frame rate, and aspect ratio at the start and build the whole film to them, and delivery becomes far simpler. Let me walk through the parameters you'll see on every spec sheet.
The specs that get checked
Know each of these and what it controls:
- Resolution. The pixel dimensions — 1920×1080 (HD/2K-ish), 3840×2160 (UHD/4K), and cinema's 2K (2048×1080) or 4K (4096×2160). Deliver the resolution asked for; don't upscale a lower-res film to fake a higher one.
- Frame rate. Frames per second — 23.976/24, 25, 29.97, 30, etc. This is the one to lock at the very start, because it's baked into your entire project. Delivering the wrong frame rate causes judder or sync problems and is a common rejection.
- Aspect ratio. The shape of the frame — 1.85:1, 2.39:1 (scope), 16:9. Cinema specs care about this precisely; delivering the wrong aspect can mean black bars in the wrong places or a stretched image.
- Color space & bit depth. The color standard — Rec.709 (HD/streaming), DCI-P3 (cinema/DCP), Rec.2020/HDR for high-end. Deliver in the color space the spec asks for, or your carefully graded film will look wrong on their system.
- Audio configuration. Channel layout — stereo (2.0), 5.1 surround, and whether tracks are split (discrete stems) or mixed. Specs are precise about which channel is which; a wrong config means missing or misrouted sound.
- Loudness. The measured audio level, in LUFS/LKFS, to a target standard (broadcast and streaming enforce this strictly — e.g. -23 or -24 LUFS). Too loud or too quiet gets flagged; you often need to run a loudness-normalization pass.
Lock it early, verify it late
Two principles turn this list from intimidating into manageable. First, lock the fundamentals at the start of the project. Frame rate, resolution, and aspect ratio should be decided before you shoot or at least before you edit, and your whole project built to them, because they're extremely painful to change late — converting frame rates introduces artifacts, changing aspect ratio re-frames every shot, and upscaling resolution never truly adds detail. If you know you're aiming for cinema, that informs choices from the camera onward. The filmmakers who deliver painlessly are the ones who worked to a target spec the whole way through, so their finished film already is the shape their deliverables need. Second, verify against the spec before you send. When a deliverable is exported, check every one of these parameters against the destination's requirements — resolution, frame rate, aspect, color space, audio config, loudness — the same way you checked codec and container last chapter. Loudness especially trips people up because it's invisible: your mix might sound great but measure at the wrong LUFS for a broadcaster, so you run a loudness meter (many are free, and NLEs increasingly have loudness normalization built in) and correct it to their target. A useful reality check: color space and loudness are the two "silent killers" here, because a file can play perfectly on your setup and still be in the wrong color standard or at the wrong loudness for the destination's calibrated system — problems you only catch by measuring, not by eyeballing. So build a habit of treating every delivery spec as a checklist and ticking off each parameter with a tool, not a guess. Master this and codecs together, and you can read any spec sheet in the world and produce a file that passes. That completes your foundations — you now understand what delivery is, the master hierarchy, codecs and containers, and the technical parameters. Module 2 gets hands-on with the format that intimidates indies most and needn't: the DCP, starting with what it actually is.
Two delivery disasters taught me these lessons. The first: I edited a film at 30fps without thinking, then a festival required 24 — converting it introduced ugly judder I could never fully fix. The second: a broadcaster rejected a delivery that sounded perfect to me, because my mix measured at the wrong loudness; I'd never even heard of LUFS. Now I lock frame rate and aspect on day one, and I run a loudness meter and a color-space check on every deliverable before it leaves. The specs that get you are the invisible ones — frame rate, color space, loudness — so I measure them instead of trusting my eyes and ears.
Run your finished film through Distribution Readiness — check your masters, deliverables, and specs against what festivals and platforms require, so you catch problems before a rejection letter does.