Best OBS Settings for Streamers: Tips and Tricks

By the WpStream Editorial Team

Last updated: June 26, 2026

There is no single best bitrate, and any guide that hands you one number is guessing. The right OBS settings start from a rule, not a preset: your video bitrate should be the lower of two limits, 70 to 80 percent of your measured upload speed, or your streaming platform’s cap, whichever is smaller. A few values never change with your hardware. Use CBR rate control, a 2 second keyframe interval, and 160 kbps audio at 48 kHz on every stream. The one setting that does change is the encoder, which follows your GPU: NVENC on NVIDIA, AMF on AMD, QuickSync on Intel, VideoToolbox on Mac, or x264 on the CPU when no GPU encoder is available. The next block is a copy-paste table you can punch straight into OBS.

Copy-Paste OBS Settings (Pick Your Row)

Rate control is CBR for every row. Test your real upload first, then never exceed your platform’s cap. Each bitrate is a starting range, not a fixed target.

One platform note before you copy a row: a Twitch non-partner stream practically tops out near 6,000 kbps (checked June 2026), so the 1080p at 60 fps row caps there for Twitch, while YouTube and your own website allow higher.

The One Rule That Sets Your Bitrate

Most guides quote a platform maximum and call it your target. That is backwards. Your combined video plus audio bitrate should stay within 70 to 80 percent of your measured upload, and only then be capped by the platform. NVIDIA’s OBS broadcasting guide makes the rule concrete with a bitrate-by-upload table that sits around 75 to 80 percent of each upload tier.

Here is the worked example. A measured 10 Mbps upload means you cap combined bitrate around 7 to 8 Mbps, not 10, and the headroom absorbs the normal wobble of a real connection. But too much bitrate over a marginal link backfires: it causes dropped frames and rebuffering, which looks far worse than a clean lower bitrate.

One catch trips up almost everyone. A generic speed test, the kind at speedtest.net or fast.com, measures against an arbitrary endpoint, not your streaming ingest path. For a stream to a WpStream channel, test with the WpStream speed tester instead, because it measures against the actual streaming ingest infrastructure. Run it at your peak usage time (evening home networks are slower) and stay conservatively below the result.

Output Settings: CBR, Keyframe, and Audio

These three values do not change with your hardware, so set them once. Set Output Mode to Advanced under Settings then Output to see the fields, and find the audio fields under Settings then Audio.

• Rate Control: CBR. Constant bitrate gives platforms and players the steady delivery rate they behave best with, while variable bitrate can spike and surprise RTMP ingest. YouTube specifies CBR for live ingest and Twitch recommends it for all broadcasters, and it is already the OBS default.
• Keyframe Interval: 2 seconds. Set it explicitly, because leaving it at 0 or auto often defaults too high. YouTube specifies keyframes every 2 seconds with a 4 second maximum.
• Audio: 160 kbps, 48 kHz, AAC, stereo. 128 kbps is the floor, and up to 320 kbps makes sense for music-heavy streams. Set the sample rate to 48 kHz, the video standard (44.1 kHz is the music-world default, and mixing the two forces a resample that costs quality for no benefit).

Finally, keep “Enforce streaming service encoder settings” checked; it auto-corrects values a platform would otherwise reject.

Bitrate by Resolution and Frame Rate

The hero table gave you a row. This is the full ladder behind it, still capped by the same rule: the lower of 70 to 80 percent of your upload and the platform maximum.

OBS-aligned starting points for x264 at the veryfast preset, 30 fps:

YouTube’s recommended live H.264 ranges, in Mbps:

Frame rate changes the math. As a general guide, 60 fps needs roughly 50 to 100 percent more bitrate than 30 fps to hold the same clarity. That means a tight upload will make a clean 1080p at 30 fps look sharper than a starved 1080p at 60 fps. Choose 60 fps for gameplay and high motion, 30 fps for talking-head and slower content.

Video Settings: Resolution, Downscale, and FPS

Beginners often get the resolution fields backwards, so set them under Settings then Video with care. Your Base Resolution, labeled Canvas, is what you capture, usually your desktop or game resolution such as 1920×1080. Your Output Resolution, labeled Scaled, is what you actually send. When your upload cannot support native resolution at a clean bitrate, downscale the output to a common target such as 1920×1080, 1280×720, or 852×480.

