Beyond the Hype: Where MoQ Fits in Live Streaming
Media over QUIC (MoQ), became one of the most discussed topics at NAB this year as the streaming industry continues looking for better ways to deliver low-latency live video at scale. Much of the attention comes from a growing realization that existing delivery architectures are starting to show their limits, especially as streaming services move further into large-scale live sports, interactive experiences, and real-time audience engagement.
At the same time, the conversation around MoQ can sometimes move faster than the technology itself. There is strong momentum behind the initiative and encouraging technical demonstrations, but there is still a meaningful gap between early interoperability testing and operating a mature, large-scale production ecosystem. That is why it is important to approach MoQ pragmatically and understand both what it changes technically and where it realistically fits within existing streaming architectures.
Most streaming services today still rely on HTTP-based adaptive bitrate delivery through technologies like HLS and MPEG-DASH. These workflows have evolved considerably over the last fifteen years and remain extremely effective for large-scale video distribution. They enabled streaming to scale globally across billions of devices while supporting advanced CDN optimization, caching, DRM integration, and monetization workflows such as dynamic ad insertion.
But the foundations of that architecture were not originally designed for real-time media distribution at internet scale. Traditional adaptive bitrate streaming follows a pull-based model where the player continuously requests video segments from the server through HTTP transactions. That process works well for reliability and scalability, but it also introduces overhead and delay that become increasingly difficult to optimize as latency targets get lower.
This challenge becomes much more visible during major live events where millions of viewers connect simultaneously. Streaming platforms face large traffic peaks, growing infrastructure costs, and increasing pressure around quality of experience. Viewers expect lower latency, faster startup times, and fewer playback issues regardless of audience size. At the same time, new experiences such as live betting, synchronized watch parties, creator commentary, multi-angle viewing and real time fan engagement require much tighter synchronization than traditional streaming architectures were built to support.
What MoQ actually changes
At a technical level, MoQ modernizes the transport layer used for live media delivery. Instead of relying entirely on HTTP over TCP, MoQ is built on QUIC and WebTransport technologies which were designed for more responsive and real time communication. The architecture moves closer to a push based model where media can be distributed more continuously rather than relying on repeated request response exchanges between player and server.
That distinction is important because it changes how live media behaves across the network. Lower latency becomes easier to achieve. Synchronization between viewers improves. Interactive streaming applications become more practical to support at scale.
MoQ is not intended to replace codecs, packaging formats or every existing streaming workflow. It is better understood as a transport evolution designed to improve how media moves across networks for real time applications.
Another major reason momentum is building around MoQ is interoperability. Streaming depends on an ecosystem involving CDN providers, cloud infrastructure vendors, video players, DRM systems, operators and devices that all need to work together. The industry has seen proprietary low latency technologies emerge before, but most struggled to gain widespread adoption because fragmented ecosystems create operational complexity and limit scalability.
Where MoQ makes the most sense today
This hybrid thinking is important because traditional adaptive bitrate streaming still solves many problems extremely well. HLS and DASH ecosystems continue to evolve and low latency variants such as LL HLS and low latency DASH are improving steadily. Existing CDN infrastructures also support sophisticated routing, proxying, load balancing and ad insertion capabilities that have benefited from years of operational maturity.
There are still several areas where MoQ requires further development before broader deployment becomes realistic. Ad insertion is one example because advertising workflows involve multiple ecosystem partners and deeply established HTTP based processes that cannot simply be replicated immediately in MoQ environments. Large-scale operational testing is another important factor because performance characteristics at internet scale are still being evaluated.
As a result, the strongest near term opportunities for MoQ will likely be in areas where real time interaction fundamentally changes the user experience. Conversational applications, live auctions, sports betting, synchronized watch parties and interactive creator led experiences are all examples where lower latency and tighter synchronization provide immediate value. MoQ also appears well positioned as a possible long term evolution for some real time streaming applications currently relying on WebRTC based infrastructures that were never optimized for large scale media delivery.
The operational challenges are just as important as the protocol
There are also infrastructure considerations around QUIC itself. Compared with mature HTTPS and TCP environments, QUIC-based delivery can increase CPU consumption because many hardware acceleration and kernel optimization techniques were developed specifically for TCP over many years. Operators are also evaluating how QUIC traffic coexists alongside traditional TCP traffic across shared networks because both transport models will need to operate together for a long time.
Broadcasters and streaming platforms are unlikely to rebuild their infrastructures from scratch around MoQ. Instead, the industry is moving toward hybrid deployment models where existing HTTP workflows remain in place while MoQ components are introduced selectively for specific low latency or interactive services. Some architectures already combine HTTP input with HTTP and MoQ output together in order to simplify transition and preserve compatibility with existing ecosystems.
This type of incremental adoption reflects the reality of how streaming technologies usually evolve. New protocols and delivery methods rarely replace existing systems overnight, particularly when the installed ecosystem is so large and operationally mature.
Evolution rather than replacement
The future of streaming will likely be hybrid for the foreseeable future. Established adaptive bitrate streaming technologies will continue supporting large scale video delivery while newer transport architectures like MoQ gradually expand into use cases that demand lower latency and more real-time interaction.
The discussion around MoQ is therefore not really about replacing streaming as we know it today. It is about understanding which parts of the existing architecture still work well, which limitations are becoming harder to ignore and where new transport technologies can improve the next generation of streaming experiences.
[Editor's note: This is a contributed article from Broadpeak. Streaming Media accepts vendor bylines based solely on their value to our readers.]
Related Articles
In this wide-ranging interview from Streaming Media 2025, Vindral CEO Daniel Alinder and Streaming Media Contributing Editor Timothy Fore-Siglin discuss Vindral's hybrid live streaming solution, the versatility of the emerging Media Over QUIC (MoQ) protocol, and the benefits of tunable, configurable latency for high-interactivity live streams at scale.
13 Nov 2025
With emerging and still-developing streaming technologies and protocols like Media over QUIC (MoQ) and web transport, some basic definitions are in order to differentiate them from one another and to ensure that they aren't used interchangeably. Akamai's Will Law, an expert on all things QUIC, provides a cogent and crucial breakdown of QUIC and associated terminology in this discussion with Help Me Stream Research Foundation's Timothy Fore-Siglin from the latest Streaming Media Connect.
18 Jul 2025
Media Over QUIC aspires to streamline the entire streaming process by bringing both contribution and distribution into a single protocol again, reducing the need for intermediary transformations. Since MoQ is still in the early stages of development, it will take some time to see it deliver on this promise.
05 Dec 2024