PS5 Capture Card 2026: 4K60 in OBS, 14 Steps, 40 Min

A capture card is the tax you pay to prove, in high definition, that you are bad at video games in front of strangers. Sony does not make this easy. The PS5 ships with content protection switched on by default, a USB bandwidth ceiling that quietly throttles the shiny 4K card you just bought, and a settings menu that buries the one toggle you actually need three submenus deep. None of this is printed on the box, because the box is trying to sell you something, and the truth does not fit in a starburst graphic.

This is the long version: fourteen numbered steps from a sealed carton to a verified 4K60 recording in OBS, with a rationale for every step, the encoder math nobody prints on the packaging, and a troubleshooting table for the moment the screen goes black and you start drafting a refund email. Budget roughly forty minutes if the PC is already built and you read the parts about USB ports. Skip those parts and budget an afternoon plus the aforementioned refund email. If you only need 1080p60 and want the faster, cheaper path, the 12-step 1080p60 walkthrough covers that variant in less time and on lesser hardware.

The 4K60 Reality Check

Every capture card in 2026 advertises a big number on the front of the box. That number is almost never the whole truth, and on a PS5 it is frequently the least important spec in the conversation. Before you spend a cent, you need to understand three things: what your console actually outputs, what your card actually ingests, and the precise point where those two quietly disagree. Most refunds happen because the buyer never separated those questions.

What "4K60" Actually Means on a PS5

The base PS5 outputs up to 4K at 120 Hz over HDMI 2.1, and the PS5 Pro pushes that envelope further, with more titles targeting high frame rates and higher internal resolutions via PSSR upscaling. But most games do not render a clean, native 3840x2160 at a locked 60 frames per second. They lean on dynamic resolution scaling, checkerboard reconstruction, or machine-learning upscaling, and then the console emits a 4K container signal regardless of what was actually drawn underneath. Your capture card sees the output signal, not the render target. So "4K60 capture" only means the card can ingest and digitize a 3840x2160 60 Hz stream. It says nothing about whether the game beneath it was ever truly 4K, and it never will.

Capture Resolution Is Not Passthrough Resolution

This is the distinction that drives the most returns, so read it twice. Passthrough is the HDMI signal the card forwards to your TV or monitor so you can see the game with your own eyes. Capture is the signal the card digitizes and ships over USB to the PC. They are routinely different numbers. The Razer Ripsaw HD passes 4K60 through to your display but captures only 1080p60. The Elgato HD60 X does 4K60 HDR and VRR passthrough yet, again, captures at 1080p60. The BlueAVS 4K60 captures 4K60 but via MJPEG compression while passing through 1080p at up to 240 Hz. A card that screams "4K" in giant letters and admits "1080p60 capture" in six-point gray text on the back is a 1080p capture card with a nice passthrough. Both numbers matter; the small one decides your recording.

