Frames OBS discarded because the network couldn't send them in time. Not the same as encoder overload — dropped frames are a network problem, not a CPU or GPU one.
The single most common complaint streamers post on r/Twitch is "OBS keeps dropping frames". The fix depends entirely on which kind of frame loss you are seeing — and OBS distinguishes three.
OBS encodes a frame, hands it to the network for upload to the streaming platform, and waits. If the upload can't keep up, the frame sits in a buffer. After a short grace period, OBS gives up on the oldest frames and drops them. Viewers see freezes, stutters or audio drift. The dropped-frames counter in the OBS status bar shows how many have been discarded since the stream started.
Full troubleshooting in how to reduce stream lag. The Live Monitor feature shows dropped frames in real time during the broadcast.
Dropped frames sit at the intersection of bitrate, rate control and the encoder. They are distinct from buffering on the viewer side, which is a CDN problem.
Because dropped frames measure end-to-end delivery, not raw bandwidth. Wi-Fi packet loss, ISP routing to the ingest server, household network contention and even a noisy cable can all cause drops on a connection that benchmarks at gigabit speeds.
Zero. Even a 0.1% drop rate is visible to viewers as occasional stuttering. If you see any sustained drops, treat it as a fault to fix rather than tolerate.
It fixes drops caused by insufficient upload bandwidth. It will not fix drops caused by Wi-Fi packet loss, a bad ingest route or background sync apps. Diagnose the cause before changing bitrate, otherwise you lose stream quality for no benefit.