A good streaming PC setup is less about maxing every quality slider and more about protecting consistency. Viewers will tolerate a slightly softer image; they will not tolerate dropped frames, audio drift, crackling microphones, or a stream that becomes choppy whenever a game gets busy. Prioritize encoder headroom, stable frame pacing, clean audio, and a resolution that fits both your hardware and your internet upload capacity.
For most single-PC game streams in 2026, start with hardware encoding, 1080p at 60 FPS when the system can sustain it, and a sensible bitrate that your platform and connection can handle reliably. Then test the exact game, scene collection, overlays, browser sources, alerts, and voice chat applications you use in real broadcasts. A settings profile that looks perfect on an empty OBS preview may fail during a crowded multiplayer match.
As an Amazon Associate we earn from qualifying purchases at no extra cost to you.
Our Top Picks
Top 3 picks at a glance
Quick Recommended Settings
| Setting | Recommended value | Why |
|---|---|---|
| OBS Output Mode | Advanced | Gives separate, predictable streaming and recording controls. |
| Stream encoder | NVENC H.264, AMD HW H.264, or Intel Quick Sync H.264 | Moves encoding work away from the CPU. |
| Output resolution | 1920×1080 | Best general-purpose balance of clarity, compatibility, and performance. |
| Fallback resolution | 1664×936 or 1280×720 | Reduces encoder and GPU load when 1080p60 is unstable. |
| Frame rate | 60 FPS; use 30 FPS for slow-paced content or weaker hardware | Smooth motion matters most for shooters, racing, and action games. |
| Rate control | CBR | Provides stable delivery for livestream platforms. |
| Video bitrate | 6,000 Kbps for 1080p60; 4,500 Kbps for 936p60; 3,000 Kbps for 720p60 | Matches common platform limits while preserving a clean image. |
| Keyframe interval | 2 seconds | Improves platform compatibility and stream seeking behavior. |
| Audio bitrate | 160 Kbps AAC stereo | Clear voice and game audio without wasting bandwidth. |
| OBS process priority | Above Normal | Helps OBS keep up during CPU contention without aggressively starving games. |
| Game frame cap | Refresh rate minus 3 FPS, or a lower stable cap | Leaves GPU headroom for compositing and encoding. |
Setting-by-Setting
Use Advanced Output Mode: Advanced
Exact value: In OBS Studio, open Settings > Output and set Output Mode to Advanced.
Trade-off: Advanced mode exposes more controls, so it is easier to create a bad combination of settings. The benefit is that your stream and local recording can use different encoders, bitrates, and file formats.
Under the Streaming tab, enable Ignore streaming service setting recommendations only if you understand your platform’s limits. Leave it off when first configuring a channel. Under Recording, use MKV as the recording format. If you need an MP4 afterward, use File > Remux Recordings; this avoids losing an entire recording after a crash or power interruption.
Choose Hardware H.264 Encoding: NVENC, AMD HW, or Quick Sync
Exact value: Go to Settings > Output > Streaming > Encoder. Select NVIDIA NVENC H.264 on compatible NVIDIA GPUs, AMD HW H.264 on compatible AMD GPUs, or QuickSync H.264 when using Intel integrated graphics.
Trade-off: Hardware encoding uses GPU or integrated-media resources and can slightly reduce game performance if the GPU is already fully loaded. CPU-based x264 can look good at slower presets, but it competes directly with the game, browser sources, Discord, and background tasks. For a one-PC setup, hardware H.264 is the dependable default.
For NVENC, set Rate Control to CBR, Keyframe Interval to 2 s, Preset to P5: Slow (Good Quality) or the closest “Quality” option, Tuning to High Quality, Multipass Mode to Two Passes (Quarter Resolution), and Profile to High. Set Look-ahead to Off and Psycho Visual Tuning to On. If encoder overload appears, change multipass to single pass before reducing resolution.
Set Canvas and Output Resolution: 1920×1080
Exact value: Open Settings > Video. Set Base (Canvas) Resolution to your display’s native gaming resolution. Set Output (Scaled) Resolution to 1920×1080. Set Downscale Filter to Lanczos, 36 samples.
Trade-off: A 1080p output is sharper than 936p or 720p, but it requires more encoding bandwidth and GPU compositing work. If you game at 1440p or 4K, keep the canvas at the game display’s native resolution but stream at 1080p rather than forcing the game itself down to 1080p.
If fine detail turns blocky during foliage, grass, particle effects, or fast camera movement, lower Output (Scaled) Resolution to 1664×936 before increasing bitrate beyond platform limits. For low-end systems, use 1280×720. In OBS, make sure each game source fills the canvas: right-click the source, select Transform > Fit to Screen, or press Ctrl+F.
Set Frame Rate: 60 FPS, With a 30 FPS Fallback
Exact value: In Settings > Video, set Common FPS Values to 60. Use 30 for talk shows, turn-based games, strategy games, or when 60 FPS creates rendering lag.
Trade-off: Sixty FPS produces much smoother motion, but doubles the number of frames OBS must render and encode compared with 30 FPS. A stable 30 FPS stream is better than an inconsistent 60 FPS stream with skipped or duplicated frames.
Match the game’s cap to what the system can truly maintain. Do not rely on an uncapped frame rate just because the average FPS appears high. Use the game’s built-in limiter when available. Otherwise, set a driver-level cap in NVIDIA Control Panel under Manage 3D Settings > Max Frame Rate, or AMD Software: Adrenalin Edition under Gaming > Graphics > Radeon Chill with matching minimum and maximum values.
Set Bitrate and Keyframes: 6,000 Kbps and 2 Seconds
Exact value: In Settings > Output > Streaming, set Rate Control to CBR, Bitrate to 6000 Kbps for 1080p60, and Keyframe Interval to 2 s.
Trade-off: Higher bitrate improves image retention in motion but requires more stable upload bandwidth and may reduce accessibility for viewers with slow connections. Do not set bitrate based on a speed test’s peak result. Leave substantial upload capacity unused for multiplayer traffic, voice chat, and normal network variation.
For 936p60, begin at 4500 Kbps. For 720p60, begin at 3000 Kbps. Use 160 Kbps for the audio track. In OBS, watch View > Stats during a real test. “Dropped Frames (Network)” indicates connection or ingest trouble, not an encoder-quality issue.
Configure Audio: 48 kHz, Stereo, 160 Kbps
Exact value: Go to Settings > Audio and set Sample Rate to 48 kHz and Channels to Stereo. Then open Settings > Output > Audio and set Track 1 to 160 Kbps.
Trade-off: Stereo is more immersive for games, but separate track routing takes a few more minutes to configure. Avoid 44.1 kHz on one device and 48 kHz on another; mixed sample rates can create resampling overhead and occasional sync oddities.
Use Settings > Audio > Global Audio Devices sparingly. Instead, add individual sources in the Sources dock: Audio Input Capture for the microphone and Application Audio Capture (Beta) for game or chat audio. This prevents desktop notifications, browser tabs, and system sounds from accidentally reaching the stream.
By Hardware Tier
Low Tier: 720p30 or 720p60 With Conservative Scenes
For older CPUs, entry-level GPUs, or systems that already struggle in the game, use 1280×720. Start at 30 FPS, 2500-3000 Kbps CBR, and hardware H.264 encoding if available. If the game remains stable, move to 60 FPS at 3,000 Kbps. Use a single game capture source, static overlays, and no animated browser widgets. Disable OBS preview by right-clicking the preview and selecting Enable Preview to toggle it off after scene setup.
Cap the game at a stable value rather than chasing monitor refresh rate. Lower in-game shadows, volumetrics, ray tracing, render scale, and crowd density first; those settings often create the worst frame-time spikes.
Mid Tier: 936p60 or 1080p60
A modern mainstream GPU and six-core-or-better CPU can usually target 1664×936 at 60 FPS and 4500 Kbps, or 1920×1080 at 60 FPS and 6000 Kbps. Use the hardware encoder’s Quality or P5 preset, two-pass quarter-resolution mode where available, and psycho visual tuning enabled.
Keep game GPU utilization below the point where OBS starts reporting rendering lag. A practical approach is to cap the game 3 FPS below display refresh, then lower the cap further if the GPU remains pinned during demanding scenes. For example, a 144 Hz monitor can begin with a 141 FPS cap, but a 90 or 120 FPS cap may be more reliable in a heavy game.
High Tier: 1080p60 With Quality Headroom
High-end hardware should still prioritize consistency over excessive output resolution. Use 1920×1080 at 60 FPS, 6000 Kbps CBR, 2-second keyframes, and a hardware encoder quality preset. A powerful PC can support more browser sources, animated overlays, replay buffers, and simultaneous local recording, but each feature consumes resources.
For local recording while streaming, use a separate recording encoder if OBS offers it. Set Settings > Output > Recording > Rate Control to CQP with a starting CQ value around 18-22; lower values create larger, higher-quality files. Record to an SSD with adequate free space, not the same nearly-full drive handling game installs and Windows updates.
Common Mistakes
Running the Game Uncapped
What causes it: The game consumes nearly all GPU time, leaving OBS unable to render scenes on schedule.
How to check: Open View > Stats in OBS. Rising Skipped Frames Due to Rendering Lag points to GPU contention.
What to do: Add an in-game FPS cap or driver-level cap, then reduce GPU-heavy graphics settings. Start with a cap 3 FPS below refresh rate.
How to undo: Remove the cap in the game settings or disable the driver-level limit.
Using Display Capture for Every Game
What causes it: Display Capture captures the entire monitor and may use more resources or expose private windows and notifications.
How to check: Look in the OBS Sources dock. If the source type says Display Capture, it is capturing the monitor rather than the game process.
What to do: Add Game Capture, set Mode to Capture specific window, and choose the game executable. Use Window Capture only if Game Capture fails.
How to undo: Hide or remove Game Capture, then re-enable Display Capture.
Changing Several Settings at Once
What causes it: Multiple simultaneous changes make it impossible to identify whether the failure is network, GPU, encoder, or audio related.
How to check: Review OBS logs through Help > Log Files > Upload Current Log File after a test, and compare timestamps with the Stats window.
What to do: Change one variable per test: first frame cap, then output resolution, then encoder preset, then bitrate.
How to undo: Restore the previous value for the last changed setting before testing another adjustment.
FAQ
Should I stream at 1080p or 936p?
Use 1080p60 when OBS remains free of rendering and encoding lag at 6,000 Kbps. Use 936p60 when motion-heavy games look too compressed at that bitrate or when the GPU needs more headroom. The 1664×936 option is often a better compromise than forcing unstable 1080p60.
Is x264 better than GPU encoding?
Not automatically. x264 uses CPU resources, while NVENC, AMD HW, and Quick Sync use dedicated or specialized hardware paths. On a gaming PC, hardware encoding is usually the safer choice because it preserves CPU capacity for the game and background applications. Test x264 only if you have abundant CPU headroom and know the game will not need it.
Why does OBS say dropped frames when my game is smooth?
Game smoothness and stream delivery are separate. In View > Stats, dropped frames usually indicate a network path problem between your PC and the streaming ingest server. Use wired Ethernet, stop cloud backups and downloads, verify the selected ingest region, and lower bitrate if the connection cannot sustain it.
How do I fix stream audio that is ahead of or behind video?
First set all devices to 48 kHz in Windows: right-click the speaker icon, choose Sound settings > More sound settings, open each device’s Properties > Advanced tab, and select a 48,000 Hz format. Then test a recording. If one source still needs adjustment, open Advanced Audio Properties in OBS and enter an offset in the Sync Offset field, starting with 50 ms adjustments.
