What is the Common Media Application Format (CMAF)?
Common Media Application Format (CMAF) defines interoperable fragmented MP4 structures and media profiles for adaptive streaming. Compatible delivery protocols can reuse the same encoded media objects.
How the Common Media Application Format (CMAF) works
CMAF standardizes media objects based on the ISO Base Media File Format so a common set of fragments can serve multiple adaptive-streaming presentations. Encoded tracks are organized into independently usable headers, segments, and chunks with timing and random-access constraints. HLS and DASH can reference those same objects through different manifest languages, reducing redundant storage and cache fragmentation. CMAF occupies the packaging layer; it does not replace codecs, manifests, players, or content protection systems.
Key facts
- 1A CMAF header carries track configuration, while following fragments carry timed samples; clients need the matching header before they can correctly decode a track.
- 2A CMAF segment contains one or more complete fragments, and each fragment contains one or more chunks. Chunks let a client fetch and decode part of a fragment before the complete fragment or segment exists. Low-latency delivery requires compatible behavior across the encoder, origin, CDN, manifest, and player.
- 3Common media objects do not guarantee one universal presentation: codec profiles, switching constraints, encryption schemes, and client capabilities still have to intersect.
When the Common Media Application Format (CMAF) matters
Use CMAF to reduce duplicate packaging when DASH and HLS delivery requirements overlap. Codec, encryption, player, and profile support must align because CMAF alone does not make every stream universally playable.
Common use cases for file formats & compression
These examples cover file formats & compression broadly, not specifically the Common Media Application Format (CMAF).
- Accepting heterogeneous uploads while producing a controlled set of delivery formats.
- Moving assets between cameras, editors, browsers, archives, and downstream APIs.
- Separating long-lived source files from compact derivatives optimized for a particular channel.
Working with file formats & compression
This guidance covers file formats & compression broadly, not just the Common Media Application Format (CMAF).
A parser reads the file structure, identifies contained streams and metadata, and exposes them to a decoder or application. Conversion usually decodes the source representation and writes compatible information into a different structure or encoding.
This category covers file and bitstream formats, their structures, and the compression methods they use. A filename extension can be misleading, so evaluate the detected format, decoding support, metadata, transparency, color, timing, patents, and archival needs before choosing an output.
What you gain
- A suitable format preserves the properties a workflow actually needs.
- Standardized structures allow files to move between compatible tools and systems.
- Format conversion can improve delivery size, editability, or long-term accessibility.
What it costs
- Modern formats can save bandwidth but may need fallbacks for older clients and production tools.
- Converting to a simpler format can discard transparency, animation, metadata, color precision, or editability.
- Archival suitability, browser support, and editing support often favor different choices.
Before production
- 1Inspect the detected container, codec, MIME type, and magic bytes instead of trusting a suffix.
- 2Verify decoder support and preserve metadata, color, transparency, or timing when required.
- 3Retain the source when the chosen delivery format is lossy or tied to current software.