If you record console gameplay through a capture card, the difference between a crisp upload and a blurry, desynced mess usually comes down to a handful of settings buried in your capture software. The good news: you do not need to tweak fifty sliders. Prioritize three things, in order. First, match the capture resolution and frame rate to what your console actually outputs, because a mismatch forces scaling and dropped frames. Second, lock your record bitrate high enough that fast motion does not turn to mush, since bitrate matters more than codec branding for perceived quality. Third, keep audio sample rates identical on both legs of the chain, because sample-rate mismatch is the number-one cause of drift and desync that viewers notice within thirty seconds. Everything else is refinement. This guide covers the settings that matter, the trade-offs behind each value, and how to configure different hardware tiers without guessing.

These values work for the majority of PlayStation 5, Xbox Series X, and Nintendo Switch 2 setups using a PCIe or USB capture card. Adjust from here based on your hardware tier below.

Setting Recommended value Why
Console video output 2160p60, RGB range: Full Feeds the card a clean, uncompressed signal before downscaling.
Capture resolution 1080p60 The sweet spot for upload platforms; scaling down from 4K sharpens the image.
Recording format H.264 (AVC), MP4 or MKV container Widely compatible, hardware encoders handle it easily, and MKV survives crashes.
Video bitrate (CBR) 40,000 Kbps at 1080p60; 80,000 Kbps at 2160p60 High enough that fast motion, rain, and particles hold detail.
Keyframe interval 2 seconds Standard for streaming platforms and safe for editing on most timelines.
Audio sample rate 48,000 Hz everywhere Matching rates across card, mixer, and software prevents drift and desync.
Audio bitrate 320 Kbps AAC Transparent for gameplay and voice; negligible file-size cost.
HDR Off for recording SDR color space avoids washed-out or clipped captures unless your full pipeline supports HDR.

Setting-by-Setting

Console output resolution and refresh rate

Set the console itself to the highest output your capture card can pass through, not just record. On a PS5, go to Settings, then Screen and Video, then Video Output, and set Resolution to 2160p and Video Output Information to check HDR status. On Xbox Series X, open Profile and system, then Settings, then General, then TV and display options, and set Resolution to 4K UHD and Refresh rate to 60Hz (120Hz only if your card explicitly supports 1440p/120 or 4K/120 passthrough, such as recent PCIe cards with HDMI 2.1 input). The trade-off: pushing 120Hz output through a card limited to 60Hz capture either fails silently or forces the console to renegotiate. If your card tops out at 4K/60 input, keep the console at 60Hz and disable VRR for the recording session. On Switch 2, docked output is fixed at up to 1080p60, so leave it alone and configure only the card side.

HDMI range: Full vs Limited

Full range uses 0–255 brightness values per channel; Limited (video range) uses 16–235. A mismatch is the classic cause of “washed out” or “crushed black” captures. What causes it: the console outputs Full while the capture software interprets Limited, or vice versa. How to check: record a ten-second clip of a black screen with a small white logo and inspect it in a video player with a known-good monitor; blacks that look gray indicate range mismatch. What to do: set the console to Full (PS5: Video Output, then RGB Range; Xbox: TV and display options, then Color space), then in your capture software choose Full as well — in OBS Studio it is under Settings, then Advanced, then Video, then Color Format NV12, Color Space Rec. 709, Color Range Full. The trade-off: some older cards and TVs handle Limited more gracefully, and certain streaming encoders expect video range, so if you see posterized darks after switching to Full, revert both console and software to Limited together.

Capture resolution: record at 1080p60 even from a 4K console

The exact value: 1920 x 1080 at 60 frames per second for most recordings. What causes the temptation to record in 4K: cards advertise it, and it feels like the max-quality choice. The trade-off is real, though: 4K recording doubles file size and encoder load for a benefit most viewers cannot see on a compressed upload. How to check your current setting: in OBS, right-click the capture card source, choose Properties, and look at the Resolution/FPS Type — set it to Custom and pick 1920×1080 if the card offers internal downscaling, or use the software’s own downscale filter (Settings, then Video, then Output (scaled) Resolution 1920×1080, Lanczos filter) if it does not. To undo: set the capture source back to the card’s native resolution if you plan to archive raw footage for future re-edits.

Bitrate and rate control

