What Are Dropped Frames in Live Streaming? [Guide]

Dropped Frames

Dropped frames are video frames that a live-streaming encoder cannot successfully send to the platform's ingest server. In OBS Studio, the "Dropped Frames (Network)" counter usually indicates that the connection is unstable or cannot consistently support the selected video bitrate.

When enough frames are dropped, viewers may see stuttering, freezes, missing motion, quality changes, buffering, or a disconnected stream.

What happens when a frame is dropped?

A live encoder captures, renders, compresses, and transmits a continuous sequence of video frames. If the connection cannot send data quickly enough, the encoder may discard some already encoded frames so it can continue trying to deliver the live feed without falling increasingly behind.

A small isolated network interruption may be difficult for viewers to notice. Sustained or rapidly increasing dropped-frame counts can make the stream visibly choppy or cause the encoder to disconnect from YouTube.

Dropped frames vs. rendering and encoding lag

"Dropped frames" is often used loosely, but OBS separates three different kinds of frame loss:

OBS diagnostic	Typical cause	What failed
Dropped frames (network)	Unstable connection, insufficient sustained upload capacity, routing, firewall, or ingest-server path issues	Encoded frames could not be transmitted reliably
Frames missed due to rendering lag	GPU overload or scene-compositing bottleneck	The frame was not rendered on time
Skipped frames due to encoding lag	CPU or hardware-encoder overload	The rendered frame was not encoded on time

The distinction matters because the fixes are different. Lowering bitrate may help network-dropped frames, but it will not necessarily fix a GPU that cannot render a complex scene. Simplifying scenes may fix rendering lag without improving an unstable internet route.

Are dropped frames a YouTube Analytics metric?

No. Dropped frames are primarily an encoder or broadcast-health diagnostic, not a standard audience metric like Concurrent Viewers or watch time.

In Live Control Room, YouTube monitors the feed it receives and displays stream-health warnings. Those warnings can identify problems such as unsupported codecs, incorrect bitrate, mismatched resolution, excessive frame rate, or improper keyframe frequency. The encoder may separately show its own dropped-frame counter.

Common causes of network-dropped frames

• A bitrate that is too high for the connection's stable upload capacity.
• Wi-Fi interference, weak signal, or congestion.
• Other devices, cloud backups, uploads, or applications consuming upstream bandwidth.
• Packet loss, high jitter, or short connection stalls even when a speed test looks fast.
• A router, modem, network adapter, cable, firewall, VPN, or security tool disrupting the connection.
• An unstable route between the creator's network and YouTube's ingest infrastructure.
• Sending primary, backup, or simultaneous streams without enough combined upload headroom.

Why a fast speed test does not rule out dropped frames

A speed test usually measures short-term throughput to a nearby test server. Live streaming requires a stable, continuous connection to a specific ingest server. A connection can report high upload speed while still experiencing packet loss, jitter, route instability, or brief stalls that force the encoder to drop frames.

Use the stable upload result—not the best momentary result—when selecting bitrate. Leave room for normal network variation and any other upload activity.

How to troubleshoot dropped frames

1. Confirm the diagnostic. Check whether OBS reports network-dropped frames, rendering lag, or encoding lag. Do not assume every stutter is a network problem.
2. Check YouTube stream health. Review warnings in Live Control Room and correct any bitrate, codec, resolution, frame-rate, or keyframe errors.
3. Lower the video bitrate. Choose a bitrate the connection can sustain continuously, not just during a brief speed test.
4. Use wired Ethernet. A direct wired connection is generally more stable than Wi-Fi for an important broadcast.
5. Pause competing uploads. Stop cloud syncing, file uploads, backups, game downloads, and other upstream-heavy activity.
6. Restart and inspect network equipment. Check the modem, router, Ethernet cable, adapter drivers, and firewall settings.
7. Run a realistic private test. Include the same cameras, movement, overlays, audio, resolution, and duration planned for the real event.
8. Contact the ISP when loss persists. Provide timestamps, logs, and evidence of packet loss or connection stalls rather than only a speed-test result.

When to lower resolution or frame rate

Lowering resolution or frame rate reduces the bitrate and processing power normally required for a stable stream. A reliable 720p stream is better than an unstable 1080p or 4K stream.

If the issue is network-dropped frames, reduce bitrate first and select a matching resolution. If the issue is rendering or encoding lag, reducing resolution from 1080p to 720p or frame rate from 60 fps to 30 fps can also reduce the computer's workload.

YouTube encoder settings that affect stream stability

YouTube's current live-encoder guidance includes:

• Choose resolution, frame rate, and bitrate that the connection can reliably support.
• Use a supported video codec such as H.264, H.265, or AV1 where applicable.
• Use constant bitrate encoding.
• Send keyframes every two seconds and do not exceed four seconds.
• Test audio and movement before the event.
• Monitor stream-health messages during the broadcast.

The exact bitrate depends on resolution, frame rate, and codec. Copying another creator's bitrate without accounting for your own connection and production settings can create instability.

Dropped frames vs. buffering and latency

Problem	Meaning
Dropped frames	The encoder could not send some video frames successfully
Buffering	The viewer's player temporarily lacks enough data to continue smooth playback
Latency	The time delay between capture and viewer playback

These problems can influence each other but are not identical. A stream can have high latency without dropping frames, or viewers on weak connections can buffer even when the creator's encoder reports zero dropped frames.

What is an acceptable dropped-frame percentage?

The practical target is zero network-dropped frames. An occasional tiny spike may not create a visible problem, but a percentage that continues climbing indicates that the stream is not being delivered reliably.

There is no single YouTube rule stating that a specific nonzero percentage is universally acceptable. Judge severity by whether loss is sustained, whether the count is increasing, and whether viewers or stream-health warnings show degraded playback.

Frequently asked questions

Are dropped frames always caused by slow internet?

They usually indicate a network-delivery problem in OBS, but the issue may be stability, packet loss, routing, Wi-Fi, hardware, or firewall behavior rather than simply a low advertised upload speed.

Is encoding overload the same as dropped frames?

No. OBS reports skipped frames due to encoding lag separately. Encoding overload means the encoder cannot compress frames on time; network-dropped frames means encoded frames cannot be transmitted reliably.

Can viewers buffer when OBS shows zero dropped frames?

Yes. Viewer buffering can be caused by the viewer's device, connection, playback quality, or delivery conditions even when the creator's outgoing feed is stable.

Should I lower bitrate or resolution first?

For network-dropped frames, lowering bitrate is the most direct first step. Keep the bitrate appropriate for the selected resolution; if needed, lower resolution or frame rate as well.