Live streaming has long presented a structural tradeoff: protocols optimized for low latency, such as WebRTC, do not scale efficiently to large audiences, while protocols built for CDN-scale reach, such as HLS and DASH, impose a latency floor that makes them unsuitable for time-sensitive use cases. Media over QUIC (MoQ) is a fruitful effort to address both constraints within a single protocol — and in 2026, it is moving from standardization work to commercial deployment.
The QUIC emergence of MoQ
The live streaming industry has been working around the same fundamental limitation for over a decade. HTTP-based protocols — HLS, DASH, and their low-latency variants — have proven extraordinarily scalable and operationally mature. They power the vast majority of streaming traffic on the internet today – they work reliably at any scale, integrate naturally with CDN infrastructure, and benefit from decades of tooling and operational experience. Their segment-based model does impose a latency floor that LL-HLS and LL-DASH have progressively reduced, typically reaching the 2–6 second range in real-world deployments. For the growing class of use cases where sub-second latency matters — live sports, interactive events, live betting — that gap remains a genuine constraint.
WebRTC solved the latency problem but created a different one. Every viewer requires a dedicated session on a Selective Forwarding Unit (SFU). When reaching thousands of concurrent viewers, that architecture becomes expensive and complex to operate. WebRTC was designed for video calls, not for streaming at scale.
Media over QUIC takes entirely a different approach. Instead of segments, MoQ treats media as a continuous stream of individually addressable objects — one per video frame, one per audio chunk. Instead of pull-based HTTP requests, it uses a publish/subscribe model where intermediate relays subscribe to content once and push the stream to millions of subscribers. This is structurally different from WebRTC, where every viewer requires a dedicated session, and from HLS/DASH, where every segment request travels independently up the CDN chain. The result is an architecture that can deliver sub-second glass-to-glass latency at CDN scale.
The protocol runs on QUIC — the same transport that powers HTTP/3 — which gives it native browser support via WebTransport[1], stream multiplexing without head-of-line blocking, and intelligent handling of packet loss without the blunt instrument of TCP retransmission.
From IETF draft to industry standard
MoQ is being developed at the IETF by the Media over QUIC working group. The core specification for Media over QUIC Transport(MOQT), `draft-ietf-moq-transport`, has reached revision 18 as of May 2026, and the working group is targeting a Working Group Last Call in the coming months — the last formal gate before RFC publication.
The protocol is now widely stabilized. The data model (tracks, groups, objects), the pub/sub control messages (SUBSCRIBE, PUBLISH, FETCH), and the QUIC and WebTransport bindings are converged. What remains in active development are advanced features — mechanisms for dynamic track switching, filter-based content selection, and fill-fetch for catch-up playback — which are being refined through a rigorous program of interoperability testing.
Alongside the transport with MOQT the working group has adopted several companion specifications:
- the MOQT Streaming Format (MSF), which defines how video and audio are packaged as MoQ objects using the Low Overhead Container (LOC) for efficient frame encapsulation. MSF also describes how media and event tracks are signaled in a JSON “catalog,” serving a role similar to a DASH manifest or HLS playlist.
- its CMAF-compatible variant (CMSF) for operators already running CMAF workflows.
For operators running CMAF-based workflows today, the CMSF format provides a defined migration path: the same fMP4 chunks can be packaged as MoQ objects, reusing existing encoder infrastructure while gaining the benefits of MoQ delivery, as demonstrated by Ateme at NAB 2026.
An ecosystem that moved faster than the RFC
The industry did not wait for the RFC. At Mile High Video 2026 in Denver, MoQ dominated the technical program. Topics ranged from ABR adaptation strategies for MoQ to live sports watch parties, VOD synchronized playback, and AI-generated event timelines. The volume of MoQ research presentations in a single conference edition is itself a signal: MoQ is where the industry’s engineering attention has moved to.
At NAB Show 2026 in Las Vegas, demonstrations from over a dozen vendors made MoQ tangible and cross-vendor for the first time. Ateme demonstrated DRM-protected low-latency live MoQ streaming in partnership with EZDRM and also demonstrated sub-second latency delivery while maintaining high video quality — a combination that has historically forced a tradeoff. Ateme engineers have also contributed directly to the open-source ecosystem, providing key contributions for MoQ support to Shaka Player -the reference open-source javascript player – which was tested against the live Ateme TITAN encoder output through both Cloudflare and self-hosted MoQ relays.
Subsecond latency demonstration by Ateme at NAB 2026
There were already some hints towards commercial deployments:
Cloudflare deployed MoQ relay infrastructure across its entire edge network — 330+ cities — built on its open-source `moq-rs` implementation. nanocosmos launched MoQ in production at IBC 2025, reporting early adopter deployments reaching hundreds of thousands of concurrent viewers Oracle Video @ Edge entered the market asa MOQT relay fabric for enterprise media workflows. Red5 launched a managed MoQ relay service in partnership with CacheFly. Together, these deployments mark the transition from protocol experimentation to commercial infrastructure
In May 2026, Ateme teamed up Big Blue Marble in its Proof of Concept (PoC) to evaluate MoQ. This PoC aims to test MoQ in a live sports environment, utilizing live broadcast feeds to assess MoQ’s performance, scalability, and operational readiness for future live event streaming.
The OpenMOQ consortium: coordinating the ecosystem
With multiple organizations moving simultaneously, the risk of fragmentation is real. That is the problem OpenMOQ was created to solve.
Founded in September 2025, OpenMOQ is an industry consortium – of which Ateme is a member – focuses on interoperability, shared tooling, and coordinating MoQ adoption across the vendor ecosystem. It is not a standards body – the IETF remains the home of the specification — but a coordination layer that ensures the implementations converging on the IETF drafts can are interoperable to each other in production.
The practical significance of OpenMOQ is that it changes the dynamics for operators evaluating MoQ. When multiple CDNs, encoder vendors, and player SDK providers are coordinating on interoperability, the risk of betting on a single vendor’s interpretation of the spec drops considerably.
What MoQ changes for operators — and what it doesn’t
MoQ is not a wholesale replacement for existing infrastructure. HLS and DASH will continue to serve the vast majority of streaming traffic for years, and for non-latency-sensitive content they remain the right choice. The use cases where MoQ changes the equation are those where sub second latency matters: live sports and betting, interactive events and any scenario where viewers need to experience the same moment simultaneously. In those contexts, MoQ offers something genuinely new: the ability to achieve WebRTC-class latency with CDN-class scale, without operational overhead.
While this blog post mainly mentions the B2C, secondary distribution aspects, it is worth mentioning that MoQ is a highly interesting candidate for primary distribution. MoQ would allow a broadcaster to publish once into the relay network and have affiliates, regional distributors, and platform partners subscribe directly via MOQT. Ateme participated to the Oracle Video @ Edge NAB 2026 demo, which demonstrated this use-case. MoQ for primary distribution allow scaling far more easily when affiliates multiply. MoQ’s pub/sub model means the broadcaster publishes once; the relay network handles the distribution.
What the standard still needs to address
Several gaps are worth naming for anyone making architectural decisions today.
Monetization and ad insertion are partially specified in MSF. Ad insertion support in MoQ is partial. The MSF Event Timeline already can carry SCTE-35 cue points for client-side ad insertion. An extension is considered to allow server-guided ad insertion. Beyond that, the picture is incomplete: server-side ad stitching is not standardized, and MoQ has no equivalent yet to the interstitial mechanisms defined in HLS or the 6th edition of DASH.
VOD support remains limited in the current core spec. The working group has acknowledged that full video-on-demand semantics — range-based playback, trick play, seek — require patterns not yet formally specified. The Fill Fetch mechanism being finalized improves the situation for live catch-up, but VOD over MoQ is still a work in progress.
ABR switching in the relay is architecturally novel and still being defined. The Dynamic Track Selection mechanism (relay-driven quality switching based on congestion signals) and the Top Tracks Filter are both heading toward standardization, but neither is yet in the stable core draft. Player-side ABR logic for MoQ also lacks the decades of tuning that HLS/DASH ABR algorithms have accumulated.
The browser ecosystem still has gaps. WebTransport — the browser API that MoQ depends on — is now supported across Chromium, Firefox, and as of April 2026, Safari iOS 26.4. But deployment of WebTransport-capable browsers is not yet universal, and operators targeting diverse device populations will need fallback paths for the foreseeable future.
Finally, if MoQ is envisaged for Primary distribution as an alternative to SRT (mp2ts based), it may have to carry rich service information (DVB SI/PSI Tables or ATSC System Information) that describes service information including EPG data, conditional access information and regulatory metadata. A MoQ-based primary distribution system would need to define how this metadata is carried. Additionally, primary distribution content is typically protected via conditional access systems (CAS), while MoQ’s security model targets DRM.
None of these are reasons to dismiss MoQ — they are reasons to plan carefully, and to be precise about which use cases are ready for production today versus which will mature over the next two to three years.
How Ateme helps
As a global leader in video delivery solutions, Ateme is approaching MoQ on several fronts. First, at the encoder level: pushing the boundaries of ultra-low latency compression with TITAN to ensure that the quality-latency tradeoff that has long constrained live streaming simply doesn’t have to exist. Second, at the standards level: actively contributing to the interoperability and viability of the MoQ ecosystem — through membership in OpenMOQ, contributions to Shaka Player, and hands-on validation of the protocol stack in real conditions as done for NAB 2026 over the cloudfare or the oracle cloud infrastructure or in the platform of the Big Blue Marble platform.
With solutions spanning contribution, transcoding, packaging, and delivery across every network type Ateme is uniquely positioned to guide customers through the MoQ transition, whatever their infrastructure starting point.
The bottom line
MoQ is at the inflection point between promising and proven. The RFC finalization is imminent. The ecosystem is real and the market is forming. Relay infrastructure starts being deployed. The browser support gap, long a barrier to end-to-end MoQ delivery, is narrowing with WebTransport support landing across major browsers in 2026.
For technical decision-makers evaluating streaming architecture, the question for those seeking sub second end to end low latency is no longer whether MoQ matters — it is how quickly your end-to-end chain from contribution to player can be upgraded.
[1] WebTransport is the API co-developed by W3C and IETF that gives JavaScript controlled access to QUIC streams and datagrams, within a security model the browser can enforce, without exposing raw UDP sockets.