For a dual-PC recording setup, prioritize a clean 1080p60 capture signal, stable frame pacing, and a recording codec your editing system can actually handle. The capture PC does not need to duplicate every setting from the gaming PC. Its job is to receive a standards-compliant signal, preserve it with minimal dropped frames, and create files that are practical to edit and archive.

The best capture card output resolution for most dual-PC recording builds is 1920×1080 at 60 fps. It delivers excellent image quality for gameplay uploads, avoids the scaling and bandwidth complications of 1440p or 4K capture, and works reliably with mainstream capture cards, OBS Studio, and editing software. If you play at 1440p or 4K, use the card’s passthrough for your monitor while setting the capture output independently where your hardware supports it. In 2026, this remains the most dependable quality-to-storage and compatibility balance for recorded PC gameplay.

Setting Recommended value Why
Gaming PC output to capture card 1920×1080, 60 Hz, RGB, Full range Provides a clean, widely compatible signal with predictable capture performance.
Capture card input format 1080p60 SDR, 8-bit color Minimizes handshake, color, and encoder problems.
OBS Base (Canvas) Resolution 1920×1080 Prevents unnecessary scaling before recording.
OBS Output (Scaled) Resolution 1920×1080 Keeps the recording at the native captured resolution.
OBS Common FPS Values 60 Matches the capture signal and preserves smooth gameplay motion.
Recording format MKV Protects the recording if OBS, Windows, or power fails.
Recording encoder Hardware H.264 or HEVC Reduces CPU load on the capture PC.
Rate control CQP/CQ, quality value 18–22 Maintains quality more consistently than a fixed bitrate for local recording.
Keyframe interval 2 seconds Improves editing, seeking, and upload-platform compatibility.
Color format in OBS NV12, Rec. 709, Partial Matches standard SDR video workflows and avoids washed-out recordings.

Setting-by-Setting

Capture Resolution: 1920×1080

Exact value: Set the gaming PC display sent to the capture card to 1920×1080. In Windows, open Settings > System > Display, select the capture-card display, then choose Display resolution > 1920 × 1080.

Trade-off: A 1080p capture is easier to encode, store, edit, and troubleshoot than 1440p or 4K. The trade-off is that fine UI detail and text will not be as sharp as a native higher-resolution recording.

What causes problems: Sending 1440p, ultrawide, HDR, or unusual refresh rates to a card that only captures 1080p60 can produce a black screen, intermittent signal, or forced scaling.

How to check: In OBS, right-click the capture-card source, choose Properties, and inspect the displayed resolution and frame rate. A healthy source should report 1920×1080 at 60 fps.

What to do: Use the gaming PC’s duplicate-display mode if the capture card behaves as a second monitor: press Windows+P, select Duplicate, then ensure both displays are set to 1080p60. If your card supports high-resolution passthrough, keep the gaming monitor at its preferred resolution and configure the capture device’s output mode in its vendor utility.

How to undo: Return to Settings > System > Display, select the gaming monitor, and restore its original resolution and refresh rate.

Frame Rate: 60 FPS

Exact value: Set Windows to 60 Hz for the capture output, then in OBS open Settings > Video and set Common FPS Values > 60.

Trade-off: 60 fps is ideal for fast gameplay, but it requires more storage and encoder work than 30 fps. Choose 30 fps only when recording slower content or when the capture PC cannot maintain stable recording performance.

What causes problems: A mismatch such as a 59.94 fps device signal with a manually forced 60 fps workflow can create occasional duplicated or skipped frames, especially with some USB capture devices.

How to check: In OBS, open View > Stats while recording. Watch Skipped frames due to encoding lag and Frames missed due to rendering lag. Both should remain at zero or near zero during a test.

What to do: Keep the entire chain consistent: 1080p60 from the gaming PC, 60 fps in OBS, and a 60 fps timeline in your editor. If the device explicitly identifies itself as 59.94, use Settings > Video > Fractional FPS Value and enter 60000/1001.

How to undo: Switch OBS back to Common FPS Values > 60 and return the display refresh rate to 60 Hz.

OBS Canvas and Output Resolution: 1920×1080

