PS5 Capture Card 2026: 12 Steps to 1080p60 in 30 Min

The PlayStation 5 has a Share button. It has worked since launch, it records the last fifteen minutes to an hour in the background depending on how you set it, and for a large fraction of the people who think they need a capture card, it is enough. Start there. If all you want is a clip for a group chat or a vertical feed, the console already does it, and no two-hundred-dollar box is going to improve a thirty-second highlight.

You are still reading, which means you want something the Share button cannot give you: a clean 1080p60 feed into OBS, a local recording that is not strangled by the console's internal bitrate ceiling, party chat sitting in its own audio channel beside the game, or a second machine doing the encoding so the PS5 spends every watt on the frame and none on compression. That is what a capture card is for. Strip the marketing away and it is an analog-to-digital converter with a digital-rights-management problem bolted to the front. Once you understand the DRM problem — High-bandwidth Digital Content Protection, a handshake designed in the early 2000s, master-keyed and broken in public by 2010, and still sitting in your signal path in 2026 — the rest is plumbing.

This is the plumbing. Twelve numbered steps, roughly thirty minutes if your cables are certified and your USB ports are the real 5 Gbps kind, and a complete copy-paste configuration at the end. We will use the Elgato HD60 X as the reference card throughout, because it is the one most people already own and the one TechRadar still rates the best overall PS5 capture card in 2026. Every step generalizes to the AverMedia Live Gamer Ultra 2.1, an internal PCIe card, or the fifty-dollar Genki thumb drive you bought on a whim. If you do not own a card yet, skip ahead to the section on choosing one and come back.

Prerequisites: Hardware, Software, and the Cable Tax

A capture card is the cheapest part of a capture setup. The expensive parts are the host machine that encodes the signal, the USB controller that carries it, and the cables that refuse to corrupt it. Get those three wrong and the best card on the market will hand you dropped frames and grey blacks while you blame the wrong component for an afternoon.

Hardware you actually need

• A capture card. The reference here is the Elgato HD60 X at $199.99 (about £189): 1080p60 capture, 4K60 passthrough, HDR and VRR passthrough, and — the part that matters more than the spec sheet admits — a 3.5 mm aux input for party chat.
• A real USB 3.0 port. External cards push a high-bandwidth video stream and need the full 5 Gbps of USB 3.0 (USB 3.2 Gen 1). A USB 2.0 port at 480 Mbps will not carry 1080p60 cleanly, and it will drop frames in a pattern that looks exactly like a software bug but is actually a bandwidth wall. Plug into a port on the motherboard's rear I/O, not a front-panel header daisy-chained through a case, and never into an unpowered hub.
• A CPU or GPU that can encode. For x264 software encoding at 1080p60, budget a modern 6-core CPU at minimum, 8 cores if you also game on the same machine. For hardware encoding, any NVIDIA card from the GTX 16-series up has NVENC; AMD has AMF; Intel Arc and recent iGPUs have Quick Sync. Hardware encoding is the correct default in 2026 — it is free performance you already paid for and never used.
• 16 GB of RAM and an SSD with headroom. A 1080p60 local recording at a sane bitrate of 40–60 Mbps writes roughly 18–27 GB per hour. Plan storage accordingly; a disk that fills mid-stream corrupts the file you were recording, and there is no undo for that.

Software and driver versions

• OBS Studio 30.2 or newer. The 31.x branch is current in 2026 and the one to install. OBS is free, open-source, and the reference tool for everything below; if you are migrating off a vendor streaming app, our walkthrough on rebuilding a stream in OBS covers the scene and source scaffolding this guide assumes you already have in place.
• FFmpeg 6.0 or newer, if you intend to script recordings from the command line instead of clicking a button. The 7.x series is fine. This is optional, but it is how you get bit-for-bit control over the output file.
• The vendor utility, latest build. For Elgato that is the 4K Capture Utility plus Camera Hub for firmware; for AverMedia it is RECentral or the Live Streamer suite. You do not have to stream from these, but you install them because they carry the firmware updater, and stale firmware is responsible for roughly a third of the my-card-stopped-showing-up reports on every forum.
• A supported operating system. Windows 10 22H2 or Windows 11, macOS 13 Ventura or newer, or a Linux kernel new enough for UVC video (any 5.x or 6.x in practice). On Linux the HD60 X appears as a standard UVC device with no proprietary driver, which is the entire reason it is the card I recommend to people who refuse to run Windows.

