Dropped Frames on Stream and How to Fix Them in OBS

Your stream looks fine on your monitor, but viewers say it stutters, and the OBS status bar shows a red percentage climbing past 5 percent. Dropped frames on stream are frustrating because the cause can sit in three different places: your network, your encoder, or your computer's rendering. Each one has its own counter in OBS, and the fix depends on which counter is moving.

This guide walks through how to read those counters, how to test each cause in under ten minutes, and which settings actually stop the stutter.

Three kinds of dropped frames on stream

OBS reports three separate numbers, and people mix them up constantly. Open the Stats dock from the Docks menu and keep it visible while you test.

Stats line	What it means	Usual cause
Dropped frames (network)	Frames encoded but never delivered to the server	Upload speed, packet loss, Wi-Fi, distant ingest server
Skipped frames due to encoding lag	The encoder could not finish frames in time	Encoder preset too heavy, CPU overloaded
Frames missed due to rendering lag	OBS could not draw the scene in time	GPU maxed out by a game, too many sources

Anything under 0.5 percent over a long session is normal and invisible to viewers. Between 1 and 3 percent viewers start to notice small hitches. Above 5 percent the stream looks broken.

Fixing network dropped frames

If the network line is the one climbing, nothing you change in your scene will help. The data is leaving your machine and not arriving.

Run a real upload test

Speed tests show a burst number, not a sustained one. Run three tests at different times of day and take the lowest result. Your total stream bitrate, video plus audio, should sit at no more than 75 percent of that number. On a 10 Mbps upload, that means a ceiling of about 7,500 kbps, and 6,000 kbps leaves comfortable headroom. If you have not matched your bitrate to your connection yet, the guide to stream bitrate settings that match your upload speed has a full table.

Plug in a cable

Wi-Fi is the single most common cause of network drops I see when helping creators. A connection that tests at 40 Mbps can still lose bursts of packets when a microwave runs or a phone joins the network. A $10 Cat 6 cable run to the router fixes more streams than any setting. If a cable is impossible, a powerline adapter is the next best option.

Pick a closer ingest server

In Settings, Stream, choose a specific server near you instead of leaving it on auto, then compare. Twitch's inspector tool and YouTube's stream health panel both show connection stability, so stream privately for fifteen minutes on each candidate.

Turn on dynamic bitrate

Under Settings, Advanced, Network, enable "Dynamically change bitrate to manage congestion." When your connection dips, OBS lowers quality briefly instead of dropping frames. Viewers notice a soft picture far less than they notice a freeze. The piece on setting up a stream that survives a bad internet day covers other safety nets worth adding.

Fixing encoding lag

When skipped frames from encoding lag climb, your encoder is falling behind. The fastest fix is to stop encoding on the CPU.

Switch the encoder to NVENC on NVIDIA cards, AMF on AMD, or QuickSync on Intel. These run on dedicated hardware and barely touch game performance.
If you must use x264, move the preset one step faster, for example from "medium" to "veryfast." Each step roughly halves the CPU work.
Lower the output resolution. Downscaling 1080p to 936p or 720p cuts encoding work by 25 to 55 percent.
Drop from 60 fps to 30 fps for slow games, talk shows and creative streams. That halves the frames the encoder has to finish.

After each change, stream privately for ten minutes and watch the counter. Change one thing at a time so you know what worked.

Fixing rendering lag

Rendering lag means OBS itself cannot compose your scene fast enough, usually because a game is using the entire GPU. Three fixes handle most cases:

Cap the game's frame rate. If your monitor is 144 Hz but you stream at 60 fps, cap the game at 120 or even 90 fps. That frees GPU time for OBS.
Run OBS as administrator on Windows. This lets it request higher GPU priority, and it often clears rendering lag on its own.
Trim heavy sources. Browser sources with animated alerts, multiple webcam filters and large media files all cost GPU time. Disable them one by one to find the culprit.

Also check that OBS is set to use the same GPU as your game on laptops with two graphics chips. Windows sometimes assigns OBS to the weaker integrated chip.

Why more bitrate is not the answer

A lot of forum advice says to raise your bitrate when the stream looks choppy. That is backwards for dropped frames. Choppiness from dropped frames is missing data, not low quality. Raising bitrate from 6,000 to 8,000 kbps on a connection that already struggles makes drops worse, because you are asking the same pipe to carry a third more data.

The reason the advice spreads is that low bitrate causes a different problem: blocky, smeared motion in fast scenes. People see "bad stream" and reach for one fix. Look at the Stats dock first. If network drops are above 1 percent, lower the bitrate by 1,000 kbps and test again. Only raise it when drops sit at zero and the picture is still blocky.

The same goes for buying new hardware. Before spending $300 on a capture card or a new GPU, confirm which counter is moving. I have seen people upgrade a graphics card to fix what turned out to be a cheap Wi-Fi extender.

A ten minute test routine

When drops show up, run this sequence before every important broadcast until the stream is stable:

Open the Stats dock and reset counters by starting a fresh private stream.
Stream your normal scene for five minutes without a game running.
Launch the game and stream another five minutes.
Note which counter climbed and when.

If drops appear before the game launches, look at the network. If they appear only with the game running, look at rendering and encoding. That split narrows the problem in minutes instead of evenings.

Frequently asked questions

What percentage of dropped frames is acceptable on a stream?

Under 0.5 percent over a session is effectively invisible to viewers. Short spikes to 1 or 2 percent during a busy moment are tolerable. A steady rate above 1 percent means something needs fixing.

Why does OBS drop frames even with fast internet?

Fast download speed does not mean fast or stable upload. Wi-Fi interference, a distant ingest server or other devices uploading at the same time can all cause packet loss. Test with a wired connection and a manually selected server to rule these out.

Does streaming at 30 fps reduce dropped frames?

It reduces encoding and rendering lag because the computer handles half as many frames. For network drops it helps only if you also lower the bitrate. Many talk and creative streams look perfectly smooth at 30 fps.