CMAF — Common Media Application Format — is the MPEG standard that lets the same media segments serve both HLS and DASH. Before CMAF, broadcasters supporting both protocols had to encode and store two complete copies of every video: one in HLS's traditional MPEG-TS container, one in DASH's fragmented MP4. CMAF unifies them into a single fragmented MP4 format that both protocols can use, cutting storage by 50 % and simplifying the entire delivery pipeline.
The mechanics: CMAF defines a strict, interoperable flavour of fragmented MP4 (fMP4) with consistent rules for segments, encryption (cenc), captions and metadata. The packager produces CMAF segments, and the same files get advertised via an HLS playlist for Apple devices and a DASH manifest for everything else. Viewer-side, an iPhone fetches the HLS playlist and downloads CMAF segments; a Chrome browser on Android fetches the DASH manifest and downloads the same CMAF segments from the same CDN locations. Caching becomes far more efficient because the same content lives at the same URLs for both audiences.
For a product team in 2026, CMAF is the universal target for new streaming infrastructure. Apple Low-Latency HLS (LL-HLS) is CMAF-based; DASH-IF's recommended profiles are CMAF-based; every modern packager (Shaka Packager, AWS MediaPackage, Bitmovin) outputs CMAF by default. The migration from "separate HLS and DASH pipelines" to "one CMAF pipeline serving both" is essentially complete at major streaming services. If you're building a streaming product today, ship CMAF. The Wowza state-of-2026 report calls CMAF "best-in-class implementation logic" with feature parity now the default across HLS and DASH.