Cables, HDCP, and the tax on doing this cheaply

The PS5 outputs over HDMI 2.1 and can drive 4K120 and 8K. To pass any of that through the card to your television, every cable in the chain has to be a certified Ultra High Speed HDMI cable rated for 48 Gbps. The unlabeled cable that came with a soundbar in 2017 is not it, and the failure mode is not a clean error message — it is sparkles, a pink or green tint, or an intermittent black screen you will waste an hour blaming on the card. Buy certified, keep cable runs under two metres, and the problem simply evaporates.

Then there is HDCP. The PS5 negotiates HDCP 2.3 on its HDMI output by default. Sony, to its credit, leaves game content unencrypted so the Share button and capture cards both work — but the system UI and the media apps (Netflix, the 4K Blu-ray player, Disney+) are protected, and pointing a capture card at them produces a lawful, deliberate black screen. That is not a malfunction. That is the Digital Millennium Copyright Act expressed as a missing picture. There is a toggle for it, we will reach it at step 8, and no, you cannot use that toggle to capture protected video no matter how much the situation seems to call for it.

How a PS5 Capture Card Actually Works

Before you connect anything, understand the two jobs the card is doing at the same time, because nearly every setup mistake people make comes from quietly conflating them.

Passthrough and capture are two different resolutions

A capture card sits between the PS5 and your display. The signal arrives on HDMI IN from the console, and the card does two things with it simultaneously: it forwards a copy out of HDMI OUT to your television, which is called passthrough, and it digitizes a second copy and sends it over USB to your PC, which is the capture. These two paths can run at different resolutions and refresh rates, and on most cards they deliberately do.

The Elgato HD60 X is the clean example. It passes 4K60, with HDR and VRR, straight through to your TV untouched, so the person holding the controller sees a full 4K picture, while it captures 1080p60 to the PC. You are not recording in 4K. You are playing in 4K and recording in 1080p, and Elgato's own documentation has verified since 2024, and reaffirmed for 2026, that this split imposes no slowdown and no visual penalty on the gameplay side. The recording is the compromise; the game is not.

The AverMedia Live Gamer Ultra 2.1 pushes the decoupling further. It will let you play at 4K120 while recording at 4K60 — the play and record paths are genuinely independent — which is a trick the Elgato cards structurally cannot perform. If your single priority is the smoothest possible game feel while still banking a high-resolution recording, that asymmetry is the entire argument for the AverMedia over the Elgato.

The HDMI 2.1 capture ceiling nobody puts on the box

Here is the fact the spec sheets bury under headline numbers: as of 2026, no PS5 capture card captures 4K at 120 Hz. Not the HD60 X, not the Ultra 2.1, none of them. The reason is silicon. Capturing 4K120 requires an HDMI 2.1 capture pipeline, and the capture-side chips in current consumer cards are HDMI 2.0. They can pass through 4K120 to your TV — the passthrough path is essentially a wire with a repeater — but the digitizing path tops out at 4K60, or trades resolution for refresh below that.

So when a card advertises 4K144, read it like a lawyer. The AverMedia Ultra 2.1 records up to 4K144 from sources that feed it that way, but its PS5-relevant passthrough caps at 2K (1440p) at 144 Hz or 1080p at 240 Hz, and its HDR capture sits at 4K60. The 144 is a headline, not a PS5 capture number. The PS5's HDMI 2.1 output can drive 4K120 natively — part of the raw output advantage we picked apart in the PS5 versus Series X teraflops breakdown — but the card in front of it is the bottleneck, and anyone selling you a sub-$300 box that captures 4K120 from the PS5 is selling you the passthrough spec and hoping you do not read this paragraph.

Internal PCIe versus external USB