The exact values: 40,000 Kbps for 1080p60 H.264, 80,000 Kbps for 2160p60, using CBR (constant bitrate) rather than VBR. What causes blocky motion: too-low bitrate combined with a rate control mode that starves high-motion scenes. How to check: record thirty seconds of a demanding scene — racing, fast camera pans, heavy particle effects — and step through frame by frame; smearing around moving edges means insufficient bitrate. What to do: in OBS, Settings, then Output, then Recording, set Type to Standard, Video Bitrate to 40000, Rate Control to CBR. To undo or reduce: drop to 30,000 Kbps only if your storage cannot keep up; below that, switch to hardware HEVC at 25,000 Kbps instead of starving H.264. If your card ships with its own software (Elgato 4K Capture Utility, AVerMedia RECentral), the equivalent is a Video Bitrate slider — set it to the same values.

Codec and container

The exact choice: H.264 in MKV for the recording, remuxed to MP4 afterward. What causes corrupted recordings: MP4 files cut off mid-write when software crashes, because MP4 needs its index finalized. How to check: look in OBS under Settings, then Output, then Recording, at the Recording Format dropdown. What to do: choose MKV (or Hybrid MP4 on current OBS versions, which is crash-safe), then after recording use File, then Remux Recordings to convert to MP4 for editing. The trade-off: HEVC and AV1 halve your bitrate needs and look better per megabit, but older editing timelines and some devices struggle with them; H.264 remains the safest universal choice, with HEVC a sensible upgrade if your whole workflow supports it.

Encoder: hardware vs software

The exact setting: NVENC (NVIDIA), Advanced Media Framework/VCE (AMD), or Quick Sync (Intel) rather than x264 software encoding, when your recording PC also has to render or play. The trade-off: x264 at a slow preset squeezes out slightly better quality per bitrate but eats CPU cores; hardware encoders are nearly free performance-wise and modern implementations are close enough that the difference is invisible at 40,000 Kbps. How to check encoder load: in OBS, enable Stats Dock via Docks, then Stats, and watch CPU usage — if recording pushes it past 80 percent, switch encoders. In NVENC properties, use Preset P5, Multipass Mode: Two Passes (Quarter Resolution), Psycho Visual Tuning enabled.

Audio: sample rate, devices, and offset

The exact values: 48,000 Hz sample rate system-wide, 320 Kbps AAC, and a manual sync offset only after measuring. What causes audio drift: one device running at 44,100 Hz while another runs 48,000 Hz forces resampling that accumulates error over long sessions. How to check: in Windows, right-click the speaker icon, then Sound settings, then Advanced, then All sound devices, and confirm every playback and recording device shows 48,000 Hz (24-bit or 16-bit). In OBS, Settings, then Audio, then Sample Rate 48000 Hz. For lip-sync, record a clip of the console’s test-tone or a character speaking, check offset in your editor, and enter a Global Audio Sync Offset in OBS under Advanced Audio Properties — values are typically within plus or minus 200 milliseconds; adjust in 20 ms steps. To undo: reset the offset to zero before re-measuring rather than stacking corrections.

HDR and color space

The exact value: HDR off on the console while recording. What causes washed-out captures: the console outputs HDR10 (Rec. 2100 PQ), but the card and software encode it as SDR without proper tone mapping. How to check: on PS5, Video Output, then HDR, set to Off; on Xbox, Color depth and Color space settings plus the card’s own software will show an HDR flag when active. What to do: disable HDR at the console before launching your capture session, and set OBS color space to Rec. 709 as above. The exception: cards with genuine HDR passthrough-and-record support and HEVC 10-bit output can capture HDR correctly — but only commit to that if your entire edit and export pipeline is 10-bit, otherwise SDR is the lower-risk setting.

By Hardware Tier

Low tier: budget USB card, older laptop

With a sub-$60 HDMI dongle and a machine without a discrete GPU, do not fight the hardware. Record at 1080p30 (set Output Resolution to 1920×1080 and common FPS Value to 30 in OBS Video settings), drop bitrate to 20,000 Kbps H.264 CBR, and use Quick Sync if the CPU supports it, otherwise x264 at preset veryfast. Keep the console output at 1080p60 so passthrough to your TV stays smooth while you record 30 fps. Expect to disable overlays, close background apps, and record to an internal SSD — USB cards on laptops frequently stutter when writing to slow external drives.

Mid tier: 1080p60 or 4K/60 passthrough card, mid-range desktop

