Reference Glossary
Codec
The algorithm — such as H.264, H.265, or ProRes — that compresses video or audio data for storage and decompresses it for playback, distinct from the container file that holds it.
Why it matters in a DAM
A DAM's transcoding pipeline lives or dies on codec choice: H.264 gives broad playback compatibility and small files suited to web preview, while ProRes preserves near-original quality for editorial handoff at a much larger file size. Generating the wrong codec for a use case — an editorial-grade codec pushed to a website, or a web-compression codec handed to an editor — either breaks browser playback, bloats bandwidth costs, or hands editors a proxy too degraded to work with.
A worked example
Common mistake
Generating one 'universal' preview codec for every downstream use, so editorial teams get a low-bitrate proxy that's unusable for grading while web teams get an oversized editing-grade file that neither loads quickly nor was needed at that quality.
The codec is the compression algorithm doing the actual work inside a video or audio file — deciding what data to keep, what to approximate, and how to reconstruct a playable stream from it. It’s a different layer from the container: the same H.264 stream can be wrapped in an MP4 or a MOV file with no difference in visual quality, because the container just organizes tracks, while the codec determines fidelity and file size.
Codec choice is where a DAM’s transcoding rules translate directly into cost and usability. H.265 (HEVC) can deliver comparable quality to H.264 at roughly half the file size, which matters for storage and delivery bandwidth at scale, but it demands more processing power to encode and decode and isn’t supported as universally, so libraries serving broad audiences often default to H.264 for compatibility despite the larger files. Editorial codecs like ProRes sit at the opposite end — minimal compression loss, large files — and are reserved for masters and post-production handoff rather than general delivery.
Frequently asked
What is a codec?
The compression algorithm, such as H.264, H.265, or ProRes, that compresses video or audio data for storage and decompresses it for playback, distinct from the container file that holds it.
How does codec choice affect a DAM's transcoding pipeline?
H.264 gives broad playback compatibility and small files suited to web preview, while ProRes preserves near-original quality for editorial handoff at a much larger file size.
How much smaller is H.265 compared to H.264?
Roughly 40-50% smaller at comparable visual quality, though it demands more processing power to encode and decode and isn't supported as universally.
Why do libraries serving broad audiences often default to H.264 despite larger files?
Because H.265's smaller files come at the cost of less universal decoder support, so compatibility often wins over storage savings for general delivery.
What's the mistake of generating one "universal" preview codec for every use?
Editorial teams end up with a low-bitrate proxy that's unusable for grading, while web teams get an oversized editing-grade file that neither loads quickly nor was needed at that quality.
Does the container a codec is wrapped in affect visual quality?
No. The same H.264 stream can be wrapped in an MP4 or a MOV file with no difference in visual quality, since the container just organizes tracks while the codec determines fidelity and file size.
Sources
- H.265 (HEVC) can deliver comparable visual quality to H.264 at roughly 40-50% smaller file size, though it requires more processing power to encode and decode. checked 2026-08-07 — getstream.io