Why these settings matter
OBS Studio ships with defaults that work on almost any machine, which is not the same as settings that look good on yours. The defaults stream at your monitor resolution with a conservative bitrate and a software encoder, so a typical first stream is soft, blocky in fast motion, and costs more frames than it needs to. This guide covers the settings that actually change picture quality and stability: encoder choice, bitrate, resolution and frame rate, keyframes, and the audio chain. Every recommendation states its reasoning, so you can adapt it rather than copy it blindly.
Recommended settings at a glance
| Setting | Twitch 1080p60 | YouTube 1080p60 |
|---|---|---|
| Encoder | NVENC H.264 | NVENC H.264 |
| Rate control | CBR | CBR |
| Bitrate | 6000 Kbps | 8000 to 12000 Kbps |
| Keyframe interval | 2 seconds | 2 seconds |
| Preset | Quality | Quality |
| Profile | high | high |
| Base resolution | 1920x1080 | 1920x1080 |
| Output resolution | 1920x1080 | 1920x1080 |
| Frame rate | 60 | 60 |
| Audio sample rate | 48 kHz | 48 kHz |
| Audio bitrate | 160 Kbps | 160 Kbps |
Treat the bitrate row as a ceiling set by your upload speed, not a target. Test your real upload, then stream at no more than about 70 percent of it so the connection keeps headroom for everything else on your network.
1. Choose the right encoder
The encoder has the largest single effect on both quality and performance, and it is the setting most new streamers leave alone. OBS offers software encoding through x264, which uses your CPU, and hardware encoding through NVENC on NVIDIA, AMF on AMD, or QuickSync on Intel.
On a single-PC setup, use hardware encoding. NVENC on GTX 16-series and newer cards runs on a dedicated block of the GPU that is not doing your game rendering, so the performance cost is close to zero. The quality gap that made x264 the standard recommendation years ago has largely closed: at 6000 Kbps, current NVENC is comparable to x264 on medium, and it does not cost you frames in the game you are streaming.
Pick x264 in two cases only. The first is having no supported GPU encoder. The second is a two-PC setup where a dedicated encoding machine has CPU capacity doing nothing else, where x264 on medium or slow can pull slightly ahead at low bitrates. On one machine running a demanding game, x264 will cost you frames and the trade is rarely worth it.
Set the preset to Quality, the profile to high, and enable Look-ahead and Psycho Visual Tuning if your card supports them. Look-ahead lets the encoder distribute bits across upcoming frames, and Psycho Visual Tuning weights detail toward what the eye actually notices.
2. Set bitrate to what your connection can hold
Bitrate is how much data per second you send, and it is where most quality problems begin. Too low and fast motion smears into blocks. Too high and you drop frames, which is worse for viewers than a slightly softer picture, because dropped frames show up as stutter and audio desync.
Twitch caps non-partnered accounts at around 6000 Kbps in practice, so 6000 with CBR is the standard for 1080p60 there. YouTube is more generous and handles 8000 to 12000 Kbps at the same resolution, which is genuinely visible in high motion content. Always use CBR rather than VBR: platforms expect a constant stream, and variable rate control produces buffering on the viewer side.
The real limit is your upload speed, not the platform cap. Run a speed test, take your upload figure, and stream at roughly 70 percent of it. A 10 Mbps upload supports about 6000 Kbps with margin. An upload under 6 Mbps means dropping to 4500 Kbps, or streaming 900p60 instead, which looks better than a 1080p stream starved of bits.
Set the keyframe interval to 2 seconds. Keyframes are complete frames the decoder can start from, and platforms require them at a predictable interval for their transcoding pipeline. Leaving it on automatic causes problems on both Twitch and YouTube.
3. Resolution and frame rate
OBS has two resolution settings, and confusing them is a common cause of a soft stream. Base canvas resolution is the size of the scene you compose in. Output scaled resolution is what gets sent to the platform. If they differ, every frame is scaled, which costs a little performance and some sharpness.
The simplest configuration is base 1920x1080 and output 1920x1080, so nothing is scaled. If you game on a 1440p monitor, either set the base to 2560x1440 and accept a downscale to a 1080p output, or set the base to 1080p and let your capture source scale once. If you do scale, set the downscale filter to Lanczos. Bilinear is faster but visibly softer, and the difference is easy to see on text and UI elements.
On frame rate, 60 fps is right for gameplay because motion clarity is most of what viewers read as quality in fast content. For a talking head stream, podcast, or anything largely static, 30 fps at the same bitrate gives each frame twice the data and can look cleaner. Match your capture source: if a capture card delivers 1080p60, streaming at 30 throws away half of what it sends. Our capture card guide covers which cards deliver a clean 60 fps feed.
4. The audio chain
Viewers forgive a soft picture and leave over bad audio, so this deserves more attention than it usually gets. Start in Settings, Audio and set the sample rate to 48 kHz. Streaming platforms expect 48 kHz, and running at 44.1 kHz forces a resample that can introduce artifacts. Set the audio bitrate to 160 Kbps, which is transparent for voice and costs almost nothing against your video budget.
Add three filters to your microphone source, in this order. A Noise Gate closes the mic between sentences so room tone, keyboard noise and fan hum do not sit under your voice. Start with a close threshold near -35 dB and an open threshold near -30 dB, then adjust by listening rather than by numbers, since the right values depend entirely on your room. A Compressor at about 4:1 evens out the difference between quiet talking and shouting at a clutch moment. A Limiter at -3 dB catches anything that still spikes, preventing clipping.
Do not put these filters on desktop audio. Game audio and music have a dynamic range you want to keep, and gating them produces audible pumping. Monitor on closed-back headphones rather than speakers, because an open speaker feed gets picked up by the mic and echoes back to viewers.
If you are routing several sources, a hardware mixer or an audio interface gives you control OBS filters cannot: physical gain, real preamps, and separate channels for game, chat and mic. Our audio mixer guide and audio interface guide cover the hardware side, and the XLR mixer guide is the one to read if you are moving from a USB microphone to XLR.
5. Reading the stats window
Open View, Stats in OBS and keep it visible while you test. It separates three failure modes that look identical to viewers but have completely different fixes.
Dropped frames (network) means your bitrate exceeds what your connection can sustain to that ingest server. Lower the bitrate, switch to a wired connection, or select a closer server. Nothing about your CPU or GPU will help.
Skipped frames (encoding lag) means the encoder cannot keep up. On x264, move to a faster preset or switch to NVENC. On NVENC, lower the output resolution or frame rate.
Missed frames (rendering lag) means the GPU is saturated by the game and OBS together. Cap your in-game frame rate a little below your monitor refresh rate so the GPU keeps headroom for compositing, and reduce the number of active sources and filters in your scene.
Where to go from here
Software settings only take you as far as your signal chain allows. A perfectly configured OBS cannot fix a noisy microphone, a webcam starved of light, or a capture card that only passes 30 fps. Once the settings above are in place and your stats window is clean, the next gains come from hardware.
To plan that side, use the setup builder, which checks that parts work together and totals the cost including cables, or browse the parts database directly. For neutral technical reference, see the official OBS Studio site and its knowledge base.
Frequently Asked Questions
What bitrate should I use for streaming at 1080p60?
For 1080p60 on Twitch, 6000 Kbps with CBR rate control is the standard target, and 6000 is also the practical ceiling for non-partnered accounts. YouTube accepts more headroom, so 8000 to 12000 Kbps at 1080p60 is normal there. Set the keyframe interval to 2 seconds on both platforms. If your upload speed is under about 10 Mbps, drop to 4500 Kbps or stream at 900p rather than pushing a bitrate your connection cannot hold.
Should I use NVENC or x264 in OBS?
Use NVENC if you have an NVIDIA GTX 16-series or newer GPU. It encodes on dedicated silicon, so it costs almost no gaming performance, and modern NVENC quality at 6000 Kbps is close to x264 on the medium preset. Use x264 only if you have no supported GPU encoder, or you stream from a separate encoding PC with CPU headroom to spare. On a single-PC setup, x264 at faster or medium presets will cost you frames in demanding games.
Why is my OBS stream dropping frames?
Dropped frames in the OBS stats window mean network, not CPU. Your bitrate is higher than your connection can sustain, or the route to your ingest server is congested. Lower the bitrate by 1000 Kbps and test again, try a closer ingest server, and use a wired connection instead of Wi-Fi. Rendering lag and encoding lag are different problems: those mean your GPU or CPU has run out of headroom, and the fix is a lighter encoder preset or a lower output resolution.
What OBS audio settings should I use for a microphone?
Set the sample rate to 48 kHz in Settings, Audio, because that matches what streaming platforms expect and avoids a resample. Add a Noise Gate to cut room tone between sentences, a Compressor at roughly a 4:1 ratio to even out level, and a Limiter at -3 dB as a safety net against clipping. Apply these as filters on the microphone source, not on desktop audio, and monitor on closed-back headphones so the mic does not pick up your own stream.
What is the difference between base resolution and output resolution?
Base canvas resolution is the size of the scene you compose in OBS. Output resolution is what actually gets sent to the platform. Keeping both at 1920x1080 avoids any scaling. Setting the base to 2560x1440 and the output to 1920x1080 lets you compose against a larger canvas while still streaming 1080p, at the cost of a downscale on every frame. Use the Lanczos downscale filter if you scale, since bilinear softens the image noticeably.