MoQ aims to bridge WebRTC latency and HLS scale
![MoQ aims to bridge WebRTC latency and HLS scale](["https://streaminglearningcenter.com/wp-content/uploads/2026/05/MOQ_1a.jpg","https://streaminglearningcenter.com/wp-content/uploads/2026/05/MOQ_1a.jpg","https://streaminglearningcenter.com/wp-content/uploads/2026/05/MOQ_1a-1024x619.jpg","https://streaminglearningcenter.com/wp-content/uploads/2026/05/MOQ_3a-710x1024.jpg","https://streaminglearningcenter.com/wp-content/uploads/2026/05/MOQ_2.jpg"])
This article introduces Media over QUIC (MoQ), a new QUIC-based protocol aiming to bridge the gap between WebRTC's real-time, low-latency interactivity and HLS/DASH's large-scale, CDN-friendly delivery. MoQ is described as delivering sub-second latency while maintaining CDN-scale capabilities, addressing a fundamental tension in live streaming protocols.
Key Takeaways
- MoQ is built on QUIC, the transport protocol behind the proposal.
- The protocol targets sub-second latency for live streams.
- MoQ is described as aiming for CDN-scale delivery, not just point-to-point interactivity.
- The article positions MoQ between WebRTC and HTTP-based HLS/DASH.
- WebRTC is cited as the low-latency option for video calls, conferences, and interactive live streams.
Why It Matters
MoQ matters because it directly addresses live streaming’s core tradeoff: WebRTC offers real-time interactivity, while HLS and DASH offer HTTP-based CDN delivery at scale. If MoQ can hold sub-second latency while preserving CDN compatibility, it narrows the gap between those two camps in the streaming stack. The strategic angle is that a QUIC-based approach could sit closer to existing internet transport patterns than WebRTC’s model. The key signal to watch next is whether MoQ progresses from this protocol concept into concrete deployment or implementation details.
Read full article at streaminglearningcenter.com