Media over QUIC (MoQ) Status 2026: WebRTC's Successor or Sidekick?

Media over QUIC reached draft-17 in March 2026 with a December 2026 IESG publication target. It is real, it is funded, and Cloudflare's relay is live. It is also still not a finished standard, and it does not replace WebRTC for AI voice today.

What MoQ is

Media over QUIC Transport (MOQT, draft-ietf-moq-transport-17) is an IETF effort to move real-time media off RTP/SRTP onto QUIC streams. The data model is publishers-relays-subscribers; tracks are sequences of groups, groups contain objects, relays cache and forward. It is built for very large fan-out (millions of subscribers per track) with sub-second latency.

The selling pitch over WebRTC: one transport for both unicast voice calls and live broadcast, with the same congestion control, the same head-of-line-blocking-free streams, and the same NAT story (QUIC traverses better than SRTP). For AI voice specifically, the appeal is the unified transport story — your inference cluster could publish into the same relay mesh as your live audio, simplifying the data path for retrieval-augmented voice agents that need real-time context.

Architecture

```mermaid flowchart LR Pub[Publisher / AI agent] -- objects --> Relay1[MoQ relay 1] Relay1 --> Relay2[MoQ relay N] Relay2 --> Sub1[Subscriber A] Relay2 --> Sub2[Subscriber B] ```

MoQ relays cache by group, so a late joiner can be served the last keyframe without round-tripping to the publisher. For broadcast that is a huge win. For one-to-one AI voice it does not matter — there is no fan-out.

Status as of May 2026

• Spec: draft-17 (March 2 2026), target IESG December 2026.
• Browsers: WebTransport is now Baseline (Safari 26 added it in March 2026). MoQ on top of WebTransport runs in Chrome/Edge with a flag, Firefox behind a pref, Safari not yet.
• Infrastructure: Cloudflare runs MoQ relay across 330+ cities. Akamai, Meta, Twitch are deploying.
• Production: live broadcast (Twitch, TikTok experiments) yes. AI voice production: not yet.

The 2026 milestone that actually matters: WebTransport crossed Baseline. Your application layer can now safely speak QUIC across all major browsers without polyfills. Whether you build MoQ on top of that, or just use WebTransport for signalling alongside WebRTC media, is the practical 2026 question.

CallSphere position

CallSphere is not migrating production voice from WebRTC to MoQ in 2026. Reasons:

• Our use cases are 1:1 (AI agent ↔ user) plus a small handoff fan-out. No broadcast advantage from MoQ.
• WebRTC's media stack (DTLS-SRTP, Opus, jitter buffer, AEC, AGC) is a 15-year solution. MoQ requires you to redo all of that on top.
• OpenAI Realtime, LiveKit, Cloudflare Realtime SFU, and Pion Go gateway 1.23 all speak WebRTC.

We are tracking MoQ for two specific cases:

• Live event recordings played back to thousands of agents/users from Real Estate (OneRoof, /industries/real-estate) — the fan-out is real.
• Browser /demo dual-stack experiments using WebTransport for signalling next to WebRTC media.

Explore a live demo and compare current plans to find the right fit for your business.

Code snippet (early MoQ subscribe via WebTransport)

```ts const wt = new WebTransport("https://moq.example.com/relay"); await wt.ready;

const reader = wt.incomingUnidirectionalStreams.getReader(); while (true) { const { value: stream, done } = await reader.read(); if (done) break; // each stream is a MoQ object on a track for await (const chunk of stream as any) { // dispatch chunk to decoder } } ```

Build steps (for early adopters)

1. Wait for MoQ-transport draft to stabilize (post draft-20 is a reasonable bar).
2. Use WebTransport (Baseline since March 2026) only for signalling first; keep media on WebRTC.
3. If you must experiment with media, use Cloudflare's relay; do not run your own.
4. Plan for the absence of a built-in jitter buffer — you write that yourself in MoQ.
5. Keep WebRTC as the production fallback indefinitely for one-to-one voice.
6. Track the Cloudflare and Meta open-source moq-rs / moq-js implementations for reference.
7. Audit your codec choice — MoQ does not mandate Opus and many demo stacks use AAC.

Common pitfalls

• Treating draft RFCs as stable — wire formats may still change before publication.
• Skipping jitter buffering — MoQ does not give you one; pre-2027 you build it.
• Over-rotating off WebRTC — codecs, AEC, AGC, congestion control are 15-year investments.
• Choosing MoQ for 1:1 voice — wrong fit; benefits are in fan-out broadcast.
• Believing universal browser support — WebTransport yes, MoQ application layer no.

FAQ

Will MoQ replace WebRTC? Not for one-to-one voice. For broadcast it likely will.

Is WebTransport part of MoQ? WebTransport is the browser-side QUIC transport. MoQ is the application protocol. Yes, related, no, not the same.

Does Safari support MoQ? Not yet. WebTransport yes (since 26.0); MoQ application layer no.

Should I learn MoQ? Yes — for the 2027–2028 horizon. Do not bet production on it in 2026.

Can MoQ carry voice calls? Technically yes; in practice the missing AEC/jitter pieces make it impractical for 1:1.

When will MoQ be RFC? IESG publication targeted December 2026; an RFC could ship by mid-2027.

Should I switch from RTMP to MoQ? For broadcast, yes — within 12–18 months. For voice agents, not in 2026.

Does WebTransport on Safari include datagrams? Yes since 26.0; the datagram path is what makes MoQ feasible there.

Production playbook for AI voice teams in 2026

Three rules for tracking MoQ without betting on it:

1. Read the drafts quarterly. Wire format is still moving. Add a recurring calendar item; don't assume LinkedIn will surface the right post.
2. Keep the WebRTC stack ready. Even if MoQ wins for fan-out, your unicast voice agent will keep using WebRTC for years.
3. Pilot WebTransport first. Use it for signalling alongside WebRTC, get the QUIC operational story right, then revisit MoQ media in 2027.

Cloudflare's open-sourced moq-rs and Meta's moq-js are the right reference implementations to read. The ecosystem is small enough that you can fit the whole story in your head; it is also growing fast enough that you should re-check every quarter.

Watch list 2026

• draft-ietf-moq-transport-18+ — wire-format finalization is the inflection point.
• Safari MoQ media support — tracking via WebKit nightly TPs.
• Cloudflare relay pricing — currently free for early adopters; commercial pricing will land in 2026 H2.
• Common Media Application Format (CMAF) over MoQ — the "what does the codec look like?" answer is still being defined.

Sources

• https://datatracker.ietf.org/doc/draft-ietf-moq-transport/
• https://blog.cloudflare.com/moq/
• https://www.ietf.org/blog/moq-overview/
• https://webrtc.ventures/2026/04/webtransport-is-now-baseline-what-it-means-for-real-time-media/
• https://www.nanocosmos.net/blog/media-over-quic-moq/
• https://www.wink.co/documentation/WINK-MoQ-Implementation-Analysis-2025.php

Explore a live demo and compare current plans to find the right fit for your business.