Here is the fact that resolves most of the confusion around this, and almost nobody leads with it:

In OBS, "dropped frames" means your network. That is all it means.

Not your CPU. Not your GPU. Not your encoder. OBS uses three precise, separate terms for three separate failures, and because everyone in every forum thread calls all three "dropping frames", people spend hours applying network fixes to an encoder problem.

The single most useful consequence:

If you are recording to disk and not streaming, your dropped frame count is zero. It cannot be anything else. There is no network in a local recording. If your local recording stutters, you have a different problem, and this article will point you at it in about thirty seconds.

The three counters, and what they actually mean

Open View, Docks, Stats. These are the three numbers, with the exact names OBS gives them:

Reproduce your problem and watch which number climbs.

• Climbing Skipped frames? Your encoder is overloaded. That is a completely different fix and it has its own guide: OBS encoding overloaded.
• Climbing Frames missed? Your GPU is starved. Scroll to the rendering lag section at the bottom of this page.
• Climbing Dropped Frames (Network)? You are in the right place. Read on.

If you want the full triage flow across all three, start at OBS lagging: diagnose it before you fix it.

Network drops: the actual problem

A network drop means OBS produced a frame, encoded it perfectly, handed it to your connection, and your connection could not carry it in time. So OBS threw it away rather than let the stream fall further and further behind real time.

There is exactly one root cause, and everything below is a variation of it:

Your bitrate is higher than what your connection can sustain.

Note the word sustain. This is the trap.

Fix 1: Set your bitrate against your sustained upload, not your speed test

When you run a speed test, you get your connection's peak burst speed over a few seconds, on an idle line, to a nearby server chosen for the purpose. A stream is nothing like that. A stream is a continuous, hours-long upload competing with everything else in your house.

Set your bitrate to roughly 50 to 70 percent of your tested upload speed. If your speed test says 10 Mbps up, do not stream at 9000 Kbps. Stream at 6000, and even that assumes the line is otherwise quiet.

Sensible targets:

If you are dropping frames, cut your bitrate by a third and test again. It is the fastest way to confirm the diagnosis, and if the drops stop, you have your answer. Lowering resolution does not fix network drops, by the way. Only bitrate does. A 720p stream at 6000 Kbps drops exactly as many frames as a 1080p one at 6000 Kbps.

Fix 2: Turn on dynamic bitrate

This is close to a free win and it has been in OBS for years, hidden where nobody looks.

1. Settings, Advanced.
2. Scroll to Network.
3. Tick Dynamically change bitrate to manage congestion.

Without it, OBS keeps hammering out 6000 Kbps into a connection that has temporarily sagged to 4000, and every frame that will not fit is destroyed. With it, OBS lowers the bitrate to match reality and raises it again when the line recovers. You trade a few seconds of softer image for zero dropped frames, and your viewers will take that trade every time, because a momentary quality dip is invisible and a freeze is not.

Turn it on. There is very little reason not to.

Fix 3: Get off Wi-Fi

Wi-Fi is the most common cause of dropped frames, and it is the hardest one for people to accept, because their Wi-Fi "works fine" for everything else.

It does. Browsing, video calls and downloads are all tolerant of a lost packet: they just ask for it again, a few hundred milliseconds later, and you never notice. A live stream cannot do that. A frame that arrives late is a frame that is useless, and OBS discards it.

Wi-Fi drops packets constantly. A microwave, a neighbour's network, a Bluetooth device, someone walking between you and the router: any of it produces a brief interference spike that a stream cannot absorb.

Run an Ethernet cable. It solves this permanently and it is the single highest-value fix on this page. If you genuinely cannot, use 5 GHz rather than 2.4 GHz, get line of sight to the router, and drop your bitrate further than the table above to buy yourself margin. But you are managing the problem rather than solving it.

Fix 4: Change your ingest server

You are streaming to a specific server, and if it is far away or having a bad day, your packets take a long, lossy route.

