HLS and DASH Protocols
You'll learn how HLS and DASH use manifest files and segmented delivery to enable adaptive streaming across different devices and networks.
The Core Idea
Both HLS (HTTP Live Streaming) and DASH (Dynamic Adaptive Streaming over HTTP) break videos into small segments (typically 2-10 seconds each) and describe them in manifest files. Clients download the manifest, select appropriate quality segments based on bandwidth, and continuously fetch segments while adjusting quality in real-time.
How Manifest Files Work
The manifest is like a menu at a restaurant — it lists all available qualities (bitrates/resolutions) and tells the client where to find each video segment.
-
HLS uses
.m3u8playlists (text-based)- Master playlist → lists quality variants
- Media playlists → list segment URLs for each quality
-
DASH uses
.mpd(Media Presentation Description) in XML- Single manifest describing all representations
- More flexible codec and format support
Segment Delivery
Both protocols deliver segments over standard HTTP, enabling use of existing CDNs and web infrastructure. The client's player downloads segments sequentially, buffering ahead while monitoring network conditions to switch quality levels seamlessly.
Key Differences
| Feature | HLS | DASH |
|---|---|---|
| Format | Apple (widely supported) | Industry standard (ISO) |
| Manifest | .m3u8 plain text | .mpd XML |
| Codec flexibility | Limited | Highly flexible |
| Browser support | Native on iOS/Safari | Requires Media Source Extensions |
Key Takeaway: HLS and DASH enable adaptive streaming by splitting videos into segments described in manifest files, allowing clients to dynamically adjust quality based on bandwidth while delivering content over standard HTTP infrastructure.