OBS Studio has a lot of menus, and most guides throw every setting at you at once. If you just want to record game clips that look good and don't fall over halfway through a session, you really only need to get a handful of things right.
1. Pick the right encoder
Go to Settings → Output → Recording and check the Encoder dropdown. If your GPU is anything reasonably recent (NVIDIA, AMD, or Intel with a hardware encoder), use the hardware option — NVENC, AMD HW, or QuickSync — instead of x264. Hardware encoding offloads the work from your CPU to a dedicated chip on the GPU, which means recording has a much smaller impact on your actual frame rate in-game. x264 (software encoding) generally looks slightly better at the same bitrate, but it costs real CPU headroom that most gaming rigs would rather spend on the game itself.
2. Set a sane bitrate
Bitrate is the single biggest factor in how clean your footage looks. For 1080p at 60fps, somewhere in the 20,000–40,000 Kbps range is a solid starting point for local recording — you have far more bitrate headroom for a local file than you would for a live stream, so there's little reason to go as low as streaming presets suggest. For 1440p or 4K, scale up accordingly (rough rule of thumb: bitrate scales with total pixels).
If your clips look blocky in fast motion — muzzle flashes, particle effects, quick camera pans — that's almost always a bitrate problem, not a resolution problem.
3. Match your recording resolution to your actual display
Recording at a higher resolution than you need just inflates file size without adding real clarity. Match your Output resolution in Settings → Video to what you'll actually deliver — if you're going to end up exporting 1080p clips for Discord or YouTube, there's rarely a reason to record at native 4K and downscale later, unless you specifically want cropping room to reframe shots in editing.
4. Choose a recording format built to survive a crash
Under Settings → Output → Recording Format, MKV is the safer default over MP4. MP4 files write their index (the part of the file that tells a player where each frame lives) at the very end of the recording — if OBS or your PC crashes before that finalization step, the file can become partially or fully unplayable. MKV writes its structure incrementally, so a crash mid-recording still leaves you with a working file up to that point. OBS even has a "Remux Recordings" utility (under File) to convert a finished MKV into MP4 afterward if you need MP4 specifically for an editor.
5. Don't record audio tracks you won't use
By default OBS can record game audio, mic audio, and Discord/desktop audio as either one mixed track or several separate tracks. Separate tracks are extremely useful if you plan to edit — you can duck game audio under commentary, mute a Discord ping retroactively, or drop in music later. But there's no reason to record five audio tracks if you only ever use two; each unused track is quietly bloating every file you record from then on.
A reasonable "just tell me what to click" preset
- Encoder: Hardware (NVENC/AMD HW/QuickSync)
- Rate Control: CBR
- Bitrate: 30,000 Kbps for 1080p60
- Recording Format: MKV
- Audio Tracks: Game + mic, separate tracks
From there, the main thing left is storage — high-bitrate MKV recordings add up fast, and pulling just the audio out of old clips (rather than keeping every full recording forever) is a quick way to keep a highlight's audio without hanging onto gigabytes of raw video you've already edited down.