HLS vs DASH: Which Streaming Protocol Should You Use?
HLS vs DASH: both stream video in small chunks over HTTP. Compare device support, latency, and DRM, and see why FAST platforms ship HLS first in practice.
HLS and DASH are the two dominant protocols for streaming video over the internet. Both work the same way: video is split into small segments, listed in a manifest file, and fetched over plain HTTP, with the player switching quality levels as bandwidth changes. HLS (HTTP Live Streaming) was created by Apple in 2009 and uses .m3u8 text manifests. DASH (Dynamic Adaptive Streaming over HTTP, often MPEG-DASH) is the ISO open standard from 2012 and uses .mpd XML manifests. The practical difference is device support: Apple devices require HLS, which is why most FAST and CTV services ship HLS first.
The choice matters less than it used to, because the CMAF format lets both protocols share the same video segments. This guide compares them fairly, explains the device reality, and shows where the industry landed.
How are HLS and DASH the same?
Start with the overlap, because it is most of the picture. Both protocols are adaptive bitrate streaming over HTTP:
- The encoder produces a ladder of renditions, from low to high quality.
- Each rendition is chopped into segments of a few seconds.
- A manifest lists the renditions and segments; the player reads it, picks a rendition, and fetches segments in order.
- When bandwidth drops, the player steps down the ladder without stopping playback.
Because everything is standard HTTP, both protocols ride ordinary CDNs and web servers. No special streaming servers, no persistent connections. Either protocol can carry a live 24/7 channel or on-demand titles, and both support ad insertion via SSAI and break signaling via SCTE-35.
HLS vs DASH: the differences that matter
| HLS | DASH | |
|---|---|---|
| Origin | Apple, 2009 | MPEG/ISO open standard, 2012 |
| Manifest | .m3u8, plain text playlist | .mpd, XML |
| Segment formats | MPEG-TS or fMP4 (CMAF) | fMP4 (CMAF) |
| Apple device support | Native and required | Not supported in Safari or Apple TV natively |
| Other device support | Universal via native players or hls.js | Broad on Android, smart TVs, and browsers via MSE |
| Codec flexibility | Historically constrained by Apple's spec | Codec-agnostic by design |
| DRM | FairPlay (plus others via CMAF) | Widevine and PlayReady |
| Low latency | LL-HLS extension | LL-DASH / CMAF chunked transfer |
DASH is the more flexible spec on paper: codec-agnostic, fully standardized, and expressive XML. HLS wins on deployment reality: it is the only protocol Apple devices accept, and every other device class plays it too. In browsers, Safari plays HLS natively while Chrome and Firefox play it through the hls.js library, which is how Vidiyo channels play in a web browser with no app install.
Why do FAST platforms ship HLS?
Because a FAST channel lives or dies on device reach, and one protocol covers everything. A channel must play on Roku, Fire TV, Apple TV, iOS, Android, smart TVs, and the web. HLS plays on all of them. DASH plays on most, but not on Apple's platforms, so a DASH-only service abandons iPhone, iPad, Apple TV, and Safari viewers.
Running both protocols is possible and common at large scale, but it doubles packaging paths, manifest logic, and testing surface. For an independent operator, single-protocol HLS is the pragmatic choice, and it is what Vidiyo streams end to end: channels play in the browser and in apps on Roku, Fire TV, Apple TV, iOS, and Android from one HLS pipeline. If you want to see what the playlists actually look like, read HLS manifests explained, and run any live playlist through the free HLS manifest validator.
DASH earns its keep in specific situations: Android-heavy audiences, DRM stacks built on Widevine and PlayReady, and broadcaster ecosystems in Europe where DASH is entrenched. Studio-grade DRM requirements are the most common reason a service runs DASH beside HLS.
What is CMAF, and does it end the debate?
CMAF (Common Media Application Format) is the convergence point. It standardizes the segment format, fragmented MP4, so one set of encoded segments can serve both protocols. The origin stores the video once; HLS and DASH become two thin manifest layers over identical files. That roughly halves storage and CDN cache footprint for dual-protocol services, and it carries a common encryption scheme so one segment set can serve multiple DRM systems.
CMAF did not merge the manifests, so HLS and DASH remain distinct protocols. But it turned "HLS vs DASH" from an infrastructure fork into a packaging detail, which is why the debate has cooled. New services mostly ship CMAF segments with HLS manifests first and add DASH when a device or DRM requirement forces it. Terms like CMAF, manifest, and rendition are all defined in the FAST TV glossary.
Quick answers
Is HLS better than DASH? Neither is better outright. DASH is the more flexible open standard; HLS has universal device support because Apple requires it. For maximum reach with one protocol, HLS wins.
Does DASH work on Apple devices? Not natively. Safari, iOS, and Apple TV require HLS, which is the single biggest reason services ship HLS first.
Can one video serve both HLS and DASH? Yes, with CMAF. Both protocols can reference the same fragmented MP4 segments, so you store the media once and generate two manifests.
Which protocol do FAST channels use? Overwhelmingly HLS, because it reaches every major device class from one pipeline. Large operators sometimes add DASH for Android-centric or DRM-heavy distribution.
What's next
Ready to launch your TV channel?
Vidiyo handles HLS playout, SSAI, EPG, and cross-platform distribution so you can focus on programming.