Do not just trust the "Auto" option. In Settings, Stream, pick the server closest to you and test it. Twitch users can run the Twitch Bandwidth Test (there is a checkbox for it in OBS's stream settings under some services) to measure actual throughput to each ingest, and the nearest server is not always the best one.

If your drops started suddenly and nothing on your end changed, this is a strong suspect. Try a different ingest before you tear your setup apart.

Fix 5: Bind to the right network adapter

Obscure, and a genuine cause of drops that survives every other fix.

If you have more than one network adapter, and you probably do without knowing it, OBS might be trying to send your stream out through the wrong one. VirtualBox, VMware, Hyper-V, Docker, and most VPN clients all install virtual adapters, and they sit in the list looking exactly like a real network connection.

1. Settings, Advanced, Network.
2. Set Bind to IP from Default to the actual IP address of your real network adapter.

If you have never heard of this and you have a VM or a VPN installed, check it. People chase this one for weeks.

While you are here: turn off your VPN while streaming. It adds latency, it caps your throughput, and it routes your video through an extra machine that has no interest in delivering it on time.

Fix 6: Find out what else is using your upload

Your stream is not the only thing uploading, and upload bandwidth is usually a small fraction of download.

• Cloud backup and sync. Dropbox, Google Drive, iCloud, OneDrive and Backblaze will all happily saturate your upstream. Pause them.
• Game and app updates. Steam, Epic and Windows Update do peer-to-peer uploads. Steam in particular seeds content to other users by default.
• Other people in the house. A video call is a sustained upload. So is someone else streaming.
• Torrent clients. Obvious once you remember they are running.

The clue that gives this away: if your drops happen at roughly the same time every day or every session, it is almost always a scheduled backup. Look at what runs on a schedule before you look at anything else.

If your router supports QoS, give your streaming machine priority. It is a proper fix for a shared connection.

The other kind: rendering lag

If your Stats dock shows Frames missed due to rendering lag instead, none of the above applies. Your network is fine. Your GPU cannot composite the OBS canvas fast enough, usually because something else has taken all of it.

This is the one that hits gamers, and it also hits anyone recording a 4K display.

Cap your game's frame rate. This is the fix, most of the time. If your game is running uncapped at 250 fps, it is using 100 percent of your GPU to render frames your monitor never shows, and OBS is left fighting for the scraps it needs to draw its own canvas. Cap the game at your monitor's refresh rate, in-game or in the driver control panel. The game will look identical. OBS will stop missing frames.

Run OBS as administrator. Right-click the shortcut, Run as administrator. Windows gives GPU scheduling priority to the focused, elevated application, which is your game. Running OBS elevated lets it compete on equal terms. Five seconds, no downside.

Lower your Base (Canvas) Resolution. If your canvas is 4K, OBS is compositing a 4K image every single frame before it even downscales it for output. In Settings, Video, dropping the base canvas to 1920x1080 cuts that work by 75 percent. Your layout scales with it.

Set Downscale Filter to Bicubic, not Lanczos. Lanczos is sharper on paper and noticeably more expensive on the GPU.

Cut the source count. Every source, every filter, every browser overlay is drawn each frame. If your scene has accumulated overlays you never look at, they are still being rendered.

Or record something that has none of these failure modes

A local screen recording cannot drop a frame on the network, because there is no network. It is worth noticing how much of the difficulty above comes from OBS being a broadcast tool that you are using as a recorder: three counters to interpret, an ingest server to pick, a network adapter to bind, and a bitrate to negotiate against your ISP.

If you are making tutorials, product demos or course lessons, you do not need any of that machinery, and it is costing you real time.

Cubix Capture records locally, picks your hardware encoder for you, and has no bitrate to guess and no stream to keep fed. What it does instead is the work that is actually yours: it follows your cursor and zooms into what you are clicking, smooths the mouse path, and hands you a finished, mobile-readable tutorial the moment you press stop.

Keep reading: OBS lagging, diagnose it before you fix it · OBS encoding overloaded · OBS high CPU usage · OBS screen recording lag fix