Why it matters

Wrong protocol choice hurts UX or budget. Understanding options guides decisions.

Advertisement

The architecture

HLS: HTTP-delivered chunks + playlist manifest. Widely supported.

DASH: similar HTTP chunk-based approach. Open standard.

WebRTC: sub-second latency; peer or SFU.

Streaming protocolsHLSchunks + m3u8DASHchunks + MPDWebRTCsub-second real-timeLatency: HLS/DASH multi-second, LL-HLS/LL-DASH sub-second, WebRTC hundreds of ms
Protocol trade-offs.
Advertisement

How it works end to end

HLS latency: standard 6-30 seconds. Low-Latency HLS (LL-HLS) 1-3 seconds.

DASH: similar. LL-DASH exists.

WebRTC: hundreds of ms. Complexity higher.

Choice: HLS/DASH for large-audience VOD/live. WebRTC for interactive (video calls, live auctions).