OBS Settings That Actually Hold Up: Bitrate, Encoder and Resolution
Most OBS guides hand you a preset without saying what it costs. Here's how to pick bitrate, encoder and resolution based on your upload speed and your GPU — and how to read the dropped frames counter.
The short answer
For Twitch at 1080p60, use 6000 kbps with NVENC (HEVC or AV1 on a 40-series card, H.264 otherwise), keyframe interval 2, preset Quality, and a 900p canvas if your upload is below 10 Mbps. Never allocate more than about 70% of your measured upload to the stream. Dropped frames in OBS mean a network problem; skipped frames mean the encoder is overloaded — they have completely different fixes.
Verified and last updated August 12, 2026.
- Time needed
- 25 min
- Difficulty
- Intermediate
- Read time
- 5 min
Every OBS guide gives you the same numbers and none of them explain what happens when your connection does not cooperate. Then you go live, the stats panel turns red, and you have no idea which of the three different frame counters is the one that matters.
So this is ordered by decision rather than by menu. Measure, choose, then configure.
The three counters and what they mean
OBS reports three separate failures and they have nothing to do with each other. Dropped frames = the network could not send them; your upload is the problem. Skipped frames = the encoder could not keep up; your CPU or GPU is the problem. Lagged frames = the rendering pipeline stalled; usually a source or scene issue. Fixing the wrong one is the most common streaming mistake I see.
Step 1: Measure your real upload first
Not the number on your contract. The number you actually get, at the hour you actually stream, on the connection you actually use.
Run a speed test at 9pm on a weekday, not 11am on a Sunday. Household contention is real and evening is when it bites.
Then take 70% of that. If your measured upload is 10 Mbps, your stream budget is 7000 kbps total — and that total includes audio, which is typically 160 kbps, plus protocol overhead. The remaining 30% is headroom for the moments when the connection dips, and without it every dip becomes a dropped frame.
Step 2: Choose the encoder that matches your hardware
This decision used to be genuinely contested. It mostly is not any more.
- NVIDIA 40-series or newer: NVENC AV1 if the platform supports it, otherwise NVENC HEVC or H.264. AV1 gives you roughly 1080p-at-6000 quality for around 4000 kbps.
- NVIDIA 20/30-series: NVENC H.264, Quality preset. Excellent, and effectively free in CPU terms.
- AMD RX 7000 or newer: AMF with AV1. Earlier AMD encoders were genuinely weaker than NVENC; RDNA 3 closed most of that gap.
- Intel Arc: QuickSync AV1, which is surprisingly good and one of the better arguments for an Arc card as a secondary GPU.
- No usable hardware encoder: x264, preset
veryfast. Anything slower will interfere with your game on a single PC.
The reason NVENC wins on a single PC is not that it produces better images than x264 — at equal settings it does not quite. It is that it runs on separate silicon, so it does not compete with the game for CPU time. A slightly less efficient encode that leaves your game running at full speed is the better trade.
Step 3: Set bitrate and resolution as one decision
The mistake here is treating these as independent. They are not: bitrate divided by pixels is what determines how the stream actually looks.
A 1080p60 stream at 3000 kbps looks worse than a 720p60 stream at 3000 kbps, because the same data is spread over 2.25 times as many pixels. Fast-moving content in particular falls apart — a 1080p60 shooter at low bitrate turns into a smear during any camera movement.
If your budget is under 4500 kbps, use 900p (1600×900) or 720p. If you are at 6000, 1080p60 is comfortable. This is the setting people are most reluctant to change and the one that most improves how their stream looks.
Step 4: The output settings that matter
In Settings → Output → Advanced:
- Rate control: CBR. Streaming platforms require constant bitrate. Use CQP or CRF only for local recording.
- Keyframe interval: 2 seconds. Not 0, not auto. Twitch and YouTube both need 2, and getting this wrong causes viewer-side buffering that you will never see yourself.
- Preset: Quality (NVENC) or
veryfast(x264). - Profile: high.
- Look-ahead: off for live streaming, on for local recording. It adds latency.
- Psycho Visual Tuning: on if available. It costs a little performance and meaningfully improves motion.
In Settings → Video:
- Base canvas: your monitor resolution.
- Output scaled: whatever you chose in step 3.
- Downscale filter: Lanczos. Bicubic is acceptable, bilinear is not — it is noticeably soft.
- FPS: 60 for gameplay, 30 for talk content on a constrained upload. 30 at a given bitrate looks sharper than 60 at the same bitrate.
Step 5: Read the stats panel properly
Open View → Stats and keep it visible while you test.
That last row is worth dwelling on. An uncapped game consuming 100% of your GPU leaves nothing for the encoder or the compositor. Capping the game 3–5 FPS below your refresh rate frees up exactly the headroom OBS needs, and it is the fix for more streaming problems than any OBS setting.
Key takeaways
Frequently asked questions
What bitrate should I use for Twitch at 1080p60?
6000 kbps is the practical ceiling for non-partnered channels and it is what most people should use, provided your upload can sustain it. Twitch technically accepts higher, but anything above 6000 risks buffering for viewers on the source-quality stream since transcoding is not guaranteed for smaller channels. If your upload cannot comfortably sustain 6000, drop resolution to 900p rather than lowering bitrate at 1080p — a clean 900p looks considerably better than a starved 1080p.
NVENC or x264 — which is better in 2026?
For single-PC streaming, NVENC, and it is not close any more. The old advice that x264 medium beats NVENC dates from the pre-Turing encoder. Modern NVENC at Quality preset is visually comparable to x264 fast or faster while costing your CPU essentially nothing, which matters enormously when the same machine is running the game. x264 only makes sense on a dedicated streaming PC with CPU headroom to spare.
Should I use AV1?
If you have a 40-series NVIDIA card or RX 7000 AMD card and you are streaming to a platform that accepts it, yes — AV1 delivers roughly the same quality at about 30% less bitrate, which is transformative on a limited upload. Twitch has been rolling out enhanced broadcasting with AV1 support; YouTube accepts it. Check the platform's current status before committing, as this has been changing quickly.
Why do I drop frames only sometimes?
Dropped frames are always the network, and intermittent dropping usually means contention rather than insufficient capacity. Someone else on your connection starting a large upload, a cloud backup kicking in, or Wi-Fi interference at particular times of day. Stream over Ethernet if there is any way to do it, and check whether a backup client is scheduled during your stream hours — that catches a surprising number of cases.
Do I need a second PC for streaming?
Far less than you used to. Hardware encoders removed most of the reason for a two-PC setup — NVENC runs on dedicated silicon and takes a few percent of GPU time, not CPU time. A two-PC setup still helps if you play CPU-heavy competitive titles at very high frame rates, or if you want elaborate production with many sources. For most people starting out, it is money better spent on a microphone.
About the author
Competitive & Settings Editor
Dan played CS:GO semi-professionally in a regional ESEA Main roster between 2017 and 2020, and has hit Radiant in VALORANT in three separate acts. He now spends most of his competitive energy on the unglamorous side of the game: input latency, sensitivity consistency and warm-up routines that actually transfer.
Found something wrong? Games patch and fixes go stale. If a step here no longer works, tell us at hello@spyld.com and we will retest it. Read how we test and our editorial policy.