This is the tier the Quick Recommended Settings table describes. Record 1080p60 at 40,000 Kbps, hardware encoder with the settings listed above, MKV container, 48 kHz audio. Enable the card’s internal downscaler if available, since on-card scaling frees CPU cycles. This tier comfortably handles two-hour sessions; verify with a fifteen-minute test recording and check the Stats dock for dropped frames before a long session.

High tier: HDMI 2.1 card, dedicated capture rig

With a 4K/120-capable PCIe card and a second PC or an unburdened gaming rig, record native 2160p60 at 80,000 Kbps in HEVC (or AV1 if your encoder and editing suite support it), CBR, keyframe interval 2 seconds, Main10 profile for 10-bit color. Keep a separate scene collection in OBS for 4K capture so you are not reconfiguring per session. If you archive raw footage, also enable an additional “replay/archive” output at high bitrate, then export a separately encoded 1080p file for upload. Do not record 4K/120 for delivery — no major platform serves it, and file sizes become unmanageable; reserve high-refresh capture for slow-motion material edited to 60 fps delivery.

Common Mistakes

Sample-rate mismatch causing drift. What causes it: one device at 44,100 Hz, another at 48,000 Hz. How to check: record ten minutes, then compare audio length to video length in your editor. What to do: set every device to 48,000 Hz in Windows Sound settings and in OBS under Settings, then Audio. How to undo: none needed once rates match; re-record the affected material.

Black screen or flickering capture. What causes it: HDCP handshake failure — consoles ship with HDCP enabled. How to check: capture shows a black screen with audio, or flickers when the TV changes modes. What to do: disable HDCP (PS5: Settings, then System, then HDMI, then Enable HDCP off; Xbox: Settings, then General, then TV and display options, then Video modes, then uncheck “Allow HDCP” under advanced — note Xbox requires no app content playing to toggle it), and use a certified Premium High Speed or Ultra High Speed HDMI cable. How to undo: re-enable HDCP if you use the card’s HDMI output with protected streaming apps.

Recording at wrong fps causing judder. What causes it: OBS set to 30 fps while the card delivers 60, or a fractional mismatch like 59.94 vs 60. How to check: Docks, then Stats, shows “skipped frames due to encoding lag,” and the capture source properties show the actual input mode. What to do: set Settings, then Video, then Common FPS Values to 60 and force the capture source to 1920×1080 at 60 fps in its properties. How to undo: revert to the source’s default resolution/fps type if forcing a mode breaks passthrough.

Washed-out or crushed colors. What causes it: Full/Limited range mismatch or wrong color space (Rec. 601 vs 709). How to check: view known content and compare blacks and saturation against the TV. What to do: set Full range and Rec. 709 identically on console and software, per the color section above. How to undo: switch both back to Limited together — never one side only.

Bitrate starving on long sessions. What causes it: writing 4K captures to a drive that cannot sustain the write speed, producing encoded-frame skips. How to check: record twenty minutes to the target drive, then scan the file for stutters. What to do: record to a drive rated for sustained writes of at least 150 MB/s, or reduce bitrate one step. How to undo: delete the test file and re-run the check after changes.

FAQ

Should I record at 4K or 1080p if my console outputs 4K?

Record at 1080p60 for delivery unless your card and storage handle 2160p60 at 80,000 Kbps without dropped frames and you archive raw footage. Downscaling from a 4K console feed to a 1080p recording actually looks sharper than a native 1080p console signal, because the console renders at full resolution before the card downscales.

Why does my recorded audio drift out of sync over time?

Almost always a sample-rate mismatch between the capture card’s audio input, a USB microphone, and the recording software. Set everything — Windows devices, OBS, and any audio interface panel — to 48,000 Hz. If drift persists after matching rates, measure the offset from a test clip and apply a one-time sync offset in Advanced Audio Properties rather than correcting in the editor every session.

Do I need a capture card at all, or can I use the console’s built-in capture?

Built-in console recording works for quick clips but caps you at 1080p (often 30 fps on some titles), short durations, and console-controlled bitrates. A capture card gives you full control over codec, bitrate, container, and audio routing, plus unlimited session length — necessary for long-form videos, streams, and anything you plan to edit seriously.

What bitrate should I use for uploading to video platforms?

Record at the highest bitrate your hardware sustains — 40,000 Kbps for 1080p60 H.264 or 80,000 Kbps for 2160p60 — because platforms re-encode your upload regardless. Upload quality is determined by your source file’s ceiling; the platform’s own recommended upload bitrates are minimums, not targets. A high-bitrate source survives the re-encode with far less damage than a file recorded at platform-recommended settings.

Related guides