Dropped frames (network) while streaming
The Stats dock shows dropped frames climbing and viewers see buffering. Work through upload capacity, ingest server choice and local network contention.
Published
What the symptom means
"Dropped frames (network)" in View → Stats means OBS encoded the frames successfully but could not deliver them to the ingest server fast enough, so it discarded them to stay live. The encoder and GPU are not the problem; the path between your machine and the platform is.
Check in this order
- Measure real upload, repeatedly. Run several speed tests at the time of day you stream. A connection that reports plenty of headroom at noon can be congested at peak evening hours.
- Lower the bitrate as a test. Halve it for five minutes. If drops stop, the ceiling is bandwidth. Set the working bitrate meaningfully below the measured sustained upload rather than at it.
- Change ingest server. The closest server geographically is not always the best routed. Try the next nearest option in the streaming service settings.
- Use a cable. Wi-Fi drops are usually invisible in a speed test and obvious over a two-hour stream. Ethernet removes an entire class of intermittent loss.
- Find the other traffic. Cloud backup, game updates, a second device streaming video, or a VPN client will all take upload capacity away from OBS.
Settings that help
Enable dynamic bitrate if your platform and OBS version support it, so the encoder reduces quality instead of dropping frames during a congestion spike. Set the network buffer behaviour to its default; increasing buffers hides the symptom for a few seconds and then drops a larger burst.
When it is not your connection
If drops start at the same moment across multiple streamers on the same platform, check the platform's status page before changing anything. Reconfiguring a working setup during a provider incident usually leaves you with a broken setup afterwards.