GLOSSARY
Codec
A codec (compressor-decompressor) determines how your image data is encoded for storage and decoded for playback. The wrong codec choice at acquisition can permanently limit what you can recover in post.
What a codec actually does
A codec is not a container format — that's a common confusion. MP4 and MOV are containers; H.264 and ProRes are codecs that live inside them. Codecs split into two fundamental architectures: intra-frame and inter-frame. Intra-frame codecs (ProRes 422, ProRes 4444, DNxHR HQX, Apple ProRes RAW) compress each frame independently. Every frame is a self-contained I-frame. This means the decoder can jump to any frame instantly — critical for editing, where the NLE scrubs through footage randomly. ProRes 422 at 4K runs roughly 500–750 Mbps depending on content complexity; ProRes 4444 XQ can hit 1500 Mbps. These bitrates are massive but necessary for preserving chroma detail and latitude. Inter-frame codecs (H.264, H.265/HEVC, VP9, AV1) compress groups of pictures (GOPs). An I-frame is stored fully, then subsequent P-frames and B-frames store only the difference from reference frames. A Long-GOP structure might have an I-frame every 15–30 frames. This is incredibly efficient — H.265 can deliver visually similar quality at roughly 50% the bitrate of H.264 — but it's computationally expensive to decode for random access. Editing H.265 natively in Premiere Pro or Resolve will tax your CPU heavily, dropping playback frames on all but the most powerful machines. Then there's chroma subsampling. 4:4:4 preserves full color resolution — every pixel has its own unique chroma value. 4:2:2 halves horizontal chroma resolution. 4:2:0 quarters both horizontal and vertical chroma resolution. On a 3840x2160 frame, 4:2:0 means your color information is only 960x1080 — that's why green screen keys on 4:2:0 H.264 footage produce blocky, jagged edges around hair.
When codec choice actually matters
The acquisition codec vs delivery codec distinction is non-negotiable. Shoot on the highest-quality codec your camera and media support. On an ARRI Alexa, that's ARRIRAW at ~3.2 Gbps. On a Sony FX6, that's XAVC S-I (All-I, 4:2:2 10-bit at 600 Mbps) or RAW via Atomos. On a Canon R5, it's Canon RAW Light at ~1.5 Gbps. The 100 Mbps 4:2:0 8-bit H.264 that most mirrorless cameras default to is adequate for YouTube delivery but devastating for color grading — push the shadows more than a stop and you'll see banding, macroblocking, and color breaks that no amount of NR or secondary correction can fix. For delivery, H.265 at 15–30 Mbps is the sweet spot for streaming. Netflix mandates a minimum average bitrate of ~15 Mbps for 4K SDR content; Apple TV+ targets higher. But the encoding pass for delivery is a separate, final step — it should never be confused with the codec you edit and grade on. The professional pipeline is: shoot high-bitrate intra-frame or RAW, edit and grade on that (or optimized ProRes proxies), then encode to H.265/AV1 for distribution.
Codec FAQ
Is ProRes always better than H.264?
For editing and grading, unequivocally yes. ProRes is All-I, visually lossless, and decodes with minimal CPU overhead. H.264 is Long-GOP, lossy, and requires heavy computation to scrub. But for final delivery, H.265 at appropriate bitrates is more efficient than ProRes — a 50 Mbps H.265 stream looks excellent on consumer displays.
Does 10-bit vs 8-bit actually matter?
Massively. 8-bit gives you 256 levels per channel; 10-bit gives you 1,024. When you grade 8-bit footage and push a curve, the gaps between levels become visible banding, especially in skies and gradients. 10-bit provides 4x the precision, which is why broadcast standards mandate 10-bit minimum.
Should I transcode H.264 to ProRes before editing?
In Resolve, the optimized media workflow handles this — generate ProRes or DNxHR proxies, edit, then relink to originals for final render. In Premiere, use Proxies. Don't just transcode manually and import — you'll double your storage for no added quality benefit. The transcoding doesn't recover information the H.264 already threw away.
Need Professional Help With This?
Wrong codec at acquisition can't be fixed in post — but the right post pipeline can maximize whatever you captured. We optimize every step from ingest to delivery.
Get a Free Consultation