The Downscale Filter decides how that shrink looks. Bicubic is the all-round default; Lanczos, the 36-sample option, gives maximum sharpness when you have headroom, and NVIDIA recommends it alongside NVENC because the GPU encoder runs at low utilization. Use Bilinear only if the machine is struggling. For frame rate, pick 30 or 60: 60 is smoother but costs more bitrate and encoder load, while 30 is sharper at low bitrate. When the encoder is overloaded, lowering output resolution and FPS is the first lever to pull.

Pick Your Encoder: x264, NVENC, AMF, QuickSync, VideoToolbox

This is the most-searched decision, and every brand deserves equal treatment. Per OBS, x264 software encoding gives the best quality per bitrate, but it is CPU-heavy and can cost you game FPS on a single PC. Hardware encoders offload that work to the GPU with very good quality and little performance impact on modern cards. So on a current GPU, prefer the hardware encoder, and fall back to x264 only when you have no usable one.

• x264, the software path (the CPU does the encode, and your framerate feels it). CPU Usage Preset is veryfast, the OBS baseline. Presets slower than medium show diminishing returns, and you can offset a faster preset with more bitrate. Profile is High, Tune none.
• NVENC on NVIDIA. For GTX 16-series, RTX 20-series, and newer. Preset is P6, Slower and Better Quality. Tuning is High Quality. Multipass is Two Passes, Quarter Resolution. Look-ahead is on, Psycho-Visual Tuning is on. Max B-frames is 4, dropped to 2 if Look-ahead is off. Profile is High. RTX 40-series adds AV1.
• AMF on AMD. Modern Radeon, RDNA2 and RDNA3 competitive. The encoder appears as AMD HW H.264. Set Preset to Quality, or High Quality on newer cards. Profile is High, keyframe 2 seconds, CBR. RX 7000-series adds AV1.
• QuickSync on Intel. Intel iGPUs, plus Intel Arc for AV1. The encoder appears as Intel QuickSync H.264. Set Target Usage to Quality. Profile is High, keyframe 2 seconds, CBR. Older iGPUs trail x264 veryfast, while modern ones are competitive.
• Apple VideoToolbox on Mac. Apple Silicon and Intel Macs. The encoder appears as Apple VideoToolbox H.264. Set CBR where the build exposes it, since its rate-control granularity is narrower than NVENC. Profile is High, keyframe 2 seconds.

AV1 is the 2026 wrinkle. NVIDIA’s NVENC AV1 on RTX 40-series cards is about 40 percent more efficient than H.264 on average, and Intel Arc and RX 7000 cards also support hardware AV1. YouTube accepts AV1 ingest through Enhanced RTMP, so the payoff is a cleaner image at the same bitrate, or similar quality at a lower one (your viewers see the picture, never the codec). Use AV1 only when both your GPU and the destination support it; otherwise H.264 stays the safe RTMP default.

Streaming vs Recording Settings

Your live settings are not your archive settings. Streaming uses CBR because the network needs a predictable rate; a local recording has no such constraint, so use a quality-targeted mode instead: CQP on NVENC, AMF, or QuickSync, or CRF on x264, set to about 20 to 23, where a lower number means higher quality and a bigger file and 20 is visually near-lossless. Record to MKV, which survives a crash without corrupting the file, then remux to MP4 for editing. A stream sized for a 6 Mbps pipe is not the archive you want for a re-upload.

Fix Dropped Frames, Lag, and Encoding Overload

When something goes wrong live, the trick is fixing the right thing, and OBS tells you which one. Open the Stats dock first, under View then Docks then Stats. It separates the three failure types so you fix the right one.

• Dropped frames are a network problem. Your bitrate is exceeding your stable upload. Lower it toward 70 to 80 percent of your measured upload, switch to a wired connection, or test again at a quieter time.
• Encoding overloaded means the encoder cannot keep up. Fix it in order: lower output resolution and FPS first, since that is the biggest lever, then use a faster x264 preset, then switch from x264 to a hardware encoder to offload the CPU.
• Rendering lag is a GPU problem. The GPU is busy compositing. Simplify scenes and sources, because OBS composites every source on every frame, close other GPU-heavy apps, or lower the canvas resolution.

