Best OBS Studio Recording Settings for High-Quality Video

So you downloaded OBS Studio, pressed record, and the footage looks like a smeared JPEG from 2011. Welcome to the club. OBS ships with defaults that are okay for streaming to a potato but rubbish for archiving a tutorial, a gameplay session, or a talking-head video you actually want to edit later.
The good news is that getting the right recording settings takes a few minutes once you know what boxes actually matter, and when you fix them you never think about it again.
This guide runs through the settings that actually count, not every checkbox in the Output tab. We'll look at encoder choice, bitrate, resolution and framerate, format and container, and the small handful of advanced settings that matter if you plan to edit the footage instead of just uploading it straight.
If you're on the hunt for better streaming quality for Twitch or YouTube Live, some of this overlaps but the priorities are different. Recording is about quality first and file size second. Streaming is about fitting a clean image inside a fixed upload bandwidth.
Start With Output Mode: Advanced
Click Settings then Output. The first change we're going to make is to the Output Mode dropdown at the top. You need to switch from Simple to Advanced. Simple mode hides the settings that actually matter. Advanced mode looks scarier but everything you need is there right in plain view.
Once you're in Advanced, click the Recording tab (the one next to Streaming). The recording settings are entirely separate from streaming settings, which is the whole point of this mode. You can stream at 6000 kbps to Twitch and record at something much higher for archival purposes, all at the same time. Simple mode can't really manage that cleanly.
Pick the Right Encoder
The encoder is doing all the heavy lifting, and it's the single most important setting in the whole app. You have a few options, depending on your hardware.
Nvenc (Nvidia GPUs)
If you have an Nvidia GPU from the last six or seven years, use Nvenc. Specifically, the option for Nvidia Nvenc H.264 (or Nvidia Nvenc Hevc if it's available). Nvenc runs on a dedicated chip on the GPU, so it puts almost no load on your CPU or your gaming performance.
Modern Nvenc (the Turing architecture and onward, meaning RTX 20-series and up) basically gives you the same image quality as a good CPU encode but with far less overhead. Threads on r/obs are full of people realizing their blurry footage was because they left the encoder on x264 with a low CPU preset.
If you're serious about recording, you should honestly get a modern Nvidia card if your current system can't keep up. Plenty of GPUs available at B&H and the same cards show up on Amazon too if you'd like to compare.
AMD AMF and x264
AMD's hardware encoder (AMF) has come a long way in recent generations, especially on RX 7000-series and newer. If you're on an older AMD card the quality is quite a bit behind Nvenc at the same bitrate, so you'll have to push the bitrate higher to compensate. It still works fine, you just have to tune it.
x264 uses your CPU to encode. If you've got a meaty multi-core CPU and you're not doing anything else while you're recording, x264 on the medium or slow preset will give you the best possible image quality per bitrate. If you're recording gameplay or running a busy desktop, x264 is going to absolutely wreck your framerate.
For gameplay capture, don't use x264 unless you have no GPU encoder available. QuickSync on Intel Arc or a recent Intel CPU is a nice middle ground, not quite as clean as Nvenc but with minimal CPU hit.
Bitrate, Resolution, and Framerate
Bitrate is where most blurry recordings come from. The default streaming bitrate (2500-6000 kbps) is far too low for local recording. You're not fighting an upload pipe, you're writing to an SSD. Just give it more data.
Rough recommendations by resolution, using CBR (constant bitrate) for recording:
- 1080p 30fps: 20,000-30,000 kbps (20-30 Mbps)
- 1080p 60fps: 30,000-50,000 kbps
- 1440p 60fps: 50,000-80,000 kbps
- 4K 60fps: 80,000-120,000 kbps
Those numbers seem enormous compared to streaming bitrates. That's the point. A one-hour 1080p60 recording at 40 Mbps comes out around 18 GB, which is fine for a modern NVMe SSD.
If file size is a bigger concern than absolute quality, just lower the bitrate until the image starts showing compression artefacts in fast motion, and then raise it back up a notch.
For recording, always use CBR or CQP/CRF. Don't use VBR on recordings unless you have a specific reason. CQP (for Nvenc) or CRF (for x264) is actually the smart mode for recording, with constant quality no matter how complex a scene is. CQP 18-23 for Nvenc produces genuinely beautiful footage. Lower numbers are less compressed (more quality), and 18 is nearly lossless.

For the Base (Canvas) Resolution and Output (Scaled) Resolution, under Settings then Video, you're almost always meant to set them the same for recording. If your monitor is 1440p, record at 1440p. Don't make OBS downscale to 1080p, because OBS's downscaling filters (Lanczos, Bicubic) make things a tiny bit softer. Let your editor or upload platform deal with scaling later.
The one exception here: if your GPU can't encode at your native resolution without dropped frames, drop the output resolution a step. Better to have a clean 1080p than a stuttering 1440p.
For framerate, 60fps is worth the bitrate cost for gameplay and anything with fast motion. For tutorials, talking heads, software demos, or just a simple screen recording where nothing moves fast, 30fps is fine and saves you nearly half the file size.
OBS supports 24fps for a vlog edit to get some nice cadence, but screen content generally looks weirdly juddery at 24. Don't record at 120 or 144fps unless you have a really specific reason. Most editors will drop frames anyway when conforming to a 60fps timeline.
Format, Audio, and Advanced Settings
Format trips people up. OBS defaults to MKV (Matroska) and you should keep it that way. MKV is a container that handles crashes gracefully. If your PC locks up mid-record, you lose nothing, the file is still playable up to the crash point. MP4 files can corrupt completely if the write doesn't finish cleanly. Lost recording, lost tutorial, lost gameplay highlight.
If you need MP4 for editing or upload, enable "Automatically remux to mp4" under Settings then Advanced then Recording. OBS will make an MP4 copy of every finished recording without re-encoding, meaning no quality loss, in seconds. Best of both worlds.
For the actual Recording Format dropdown, use "Hybrid MP4" if it's available in your OBS version, otherwise plain MKV. Hybrid MP4 is a newer option that gives you the crash resistance of MKV with the compatibility of MP4.

Under Settings then Audio, set Sample Rate to 48 kHz. That's the standard for video. 44.1 is a music mastering rate and will cause you headaches when you import into a video editor. For the audio bitrate on your recording track, 192 kbps AAC is plenty. 320 kbps if you're being paranoid. Don't go below 160 kbps if there's any voice content.
Use separate audio tracks if you're mixing mic and desktop audio. Under Output then Recording, check Track 1 (mix), Track 2 (mic only), Track 3 (desktop only). In your editor you can then balance them independently instead of getting stuck with whatever OBS mixed together.
A good USB microphone does more for your recording quality than any settings tweak. Your encoder can't fix laptop-mic audio, and no bitrate in the world saves a muddy room tone from your speakers leaking audio into your keyboard pitter patters.
Some more settings under Output then Recording that actually matter:
- Keyframe Interval: 2 seconds for streaming, but for recording you can push that up to 4, or even 0 (auto). Longer keyframe intervals mean you'll use your bitrate more economically. For editing, stick to 2 because editors scrub better with shorter GOPs.
- Preset (Nvenc): P5 (Slow) or P6 (Slower) for quality. P7 is the highest quality preset but can bog down your GPU encoder. P1-P4 are faster but sacrifice image quality.
- Tuning (Nvenc): High Quality for recording. Low Latency is for streaming.
- Profile: High. Not Main, not Baseline.
- Look-ahead and Psycho Visual Tuning: If available on your list for Nvenc, turn them both on. They provide a quality increase with very little overhead on modern cards.
Recording Workflow and Common Issues
Point your recording path at a fast SSD, and have space. If your recordings are going to a spinning disk, you'll risk dropped frames if you are capturing at a higher bitrate and a high framerate, especially at 1440p and 4K. If you are recording to the same drive your game is running from, you'll suffer stutters too. You want a separate SSD for your recordings and your editing scratch.
If you're broadcasting and recording from console or you have a dual-PC streaming setup, this is where a capture card comes into play. OBS takes this capture card input like any other video source, but your recording settings still apply to the finished file. For multi-camera work, see our guide to multi-camera live streaming setup for the general workflow.
If you're recording for upload instead of going live, your next stop is an editor. OBS outputting raw H.264 Nvenc cuts fine in DaVinci Resolve, Premiere and most normal editing software. If you're doing heavy colour grading or advanced compositing you may want to transcode to a mezzanine codec like DNxHR or ProRes first, but for cuts-and-titles editing, the H.264 file you output from OBS is genuinely fine.
We have a run-down of free video editing software for YouTube if you need an editor that can handle H.264 without choking. There's also a more general comparison of free recording and editing software that pairs OBS with editors people actually use.
And a thing to know. OBS high bitrate H.264 actually plays back smoother in editors than a similar bitrate coming off a mirrorless camera, because the GOP structure is cleaner. Don't just assume you need to transcode because it's H.264.
Common problems and fixes:
- Blurry footage during motion: bitrate is too low. Push it up 50% and try again.
- Choppy playback: your encoder can't keep up. Drop your preset down to a faster one, or drop the resolution down one step.
- Large file sizes: use CQP instead of CBR, set CQP to 23 or 24.
- Desynced audio: switch recording format to MKV or Hybrid MP4. MP4 has awful sync support.
- Dropped frames count increasing: you're going over your disk write speed (get a faster SSD) or your GPU is saturated (lower framerate or resolution).
Frequently Asked Questions
What bitrate should I set my OBS recording at for 1080p 60fps?
Somewhere between 30,000 and 50,000 kbps on CBR, or CQP 20-22 if you're using Nvenc or AMD AMF. Below 20 Mbps at 60fps you'll start to see compression artifacts in quick moving scenes like gaming or sport.
For a head and shoulders you can use 20-25 Mbps at 60fps. If you'll be working off the footage you should pick the higher end of bitrate, as exporting to composition afterwards will compound any compression damage, whereas drive space is very cheap. Quality is not.
Should I use MP4 or MKV for OBS recordings?
MKV, and turn on automatic remux to MP4 under Advanced settings. MKV survives crashes, MP4 does not. If OBS crashes, or if your whole computer locks up mid-record, the MKV file is still 100% usable up to that point. MP4 in that situation is often completely wrecked.
The remux process is lossless and takes seconds, so there's no reason to settle for having only one. Hybrid MP4 (in recent versions of OBS) is the best of both worlds: MP4 compatibility with MKV-level crash resilience.
Why do my OBS recordings look worse than my stream?
You're probably still on Simple output mode, and OBS is using your streaming bitrate for recording. Switch to Advanced mode and select the Recording tab separately. Streaming bitrates are limited by your upload speed and rate limits per platform (Twitch capped around 8000 kbps, YouTube higher but still not insane).
Recording has no such cap. Crank it up to 30-50 Mbps, and you'll immediately see why that's a good idea. Also make sure you're on Nvenc or AMF, and not the default x264 on veryfast preset.
Is Nvenc better than x264 for recording?
If you're a typical person, yes. Nvenc as of Turing architecture and newer (RTX 20-series and up) produces files visually indistinguishable from x264 medium preset at the same bitrate, and it doesn't hit your CPU.
x264 on slow or slower presets technically produces marginally cleaner encodes at very low bitrates (not that anybody should be recording at very low bitrates). Use the bitrate you want to use and let Nvenc do its thing. You'll keep your framerate up and your thermals happier. See the OBS advanced recording settings guide for the official encoder breakdown.
What framerate is best to record with OBS?
60fps for gameplay, action, or anything that moves quickly. 30fps for tutorials, software, talking heads, or screen recordings of things that don't move very quick. 30fps cuts your file size about in half over 60fps at the same bitrate, and you won't notice on a static desktop.
Unless you've got some very specific slow-motion workflow in mind, you're just wasting bitrate and hard drive space recording everything at 120-plus fps. When you try to put it on a 60fps timeline, your editor will downconvert it anyway.
Do I need a powerful PC to record well with OBS?
Less than you might think if you use a GPU encoder. A modern Nvidia RTX card can handle 1080p60 recording at about 40 Mbps with no meaningful hit to game framerate. If you're doing x264 on CPU, you do want at least a recent 8-core chip (Ryzen 7 or Core i7/i9) to record anything demanding.
For pure screen recording or talking-head content at 1080p 30fps you can get by on comparatively low-end hardware. The SSD matters more than people think. A fast NVMe SSD will prevent the dropped-frames stutter that ruins long recording sessions.