Media over QUIC (MoQ)
Media over QUIC (MoQ) is an emerging IETF protocol for live and on-demand video that runs on QUIC, the fast transport behind HTTP/3. MoQ aims to combine the delay of under a second of WebRTC with the large-scale delivery of HLS and DASH. Media flows through relays that can fan out a stream to many viewers, much like a CDN, while letting late or less important data be dropped.
Why it matters
Today, a business picks between the low delay of WebRTC and the cheap, large-scale delivery of HLS. MoQ aims to remove that choice, which could let live sports, betting and game streams reach huge audiences in near real time without separate systems for interactive and passive viewers.
How it works
- A publisher sends media as tracks of small objects over QUIC connections.
- Relays, similar to CDN servers, receive the tracks and fan them out to subscribers.
- Viewers subscribe to the tracks they want, such as a specific quality level.
- When the network is congested, relays can drop late or less important objects so live playback continues.
Is Media over QUIC ready for production?
Not fully. MoQ is still being standardized by an IETF working group, and specifications are changing. Some CDN providers run early relay networks and teams are testing it, but players, encoders and tooling are less mature than for HLS or WebRTC. Most businesses should watch MoQ and run trials rather than move core workloads yet.
MoQ vs WebRTC: what is the difference?
Both aim for very low delay, but MoQ is designed for large-scale distribution through relays, while WebRTC was built for calls between a few participants. WebRTC is mature and widely supported. MoQ is newer and aims to fan out live streams to many viewers more like a CDN, with control over which data can be dropped.
Where it's used
Major CDN providers have launched early MoQ relay networks, and live and game streaming platforms are testing them to bring near real-time delay to very large live audiences.