For a deeper read, upload an OBS log to the official Log Analyzer, which flags dropped frames, render lag, and config warnings line by line. And before a broadcast that matters, run a private test stream, for example to a WpStream test channel, to confirm a clean ingest.

Send These Settings to Your Own Website with WpStream

Disclosure: WpStream is the publisher of this guide.

Everything above is destination-agnostic. Twitch and YouTube are just two RTMP endpoints, and you can point the exact same OBS settings at your own WordPress site instead, keeping full control of the player, the page, and your audience data.

Connecting OBS to a WpStream channel is a two-field change. In WpStream you create a live channel and copy its RTMP server URL and stream key. In OBS, open Settings then Stream, set Service to Custom, and paste both values. Everything from the sections above, CBR, the 2 second keyframe, your tier’s bitrate, and your hardware encoder, applies unchanged, because custom RTMP is encoder-agnostic. Test your upload with the WpStream speed tester first, then set OBS bitrate to 70 to 80 percent of that rate.

Viewer-side quality is handled for you. WpStream delivers through a multi-CDN network with adaptive bitrate, so each viewer’s player steps quality down on a weak connection while your only job in OBS stays a clean, stable CBR ingest. Glass-to-glass latency lands at a few seconds.

On plans: Lite at 24 dollars per month or a 36 dollar one-time license and Plus at 59 dollars per month, add recordings, content protection, and pay-per-view. You can learn more on the WpStream site, see how to stream from OBS to your own website, or embed your live stream on your site.

Key Takeaways

• The best OBS bitrate is the lower of two numbers: 70 to 80 percent of your measured upload, or your platform’s cap.
• Use CBR rate control, a 2 second keyframe interval, and 160 kbps audio at 48 kHz on every stream, regardless of hardware.
• Match the encoder to your GPU: NVENC on NVIDIA, AMF on AMD, QuickSync on Intel, VideoToolbox on Mac, x264 on the CPU as a fallback.
• A clean 1080p at 30 fps stream looks sharper than a starved 1080p at 60 fps, which needs roughly 50 to 100 percent more bitrate.
• The same OBS settings stream to your own WordPress site through a custom RTMP URL, with no change to encoder or bitrate.

Frequently Asked Questions

What bitrate should I use in OBS?

Use the lower of two limits: 70 to 80 percent of your measured upload, or your platform’s maximum, so a 10 Mbps upload caps combined bitrate around 7 to 8 Mbps. As starting points, 720p at 30 fps wants 3,000 to 4,500 kbps and 1080p at 30 fps wants 5,000 to 8,000 kbps. Twitch non-partner streams top out near 6,000 kbps, and the WpStream speed tester checks your real ingest path.

Should I use x264 or NVENC in OBS?

Use your GPU’s hardware encoder, NVENC on NVIDIA, AMF on AMD, QuickSync on Intel, or VideoToolbox on Mac, if you have a modern card. It offloads encoding from the CPU with very good quality and minimal performance cost, which matters most when you game and stream on one PC. Use x264 at veryfast only when you have no usable GPU encoder. Either works the same when you point OBS at a WpStream channel, because custom RTMP is encoder-agnostic.

What keyframe interval is best for streaming?

Set the keyframe interval to 2 seconds. YouTube specifies keyframes every 2 seconds with a 4 second maximum, and leaving the value at 0 or auto often defaults too high, so set it explicitly. The same 2 second interval applies whether you stream to Twitch, YouTube, or a WpStream channel on your own site.

Why does OBS say encoding overloaded?

That warning means your encoder cannot keep up in real time. Fix it in order: lower output resolution and frame rate first, then use a faster x264 preset, then switch from x264 to a hardware encoder to offload the CPU. Open the Stats dock to confirm whether the cause is encoding overload, dropped frames from the network, or rendering lag on the GPU. When you stream to a WpStream channel, adaptive delivery handles weak viewer connections.

Dial in the three constants once, match the encoder to your hardware, then let your measured upload set the bitrate. That single discipline beats chasing a magic number. As upload speeds rise and AV1 hardware spreads, the same logic holds: you get a cleaner image at whatever bitrate your connection can sustain. The only real choice left is where the stream lands, and pointing OBS at your own site through a custom RTMP URL keeps the player, the page, and every viewer data point yours. When you are ready to build the rest, here is the full live streaming setup beyond OBS itself.