How to Reduce Stream Latency and Delay: 8 Proven Fixes

Quick answer: To reduce stream latency, switch to a low-latency protocol (WebRTC for sub-second, or SRT and low-latency HLS for a few seconds), turn on your platform's low-latency mode, set your keyframe interval to 1 to 2 seconds, use constant bitrate with a fast encoder preset, right-size your bitrate to your upload speed, and connect over wired Ethernet. Most streams sit 10 to 30 seconds behind real time by default, but the right settings can bring that under 5 seconds, and under 1 second when true real-time interaction is required.

Here's how each fix works and when to use it.

What is stream latency?

Stream latency, often called glass-to-glass latency, is the delay between the moment your camera captures something and the moment a viewer sees it on their screen. A default setup using RTMP to standard HLS often runs 10 to 30 seconds behind. That's fine for a one-way broadcast, but it breaks anything interactive, like live Q&A, auctions, gaming chat, sports, or remote guidance, where every second of delay is felt.

The delay comes from several places stacked together: the transport protocol, how the video is segmented for delivery, buffering in your encoder, network congestion, distance to the ingest server, and the buffer in the viewer's player. Reducing latency means trimming each of these.

1. Choose a low-latency protocol

Protocol is the single biggest lever, because it sets the floor for how low you can go.

• WebRTC delivers sub-second latency, usually under 500 milliseconds. Use it when viewers need to interact in real time.

• SRT is a low-latency transport that performs well over unstable networks, with tunable latency in the low seconds.

• Low-latency HLS (LL-HLS) and low-latency DASH bring segmented streaming down to roughly 2 to 5 seconds while keeping broad device support.

• Standard RTMP ingest to standard HLS is reliable and widely supported, but the HLS packaging is what adds most of the 10 to 30 second delay.

If you only change one thing, change this.

2. Turn on your platform's low-latency mode

Most major platforms have a built-in low-latency setting that is not always on by default. Enabling it can cut delivery delay from tens of seconds down to 2 to 3 seconds with no other changes. Check your platform's stream settings for a "low latency" or "ultra low latency" toggle before touching anything more technical.

3. Set the right keyframe interval

Your keyframe interval, also called the GOP length, controls how often a full reference frame is sent. Shorter intervals let the player start and recover faster, which lowers latency. Set it to 2 seconds for most platforms, or 1 second when you need the tightest delay. Many services actually require a fixed 2-second keyframe interval, so avoid "auto," which can hurt both latency and stability.

4. Tune your encoder for speed

Encoder buffering quietly adds delay, so tune for responsiveness:

• Use constant bitrate (CBR) rather than variable, so delivery stays predictable.

• Pick a faster preset. Slower presets improve compression but add encoding time; "veryfast" is a common balance for live.

• Enable a zero-latency tuning option if your encoder offers it, which strips out lookahead and B-frame buffering built for recorded video.

• Reduce or disable B-frames and lookahead for the lowest possible encode delay.

• Use a hardware encoder (such as NVENC, Quick Sync, or AMF) to offload work from your CPU and keep encode times low.

These settings trade a little compression efficiency for meaningfully lower latency.

5. Right-size your bitrate

A bitrate that's too high for your connection is one of the most common hidden causes of delay. When you push more data than your upload can comfortably carry, packets queue up, get retransmitted, and latency climbs while the stream buffers.

Set your bitrate to leave headroom. A good rule is to use no more than about 60 to 70 percent of your tested upload speed, so there's room for network fluctuation. Dropping resolution or frame rate slightly can also help a strained connection stay stable and current.

6. Use a wired connection and clean up your network

Wi-Fi introduces jitter and packet loss that force buffering, which adds delay. A wired Ethernet connection is the simplest reliability upgrade you can make. Beyond that:

• Stop other bandwidth-heavy activity on the same network while streaming.

• Watch for packet loss, which is a frequent cause of rising latency and stutter.

• On unreliable networks, a protocol like SRT or a bonded or backup connection helps hold latency steady.

7. Pick the nearest ingest server

The physical distance between you and your platform's ingest server adds real delay. Most services let you select or auto-detect the closest server. Choosing one near you shortens the network path and shaves latency, especially for international streams.

8. Reduce buffering on the player side

Even a perfectly tuned stream can look delayed if the viewer's player holds a large buffer. Player buffer size is often set for smoothness over speed. Where you control the player, reduce the buffer and enable the low-latency playback mode so viewers stay closer to real time. On third-party platforms, the low-latency mode from fix 2 handles most of this for you.

What latency should you actually aim for?

Match the target to the use case rather than chasing the lowest possible number:

• Under 1 second: real-time interaction, such as remote guidance, live auctions, or two-way conversation. WebRTC territory.

• 2 to 5 seconds: interactive broadcasts like gaming, live shopping, and Q&A. LL-HLS, SRT, or a platform low-latency mode.

• 10 to 30 seconds: one-way broadcasts where delay doesn't matter. Standard HLS is fine.

One important trade-off: the lower your latency, the smaller your safety buffer, which means less resilience to network hiccups. On shaky connections, pushing latency too low can cause more stutter, so balance responsiveness against stability.

Frequently asked questions

What is a good latency for live streaming? It depends on the use. Sub-second is ideal for true interaction, 2 to 5 seconds is a strong low-latency target for most interactive streams, and under 10 seconds is acceptable for one-way viewing.

What causes live stream delay? Delay stacks up from the protocol and how video is segmented, encoder buffering, bitrate and network congestion, distance to the ingest server, and the viewer's player buffer.

Does lowering bitrate reduce latency? Not directly, but right-sizing your bitrate prevents the network congestion and retransmissions that drive latency up. An overshot bitrate is a common cause of buffering.

Which protocol has the lowest latency? WebRTC, which typically delivers sub-second, glass-to-glass latency and is built for real-time interaction.

Why is my stream 20 to 30 seconds behind real time? That's the signature of standard HLS delivery. Enable your platform's low-latency mode or move to a low-latency protocol to close the gap.

A note on real-time use: for one-way broadcasts, a few seconds of delay is harmless, but for interactive and mission-critical work, such as remote expert guidance, live operations, or field coordination, sub-second latency changes what's possible. That's the gap purpose-built low-latency platforms and protocols like WebRTC and SRT are designed to close.