OBS Studio Optimization Guide for Streaming

Use Game Capture, Not Display Capture

The single most impactful change you can make. Display Capture grabs your entire screen through the Windows compositor, which adds latency and uses more GPU resources. Game Capture hooks directly into the game's rendering pipeline — it's faster, lighter, and produces a cleaner image.

1. In your scene, click + under Sources
2. Select Game Capture
3. Set Mode to Capture specific window and select your game
4. If a game doesn't work with Game Capture, try Window Capture first — on Windows 10 and 11 it uses Windows Graphics Capture (WGC), which is nearly as efficient as Game Capture for most applications. Only fall back to Display Capture as a last resort.

Game Capture also avoids accidentally showing notifications, chat windows, or your desktop on stream.

Cap Game Capture to 60 FPS

OBS Game Capture can limit how many frames it pulls from the game, reducing GPU workload without affecting your in-game frame rate. You keep your 144+ fps gameplay while OBS only processes 60 frames per second for the stream.

1. Right-click your Game Capture source → Properties
2. Check Limit capture framerate
3. This caps the capture to your OBS output frame rate (typically 60fps)

This is better than capping your in-game frame rate because you still get the full responsiveness of high refresh rate gaming — your viewers just see a smooth 60fps stream.

Use a Hardware Encoder (NVENC / AMF)

The default x264 encoder runs on your CPU, directly competing with your game for processing power. Hardware encoders offload this to dedicated silicon on your GPU with almost zero performance cost.

1. Go to Settings → Output → Set Output Mode to Advanced
2. Under the Streaming tab, set Encoder to:
   • NVIDIA NVENC H.264 (NVIDIA GPUs)
   • AMD HW H.264 (AVC) (AMD GPUs)
   • QuickSync H.264 (Intel iGPU)
3. Set Rate Control to CBR (constant bitrate — required by Twitch, recommended by YouTube)
4. Set Bitrate: 6000 Kbps for Twitch (their cap), 4500–9000 Kbps for YouTube 1080p60
5. Set Keyframe Interval to 2 seconds (required by Twitch)
6. Set Preset to P5: Slow for NVENC — higher presets burn GPU for marginal gain at streaming bitrates
7. Set Profile to High

Newer GPUs: If you have an NVIDIA 40-series or AMD RDNA2+, you can use HEVC or AV1 encoders instead of H.264. These deliver better quality at the same bitrate. YouTube supports both — Twitch currently only supports H.264.

Resolution and Scaling

Mismatched canvas and output resolutions force OBS to rescale every frame, which costs GPU cycles.

• Canvas Resolution: Match your monitor (e.g., 1920x1080). If you game at 1440p or 4K, set canvas to that and let OBS downscale.
• Output (Scaled) Resolution: 1920x1080 or 1280x720
• Downscale Filter: Lanczos (sharpest quality)

Find these in Settings → Video.

A tip that surprises people: 720p60 at 4500 Kbps often looks better than 1080p60 at 4500 Kbps. Lower resolution means less compression per pixel, which means fewer artifacts. If you're not a Twitch Partner with higher bitrate allowances, consider 720p.

Audio Settings

• Sample Rate: 48 kHz (Settings → Audio). Match this to your audio interface or headset. Mismatched rates cause resampling overhead.
• Audio Bitrate: 160 Kbps (Settings → Output → Audio tab). 128 is acceptable, 320 is wasteful for streaming. 160 is the sweet spot.

OBS Performance Tweaks

Process Priority:

• Settings → Advanced → Process Priority → Above Normal
• Prevents Windows from deprioritizing OBS when your game is demanding resources. Reduces dropped frames during intense scenes.

Disable Preview:

• Right-click the preview area → uncheck Enable Preview
• The preview renders your scene a second time, costing 1–3% GPU. Studio Mode doubles this. Only enable preview when you're actively adjusting scenes.

Browser Sources:

• Each browser source runs its own Chromium instance. Use Image sources for anything static (overlays, logos, borders).
• For browser sources you only use occasionally (alerts, polls), enable "Shutdown source when not visible" in the source properties.

Clean Up Sources:

• Hidden sources in active scenes still consume some resources. Delete sources you're not using rather than just hiding them.

Network Settings

In Settings → Advanced → Network:

• Enable Dynamically change bitrate to manage congestion — if your connection fluctuates, OBS will lower bitrate temporarily instead of dropping frames. Better a brief quality dip than a frozen stream.

Color Space

Set these in Settings → Advanced:

• Color Format: NV12
• Color Space: 709
• Color Range: Partial

This matches what Twitch and YouTube expect. Using "Full" range causes washed-out colors for most viewers because their displays interpret Partial range by default.

Monitor Your Performance

OBS has a built-in diagnostics panel that tells you exactly where your bottleneck is.

• Open View → Stats during your stream
• Watch three numbers:
  • Frames missed due to rendering lag → GPU bottleneck (lower output resolution, disable preview, check encoder preset)
  • Skipped frames due to encoding lag → CPU/encoder bottleneck (switch to NVENC, use faster preset)
  • Dropped frames → Network bottleneck (lower bitrate)

Fix the right problem instead of guessing.