CMAF Adoption Guide

The Two-Protocol Problem

For years, the streaming industry was split. Apple devices demanded HLS (using TS, Transport Stream containers), while the rest of the world moved to DASH (using fMP4 containers). This meant every streaming platform had to encode, store, and cache two entirely separate copies of the same video.

Storage costs doubled. CDN caching efficiency plummeted because Edge servers had to store both the TS version and the fMP4 version of a 1080p rendition, fracturing the cache hits.

The Solution: CMAF

The Common Media Application Format (CMAF) was developed by Apple and Microsoft to end this madness. CMAF standardizes the media container as fMP4 (specifically, ISO Base Media File Format). Now, you generate a single set of CMAF media chunks.

You then generate two lightweight text files: an HLS `.m3u8` manifest and a DASH `.mpd` manifest. Both manifests point to the exact same fMP4 files.

Architecture	Storage Multiplier	CDN Cache Efficiency	Complexity
Legacy (HLS TS + DASH fMP4)	2.0x	Poor (Fractured)	High
Modern (CMAF)	1.0x	Excellent (Unified)	Low

Common Mistakes

• Forgetting legacy Apple devices: CMAF requires iOS 10+ and macOS Sierra. Older devices cannot parse fMP4 in HLS. However, given current OS adoption rates, this is a negligible edge case for most consumer applications.
• Improper byte-range addressing: CMAF can be delivered as discrete files per chunk, or as one large file using HTTP byte-range requests. Misconfiguring byte-range requests on your CDN can lead to catastrophic caching failures.

FAQ