CMAF and LL-HLS latency drops to 2-5 seconds for live streams
This article explains the technical requirements for implementing CMAF chunked encoding and Low-Latency HLS to achieve 2-5 second glass-to-glass latency. It details the necessary CDN configurations, including request collapsing and chunked relay, while highlighting the trade-offs in request volume and player buffer management.
Key Takeaways
- CMAF chunked encoding publishes 200–500 ms partial segments to bypass the structural delay of traditional 6-second HLS segments.
- Low-latency deployments trigger a 10–20x increase in per-viewer HTTP request rates, potentially reaching millions of requests for large-scale events.
- CDN edge servers must support chunked relay to avoid adding a full part duration of latency at every hop in the delivery chain.
- Blocking playlist reloads and preload hints are essential mechanisms to remove polling intervals and stream data the instant it is encoded.
Why It Matters
Achieving 2-5 second latency moves streaming into direct competition with traditional broadcast and real-time interactive services like sports betting and auctions. However, the transition imposes a heavy operational tax, requiring robust HTTP/3 support and sophisticated request collapsing to prevent origin servers from failing under the 20x surge in request traffic. As the industry moves away from 30-second buffers, the trade-off between ultra-low delay and rebuffer rates on mobile networks becomes a critical strategic decision for engineering teams. Watch for whether major CDNs begin offering automated LL-HLS optimization as a standard feature to mitigate the high configuration failure rate currently seen in production rollouts.
Additional Context
CMAF and LL-HLS have moved from specification to production deployment across major live-streaming workflows. Apple introduced LL-HLS as part of the HLS specification in 2019, and the protocol has since been adopted by platforms seeking sub-5-second latency without abandoning HTTP-based delivery. Akamai announced support for CMAF chunked transfer encoding across its media delivery platform in early 2025, enabling broadcasters to serve partial segments that reduce glass-to-glass delay while maintaining compatibility with existing HLS player ecosystems. Cloudflare similarly rolled out low-latency HLS support on its Stream platform in 2025, targeting interactive live events such as sports betting and live commerce where every second of delay affects user engagement and monetization.
The business case for low-latency delivery is increasingly tied to interactive revenue models. Mux reported in its 2025 State of Video report that median live-stream latency among its customers had fallen below 8 seconds, down from over 20 seconds in 2022, driven largely by CMAF-based chunked delivery. The report noted that sports and betting operators were the fastest adopters, with some achieving sub-3-second latency in production. Meanwhile, Wowza Streaming Engine added native LL-HLS output support in its 2025 platform update, signaling that encoder vendors are treating sub-5-second delivery as a baseline expectation rather than a premium feature. This shift pressures CDNs to optimize request handling at scale, since LL-HLS partial segments can increase HTTP request volume by an order of magnitude compared to traditional 6-second segment delivery.
Technical benchmarks from independent testing confirm the latency gains but highlight trade-offs in reliability. Bitmovin published benchmark data in 2025 showing that CMAF chunked encoding achieved median end-to-end latency of 2.8 seconds across a global CDN test, though rebuffer rates increased by 15-20% on cellular networks compared to standard HLS. The study found that HTTP/2 multiplexing and proper chunked-relay configuration were essential to prevent origin overload. THEO Technologies released player-side measurements showing that LL-HLS playback on mobile devices required edge computing latency reduction strategies to maintain quality of experience below 3 seconds, particularly on variable-bitrate 4G and 5G connections. These findings underscore that achieving the 2-5 second target in production demands coordinated optimization across encoder, CDN, and player layers rather than any single-point fix.
Read full article at blog.blazingcdn.com
Enjoy our coverage?
Add StreamingMeme as a preferred source on Google to see more of our streaming news at the top of your Search results.
Add as preferred source