Exact value: In OBS, go to Settings > Video. Set Base (Canvas) Resolution to 1920×1080 and Output (Scaled) Resolution to 1920×1080. Set Downscale Filter to Lanczos, 36 samples only if you are scaling another source; otherwise it has little effect.

Trade-off: Matching canvas and output prevents blur from avoidable scaling. Recording at 1440p from a 1080p capture source does not add real detail; it only creates larger files and can make compression artifacts more visible.

What causes problems: An OBS canvas set to 2560×1440 or 3840×2160 while the capture source is 1080p forces enlargement. This can soften HUD elements and make text look less crisp.

How to check: In the OBS preview, right-click the capture source and select Transform > Edit Transform. Confirm that the source is not being stretched beyond 1920×1080.

What to do: Click the source, choose Transform > Reset Transform, then use Transform > Fit to Screen with the canvas set to 1920×1080.

How to undo: Restore your prior canvas and output values in Settings > Video.

Color Settings: NV12, Rec. 709, Partial

Exact value: Open Settings > Advanced in OBS. Under Video, set Color Format to NV12, Color Space to Rec. 709, and Color Range to Partial.

Trade-off: This is the standard SDR recording combination and is broadly compatible. Full-range RGB can look correct in a fully matched workflow, but it is more likely to create crushed blacks or washed-out video when an editor, player, or upload service interprets it differently.

What causes problems: A gaming GPU set to RGB Full while the capture card or OBS expects limited-range video can shift black and white levels.

How to check: Record a short dark scene containing black UI elements and bright white text. If blacks appear gray, or shadow detail disappears into solid black, the ranges are mismatched.

What to do: In NVIDIA Control Panel, use Display > Change resolution and set the capture display’s Output color format and Output dynamic range consistently. For the recommended OBS setup, use a standard SDR output and avoid enabling HDR for the capture display.

How to undo: Return the GPU output settings to their previous format and reset OBS to the prior color values.

Recording Encoder and Quality: Hardware H.264, CQP 20

Exact value: In OBS, open Settings > Output, change Output Mode to Advanced, then open the Recording tab. Select your hardware H.264 encoder, set Rate Control to CQP or CQ, and start with a quality value of 20. Set Keyframe Interval to 2 s.

Trade-off: Lower CQP values create larger, cleaner files; higher values reduce file size but increase visible compression. Use 18 for demanding footage with fine detail, 20 as a balanced starting point, and 22 when storage is limited.

What causes problems: Using x264 software encoding on an underpowered capture PC can cause encoder lag. Using an extremely low quality value can also overwhelm disk write speed.

How to check: Record a 10-minute match segment and open View > Stats. Check for encoding lag and verify the recording drive has ample free space.

What to do: Use the GPU’s hardware encoder first. If lag persists, raise CQP from 20 to 22, lower preset quality one step, or record to an internal SSD rather than an external hard drive.

How to undo: Restore the former encoder, preset, and CQP value in Settings > Output > Recording.

By Hardware Tier

Low Tier: 1080p60 Capture Card and Basic Capture PC

Use 1920×1080 at 60 fps, SDR, NV12, Rec. 709, Partial range, and hardware H.264 at CQP 22. Record in MKV to an internal SSD. Avoid browser sources, animated overlays, multiple webcam filters, and unnecessary scene duplicates. If OBS Stats shows encoder lag, use CQP 23–24 or reduce recording to 30 fps before lowering resolution.

What causes problems: USB bandwidth sharing and weak CPUs commonly affect entry-level systems.

How to check: Connect the capture card directly to a rear motherboard USB port, not a hub, and test with other high-bandwidth USB devices disconnected.

What to do: Use a USB 3.x port, disable USB selective suspend in Control Panel > Power Options > Change advanced power settings, and keep the capture card on its own controller where possible.

How to undo: Re-enable USB selective suspend if it was previously part of your power-saving setup.

Mid Tier: 1080p60 or 1440p60 Capture Hardware

