ExplainerTechnology

Low-latency live streaming: why streams lag behind broadcast and how it’s being fixed

Low-latency live streaming explained: why streams lag behind broadcast, where the delay comes from, and how LL-HLS, LL-DASH and WebRTC cut it.

Low-latency live streaming: family watching football on a large TV showing a streaming hub interface
Illustration (AI-generated image)

During a big match, it's common to hear a cheer from next door, or see a goal alert on your phone, before the goal happens on your stream. Live streams often run noticeably behind traditional broadcast, a problem that matters most for sports streaming and one that low-latency live streaming is designed to fix. That gap is latency: the time between something happening in front of the camera and it appearing on your screen.

Where the delay comes from

Latency builds up at every stage:

  1. Capture and production: cameras, graphics, replays and the broadcast production chain.
  2. Contribution: getting the feed from the venue to the encoding facility.
  3. Encoding: compressing the video efficiently takes some look-ahead time.
  4. Packaging into segments: classic HLS and DASH wait until a whole segment of several seconds exists before publishing it.
  5. CDN delivery: segments move through caching layers.
  6. Player buffer: players typically hold several segments in reserve so a network hiccup doesn't cause a stall. This buffer is usually the biggest single source of delay.

With traditional segment durations and buffer settings, live streaming latency can be well behind broadcast. How far behind varies widely between services.

Typical ranges, in broad terms

Industry discussions usually group latency into rough bands:

Band Rough range Typical use
Standard streaming Tens of seconds Most live streams using conventional segment settings
Reduced latency Several seconds to around ten Tuned HLS/DASH and many sports services
Low latency A few seconds LL-HLS, low-latency DASH
Real-time Under a second WebRTC, interactive video

Broadcast TV itself isn't instant. It typically has a few seconds of delay from encoding and transmission. The goal for streaming services is usually to match or approach broadcast, not to reach zero.

Measuring it yourself

A simple way to compare: watch the same live event on two sources side by side, such as an antenna broadcast and a stream, and note when a visible event, like a goal or a clock change, appears on each. A running on-screen clock makes this easy. Repeat a few times, because the delay can drift during a stream.

The trade-off: latency vs stability

A buffer exists to protect against stalls. Shrink it and the stream reacts faster but has less margin when your connection dips. Every low-latency technique is a way to cut delay without giving up too much stability.

Low-latency live streaming techniques

Shorter segments

The simplest approach is to use shorter segments and a smaller buffer. It helps, but very short segments add overhead and can hurt compression.

CMAF chunked transfer

With CMAF, a segment can be split into small chunks that are delivered while the segment is still being encoded. The player can start on the first chunk without waiting for the whole segment.

Low-Latency HLS (LL-HLS)

Apple's LL-HLS adds partial segments, blocking playlist reloads (the server holds a request until new content exists, instead of the player polling) and preload hints, so players learn about upcoming parts in advance.

Low-latency DASH

DASH offers a comparable low-latency mode using chunked CMAF delivery and timing information that lets players stay close to the live edge. The DASH Industry Forum publishes interoperability guidance.

WebRTC

WebRTC, the technology behind browser video calls, can deliver sub-second latency. It's well suited to interactive uses such as auctions, betting-adjacent experiences and watch parties. It is harder and costlier to scale to huge audiences than HTTP-based streaming.

Contribution latency: the part viewers never see

Before a live event reaches any viewer, it has to travel from the venue to the broadcaster or streaming service. This contribution link uses professional protocols and networks designed for reliable, low-delay transport. Examples include satellite uplinks, dedicated fibre and protocols such as SRT (Secure Reliable Transport) over the internet. Delays here add to everything downstream, so services working on low latency look at the whole chain, not just the player.

The CDN's role

Content delivery networks must support low-latency features for them to work at scale. For example, LL-HLS relies on the server holding a playlist request until new content exists. CDNs have to handle that efficiently for millions of viewers at once. This is one reason low latency is often introduced first for specific events or devices rather than everywhere at once.

Comparison

Approach Typical goal Scales on standard CDNs Notes
Classic HLS/DASH Stability first Yes Largest delay
Tuned short segments Moderate reduction Yes Simple, some overhead
LL-HLS / LL-DASH A few seconds Yes, with CDN support Needs player and CDN support
WebRTC Sub-second Harder Best for interactivity