Cards come in two body types. External cards — the HD60 X, the HD60 S, the Genki ShadowCast, the Nearstream CCD30 — connect over USB, usually USB 3.0 or, for the newer ones like the CCD30, USB 3.2 Gen 2. They are portable, they require no case to be opened, and they carry slightly higher latency on the capture path because the signal makes a round trip over USB before your software ever sees it. For ninety-nine percent of streamers that latency is invisible, because you play off the passthrough television, not the capture preview.

Internal cards — the Elgato Game Capture 4K Pro, the AverMedia GC573 Live Gamer 4K — drop into a PCIe slot on the motherboard. The 4K Pro launched in 2025 with 8K passthrough as futureproofing and the specific selling point of eliminating the USB-C cable clutter of an external rig; the GC573 is the long-running PCIe workhorse aimed at serious streamers in 2026. PCIe gives you lower latency and steadier throughput than USB because the card talks straight to the system bus with no external controller in between. The cost is that you need a desktop with a free slot, which rules it out for laptop and console-only setups. If you stream from a desktop and you do this for a living, internal is the right call; for everyone else, external is fine and the latency difference is a rounding error.

Picking the Right Card for a PS5 in 2026

Four cards cover almost every real use case. The rest of the market is noise, rebadges, and the occasional thumb drive that punches above its weight.

Elgato HD60 X — the one to buy unless you have a reason not to

$199.99, about £189. 1080p60 capture, 4K60 HDR and VRR passthrough, a 3.5 mm aux input for party chat, and broad plug-and-play support across Windows, macOS, and Linux. It is the default for the same reason the Honda Civic is the default: it does the common thing correctly, cheaply, and without drama. Elgato's own PS5 capture guide and TechRadar both land on it as the baseline, and nothing in this tutorial will be harder than it needs to be because you chose it. The 3.5 mm port deserves a specific mention: it is how you record party chat alongside game audio without a second hardware mixer, and it is exactly the feature the cheaper cards strip out to hit their price.

AverMedia Live Gamer Ultra 2.1 — for high-refresh and decoupled capture

Released in early 2025, the Ultra 2.1 is the best external card for high-refresh PS5 streaming. It is a plug-in device on an HDMI 2.0 capture pipeline, but it supports 4K60 HDR capture, VRR passthrough up to 1440p at 144 Hz or 1080p at 240 Hz, and recording up to 4K144 from sources that supply it. Its one genuinely unique trick, the one covered above, is letting you play at 4K120 while recording at 4K60 — the Elgato cards cannot decouple play and record resolution like that. Buy it if you run a high-refresh display and refuse to compromise the game feel just to get a recording.

Budget, internal, and everything else

At the bottom of the price ladder, the Genki ShadowCast is a thumb-drive-sized device that takes HDMI in and hands 1080p60 out over USB-C. It has no passthrough, no aux port, and no pretensions, and for a budget-conscious streamer in 2026 it is a genuinely sane fifty-dollar entry point. One rung up, the Nearstream CCD30 runs a USB 3.2 Gen 2 interface, captures 1080p60 HDR, and passes through 4K144 with HDR and VRR — more passthrough headroom than the HD60 X for a high-refresh setup that still only needs a 1080p recording. And if you have a desktop and a budget, the internal cards — Elgato's 4K Pro, AverMedia's GC573 — are the professional answer, trading portability for lower latency and a tidier desk. Here is the field at a glance:

PS5 Capture Card Setup in 12 Steps

Twelve steps, in order, each with the reason it exists, because a step without a rationale is a step you will skip and then regret. Do them in sequence. The order is not arbitrary; the HDMI handshake is negotiated at power-on, and several of these steps exist purely to make that handshake go cleanly the first time.

The twelve-step sequence

