
On this page 13 sections
OBS Studio is free, powerful and used by millions of streamers. It is also full of settings that can make a stream look fantastic or fall apart. This guide gives you the best OBS settings for streaming in 2026, explains what each one does, and shows how to adjust them for your internet connection and hardware. It covers YouTube, Twitch and Kick, and the same ideas work for most other platforms.
Before changing anything, run the Auto-Configuration Wizard once (Tools → Auto-Configuration Wizard). It tests your connection and hardware and gives you a sensible starting point. Then use the sections below to fine-tune.
Step 1: know your upload speed
Everything else depends on this. Run a speed test on the streaming computer, ideally wired, at the time of day you usually stream. Look at the upload figure, and plan with the lowest result you see, not the best.
Your stream’s total bitrate should be no more than about two-thirds of that upload. On a 10 Mbps upload, keep video plus audio under roughly 6.5 Mbps. Our guide to upload speed for live streaming explains why that headroom matters, and the bandwidth calculator does the arithmetic.
Step 2: Output settings
Open Settings → Output and switch Output Mode to Advanced. Under the Streaming tab:
Encoder. Choose a hardware encoder if you have one:
- NVIDIA NVENC (GeForce GTX 16-series and RTX cards): the best all-round choice. Very good quality, almost no CPU impact.
- AMD hardware encoder on recent Radeon cards: good, and improving with each generation.
- Intel Quick Sync on Intel CPUs with integrated graphics: a solid option for laptops.
- Apple VideoToolbox on Macs: the natural choice on Apple silicon.
- x264 (software): excellent quality but CPU-heavy. Use it only with a strong CPU and a game or scene that leaves room.
Rate control. CBR. Live platforms expect a constant bitrate. Our CBR vs VBR guide explains why.
Bitrate. See the table below.
Keyframe interval. 2 seconds. Do not leave it on 0 (auto); many platforms warn or reject streams that are not set to 2. The reasons are in what is a keyframe.
Preset. For NVENC, choose a “Quality” or “Max Quality” preset (named P5 to P7 in newer versions) if your GPU keeps up. For x264, start at “veryfast” and move to “faster” only if CPU usage stays comfortably low.
Profile. High.
Look-ahead and psycho-visual tuning (NVENC): enable both if available. They improve quality in fast motion at little cost.
B-frames: 2 is a good default.
Recommended bitrates
| Output | Twitch | YouTube | Kick |
|---|---|---|---|
| 720p30 | 3,000 kbps | 2,500–4,000 kbps | 3,000 kbps |
| 720p60 | 4,500 kbps | 3,500–5,000 kbps | 4,500 kbps |
| 1080p30 | 4,500–6,000 kbps | 4,500–6,000 kbps | 6,000 kbps |
| 1080p60 | 6,000 kbps | 9,000–12,000 kbps | 6,000–8,000 kbps |
| 1440p60 | not recommended | 12,000–24,000 kbps (HEVC/AV1 better) | varies |
Platforms update their limits from time to time, so check each one’s current help page. Twitch has historically capped standard ingest around 6,000 kbps, which is why many Twitch streamers pick 936p or 900p at 60 fps as a sharper alternative to a squeezed 1080p.
Step 3: Video settings
Open Settings → Video.
Base (canvas) resolution: your monitor’s resolution, usually 1920×1080 or 2560×1440.
Output (scaled) resolution: what you actually send. Match it to your bitrate:
- Under 4,500 kbps: 1280×720.
- 4,500 to 6,000 kbps: 1280×720 at 60 fps, or 1920×1080 at 30 fps. For Twitch at 60 fps, 1600×900 is a good compromise.
- 6,000 kbps and above: 1920×1080.
Downscale filter: Lanczos gives the sharpest result. Use Bicubic if your GPU is struggling.
Common FPS values: 60 for games and fast motion, 30 for talking, cooking, music and creative streams. Halving the frame rate frees a lot of bitrate for sharper detail.
Step 4: Audio settings
Open Settings → Audio and the audio tab under Output.
- Sample rate: 48 kHz.
- Channels: Stereo.
- Audio bitrate: 160 kbps AAC is a safe default. 128 kbps is fine for speech. 320 kbps is unnecessary for most streams.
Then, in the Audio Mixer, add a Noise Suppression filter to your microphone (RNNoise works well) and a Limiter set around -3 dB, so sudden shouts do not clip. Viewers forgive a soft picture far more readily than harsh audio.
Step 5: Advanced settings
Open Settings → Advanced.
- Process priority: Above Normal can help on busy systems.
- Colour format: NV12. Colour space: 709. Range: Limited. These match what platforms expect.
- Stream delay: off unless you need it for competitive games.
- Automatically reconnect: on, with a 10-second retry delay.
- Dynamic bitrate (Network section): on. It lowers bitrate briefly during congestion instead of dropping frames.
Choosing protocol and server
Under Settings → Stream, choose your service and sign in or paste your stream key. Use the recommended server or “Auto”. If your platform offers RTMPS, prefer it; it encrypts the connection and often passes through strict networks more easily. Some platforms also accept SRT or WebRTC (WHIP) ingest, which cope better with unstable connections. The differences are covered in RTMP vs SRT vs WebRTC.
Fixing common problems
The status bar at the bottom of OBS tells you most of what you need.
“Dropped frames (network)” climbing. Your upload cannot sustain the bitrate. Lower it by 20 percent, use a wired connection, and pause cloud backups and downloads on your network.
“Encoding overloaded” or “Skipped frames due to encoding lag”. Your encoder cannot keep up. Switch to a hardware encoder, pick a faster preset, lower the output resolution or drop to 30 fps. In games, capping the game’s frame rate frees GPU time for encoding.
“Frames missed due to rendering lag”. The GPU is maxed out by the game. Cap the game’s frame rate or lower its graphics settings. Running OBS as administrator on Windows can help it get GPU priority.
Blurry during fast motion. Not enough bitrate for the resolution. Lower the resolution or frame rate, or move to HEVC or AV1 ingest if your platform supports it.
Audio out of sync. Check each source’s sync offset in Advanced Audio Properties. Capture cards often need 100 to 300 ms.
HEVC and AV1 in OBS
Recent OBS versions support HEVC and AV1 output with Enhanced RTMP, and YouTube accepts both. With a GPU that encodes AV1 in hardware, such as NVIDIA RTX 40-series or newer Intel Arc and AMD cards, you can get noticeably better quality at the same bitrate. Twitch’s support has been rolling out more gradually, so check before relying on it. If you do switch, keep an eye on viewers’ playback; the platform still transcodes for devices that cannot decode the new codec. Our codec comparison explains the trade-offs.
Test before you go live
Every platform lets you test privately. YouTube allows unlisted or private streams; Twitch has a bandwidth test mode in some tools and you can simply stream with “Store past broadcasts” on to a quiet time. Run for at least 15 minutes, watch the dropped-frames counter and the platform’s stream health panel, and play back the recording on a phone. A stream that looks great on your big monitor may be too dark or too small to read on mobile.
A starting profile you can copy
For a typical setup with an RTX graphics card and a 15 Mbps upload streaming to YouTube:
- Encoder: NVENC H.264, CBR, 9,000 kbps, keyframe interval 2, preset Quality, profile High, look-ahead on.
- Output resolution: 1920×1080, 60 fps, Lanczos.
- Audio: 48 kHz stereo, 160 kbps.
- Network: dynamic bitrate on, auto-reconnect on.
For Twitch on the same machine, drop to 6,000 kbps and consider 1600×900 at 60 fps.
Settings for weaker computers and connections
Not everyone has a high-end graphics card and fibre. If your stream struggles, work through these in order, testing after each one.
First, drop the frame rate to 30. For anything that is not fast gaming, most viewers will not notice, and it roughly halves the work your encoder does. Second, drop the output resolution to 720p. A clean 720p stream looks far better than a stuttering 1080p one. Third, use a faster encoder preset. For x264, “superfast” or “ultrafast” is acceptable on an older CPU; the picture will be a little softer, but it will be steady. Fourth, close anything else that uses the network or the GPU, including browser tabs with video, game launchers updating in the background and cloud sync tools.
On a laptop, plug into mains power and set the power plan to high performance. Many laptops quietly throttle the CPU and GPU on battery, which shows up in OBS as encoding lag. If you use Wi-Fi, move closer to the router or, better, run a cable. A single dropped Wi-Fi packet can cascade into dropped frames on stream.
Finally, remember that your audience mostly watches on phones. A slightly lower resolution with clear, steady motion and good audio will serve them better than chasing numbers. If you are unsure what your connection can handle, the bandwidth calculator and our guide to video buffering are good next stops.
Summary
The best OBS settings start with your upload speed. Use a hardware encoder, CBR, a 2-second keyframe interval and a bitrate around two-thirds of your sustained upload. Match output resolution and frame rate to that bitrate, keep audio at 48 kHz and 160 kbps, and turn on dynamic bitrate and auto-reconnect. Watch the status bar for dropped or skipped frames, fix the cause it points to, and always test privately before a big stream.
Frequently asked questions
What bitrate should I use in OBS for 1080p60?
Around 6,000 kbps for Twitch and 9,000 to 12,000 kbps for YouTube, as long as your upload speed can sustain at least 1.5 times that.
Should I use NVENC or x264 in OBS?
On a recent NVIDIA card, NVENC gives excellent quality with almost no CPU load and is the best choice for most streamers. Use x264 only if you have a powerful CPU and no suitable GPU encoder.
Why does OBS say 'encoding overloaded'?
Your CPU or GPU cannot encode fast enough. Lower the output resolution or frame rate, switch to a hardware encoder, or choose a faster preset.