What This Tutorial Delivers (and What It Won't)

This guide gets you the highest capture resolution your specific card-and-USB combination can sustain, configured in OBS Studio, with the recording verified by hand rather than taken on faith. It will not turn a 1080p60 capture card into a 4K60 one, because no software in the universe can manufacture pixels the hardware never digitized, and it will not help you strip protection from licensed video, which is a separate activity with a separate legal footnote we get to below. If native 4K60 capture is genuinely the goal, you need one of a short list of cards, and the next two sections name them.

Prerequisites and Versions

Skipping the versions here is how people end up in the troubleshooting table later. Pin every one of these down before you touch a cable, because a wrong version or a wrong cable produces symptoms that look exactly like a dead card.

Software Versions

The headline dependency is OBS Studio v40.2, released in May 2026, which added native UVC (USB Video Class) support. In practice that means a UVC-compliant capture card now appears as an ordinary camera source with no vendor driver installed at all, which is a meaningful change after years of bundled capture utilities fighting OBS for exclusive control of the device. Install it from the official build; rolling back to an older release is rarely worth the lost UVC handling. The release notes and source live on the OBS Studio GitHub repository, and the settings reference is in the OBS Knowledge Base.

You also want a recent FFmpeg (the 7.x series or newer) for listing device formats and verifying recordings from the command line; the binaries and reference are at the FFmpeg documentation. Finally, current GPU drivers: NVIDIA's 56x-series or newer for NVENC, AMD Adrenalin for AMF, or Intel Arc/iGPU drivers for QuickSync. If your card is not UVC, you still need its vendor utility (Elgato's 4K Capture Utility, AVerMedia's Gaming Utility) for firmware flashing even if you never record a single frame through it.

Hardware Requirements

Two cables, and they matter more than the card's marketing copy. For 4K120 or VRR passthrough you need genuine HDMI 2.1 cables on both the PS5-to-card and card-to-display links; HDMI 2.0 tops out at 4K60 and will silently cap your passthrough without ever telling you. On the USB side, USB 3.2 Gen 1 (5 Gbps) is the absolute floor and Gen 2 (10 Gbps) is what you actually need for uncompressed 4K60, for reasons the encoding section works out with arithmetic. The cable and the port both have to be Gen 2; a Gen 2 device in a Gen 1 port silently negotiates down to 5 Gbps, and you will never see an error, only the symptom.

You also need a display that accepts the passthrough at the resolution and refresh you intend to play at, and, obviously, the card itself. For HDMI 2.1 specifically, the standard the PS5 Pro leans on, Polygon's review notes that of the current crop, realistically only the Asus TUF CU4K30 and the upcoming Elgato 4K X fully meet it. Everything else either caps passthrough or fakes the high-refresh modes.

The PC That Can Actually Encode 4K60

The encoding load is the part buyers consistently underestimate. Software x264 encoding at 4K60 in real time will pin a consumer CPU at 100% and stuff your OBS log with skipped-frame warnings. Use a hardware encoder instead: NVIDIA NVENC (RTX 20-series and newer, with AV1 on the 40 and 50 series), AMD AMF, or Intel QuickSync. Disk is the other quiet requirement; 4K60 at a sane quality level writes roughly 0.3 to 0.6 GB per minute, so an NVMe SSD is strongly preferred, and a spinning rust drive will eventually drop frames mid-write under sustained load. Sixteen gigabytes of RAM is a sensible floor, more if you also run the game and a browser full of chat on the same machine.

Picking a Card in 2026

IGN's 2026 capture-card guide puts the field at six headline options spanning roughly $60 to $250. The table below is the honest version, with capture resolution and passthrough resolution as separate columns, because that gap is exactly where the marketing hides the part you would object to.

The 4K60-Capable Cards

If true 4K60 capture is non-negotiable, the list is short. The Asus TUF CU4K30 at $210 captures 4K60, passes through up to 2K144, and carries full HDMI 2.1, which makes it the default recommendation for PS5 Pro owners who want to archive at native resolution and still play at high refresh on a 2K monitor. The Elgato 4K X, announced in Q1 2026 and projected around $250 with pricing still unconfirmed, targets the same bracket with 4K60 over HDMI 2.1 and Elgato's traditionally clean OBS path. The wildcard is the BlueAVS 4K60 at under $60, which does genuinely hit 4K60, but only via MJPEG, a compromise the budget-traps subsection below refuses to let slide.

The 1440p and 1080p Workhorses

Most streamers do not need 4K capture and should not pay for it. The Elgato HD60 X remains the safe pick: 1080p60 capture, clean OBS integration, and 4K60 HDR/VRR passthrough so your own gameplay still looks correct on your monitor while you record the downscale. The AVerMedia GC513 Live Gamer Portable 2 Plus, also sold as the rebranded EVGA XR1 Pro, captures 1440p60 and 4K30, needs no external power, and offers low-latency preview, which makes it one of the few portable units that keep pace with PS5 Pro frame rates. The AVerMedia Live Gamer Mini (~$147) covers the same 1440p60/4K30 envelope over plain USB 3.0 plug-and-play. The NearStream CCD30 (~$60) is the budget all-rounder, built for PS5 and the Nintendo Switch 2 with OBS support out of the box. The Razer Ripsaw HD (1080p60 capture, 4K60 passthrough) and the Fifine v3 Ampligame (4K30, Twitch-via-OBS) round out the value end.

The Budget Traps (Read the Codec, Not the Box)

Here is the catch on the sub-$60 "4K60" cards: that number almost always means MJPEG. Motion-JPEG compresses every frame independently as a JPEG, which is how 4K60 squeezes through a 5 Gbps USB pipe, but it pays for that with 4:2:0 color and blocking artifacts on high-contrast edges, which is to say the text, HUDs, and health bars you most want legible. Ars Technica's June 2026 streaming-hardware piece frames it correctly: NV12 and MJPEG format flexibility is the real differentiator between cards, not the headline resolution. The BlueAVS is at least honest about being an MJPEG card. Treat MJPEG 4K60 as a compromise that exists because of bandwidth, not as a free win over a 1080p NV12 card.

HDCP: The Switch and the Law

If you do exactly one thing before plugging in a capture card, do this one. The overwhelming majority of "my new card doesn't work" posts are this single setting, and the second-most-common is a USB port. Neither is a hardware fault.

Why the PS5 Blocks Capture by Default

HDCP, High-bandwidth Digital Content Protection, is an encryption handshake negotiated across the HDMI link itself. The PS5 enables it by default so that protected streaming apps such as Netflix and Disney+ will hand over their licensed video. The side effect is that a third-party capture card without the right keys sees an encrypted stream it cannot decode, and you get a black screen, a green screen, or an explicit "HDCP error" overlay for your trouble. The card is functioning perfectly. It is simply being told, cryptographically, to mind its own business, and it obeys.

Disabling It (Step Zero)

The toggle, confirmed for 2025-era firmware and unchanged since, lives at Settings → System → HDMI → Enable HDCP. Switch it off. Game footage will now pass cleanly to the card. The trade-off is that protected streaming apps refuse to play video until you switch it back on, so if you double as a Netflix box, expect to flip this depending on the task.

# PS5 - the one toggle that matters
Settings  ->  System  ->  HDMI  ->  Enable HDCP  ->  OFF

# Trade-off: protected streaming apps (Netflix, etc.)
# refuse to play video until you switch HDCP back ON.

The Legal Line — Lore and Section 1201

Now the part The Machine cannot resist. Lore first: this used to be much worse. The PS3 wrapped essentially everything in HDCP, and capturing console gameplay in the early 2010s meant buying an HDMI splitter, an HDFury or similar, whose entire purpose was to strip the protection so a card could see the signal at all. Sony eventually shipped an official toggle, which is the very switch you just flipped. Law second: turning HDCP off to record your own gameplay is sanctioned. Sony built the switch, and your gameplay is not the content HDCP exists to protect. Pointing a stripper at HDCP-protected video, a 4K Blu-ray or a streaming service, to capture it, is circumvention of an access control under DMCA Section 1201, the part of the statute that is famously indifferent to your reasons. The capture card cannot tell the two situations apart. The statute can. Stay on the gameplay side of that line and nobody has anything to discuss.

The 14 Steps to 4K60 Capture in OBS

Fourteen steps. Each one has a reason, and the reasons are the difference between this working on the first attempt and you scrolling to the troubleshooting table. Do them in order, because several later steps assume earlier ones are already done.

Steps 1–5: Cabling, Firmware, and the PS5

1. Confirm your USB port speed. Uncompressed 4K60 needs roughly 6 Gbps (math in the next section), which exceeds USB 3.2 Gen 1's 5 Gbps, so a 4K60 card belongs in a 10 Gbps Gen 2 port or it drops to a lower mode or forces MJPEG. Verify the port before you commit to it.

   # Linux - USB tree with link speeds
   # 5000M = USB 3.2 Gen 1, 10000M = Gen 2
   lsusb -t
   
   # Expected, capture card on a 10 Gbps port:
   # /:  Bus 04.Port 1: Dev 1, Class=root_hub, 10000M
   #     |__ Port 1: Dev 2, If 0, Class=Video, Driver=uvcvideo, 10000M

   On Windows, use Device Manager, View, Devices by connection, or check for the "USB 3.x (10 Gbps)" label in the USB controller tree.
2. Cable the chain in the right order. PS5 HDMI OUT to card HDMI IN; card HDMI OUT to your display; card USB to the PC. Wire passthrough first so you can still play even if capture never initializes. A black OBS preview alongside a working TV is a software problem, not a dead card, and knowing that up front saves the refund email.
3. Update the card's firmware. 4K60 modes, VRR, and correct HDR handling routinely ship as post-launch firmware updates across both Elgato and AVerMedia. Run the vendor utility once, flash the latest firmware, then fully close it so it does not hold the device when OBS comes asking for exclusive access.
4. Set the PS5 video output. Settings → Screen and Video → Video Output. Match the card's ceiling, because there is no value in sending 4K120 to a card that caps capture at 4K60.

   # PS5 - Screen and Video / Video Output
   Resolution ............ 2160p (Automatic)
   HDR ................... On When Supported   # see HDR pitfall
   Deep Color Output ..... Automatic
   120 Hz Output ......... Automatic           # PS5 Pro / VRR titles
   VRR ................... Automatic

5. Disable HDCP. Settings → System → HDMI → Enable HDCP → OFF. Without this you get a black capture next to a perfectly working TV, and you will spend an hour blaming OBS for Sony's DRM. See the HDCP section above for the legal caveat before you do anything more exotic.

Steps 6–10: OBS Source, Format, and Resolution

6. Update OBS to v40.2. Native UVC support means a UVC card shows up as a camera source with no driver installed, which is fewer moving parts and fewer conflicts. If you are migrating off a vendor app or off Twitch Studio, the OBS migration walkthrough covers the scene and profile basics this guide assumes you already have.
7. Add a Video Capture Device source. In a scene, click the plus, choose Video Capture Device, and select your card. This is the input that everything downstream hangs off, so name it something you will recognize at 2 a.m.
8. Force Resolution/FPS Type to Custom. OBS defaults to "Device Default," which is frequently a conservative 1080p30. Set Custom, then choose 3840x2160 at 60, or your card's true maximum. If 4K60 is not even offered in the dropdown, your USB port or cable is the suspect; go back to step 1 before changing anything else.
9. Choose the Video Format deliberately. NV12 (uncompressed 4:2:0) on a 10 Gbps port; MJPEG only if the card requires it for 4K60 on a 5 Gbps link; YUY2 (4:2:2) only when chroma fidelity outranks resolution. Confirm what the card actually exposes rather than guessing.

   # Linux - list the formats the card advertises
   ffmpeg -f v4l2 -list_formats all -i /dev/video0
   # [video4linux2] Raw       : nv12  : 3840x2160 60 fps
   # [video4linux2] Compressed: mjpeg : 3840x2160 60 fps
   # [video4linux2] Raw       : yuyv  : 1920x1080 60 fps
   
   # Windows - DirectShow device + its formats
   ffmpeg -list_devices true -f dshow -i dummy
   ffmpeg -f dshow -list_options true -i video="Game Capture 4K X"

10. Match the OBS canvas to the capture. Settings → Video, set Base (Canvas) and Output (Scaled) both to 3840x2160, Common FPS Value 60. If the canvas is smaller than the source, OBS downscales and your "4K" recording is upscaled mush wearing a 4K filename.

Steps 11–14: Encoder, Bitrate, Recording, Verify

11. Switch Output Mode to Advanced. Settings → Output → Output Mode → Advanced. Simple mode hides rate control, profile, and multipass, which are precisely the knobs that decide whether 4K60 looks good or merely large.
12. Pick a hardware encoder and CQP. Set the recording encoder to NVIDIA NVENC HEVC, or AV1 on RTX 40/50. Rate Control CQP, CQ around 19, Preset P5, Tuning High Quality, Profile main10 for 10-bit. HEVC roughly halves the bitrate of H.264 at 4K for equal quality, and the dedicated ASIC keeps your CPU free for the game.

    # OBS > Output (Advanced) > Recording
    Video Encoder ...... NVIDIA NVENC HEVC   # AV1 on RTX 40/50
    Rate Control ....... CQP
    CQ Level ........... 19      # 16 ~ near-lossless, 23 ~ smaller
    Preset ............. P5: Slow (Good Quality)
    Tuning ............. High Quality
    Multipass .......... Two Passes (Quarter Resolution)
    Profile ............ main10  # 10-bit, needed for HDR
    Max B-frames ....... 2

13. Record to .mkv on an NVMe drive. Matroska survives a crash without corrupting the entire file the way an interrupted .mp4 can, and you remux to .mp4 afterward for free. At 4K60 you write hundreds of megabytes a minute, so point the recording path at fast storage and check the free space first.
14. Record 30 seconds and verify by hand. Trust nothing the GUI tells you. Capture a short clip, then confirm the resolution, codec, and frame rate actually landed where you set them.

    ffprobe -v error -select_streams v:0 \
      -show_entries stream=codec_name,width,height,r_frame_rate,pix_fmt \
      -of default=noprint_wrappers=1 ~/Videos/ps5-test.mkv
    
    # Expected output:
    codec_name=hevc
    width=3840
    height=2160
    r_frame_rate=60/1
    pix_fmt=yuv420p10le

Codecs and Encoders: NV12, MJPEG, NVENC

This is the section that explains the symptoms in the troubleshooting table before you ever experience them. Two formats are in play and people constantly conflate them: the capture format, which is how the card moves pixels over USB, and the output encoder, which is how OBS compresses the recording or stream. They are different decisions with different bottlenecks, and confusing them is how you end up with a fast card and a smeary file.

Capture Format — NV12 vs MJPEG vs YUY2

The capture format is a bandwidth negotiation, full stop. NV12 is YUV 4:2:0 at 12 bits per pixel, uncompressed. Do the arithmetic for 4K60: 3840 times 2160 times 1.5 bytes is 12,441,600 bytes per frame, times 60 frames is about 746 MB/s, which is roughly 5.97 Gbps. That is more than USB 3.2 Gen 1's 5 Gbps ceiling, which is the entire reason a 4K60 NV12 card wants a 10 Gbps Gen 2 port. MJPEG sidesteps the ceiling by compressing each frame into a JPEG, fitting 4K60 inside 5 Gbps, but it pays in 4:2:0 color and blocking on sharp edges. YUY2 is 4:2:2 at 16 bits per pixel, more bandwidth than NV12, reserved for chroma-critical work at lower resolution. As Ars Technica put it, the cards that lead are the ones flexible across NV12 and MJPEG, because that flexibility is what lets you trade quality for bandwidth on purpose instead of by accident.

Output Encoder — NVENC vs x264 vs QSV/AMF

The output encoder is a separate choice with a separate failure mode. x264 runs on the CPU and gives the best quality per bitrate at slow presets, and it will not survive 4K60 in real time on a normal desktop, dropping frames the instant the per-frame encode time exceeds the 16.67 ms frame interval at 60 fps. NVENC offloads to a dedicated block on the GPU; HEVC there roughly halves the bitrate of H.264 for equal quality, and AV1 on RTX 40/50 improves on that again. Intel QuickSync and AMD AMF are the equivalents on their respective hardware. For anything at 4K60, use a hardware encoder; the OBS Knowledge Base documents the per-vendor settings, and FFmpeg's hardware-acceleration docs cover the same encoders from the command line if you prefer scripts to menus.

Bitrate Math for 4K60

For local recording, do not set a fixed bitrate at all. Use CQP on NVENC or CRF on x264, both of which target a quality level and let the bitrate float with the scene. A CQ of 19 on HEVC at 4K60 lands somewhere around 40 to 80 Mbps depending on motion, which is roughly 0.3 to 0.6 GB per minute, hence the NVMe requirement. For streaming, you are bound by the platform's ceiling, which for most accounts sits far below what native 4K60 actually needs, so the standard move is to record 4K60 locally while streaming a downscaled 1080p60 at a platform-legal bitrate. Trying to push native 4K60 up to a service that caps you well under its bandwidth requirement just produces a smeary, macroblocked apology for a stream.

Six Pitfalls That Ruin the Recording

Six ways this goes wrong, in rough order of how often they actually happen, each with the fix that ends it.

Bandwidth and HDCP (1–2)

1. 4K card in a USB 3.0 port. The single most common waste of money in this hobby. The card negotiates down to 1080p60, or quietly forces MJPEG, and you conclude the card is defective and start a return. Fix: move it to a 10 Gbps Gen 2 port with a Gen 2 cable, and confirm with lsusb -t reporting 10000M on the device line.

2. HDCP left on. Black or green capture, flawless picture on the TV. Fix: Settings → System → HDMI → Enable HDCP → OFF. If you used a streaming app recently, this is almost certainly the culprit, because the app turned protection back on behind your back.

Encoding and Sync (3–4)

3. x264 at 4K60. Stutter, dropped frames, and an OBS log full of "skipped frames due to encoding lag" because the CPU cannot finish each frame inside 16.67 ms. Fix: switch the recording encoder to NVENC HEVC and the problem simply evaporates, often dropping encode time to single-digit milliseconds.

4. Audio drifts out of sync over time. Usually the PS5 is sending bitstream audio whose clock disagrees with the capture's. Fix: set the PS5 to Linear PCM, set OBS audio to 48 kHz, and if a fixed offset remains, dial it in with the per-source sync offset. If the desync arrives paired with other flaky PS5 behavior, a PS5 cache clear is a cheap thing to rule out before you blame the card.

Color and Compression (5–6)

5. HDR captured as SDR. Washed-out, gray, lifeless footage, because the card grabbed an HDR (Rec. 2100 PQ) signal and OBS treated it as SDR Rec. 709. Fix: either disable HDR on the PS5 for capture, or keep a full 10-bit pipeline (main10 profile, p010 pixel format) and apply a tone-map or LUT for SDR delivery. Half-measures here always look wrong, every time.

6. Believing MJPEG 4K60 equals NV12 4K60. It does not, and no amount of wishing changes the codec. MJPEG is compressed 4:2:0 and goes visibly soft on text and HUD elements. Fix: if fidelity matters, use NV12 on a 10 Gbps card and accept that the honest sub-$60 "4K60" cards are making a bandwidth compromise rather than handing you a free upgrade.

Troubleshooting Table

The fast index. Match the symptom, apply the fix, get back to losing at video games on camera.

Signal and Resolution Problems

The top of the table is signal integrity: black screens, capped resolution, missing high-refresh modes. These are almost always HDCP, USB bandwidth, or an HDMI 2.0 cable standing in where an HDMI 2.1 one was needed. None of them are the card being broken, which is simultaneously the good news and the most annoying news, because it means the fix is free and you already owned the problem.

Performance and Encoding Problems

The lower rows are performance: dropped frames, oversized files, desynced audio. These live in OBS settings, specifically encoder choice, rate control, and audio sample rate, not in the hardware. If a fix down here requires touching the PS5 at all, it is the audio format, never the capture path.

Reading the OBS Log

OBS writes everything to a log under Help → Log Files. A healthy capture device init and a recording start look like the block below; the skipped-frames line at the bottom is the one you are hunting for whenever playback stutters.

# OBS  ->  Help  ->  Log Files  (healthy capture init)
[DShow Device 'Game Capture 4K X'] settings updated:
    video device: Elgato 4K X
    resolution: 3840x2160
    fps: 60.00 (interval: 166667)
    format: NV12
    color space: 709 (limited range)
==== Recording Start ==============================
[NVENC encoder: 'recording_h265'] avg. encode time: 3.1 ms

# The line you are hunting when playback stutters:
Output 'adv_file_output': Number of skipped frames
  due to encoding lag: 412 (3.7%)

Advanced Tips

Once the baseline works, these are the upgrades that actually move the needle rather than the ones that just spend money.

Replay Buffer and Instant Clips

Enable the Replay Buffer in Output settings, bind it to a hotkey, and OBS keeps the last N seconds in memory so you can save a clip after something good happens instead of recording an entire session and scrubbing it later. NVENC makes this nearly free in CPU terms, so there is no real argument against running it constantly. It is the single highest-value setting most people never turn on.

FFmpeg Direct Capture (No OBS)

For scripted or headless recording, such as a dedicated capture box or an automated archive, you can skip OBS entirely and pull straight from the card with FFmpeg. The capture-device recipes in the FFmpeg capture wiki generalize cleanly to capture cards.

# Linux - capture card straight to 10-bit HEVC, no OBS
ffmpeg -f v4l2 -input_format nv12 -video_size 3840x2160 -framerate 60 \
  -i /dev/video0 \
  -f alsa -i hw:CARD=Capture \
  -c:v hevc_nvenc -preset p5 -tune hq -rc vbr -cq 19 -b:v 0 \
  -profile:v main10 -pix_fmt p010le \
  -c:a aac -b:a 256k \
  ~/Videos/ps5-session.mkv

# Windows uses: -f dshow -i video="...":audio="..."  (no v4l2/alsa)

VRR, HDR Tone-Mapping, and Dual-PC

VRR passthrough requires an HDMI 2.1 card, the CU4K30 or the Elgato 4K X; the capture stream itself is always fixed-rate, so VRR is purely about how the game feels on your own display and never about what gets recorded. For HDR, commit to a full 10-bit pipeline (p010, main10) or tone-map down to SDR with a LUT, but never let OBS guess at the conversion. And the professional move for zero gaming-side overhead is a two-PC rig: the gaming PC outputs to a capture card living inside a second PC that runs OBS, so encoding never steals a frame from the game. If you would rather skip the capture card entirely for a lightweight setup, PS Remote Play streams the console to a PC over the network, though it tops out at a lower resolution and adds latency you will feel in fast games.

The Complete Working Configuration

Everything above, condensed into the three blocks you can copy. Set these once, verify once, and then stop thinking about the card forever, which is the entire goal of owning one.

The PS5-Side Checklist

# === PS5 - capture checklist ===
System / HDMI / Enable HDCP ............. OFF
Screen and Video / Video Output
  Resolution ........................... 2160p (Automatic)
  HDR .................................. On When Supported
  Deep Color Output ................... Automatic
  120 Hz Output ....................... Automatic
  VRR ................................. Automatic
Sound / Audio Output
  HDMI Device Type .................... TV
  Audio Format (Priority) ............ Linear PCM   # avoids desync

OBS — Full Settings Block

# === OBS Studio v40.2 - PS5 4K60 capture profile ===

[Video]
Base (Canvas) Resolution ...... 3840x2160
Output (Scaled) Resolution .... 3840x2160
Downscale Filter .............. Lanczos   # only if you scale
Common FPS Value .............. 60

[Source: Video Capture Device]
Device ........................ <your card>   # UVC, no driver on v40.2
Resolution/FPS Type ........... Custom
Resolution .................... 3840x2160
FPS ........................... 60
Video Format .................. NV12   # MJPEG only if USB 3.0 / card requires
Color Space ................... Rec. 709   # Rec. 2100 (PQ) for 10-bit HDR
Color Range ................... Limited
Buffering ..................... Disable

[Output > Recording (Advanced)]
Encoder ....................... NVIDIA NVENC HEVC   # AV1 on RTX 40/50
Rate Control .................. CQP
CQ Level ...................... 19
Preset ........................ P5: Slow (Good Quality)
Tuning ........................ High Quality
Multipass ..................... Two Passes (Quarter Res)
Profile ....................... main10
Recording Format .............. Matroska (.mkv)
Recording Path ................ NVMe SSD

[Audio]
Sample Rate ................... 48 kHz
Channels ...................... Stereo

Verify, Then Forget It

Record a final 30-second clip, run the ffprobe check from step 14 one more time, and if the numbers match, remux to a shareable .mp4 without re-encoding a single frame.

ffmpeg -i ps5-test.mkv -c copy ps5-test.mp4

That is the whole job. The card is a transparent pipe now: HDCP off, the right USB port, NV12 where bandwidth allows, a hardware encoder doing the heavy lifting, and a recording you verified instead of assumed. The hard part was never the forty minutes of setup. It was knowing which of the box's big numbers to ignore, and you now do. For deeper work on scenes, filters, and streaming output, OBS's own documentation is the place to go; everything else in this guide you already own.