1. Power everything down first. PS5 off, PC off, capture card unplugged, both HDMI cables and the USB cable in hand. The HDMI handshake — EDID and HDCP — is negotiated when devices power on. Hot-plugging into a live chain is the single most common cause of a one-time black screen, and starting cold removes the variable entirely.
2. Connect the PS5's HDMI OUT to the card's HDMI IN. The labels trip people up constantly: IN is the source side, the side facing the console. A reversed cable yields no signal LED and sends you on a fruitless cable-swapping expedition. The card has to receive before it can forward.
3. Connect the card's HDMI OUT to your TV or monitor. This passthrough output is the picture you actually play on, and it carries near-zero latency. You never, ever play off the PC capture preview — that path has buffering and encode delay baked in. The TV is the game; the PC is the recorder.
4. Connect the card to the PC over USB 3.0, using the included cable, into a rear motherboard port. Bandwidth is the reason. The bundled cable is rated for the job; a random drawer cable may be wired to USB 2.0 spec even if the plug looks identical, and that halves your usable throughput.
5. Power on in order: TV first, then PS5, then PC. Handshake order matters. The display needs to assert its EDID — the data block that says what resolutions it accepts — before the console downstream of it negotiates an output mode through the card. Power the chain from the screen backward.
6. On the PS5, open Settings > Screen and Video > Video Output and set Resolution to Automatic. Automatic makes the console read the passthrough EDID, which the card limits to, say, 4K60, and pick the best mode the whole chain can actually carry. Force a mode the card cannot pass and you get a black screen and a panic you did not need.
7. Set RGB Range to Limited, and write down that you did. The PS5 default is Limited (the 16–235 video range). OBS has to match it exactly, or your blacks turn grey and your whites clip. This one mismatch is behind the overwhelming majority of washed-out-capture complaints, and it is a thirty-second fix once you know to look.
8. Open Settings > System > HDMI. If capturing the system UI or a media app shows a black screen, toggle Enable HDCP; and turn Enable HDMI Device Link (CEC) off regardless. HDCP is why protected sources go black, as covered earlier. CEC, the feature that lets devices switch each other's inputs, starts handshake fights with capture cards that cause random input switching and signal dropouts. Kill it.
9. On the PC, launch OBS, add a Video Capture Device source, and select the card. OBS is the reference application for the rest of this guide, and the Video Capture Device source is how it ingests the card's live feed. If the card is not in the dropdown, jump to troubleshooting before going further — do not fight a missing device by reinstalling everything at random.
10. Set the device to 1920x1080, 60 fps, NV12 (or the card's native capture format). Match the card's capture output exactly. If OBS and the card disagree on resolution or pixel format, OBS silently rescales and converts on every frame, which adds latency and CPU load for zero benefit. Exact-match means the cheapest possible path.
11. Route audio: use the embedded HDMI audio for game sound, and add the 3.5 mm aux as a separate Audio Input Capture for party chat. Keeping game and chat on separate sources is what lets you duck, mix, and — critically — mute chat from your VODs independently, which is both a privacy and a DMCA-claim safeguard. One blended channel gives you none of that control.
12. Set the OBS canvas and output to 1920x1080 at 60, choose NVENC (or x264), and click Start Recording to verify before you ever go live. Confirm the entire chain writes one clean local file first. Debugging a broken signal path while live, in front of an audience, is amateur hour. If the local recording is clean, the stream will be too.

Why the PS5 video output settings matter more than the card

Steps 6 through 8 do more for your image quality than any card upgrade under $100, so they are worth a second pass. RGB Range is the headline. The PS5 outputs Limited by default, OBS defaults to a color range you must set to Limited to match, and a mismatch crushes shadow detail into a grey smear or blows highlights into white. Set both to Limited, or both to Full, but make them agree.

HDR is the second trap. If the PS5 is outputting HDR and your card captures it as SDR without tone-mapping, the recording looks grey, flat, and desaturated — the exact opposite of what HDR promises — because HDR values stuffed into an SDR container have nowhere to go. For most capture work the correct answer is to disable PS5 HDR for the capture session, or to apply an HDR-to-SDR LUT in OBS. Keep HDR for the game on the passthrough TV; capture in SDR unless you have a deliberate tone-mapping pipeline.

VRR passthrough is the third. The HD60 X and the AverMedia both pass variable refresh rate through to your display so the game stays tear-free, but VRR lives on the passthrough path, not the capture path. Your recording is a fixed 60 fps regardless. Leave VRR on Automatic if your card supports passing it; it costs the recording nothing and saves the gameplay from tearing.

Verifying the first capture before you stream

Before OBS, prove the operating system can even see the card. On Linux that is a one-liner; on macOS and Windows the equivalent commands confirm enumeration without launching anything heavy.

# macOS — is the card enumerated?
system_profiler SPCameraDataType | grep -A2 'HD60'

# Linux — list V4L2 capture nodes, then probe the formats
v4l2-ctl --list-devices
ffmpeg -f v4l2 -list_formats all -i /dev/video0

# Windows (PowerShell) — find the DirectShow capture device
Get-PnpDevice -Class Camera | Where-Object {$_.FriendlyName -like '*Game Capture*'}

A healthy card on Linux returns its device nodes and the formats it offers. This is the expected output — if you see this, the hardware and bandwidth are fine and any remaining problem is in software or settings:

HD60 X (usb-0000:00:14.0-2):
        /dev/video0
        /dev/video1
        /dev/media0

[VIDEO CAPTURE] Index 0: YUYV 4:2:2  1920x1080  60.000 fps
[VIDEO CAPTURE] Index 1: NV12        1920x1080  60.000 fps

If that works but OBS shows nothing, the problem is OBS or a competing application holding the device open, not the card. If even this returns nothing, the card is not enumerating — suspect the USB port, the USB cable, or firmware, in that order, and consult the troubleshooting table.

OBS Configuration: Video, Encoder, and Audio

OBS is where the captured signal becomes a stream or a file. The defaults are close, but three groups of settings decide whether your output looks like a clean broadcast or a smeary mess, and all three are worth setting by hand. The official OBS knowledge base documents every field below in exhaustive detail if you want the reference behind the recommendations.

Video and canvas settings

Match the canvas to the card. The HD60 X caps at 1080p60, so your base canvas, output resolution, and FPS should all be 1080p60 with no rescale. Rescaling a 1080p source up to a 1440p canvas does not add detail; it adds blur and encoder load. Set the color space to Rec. 709 and the color range to Limited to match the PS5, as established at step 7.

[Video]
BaseResolution    = 1920x1080    # canvas — match the card's capture output
OutputResolution  = 1920x1080    # no rescale; the card already caps at 1080p60
FPSType           = Common
FPSCommon         = 60
ColorFormat       = NV12
ColorSpace        = Rec. 709
ColorRange        = Limited       # PS5 outputs limited 16-235 by default
DownscaleFilter   = Lanczos       # only matters if you ever downscale

Encoder and bitrate

Use hardware encoding. On an NVIDIA card that is NVENC (the encoder OBS labels jim_nvenc); on a CPU-only machine, fall back to x264 on the medium or faster preset. For streaming, use CBR rate control with a bitrate your platform accepts — 6000 kbps is the practical ceiling for a Twitch non-partner — and set a keyframe interval of 2 seconds, which Twitch and YouTube both require. For local recordings, switch rate control to CQP or CRF around 18 and let the bitrate float; you are not bandwidth-limited writing to your own disk.

[Output]
Mode              = Advanced
Encoder           = jim_nvenc      # NVENC on RTX/GTX; use 'obs_x264' if CPU-only
RateControl       = CBR            # CBR for streaming; CQP/CRF for local-only
Bitrate           = 6000           # kbps — Twitch non-partner ceiling
KeyframeInterval  = 2              # seconds — required by Twitch and YouTube
Preset            = p5             # NVENC quality preset (higher = slower/better)
Profile           = high
LookAhead         = true
PsychoVisualTuning = true
BFrames           = 2

Audio routing and the 3.5 mm chat trick

This is where the HD60 X earns its price over the cheaper cards. Game audio rides embedded in the HDMI signal, so it arrives automatically with the Video Capture Device source. Party chat comes off the DualSense and out the card's 3.5 mm aux port, which you add to OBS as a separate Audio Input Capture. Keeping them on separate sources — and separate recording tracks — lets you balance them independently and mute chat from a VOD later without touching the game audio.

Sources
  Video Capture Device  ->  Game Capture HD60 X     (game audio, embedded over HDMI)
  Audio Input Capture   ->  HD60 X 3.5 mm Aux        (party chat from the DualSense)
  Audio Input Capture   ->  Your USB/XLR microphone

Audio Mixer (levels / monitoring)
  Game   -6 dB    Monitor: Off
  Chat   -9 dB    Monitor: Off      # never monitor chat to the stream: DMCA + echo
  Mic    -3 dB    Monitor: Monitor and Output

One rule that catches everyone: set the monitoring on the chat and game channels to Off, not to Monitor and Output. Monitoring routes the audio back out through your system and into the stream a second time, producing an echo and, in the case of friends' voices and any music they are playing, a fresh set of copyright claims you did not consent to. Monitor your microphone if you must; leave everything else on Off.

Common Pitfalls and How to Fix Them

Seven mistakes account for the overwhelming majority of capture-card support threads. None of them are the card's fault, all of them are preventable, and most of them you have already avoided if you followed the steps in order. Here they are by category, with the fix attached to each.

Connection and signal pitfalls

Playing off the capture preview. The single most common complaint — the game feels laggy — comes from watching the OBS preview window instead of the passthrough television. The capture path has buffering and encode delay; the passthrough path does not. Fix: always play off the TV connected to the card's HDMI OUT. The preview is for the audience and for you to glance at, never to aim with.

Reversed HDMI IN and OUT. A swapped cable gives you no signal and no obvious clue why. Fix: trace it physically — PS5 into the port labeled IN, television into the port labeled OUT. The card receives on IN and forwards on OUT, every time, no exceptions.

Resolution, color, and HDR pitfalls

RGB range mismatch. Grey blacks and washed-out color almost always mean the PS5 and OBS disagree on Limited versus Full range. Fix: set the PS5 RGB Range to Limited and OBS Color Range to Limited (or set both to Full). They must agree; which one you pick matters far less than that they match.

HDR captured as SDR. A flat, desaturated, grey-looking recording from an HDR game is HDR data dumped into an SDR container with no tone-mapping. Fix: disable PS5 HDR for the capture session, or apply an HDR-to-SDR LUT in OBS. Do not leave HDR on and hope; the card will not tone-map for you.

Audio and latency pitfalls

USB 2.0 or a shared hub. Dropped frames at 60 fps that come and go look like a software fault but are a bandwidth wall. Fix: a 5 Gbps USB 3.0 port directly on the motherboard's rear I/O, never a front-panel header through a hub and never a USB 2.0 port.

Sample-rate mismatch. Audio that drifts slowly out of sync over a long recording is usually a 48 kHz versus 44.1 kHz disagreement between the console, the card, and OBS. Fix: set everything in the chain to 48 kHz — the PS5 audio output, the OBS audio settings, and any mixer in between.

Expecting 4K120 capture. The last pitfall is conceptual. People buy a card to capture 4K120 from the PS5 and are baffled when it records 4K60 or 1080p. Fix: recalibrate the expectation, because as established, no consumer PS5 capture card does 4K120 capture in 2026. Pass it through to your TV; capture at 4K60 or 1080p60.

Troubleshooting Table

When something is broken, work the table top to bottom. The order roughly tracks how common each cause is, so starting at the top and moving down is the fastest path to a fix in most cases.

The troubleshooting table

When to clear the PS5 cache or rebuild the database

If you have toggled HDCP, reseated every cable, confirmed the direction, and the console still throws an intermittent black screen or a handshake that fails on cold boot, the next suspect is the PS5 itself rather than the card. A corrupted system cache produces exactly these symptoms — flaky HDMI negotiation, video modes that fail to apply, output that works on one boot and not the next. Our twelve-step PS5 cache clear via Safe Mode walks the safe path: it is non-destructive, takes about ten minutes, and resolves a surprising share of capture problems that look like card faults but are console-side.

Driver, firmware, and the device-disappeared class of bug

The single most common reason a card vanishes from the OBS dropdown is another application already holding it open — the vendor's own capture utility, a browser tab using it as a webcam, or a previous OBS instance that did not close cleanly. Close everything that could claim the device, then relaunch OBS alone. If it is still missing, update firmware through the vendor utility and update the card's driver. Firmware updates are not optional housekeeping; capture cards ship bugs and fix them in firmware, and an out-of-date card is a known-issue magnet. On Windows, a Device Manager uninstall-and-replug forces a clean driver re-enumeration when nothing else will.

Advanced Tips

The setup above is complete and will serve almost everyone. These are the moves for people who have outgrown clicking Record — scripted capture, offloaded encoding, and squeezing the most out of the HDR and decoupled-resolution features the better cards offer.

Scripted and headless recording with FFmpeg

OBS is the right tool for a stream, but for an unattended, scriptable, bit-exact local recording — a benchmarking session, an automated archive, a headless box — FFmpeg reads the card directly. On Linux the card is a V4L2 device and the audio is an ALSA device, and one command captures both into a near-visually-lossless file. The FFmpeg device documentation covers the V4L2 and ALSA input options in full.

# Record 1080p60 from the HD60 X on Linux: H.264, near-visually-lossless
ffmpeg -f v4l2 -framerate 60 -video_size 1920x1080 -input_format nv12 \
  -i /dev/video0 \
  -f alsa -i hw:CARD=HD60X \
  -c:v libx264 -preset veryfast -crf 18 -pix_fmt yuv420p \
  -c:a aac -b:a 192k \
  ps5_capture.mkv

When the command is working you will see FFmpeg detect the raw NV12 stream, map both video and audio, and report a steady 60 fps. This is the expected output — a stable fps figure that holds at 60 is the whole game; if it sags, you have a bandwidth or disk-write problem:

Input #0, video4linux2,v4l2, from '/dev/video0':
  Duration: N/A, start: 8211.123456, bitrate: N/A
    Stream #0:0: Video: rawvideo (NV12 / 0x3231564E), nv12, 1920x1080, 60 fps, 60 tbr
Stream mapping:
  Stream #0:0 -> #0:0 (rawvideo (native) -> h264 (libx264))
  Stream #1:0 -> #0:1 (pcm_s16le (native) -> aac (native))
frame= 1800 fps= 60 q=18.0 size=  21504kB time=00:00:30.00 bitrate=5872.6kbits/s

Dual-PC streaming and offloading the encode

A PS5 capture rig is already a two-device pipeline — console feeds card feeds PC — which means the encode never touches the console; the PS5 spends all of itself on the game. To go further, dedicate the capture PC entirely to encoding and keep your main PC for nothing else, or send the OBS output over NDI to a second machine on the network so the streaming box and the capture box are separate. For most PS5 streamers this is overkill, but it is the architecture professional setups use, and OBS supports it natively. If you want to read the encoder internals or file an issue against a real bug, the OBS Studio source on GitHub is the authority.

One genuinely useful alternative deserves mention: if you do not need pixel-perfect, lag-free 60 fps and only want to play or record the PS5 on a PC with no card at all, Sony's own Remote Play streams the console over your LAN. Our Remote Play setup for 1080p at 15 Mbps covers it end to end. It is not a capture-card replacement for serious streaming — the latency and compression are real — but for casual recording on a budget of zero dollars, it is the move.

HDR, VRR, and recording at a higher resolution than you play

The AverMedia decoupling trick is the advanced feature worth the most. Because the Ultra 2.1 runs its play and record paths independently, you can drive a 4K120 display from the passthrough for the smoothest possible game feel while the card banks a 4K60 recording — you sacrifice nothing on the controller for a high-resolution archive. The Elgato cards cannot do this; on an HD60 X the recording is always 1080p60 regardless of what the TV shows. If decoupled play-and-record is the feature you want, the card choice is made for you.

For HDR, the professional path is not to disable it but to capture it and tone-map deliberately. Apply a quality HDR-to-SDR LUT as a filter on the capture source in OBS, calibrate it against a known reference frame, and you keep the vivid look HDR was for without the grey, crushed mess that an accidental SDR capture produces. It is more work than flipping HDR off, and for a casual stream it is not worth it — but for a channel where image quality is the product, it is the difference between looking broadcast-grade and looking like a phone pointed at a screen.

The Complete Working Configuration

Here is the entire chain in one place — hardware, PS5 settings, and OBS profile — for the reference HD60 X build at 1080p60. Copy it, adapt the encoder line to your GPU, and you have a known-good baseline that produces a clean stream and a clean local file.

The hardware chain

PS5 HDMI OUT into the card's HDMI IN with a certified Ultra High Speed cable; the card's HDMI OUT into your 4K display with a second certified cable for 4K60 passthrough; the card into a rear-panel USB 3.0 port with the bundled cable; the DualSense headphone jack or the PS5's audio output feeding the card's 3.5 mm aux for party chat. Nothing in this chain is over two metres, nothing routes through a hub, and every cable is certified. That is not fussiness; it is the difference between this working on the first boot and you reading the troubleshooting table on the third.

PS5 settings, verbatim

PS5 — Settings > Screen and Video > Video Output
  Resolution ............ Automatic        # reads passthrough EDID; do not force
  HDR ................... Off               # capture SDR unless you tonemap in OBS
  Deep Color Output ..... Automatic
  RGB Range ............. Limited           # MUST match OBS ColorRange
  VRR ................... Automatic         # only if the card passes VRR

PS5 — Settings > System > HDMI
  Enable HDCP ........... On (media apps)   # toggle Off only if UI capture is black
  HDMI Device Link ...... Off               # stop CEC from switching inputs

PS5 — Settings > Sound > Audio Output
  Output Device ......... HDMI (to capture card)
  Sample Rate ........... 48 kHz            # match OBS to avoid drift

OBS profile, verbatim

OBS Studio — Capture Profile (PS5 / HD60 X, 1080p60)

[Video]
  Base / Output ......... 1920x1080 / 1920x1080
  FPS ................... 60
  Color Format .......... NV12   |  Space: Rec. 709  |  Range: Limited

Sources (top to bottom)
  1. Microphone overlay / alerts (browser source)
  2. Webcam (optional)
  3. Video Capture Device: HD60 X
       Resolution/FPS ... 1920x1080 @ 60, NV12
       Audio ............ embedded HDMI game audio
  4. Audio Input Capture: HD60 X 3.5 mm Aux (party chat)

[Output] Streaming
  Encoder ............... NVENC H.264 (jim_nvenc)
  Rate Control / Bitrate  CBR / 6000 kbps
  Keyframe Interval ..... 2 s
  Preset / Profile ...... p5 / high   |  B-frames: 2  |  Look-ahead + PsychoVisual: on

[Output] Local Recording
  Type .................. Standard
  Format ................ mkv (remux to mp4 after; mkv survives a crash)
  Encoder ............... NVENC HEVC, CQP 18   |  or x264 CRF 18 (CPU)

[Audio]
  Sample Rate ........... 48 kHz
  Tracks ................ 1: stream mix  |  2: game  |  3: chat  |  4: mic

Record to MKV, not MP4, for the local file. An MKV survives a crash or a power loss with the footage up to that point intact; an MP4 that did not finalize is frequently an unrecoverable brick. Remux the MKV to MP4 losslessly after the session if you need MP4 for an editor — OBS does it in one menu click, with no re-encode.

The Verdict

A capture card is simple hardware wrapped in a DRM problem and surrounded by settings that punish carelessness. Get the cable, the USB port, and the RGB range right, and the rest is a half-hour job you do once.

Which card, in one sentence

Buy the Elgato HD60 X at $199.99 unless you have a specific reason not to: it is TechRadar's and GamesRadar's baseline pick, it does 1080p60 capture with 4K60 HDR and VRR passthrough, and the 3.5 mm aux port handles party chat that the cheaper cards make you solve with extra hardware. Step up to the AverMedia Live Gamer Ultra 2.1 only if you run a high-refresh display and want to play at 4K120 while recording at 4K60; drop to the Genki ShadowCast only if your budget is fifty dollars and your needs are modest; go internal PCIe only if you have a desktop and you stream for a living.

What this setup will and will not do

It will give you a clean, broadcast-quality 1080p60 stream and a near-lossless local recording with game and chat on separate tracks, at zero cost to your gameplay because the passthrough TV carries the real picture. It will not capture the PS5 at 4K120, because no consumer card does that in 2026 — that ceiling is HDMI 2.1 capture silicon nobody has shipped at this price yet. Set your expectations to 1080p60 capture with 4K60 passthrough, follow the twelve steps, and you have a rig that does everything the Share button cannot, which was the entire reason you bought the card.