OBS recording or stream is choppy: separate GPU load from network drops
Choose the right troubleshooting path for a choppy local recording, an encoding warning, or a stream that drops frames.
Make a short local recording with the scene that causes trouble, then compare it with the stream. A choppy saved file calls for a rendering or encoding check; rising network dropped frames while streaming calls for a connection check. Lowering every setting at once makes those two problems harder to separate.
In this guide
OBS Studio desktop on Windows, macOS, and Linux. Hardware encoders and performance options depend on the computer and OBS build. Network checks apply to live streaming, not a recording-only session.
Start with the output that actually fails
This guide is based on OBS documentation, not a hands-on test of a particular computer. Record your current output resolution, frame rate, encoder, and bitrate before changing them.
Read the Stats counters during the problem
Open View → Stats before a representative recording or stream. Note the counters at the start and end of the same passage so you can tell which ones increase while the symptom occurs.
- Frames missed due to rendering lag points you toward scene composition and GPU workload.
- Skipped frames due to encoding lag points you toward the work required to encode the output.
- Dropped Frames (Network) concerns the stream connection; it does not diagnose a recording-only session.
The counters help choose a branch; they do not identify a defective component. If the file stutters while the counters remain steady, also compare the captured application and playback software.
Choose a troubleshooting path
| What you observe | Start here | What the observation does not prove |
|---|---|---|
| Choppy recording or an encoding-overload warning | Computer workload and output settings | That your internet connection is too slow |
| Network dropped frames during a stream | Connection to the streaming service | That a new graphics card is required |
| OBS sends normally but some viewers buffer | Delivery quality and viewer conditions | That every viewer has the same problem |
If more than one symptom occurs, keep separate notes for each. A change that helps the stream connection can leave a local recording problem untouched.
If the computer cannot keep up
OBS uses GPU resources to build the scene, even when another component handles encoding. For a game recording, first cap the game's frame rate or reduce its graphics load. Close GPU-heavy applications you recognize and do not need.
Next, try a simpler scene with fewer demanding filters or browser sources. In Settings → Video, reduce the output resolution or frame rate for a controlled comparison. Leave the base canvas alone initially: changing it can require repositioning the whole layout. These options follow OBS's performance troubleshooting guidance.
Run the same kind of movement through each trial. A static desktop does not answer whether the setup can handle your usual gameplay or animated presentation.
If frames drop on the network
Compare a wired connection with Wi-Fi if practical. Lower the streaming bitrate and, where the service offers a choice, try another ingest server. Change one variable and watch whether drops continue. A speed-test result alone does not describe the full route to that server.
OBS's connection guide also describes dynamic bitrate. It can reduce bitrate during congestion, with a quality tradeoff; it does not repair the underlying connection. Avoid disabling security tools or changing a managed network without the administrator's involvement.
If only viewers report buffering
Check whether affected viewers can select a lower playback quality. OBS explains that viewer devices, connections, and available transcoding can differ even when your outgoing stream is stable. Stay within the streaming platform's published recommendations rather than assuming the highest bitrate reaches everyone best.
Before the next important session
If you need a fresh baseline, OBS provides Tools → Auto-Configuration Wizard in its Quick Start Guide. Review the resulting settings and make a representative recording before going live.
For persistent problems, use the OBS Help Portal. Include your operating system, OBS version, encoder, the failing output, and the changes that affected it. Keep private screen content and stream credentials out of shared examples.
Sources and review date
Official documentation consulted on 2026-09-20. Diagnostic suggestions are editorial guidance, not a promise of a particular result.
- OBS: Encoding Performance TroubleshootingChecked 2026-09-20
- OBS: Stream Connection TroubleshootingChecked 2026-09-20
- OBS: Stream Buffering TroubleshootingChecked 2026-09-20
- OBS: Quick Start GuideChecked 2026-09-20
- OBS Studio: English Stats interface labelsChecked 2026-09-20
- OBS Studio: Main-window menu definitionChecked 2026-09-20
A step no longer matches your app? Report a correction with the guide URL and version you use.
Related fixes
OBS Game Capture shows a black screen on Windows: checks before reinstalling
Check the selected game, fullscreen behavior, GPU assignment, and capture conflicts before replacing a working OBS setup.
OBS audio echoes or plays twice: find the duplicate capture path
Separate duplicate device capture, application audio, and monitoring feedback before changing microphone filters.
OBS recording has game audio but no microphone: check the recorded tracks
Find out whether the microphone was never captured, assigned to an unrecorded track, or simply hidden by the player’s selected audio track.