Why services don't always choose the lowest latency

If low latency is possible, why isn't every stream low-latency? Because of trade-offs:

  • More stalls on weak connections. Smaller buffers give less protection against network hiccups.
  • Higher costs. Shorter segments and more frequent requests increase load on servers and CDNs.
  • Device support. Older smart TVs and streaming sticks may not support the newest low-latency features.
  • Ad insertion and rights checks. Some business features add processing steps that are harder to make fast.

For an on-demand film, none of this matters. For a big live match, services weigh viewer complaints about delay and spoilers against the risk of more buffering.

Latency and synchronized viewing

Lower latency also helps features that depend on timing:

  • Watch parties where friends watch together remotely
  • Second-screen experiences, such as live stats and polls
  • Live betting and interactive features, where delays create unfairness or confusion

As these features spread, the pressure to reduce latency on major live events is likely to increase.

What you can do as a viewer

You can't change a service's architecture, but you can avoid adding delay:

  • Use a wired connection or strong Wi-Fi so the player doesn't need to rebuild its buffer after stalls.
  • Don't pause and resume during live events, because it pushes you further behind the live edge. Look for a "jump to live" button.
  • Turn off spoilers. Mute score notifications during matches if your stream lags.

If you see stalls rather than delay, read our buffering troubleshooting guide.

Questions people ask

Why is my stream ahead of my friend's?

Different services, devices and players use different settings, and your positions relative to the live edge can differ. Pausing, a slow start or a buffering event all push a viewer further behind.

Does a faster internet connection reduce latency?

Only slightly. Most delay comes from how the service packages and buffers video, not your connection speed. A faster, more stable connection does help the player stay at its target delay instead of falling behind after stalls.

Can I make my app use low-latency mode?

Some apps offer a low-latency or "live" setting for particular events or devices. Most don't expose a setting. The service decides.

Is latency the same as lag in games?

They're related ideas, but game latency is about the round trip of your inputs to a game server, while streaming latency is the one-way delay from camera to screen.

Why do live streams sometimes jump forward?

Some players speed up playback slightly, or jump ahead, to return to their target delay after falling behind. This can look like a brief skip.

A worked example: why two viewers see a goal at different times

Two neighbours watch the same match. One uses an antenna. The other uses a streaming app on Wi-Fi.

  • The antenna viewer sees the goal after a few seconds of production and broadcast delay.
  • The streaming viewer's feed is packaged into segments of several seconds. Their player holds several segments in reserve, and their stream briefly buffered earlier in the match, pushing it further behind.

The streaming viewer sees the goal noticeably later and hears the cheer through the wall first. If the service supports low-latency HLS or DASH on their device, the gap shrinks to a few seconds. If they had paused to grab a drink, the gap grows unless they press "jump to live." Nothing is broken. It's the expected result of the trade-offs described above.

Glossary

Term Meaning
Live edge The newest available point in a live stream
Segment A short chunk of video, typically a few seconds
Partial segment A smaller piece of a segment, used in low-latency modes
CMAF A common media format that supports chunked delivery
Contribution Transport of the feed from the venue to the service
Glass-to-glass Total delay from camera lens to viewer's screen

How services test latency

Streaming services measure latency with test streams that embed precise timestamps, comparing when a frame was captured with when it appears on a test device. They test across devices and networks, because the same stream can behave differently on a phone, a smart TV and a streaming stick. That is also why a service might enable low-latency playback on some devices before others: each platform's player needs to be tuned and tested.

Key takeaways

  • Most live streaming delay comes from segment packaging and player buffering, not the speed of your internet.
  • Low-latency formats reduce the delay by delivering partial segments sooner and keeping players closer to the live edge.
  • Lower latency means less safety margin, so a stable home connection matters more.
  • If spoilers bother you, a broadcast or managed IPTV source may still be closer to real time than a typical internet stream. See IPTV vs OTT vs cable vs satellite.

Sources and further reading

IPTV News Editorial Team

Articles on IPTV News are researched, written and edited by the publication's editorial team and published under a shared byline. Every article follows our editorial policy, cites its sources and is corrected openly under our corrections policy. Contact the team at info@iptvnews.site.