OBS troubleshooting

OBS is lagging: 9 fixes for stutter, low FPS, and encoding overload.

Lag in OBS always has one specific cause — but not always the same one. “Lag” bundles together three different failures: the encoder running out of CPU or GPU time, frames lost between game and OBS, and frames lost between OBS and the platform. This checklist tells you which one you have first, then the fix for each.

Dropped frames troubleshooterDropped vs skipped framesLow-end PC settings

Step 1: Identify which lag you have

Open View → Stats in OBS, then play your game for five minutes. Watch two numbers:

  • Skipped frames due to encoding lag: your encoder can’t keep up. This is a performance problem.
  • Dropped frames (network): frames left your machine but didn’t reach the server. This is a connection problem.
  • Missed frames due to rendering lag: OBS itself can’t draw scenes fast enough. Also performance, but on the render side.

The dropped vs skipped frames guide covers these categories in detail; the distinction matters because network problems don’t get fixed with encoder settings, and vice versa.

Fixes for encoding overload

If OBS shows “encoding overloaded” warnings or skipped frames climb during action:

  1. Switch to a hardware encoder (NVENC, Apple VT, QuickSync, or AMD HW). This alone resolves most overload cases — see the encoder comparison.
  2. If x264 is deliberate: move the preset from medium/ slower back to veryfast. The quality gain of slower presets is invisible in motion.
  3. Drop FPS before resolution: 1080p30 usually beats 1080p60 with side-by-side stutter. Dropping to 30 fps halves the encoder’s work.
  4. Lower the game’s own graphics settings. The GPU has a total budget; the OBS renderer competes with the game for it.
  5. Cap your game’s FPS to a stable value (e.g., 120 on a 240 fps GPU) or use an in-game limiter — a GPU at 100% utilization starves OBS’s capture.

Fixes for rendering lag (missed frames)

  1. Check the capture method. Game Capture beats Display Capture for full-screen games; Window Capture is correct for borderless and apps. Wrong capture adds a full-screen copy per frame.
  2. Avoid display-capturing a different monitor than the game runs on; cross-monitor capture forces additional work.
  3. Trim animated overlays. Browser sources with heavy CSS/canvas animation eat GPU. Disable them one at a time and watch the missed-frames counter.
  4. Move OBS to a dedicated GPU only if multi-GPU — on laptops, OBS pinned to the wrong GPU is a classic double-render scenario (graphics settings in Windows → display → graphics).

Fixes for dropped frames (network)

  1. Use wired Ethernet. Wi-Fi is the most common cause of dropped frames; 2.4 GHz networks drop badly under load.
  2. Lower the bitrate until drops stop — try 500 kbps steps. Rough guide: stay around 60-70% of your measured upload, not 100%.
  3. Try a different ingest server in Settings → Stream (Twitch service setting). Route quality varies by region and time of day.
  4. Pause background uploaders: OneDrive/Sync/backup apps quietly saturate upload. This one surprises people: cloud backup runs during the stream are the classic invisible cause.

The “my game stuttered, was that OBS?” distinction

If the recording shows stutter but you had none during play, OBS’s pipeline did it. If both the game and the recording stutter together, the machine’s total budget was exceeded — the fix is at the game/driver level, not in OBS. Recording locally (before streaming) is the cleanest A/B test.

Settings sanity checks

  • Match the OBS canvas and the game’s output resolution; repeated scaling costs GPU time.
  • Keyframe interval 2, CBR at the bitrate you chose. Other rate controls rarely help troubleshooting.
  • Do not run OBS as Administrator by default; it can break capture of protected windows rather than helping performance.
  • Close hardware-encoder competitors: some recording apps lock the NVENC/QuickSync sessions on shared hardware.

When the machine simply can’t stream that game

Sometimes 1080p60 of a demanding AAA title on a laptop iGPU is not achievable. The ladder that actually works — and that we cover in the low-end PC guide — is: 720p60 → 720p30 → 900p30 → 480p test builds. Own the decision rather than mourning it; viewers stay for the person and the content, not for the resolution, especially in the first months.

Useful next tools