HLS and DASH converge around CMAF, but Apple still decides reach
This article discusses HLS and DASH, the two primary HTTP-based adaptive bitrate streaming protocols used for video delivery, detailing their similarities, differences, and practical applications by major platforms. It highlights the importance of CMAF for enabling unified delivery of both protocols from a single encoding pipeline. The article also provides a decision guide based on device compatibility, codec support, and latency goals.
Key Takeaways
- HLS is native on iOS, iPadOS, macOS Safari, and Apple TV, while DASH is not supported natively on Apple devices.
- DASH is codec agnostic and can carry VP9 and AV1, while HLS is limited to H.264 and H.265 in the article.
- Low-Latency HLS and Low-Latency DASH both target roughly 2-4 second latency, with LL-HLS described as sub-three seconds.
- CMAF lets operators package video once and generate both .m3u8 and .mpd manifests from the same fragmented MP4 segments.
- Netflix uses a proprietary DASH-based architecture, while Twitch uses HLS and built its own low-latency HLS variant before Apple’s official LL-HLS spec.
Why It Matters
For most streaming operators, the decision is no longer HLS versus DASH at the infrastructure layer. CMAF lets a single encode-and-package pipeline serve both protocols, while Apple device support still makes HLS non-negotiable for broad reach. That leaves codec strategy and latency goals as the main technical differentiators: DASH brings codec flexibility, and both protocols now have low-latency options. The practical question is whether a workflow needs Apple compatibility, non-Apple codec efficiency, or both. Watch for deployments that standardize on CMAF with dual HLS and DASH manifests, especially in OTT and live sports.
Read full article at wowza.com
Get this in your inbox → Subscribe
Enjoy our coverage?
Add StreamingMeme as a preferred source on Google to see more of our streaming news at the top of your Search results.
Add as preferred source