For most recording, still use 1080p60 as the final output. If the card accepts 1440p60 and you need sharper UI footage, set OBS canvas and output to 2560×1440, use HEVC or H.264 hardware encoding, and begin at CQP 20–22. Confirm that your editor handles HEVC smoothly before committing to long sessions.

What causes problems: Capturing 1440p while editing on a modest system can make timeline playback difficult.

How to check: Import a five-minute sample into your normal editor and test cutting, seeking, and exporting.

What to do: If editing stutters, create proxies or return to 1080p60 recording. Proxies preserve the original master while making the edit responsive.

How to undo: Disable proxy generation in your editor and relink the original media if needed.

High Tier: 4K60 or High-Refresh Passthrough Hardware

Use high-resolution passthrough for the gaming monitor, but choose the recording resolution based on delivery needs. For standard gameplay videos, record 1080p60 or 1440p60. Use 4K60 only when your capture card, capture-PC GPU encoder, SSD, and editing workflow have all been tested together. For 4K SDR recording, use a 3840×2160 canvas and output, hardware HEVC or AV1 where your editor supports it, and CQP 20–22 as a starting range.

What causes problems: High-refresh gaming displays may negotiate a mode the capture card cannot capture even if it can pass the signal through.

How to check: Review the card’s vendor utility and OBS source properties after changing game resolution, HDR, or refresh rate.

What to do: Create a dedicated capture display mode such as 1440p60 or 1080p60 for recording sessions while leaving your primary monitor on its preferred mode when supported.

How to undo: Select the original monitor mode in Windows display settings and remove the dedicated duplicate-display configuration.

Common Mistakes

Recording MP4 directly: The cause is convenience, but a crash can leave the file unusable. Check Settings > Output > Recording. Set Recording Format to MKV, then use File > Remux Recordings after recording to create an MP4 copy. To undo, change the recording format back to MP4, understanding the recovery risk.

Using Display Capture on the capture PC: The cause is selecting the wrong OBS source. Check the Sources dock; it should contain Video Capture Device, not Display Capture, for the game feed. Add it with Sources > + > Video Capture Device, select the capture card, and set its resolution/FPS type to Device Default or Custom: 1920×1080, 60. To undo, remove the source with the minus button.

Capturing HDR as SDR without conversion: The cause is enabling HDR on the gaming output while using an SDR OBS project. Check Windows HDR under Settings > System > Display > HDR. Disable HDR for the capture display, or build a deliberate HDR recording workflow from capture through editing. To undo, re-enable HDR after the session.

Saving recordings to a nearly full drive: The cause is overlooking file growth during long sessions. Check the target folder in Settings > Output > Recording Path and verify free space in File Explorer. Use a dedicated SSD folder such as D:\Recordings\OBS. To undo, restore the old recording path.

FAQ

Should I record at 1080p or 1440p on a dual-PC setup?

Record at 1080p60 unless you specifically need 1440p delivery, sharper interface text, or 1440p source footage for editing. A 1080p60 master is simpler and more reliable. Do not upscale a 1080p capture to 1440p in OBS; capture true 1440p only when the card accepts it and the capture PC can encode it without dropped frames.

Can I play at 1440p or 4K while recording at 1080p?

Yes, if your capture card supports the required passthrough mode or your GPU provides a compatible duplicate-display signal. Check that OBS receives 1920×1080 at 60 fps in the source properties. If the card receives a black screen, set a dedicated 1080p60 output for the capture display. Undo it by restoring the display’s original mode after recording.

Is 30 fps ever better for capture-card recording?

It is better only when storage, encoder performance, or the content type makes 60 fps unnecessary. For strategy games, tutorials, and slower footage, 1080p30 can be acceptable. For shooters, racing games, sports games, and action titles, 60 fps is the better default because it preserves motion clarity.

Why does my recording look washed out compared with the game?

The usual cause is a full-versus-partial color-range mismatch or accidental HDR-to-SDR conversion. Check OBS at Settings > Advanced > Video and use NV12, Rec. 709, Partial for SDR. Then confirm the gaming PC output to the capture display is not using an incompatible full-range RGB mode. Change one side at a time, record a short test, and restore the prior value if the image becomes worse.

Related guides