Low-end PC streaming

OBS settings for a low-end PC or weak laptop.

A low-end PC can still stream. The trick is choosing settings your hardware can actually hold — start at 480p30 with a hardware encoder, give the stream a few minutes to prove it’s stable, then step up one notch at a time. Cranking every slider to maximum on weak hardware is the fastest way to a slideshow.

Generate low-end OBS settingsCalculate your bitrateDropped vs skipped frames

The 30-second answer

On a typical low-end laptop (older i5 / Ryzen 5, integrated graphics, 4-8 GB RAM), the safest starting preset is:

  • Base resolution: 1280x720.
  • Output resolution: 854x480 (downscale filter: Bilinear).
  • FPS: 30.
  • Encoder: NVENC (NVIDIA), QuickSync (Intel), or AMD HW H.264 — any available hardware H.264 encoder.
  • Rate control: CBR.
  • Video bitrate: 1500-2500 kbps.
  • Audio bitrate: 96-128 kbps AAC.

If that runs cleanly for 10 minutes, try 720p30 around 3000 kbps. If it doesn’t, drop one notch — usually FPS before resolution.

What “low-end” actually means

Three workloads compete for your hardware when you stream: the game, OBS encoding, and everything else in the background. You can stream on a weak PC, but only when at least one of those three gives the other two room to breathe.

  • CPU: OBS’s encoder and your game both use the CPU. Modern Intel and AMD CPUs include a hardware H.264 encoder that leaves the rest of the CPU almost free for the game.
  • RAM: OBS itself is light (a few hundred MB), but browsers and game launchers are not. Chrome and Discord alone can consume 1-2 GB. Closing them gives headroom to everything else.
  • GPU: The game is the GPU’s main job. OBS will use the GPU for downscaling and for compositing sources; newer NVIDIA GPUs can do NVENC entirely off the CPU. Integrated graphics (Intel UHD, AMD Vega iGPU) handle 480p30 well, 720p30 fine, and 1080p60 rarely.

The combination that struggles the most is a dual-core CPU without hardware encoding, a small amount of RAM, and a modern GPU-intensive game. If that’s your setup, expect to stream 480p30 only.

Why hardware H.264 matters on weak hardware

CPU-only x264 encoding on a low-end CPU eats the cycles the game needs. The fix is to use the dedicated encoder chip your CPU or GPU already has:

  • NVIDIA NVENC: available on most GeForce GTX 10-series and newer. Pick NVENC H.264 in OBS.
  • Intel QuickSync: built into most Intel CPUs from the last decade. Pick QuickSync H.264.
  • AMD HW H.264: available on most modern AMD APUs and GPUs. Pick AMD HW H.264.
  • Apple VT H.264 / VideoToolbox: on macOS, the Apple Silicon and Intel encoder both do H.264.

If your system has no hardware H.264 encoder at all (rare on machines made in the last 8-10 years), x264 with the ultrafast or superfast preset is the fallback. Expect lower picture quality; the alternative is a stream that drops frames constantly.

Settings that hurt low-end streams the most

On weak hardware, the biggest wins come from removing work, not changing sliders:

  • Close browsers and tabs. Chrome and Edge are the worst offenders; even a few tabs compete for the same CPU OBS and your game need.
  • Drop overlays and alerts. A complex animated overlay or browser-source alert burns CPU and GPU every frame. Plain scenes work better on low-end setups.
  • Cap the game’s FPS. An uncapped game pushes the GPU as hard as it can go, leaving nothing for OBS’s compositing. Cap to 60, 30, or whatever is sustainable.
  • Lower in-game graphics first. Drop resolution scale, shadows, post-processing. Game readability at lower settings beats a slideshow at high.
  • Don’t record and stream at the same time on a weak PC. Recording doubles the encoder’s load. Stream only when you can, or record gameplay separately through the game itself.

Diagnosing problems on a weak PC

Open View → Stats in OBS. Two numbers matter most:

  • Missed frames / Skipped frames: encoder or rendering pressure. Drop FPS or resolution, close overlays, switch to hardware encoding.
  • Dropped frames (network): your upload can’t keep up. Lower video bitrate or improve the connection.

The right action depends on which number is rising. Read dropped frames vs skipped frames in OBS for the full diagnostic, or paste the OBS warning into the dropped frames troubleshooter for a step-by-step path.

Stepping up safely

Once 480p30 is stable, raise the bar one notch at a time and let each preset run for 5-10 minutes before changing it again. Suggested ladder, on the same hardware:

  • 480p30 at 2000 kbps (baseline; aim for zero skipped frames).
  • 720p30 at 3000 kbps (if the first preset is clean).
  • 720p60 at 3500-4000 kbps (if your upload can hold it and skipped frames stay low).
  • 936p60 at 5000-6000 kbps (only on systems with a dedicated GPU and a solid encoder).

1080p60 is the ceiling most low-end PCs should leave alone. The extra resolution mostly shows up as encoder lag, dropped frames, and a stream that looks worse than the 720p preset the same hardware could have held.

If your laptop is on battery

Battery-mode laptops throttle aggressively to save power. Plug in before going live, and make sure the power profile is set to High Performance (Windows) or Better Battery is off (macOS). Thermal throttling is the silent killer on weak laptops — a laptop cooling pad and a hard surface help more than people expect.

Useful next guides