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

You typed "ps5 capture card" into a search box, a store took your money, and at no point did anyone tell you the phrase describes a thing that does not exist. Let us fix that first, then build you a genuine 4K60 recording chain in fourteen numbered steps, roughly thirty minutes, with every setting explained so you can repair it when it breaks. Because it will break, and it will almost always break in the same five places.

There Is No Such Thing as a "PS5 Capture Card"

Let us dispose of the premise before it costs you money, because everyone selling you a "PS5 capture card" depends on you never questioning the phrase. There is no PlayStation 5 capture card. There is no Sony-certified silicon, no console-specific encoder, no chip that knows or cares what is plugged into it. A capture card is an HDMI receiver wired to a USB controller. It sees a video signal — resolution, frame rate, color depth, and a copy-protection handshake — and it is entirely blind to whether that signal came from a PS5, a Series X, a gaming laptop, or a Blu-ray deck from 2009. "PS5 capture card" is a search term, not a product category.

This is not pedantry, and it is not a rhetorical flourish. It changes every decision you are about to make. The moment you accept that you are buying a general-purpose HDMI capture device, the marketing evaporates and four honest questions remain: what will it record, what will it pass through to your television, how does it survive the copy-protection handshake, and how much latency does it add to the picture on your screen. Answer those four and the logo on the console becomes irrelevant.

A capture card sees a signal, not a console

Every device on this page — Elgato, AVerMedia, Asus, NearStream, EVGA, Cloner Alliance — implements the same pipeline. An HDMI input receives the console's video stream. An optional HDMI output mirrors that stream, unmodified, to your TV so you can play with minimal delay; this is the passthrough path. A capture ASIC or FPGA samples the input, optionally compresses it, and shovels the result down USB to your PC, where software such as OBS Studio receives it as a standard webcam-class UVC device. Nothing in that chain is PlayStation-aware. The PS5 is simply the most-searched source, which is why manufacturers stamp "for PS5" on the box and why IGN's 2025 capture guide is exactly what it is: six perfectly ordinary HDMI cards, ranked.

Why the phrase persists anyway

The phrase survives because it is useful shorthand for a real cluster of requirements. A card that suits a PS5 in 2026 must accept the console's 4K60 (or 4K120) HDMI 2.0/2.1 output, tolerate the PS5's HDCP handshake once you have disabled it on the console, and ideally pass 4K through to a modern TV without downgrading it. Those requirements are shared by the Series X and any 4K PC, which is precisely why the same cards top every console's list. So yes, buy a card "for PS5" — just understand that you are buying a 4K60-capable HDMI capture device, and every spec that matters is printed on the box in console-neutral terms.

The one thing the console actually dictates: HDCP

There is exactly one way the PS5 makes itself special to a capture card, and it is not flattering. HDCP — the copy-protection handshake Sony wraps around the HDMI output — behaves differently on PlayStation than on Xbox. Xbox lets you disable it globally with a single toggle and forgets about it. The PS5 also lets you disable it, but it re-arms the protection for streaming-video apps and, historically, for certain first-party cutscenes. That single behavioral quirk — covered in full in the HDCP section below — is the only genuinely PS5-specific thing about "PS5 capture." Everything else is HDMI, and HDMI does not read logos.

Capture vs. Passthrough: The Only Spec That Matters

If you internalize one idea from this entire tutorial, make it this one, because it is the single most common way people waste two hundred dollars: the headline number on the box is almost always the passthrough figure, and passthrough is not recording. Capture cards advertise two completely different resolution-and-framerate ceilings, and the marketing exists to blur them together until you cannot tell which one you are buying.

Two numbers, two jobs

Passthrough is the signal the card forwards, untouched, from its HDMI input to its HDMI output and onto your TV. Because the card does nothing but relay those bits, passthrough ceilings are high — 4K120, 4K144, 1440p240, even 1080p360 on the better HDMI 2.1 cards. Capture is the signal the card actually samples, compresses, and sends to your PC to be recorded or streamed. Capture is the hard, expensive part, and its ceiling is always lower. The Elgato HD60 X passes 4K60 and 1440p120 straight to your TV, but it records at 4K30 or 1080p60. The Asus TUF CU4K30 passes 4K60; it captures 4K30 — the number is in the model name and people still miss it. The AVerMedia GC553G2 passes 4K144; it captures 4K60. Read every spec sheet as two columns, never one number, and put your finger over the bigger number while you shop.

Why "4K144" on the box does not mean 4K144 recordings

AVerMedia's Live Gamer Ultra 2.1 — the GC553G2, not the mythical "GC553Pro" that AI-generated listicles keep inventing out of thin air — is marketed on a headline 4K144 figure. That is a passthrough number. Its normal, UVC-standard capture ceiling is 4K60. There is a 4K144 capture mode, but it is a special path: it requires AVerMedia's own Streaming Center software, a Windows machine, and MJPEG compression that eats bandwidth and disk for breakfast. It is a benchmark flex, not a workflow. In practice, every mainstream 4K card on this page records at 4K60, full stop. If a store listing tells you a card "records 4K144," it has copied the passthrough spec into the capture column, and you should distrust the rest of that listing on principle. We walk through the distinction card by card in our deeper breakdown of 4K60 record versus 4K144 passthrough.

The 60 fps ceiling nobody mentions

Here is the deflating part: for most people it does not matter, because the platforms you are recording for cap out at 60 fps anyway. YouTube tops out at 4K60 for uploaded video. Twitch tops out at 60 fps and, for most non-partners, around 8 Mbps at 1080p. Every frame above 60 that a card can "capture" exists only inside your local recording, and only if your CPU, GPU, and NVMe disk can sustain writing it. A PS5 outputs 4K120 in a handful of titles, and even a PS5 Pro is bound by the same 120 fps console ceiling that PC players enjoy sneering at. For ninety-nine percent of creators, "4K60 capture, 4K120 passthrough" is the correct target, and anyone selling you more headroom on the recording path is selling you frames you will never upload.

Prerequisites: Hardware, Cables, and Software Versions

Before you buy anything or plug anything in, inventory the chain. Capture is only as strong as its weakest link, and the weakest link is almost never the card — it is a USB 2.0 port, a four-dollar HDMI cable that renegotiates itself down to 4K30 when it warms up, or a mechanical hard drive that cannot write 4K60 without hiccuping. Here is everything the 14-step setup assumes you have on the desk.

The console and display side

• A PlayStation 5 or PS5 Pro on current system software. Whether you are feeding the card a base PS5 or a PS5 Pro changes nothing about the capture chain itself — both output the same HDMI signal formats — but the Pro's higher internal frame rates make the capture-versus-passthrough distinction matter far more, because you will be tempted by cards that pass 4K120.
• A 4K television or monitor with a spare HDMI input for the passthrough feed, so you can play in real time while the PC records. For 4K120 or VRR passthrough, that display and its cable must both be HDMI 2.1 (48 Gbps). A 4K60 chain does not need any of that.
• Two HDMI cables. For 4K60, any certified High Speed / Premium High Speed (18 Gbps) HDMI 2.0 cable is fine. For 4K120/VRR passthrough you need two Ultra High Speed (48 Gbps) HDMI 2.1 cables — one console-to-card, one card-to-TV. NearStream explicitly ships and recommends certified HDMI 2.1 cabling with the CCD30 for exactly this reason: a marginal cable is the most common invisible bottleneck in the whole hobby.

The PC side

• CPU/GPU: for software (x264) encoding at 4K60, a modern 8-core CPU under real load; far easier, an NVIDIA GPU with NVENC (RTX 20-series or newer), an AMD GPU with AMF, or Intel Arc / Quick Sync for hardware HEVC/AV1 encoding that offloads the work off your processor entirely. Hardware encode is the correct default in 2026.
• USB: a USB 3.0 (5 Gbps) or faster port for any 4K card. Lightly-compressed 4K60 saturates USB 2.0 instantly; a USB 2.0 card such as the AVerMedia GC311 Mini or GC513 Portable is, by physics, a 1080p recording device no matter what the box art implies. NearStream states plainly that the CCD30 needs USB 3.0 or higher and a Windows PC, and warns that Macs may hit driver limitations in 2025–2026 — take that as a category-wide caution, not a NearStream quirk.
• Storage: an SSD, preferably NVMe. 4K60 at 80–100 Mbps writes roughly 0.6–0.75 GB per minute; a mechanical HDD's seek stalls are a leading cause of dropped frames that people misdiagnose as "a bad card."
• RAM: 16 GB minimum, 32 GB if you are also gaming on the same PC in a single-machine stream setup.

Software and versions

Install OBS Studio — version 31.x is current in 2026 and ships the NVENC HEVC and AV1 encoders — or your card's bundled app (Elgato 4K Capture Utility, AVerMedia Streaming Center / RECentral). Install the latest capture-card driver and firmware from the vendor: the Elgato downloads portal or AVerMedia's support site. Have FFmpeg on your PATH for verifying and remuxing recordings; it is the difference between "my file is corrupt" and a two-second fix. Confirm the PS5 is on current firmware. Everything else is configuration, and here is the target state you are configuring the console toward:

PS5  Settings > Screen and Video > Video Output
  Resolution ................. Automatic (2160p)
  4K Video Transfer Rate ..... Automatic      # force -40Gbps- only on a full HDMI 2.1 chain
  HDR ........................ Off            # On only if the card is HDR10-certified
  Deep Color Output .......... Automatic
  RGB Range .................. Full           # match your capture / monitor path
  ALLM ....................... On

PS5  Settings > System > HDMI
  Enable HDCP ................ OFF            # required for capture (see HDCP section)

Picking a Card in 2026: Real SKUs, Real Prices

Here is the honest 2026 field, with the model numbers that actually exist and the prices retailers actually charge — not the fantasy SKUs and stale MSRPs that clog listicles. Cross-reference against GamesRadar's best-capture-card list and PC Gamer's 2026 roundup, but read them with the capture-versus-passthrough lens from two sections ago, because even the good outlets routinely print passthrough numbers in the capture column.

The external mainstream: Elgato HD60 X, 4K S, 4K X

The Elgato HD60 X at $179.99 is the default recommendation of every guide, and it is a genuinely good card — but note carefully that it captures 4K30 and passes 4K60. The store copy that calls it a "4K60 capture card" is quoting the passthrough number at you. If you want honest 4K60 recording on an HDMI 2.0 budget, the card to actually buy is the Elgato 4K S ($159.99), which launched in August 2025 and is therefore missing from older guides that were written before it existed. PC Gamer's line on it is the whole review in one sentence: it "would be the top of the pile, if it weren't for a recent AverMedia stunner." The 4K X (~$230) is the HDMI 2.1 upgrade that captures up to 4K144 and passes 4K120 with Display Stream Compression, for the people who genuinely need 4K120 on the monitor while recording.

The AVerMedia question: it is the GC553G2

The AVerMedia stunner PC Gamer was referring to is the Live Gamer Ultra 2.1, and its real SKU is the GC553G2. It is not, has never been, and will never be a "GC553Pro" — that model number is a hallucination that search-engine AI summaries keep repeating to each other until it looks real. MSRP is $299.99; by mid-2026 it street-prices around $199. HDMI 2.1, UVC plug-and-play, passes 4K144 / 1440p240 / 1080p360 with HDR and VRR, captures a clean 4K60 in normal use. Windows Central's verdict is the accurate one: "True 4K/60 FPS recording on consoles and PC, but the software needs work." GamesRadar rates it the best external card outright. Buy it for what it records — 4K60 — and treat the 4K144 headline as the software-and-MJPEG party trick it is.

Budget, standalone, and internal options

The Asus TUF CU4K30 at roughly $120 is the budget external pick — not the $147 or $249 that assorted listings claim, both of which are wrong. Windows Central: "Brilliant external video capture on a budget." The NearStream CCD30 (~$135) is a tidy USB-C 3.1 4K60 alternative. The AVerMedia GC311 Mini and GC513 Portable 2 Plus are USB 2.0, 1080p60 recording devices; the GC513 passes 4K through to your TV but records 1080p60, so any listing promising "4K30 recording" from it is simply false. The EVGA XR1 Pro still appears on IGN's 2025 list but is a legacy product now that EVGA has exited the GPU business entirely — serviceable, unsupported, buy used at your own risk. And the Elgato Game Capture 4K Pro ($279.99) is the internal PCIe card for people who want 8K60 passthrough and zero USB clutter; GamesRadar calls it "an internal capture card with some future-proofing," Windows Central "the only capture card you'll ever need (if your PC can handle it)." The Cloner Alliance UHD-series standalone recorders capture 4K24–30 and pass 4K60; ignore any spec sheet quoting them at 2K120 or 1080p240, which is fabricated.

4K60 Capture in 14 Steps

This is the whole workflow, in order, with the reasoning for each step, because a step you perform without understanding is a step you cannot troubleshoot at 11pm before a stream. Budget about thirty minutes the first time and five the second. Have the card, two HDMI cables, a USB 3.0 cable, your PC, and your PS5 in front of you.

Before you start: the five-minute pre-flight

Update the card's firmware and driver from the vendor first, from a cold boot — roughly a third of "no signal" complaints are stale firmware meeting a new console output mode. Update OBS to 31.x. Confirm you are plugging the card into a USB 3.0 port (blue, or labeled SS) directly on the machine, not through an unpowered hub or a monitor's downstream port. Then, and only then, begin.

1. Update firmware and drivers, then reboot the PC. New PS5 output modes (VRR, ALLM, 4K120) periodically outrun old capture firmware, and a cold reboot clears any half-initialized USB state. Rationale: this eliminates the single most common cause of black screens before you waste an hour blaming cables.
2. Connect PS5 HDMI-OUT to the card's HDMI-IN. Use a certified cable; for 4K120 it must be a 48 Gbps Ultra High Speed cable. Rationale: the input link sets your capture ceiling — a cable that quietly renegotiates down to 4K30 caps everything downstream and gives no warning.
3. Connect the card's HDMI-OUT to your TV. This is the passthrough feed you actually play on. Rationale: you play on the passthrough, never on the OBS preview, because the preview carries encode-plus-USB latency measured in tens to hundreds of milliseconds and will get you killed in anything competitive.
4. Connect the card to the PC over USB 3.0 or faster. Blue port, direct, or a powered hub. Rationale: 4K60 needs the bandwidth; USB 2.0 forces the card into 1080p or silently drops frames until the recording stutters.
5. Boot the PS5 and disable HDCP. Settings > System > HDMI > Enable HDCP > Off. Rationale: the capture ASIC legally cannot forward a protected stream; with HDCP on you get audio and a black frame, which is the classic "it worked yesterday" symptom. See the HDCP section for exactly what this breaks.
6. Set the PS5's video output correctly. Match the target block in Prerequisites: Resolution Automatic (2160p), HDR Off unless your card is HDR10-certified, RGB Range Full to match your capture path. Rationale: an HDR signal into a non-HDR card produces washed-out, grey-black footage that no amount of color grading fully recovers.
7. Add the card in OBS as a "Video Capture Device" source, and set its properties explicitly. Do not trust auto. Rationale: OBS defaults to the lowest common denominator; you must force the resolution, FPS, and pixel format the card actually outputs.

   OBS  Sources > + > Video Capture Device > [your card]
     Resolution/FPS Type ...... Custom
     Resolution ............... 3840x2160
     FPS ...................... 60
     Video Format ............. NV12   # or P010 for 10-bit HDR10 capture
     Color Space .............. Rec. 709   # Rec. 2100 (PQ) for HDR
     Color Range .............. Full

8. Set the OBS canvas, output resolution, and frame rate. Video settings, not Output settings — people confuse the two constantly. Rationale: the canvas is what OBS composites at; the output res is what it encodes. Set both to 4K for archival, or downscale the output to 1080p for streaming while keeping a 4K canvas.

   OBS  Settings > Video
     Base (Canvas) Resolution ..... 3840x2160
     Output (Scaled) Resolution ... 3840x2160   # 1920x1080 to downscale for stream
     Downscale Filter ............. Lanczos (36 samples, sharpened scaling)
     Common FPS Value ............. 60

9. Route audio deliberately, exactly one path. Use the capture card's HDMI audio as your game-audio source and mute the console audio elsewhere. Rationale: the most common audio bug is capturing the game twice — once via HDMI, once via a Desktop Audio device — producing a hollow, phased echo that sounds like a broken mic.
10. Choose your encoder and bitrate in Output settings (Advanced mode). Hardware HEVC or AV1 for recording; see the OBS section below for the full block. Rationale: x264 at 4K60 will pin an 8-core CPU and drop frames the moment a game gets busy; NVENC/AV1 offloads it to dedicated silicon.
11. Set the recording format to fragmented MP4 or MKV, and point the path at your SSD. Rationale: a plain MP4 that is interrupted (crash, power loss) is unrecoverable; fragmented MP4 and MKV survive it, and you remux to standard MP4 afterward in two seconds.
12. Run a 60-second test recording of actual gameplay. Not the menu — gameplay, where the bitrate and encoder are stressed. Rationale: menus are static and encode trivially; you need to see how the chain behaves under motion before you trust it with a real session.
13. Verify the file with FFmpeg before you celebrate. Confirm resolution, frame rate, and codec are what you asked for. Rationale: OBS will happily record 1080p30 while you believe it is doing 4K60, and you will not know until you open the file — verify, do not assume.
14. Save the OBS profile and scene collection, and write down the PS5 settings. Rationale: the next firmware update or the next person who touches the console will reset something; a saved profile turns a thirty-minute rebuild into a thirty-second restore.

Expected output: what a working capture looks like

Run FFprobe on the test file. A correctly configured 4K60 HEVC capture reports this — anything less means a step above silently downgraded, and you go find which one:

$ ffprobe -hide_banner capture_test.mp4
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'capture_test.mp4':
  Duration: 00:01:00.02, start: 0.000000, bitrate: 82143 kb/s
  Stream #0:0: Video: hevc (Main), yuv420p(tv), 3840x2160, 60 fps, 60 tbr
  Stream #0:1: Audio: aac (LC), 48000 Hz, stereo, fltp, 320 kb/s

The numbers that matter: 3840x2160, 60 fps, and a bitrate in the 60,000–100,000 kb/s band. If you see 1920x1080, 30 fps, or a bitrate under 20,000, something in steps 6 through 10 did not take.

Recording and streaming at the same time

OBS can record locally and stream simultaneously, but they are separate encoders with separate settings. Record 4K60 at high bitrate to disk; stream 1080p60 at ~8 Mbps to Twitch. If your GPU has a single NVENC unit, two 4K encodes may overload it — downscale the stream output and let the record path keep the 4K. For a stream built from scratch around this exact scene tree, follow our from-scratch OBS walkthrough, which picks up where this capture chain ends.

HDCP: Why You Turn It Off, and What It Kills

HDCP is the one genuinely PlayStation-specific wrinkle in this whole exercise, and it is worth understanding rather than blindly toggling, because the toggle has consequences you will otherwise discover at the worst possible moment.

The toggle, and the law behind it

HDCP — High-bandwidth Digital Content Protection — is an Intel-originated encryption handshake carried over HDMI, designed to stop protected content from being copied off the wire. It is a DRM scheme, and stripping it is an act the DMCA's Section 1201 anti-circumvention provisions treat as unlawful, which is precisely why no legitimate capture card will strip it for you — the hardware is built to refuse a protected stream, not defeat it. When you disable HDCP on the console, you are not cracking anything; you are telling the PS5 to stop asserting protection on the signal it sends, which it is permitted to do for the game output. The path is Settings > System > HDMI > Enable HDCP, and you set it to Off.

What breaks the moment HDCP is off

Netflix, Disney+, Prime Video, and the PS5's other streaming-video apps require HDCP and will refuse to play with it disabled — you get a black screen or a protection error, not the movie. This is not a bug and it is not fixable from the capture side; those apps re-arm HDCP by contract with the studios. The practical consequence is a small ritual: HDCP off to capture games, HDCP back on to watch films. There is no per-app toggle and no middle setting. If you stream games in the evening and watch a series afterward, you will be flipping this switch, and forgetting to flip it back is the number-one cause of "my Netflix stopped working" support threads.

What stays blocked even with HDCP off

Disabling HDCP frees the game output, but the PS5 has historically re-asserted protection around certain first-party cutscenes and its own media contexts, so the occasional black frame mid-cutscene is expected behavior, not a broken card. If you need a capture path that sidesteps HDMI and HDCP entirely — for a handheld, a laptop, or a second room — PS Remote Play, which tops out at 1080p60, streams the game over the network and never touches the protected HDMI bus. It trades resolution and adds latency, but it is the correct tool when HDMI capture is impractical.

OBS Encoder and Bitrate

The card gets the signal into the PC; OBS decides what the recording looks like and how much of your hardware it costs. Get the encoder and bitrate right and a mid-range GPU records flawless 4K60 all day. Get them wrong and a flagship stutters.

Encoder: NVENC HEVC or AV1 over x264

Use hardware encoding. On an NVIDIA card, NVENC HEVC (H.265) is the sweet spot for 4K60 recording — better quality per bit than H.264 and effectively free on the dedicated encoder block. NVENC AV1 (RTX 40-series and newer) is better still and the right choice for archival. Reserve software x264 for streaming to platforms that still prefer H.264, and only if your CPU has headroom to spare. Here is a known-good 4K60 recording block:

OBS  Settings > Output   (Output Mode: Advanced)  > Recording
  Type ..................... Standard
  Recording Format ......... fragmented MP4   # or MKV, remux to MP4 after
  Video Encoder ............ NVIDIA NVENC HEVC (H.265)   # or NVENC AV1
  Rate Control ............. CBR
  Bitrate .................. 80000 Kbps       # 4K60 target: 60,000-100,000
  Keyframe Interval ........ 2 s
  Preset ................... P5: Slow (Higher Quality)
  Tuning ................... High Quality
  Multipass Mode ........... Two Passes (Quarter Resolution)
  Profile .................. main
  Psycho Visual Tuning ..... On

Bitrate math for 4K60

Bitrate is quality's price, paid in disk. At 80 Mbps, 4K60 HEVC writes about 0.6 GB per minute — 36 GB an hour — and looks excellent. Drop below ~45 Mbps and 4K60 starts smearing in high-motion scenes (foliage, particle effects, fast camera pans) because the encoder runs out of bits to describe the change between frames. Above ~120 Mbps you are mostly buying disk consumption, not visible quality. For 1080p60 the equivalent comfortable band is 12–25 Mbps. Match the bitrate to the resolution you actually chose in step 8, not the one you wish you had.

Recording versus streaming profiles

Keep them separate and switch OBS profiles per task. The recording profile targets quality and local disk. The streaming profile targets the platform's ceiling — Twitch at roughly 8 Mbps and 1080p60 for most non-partners, YouTube generous enough to accept 4K60 at 40–51 Mbps. Never stream your 80 Mbps record settings; the platform will simply drop the excess and your viewers will see a slideshow while your upload chokes:

OBS  Settings > Output  > Streaming
  Video Encoder ............ NVIDIA NVENC H.264
  Rate Control ............. CBR
  Bitrate .................. 8000 Kbps        # Twitch non-partner ceiling
  Keyframe Interval ........ 2 s              # required by Twitch/YouTube
  Preset ................... P5: Slow
  Profile .................. high

OBS  Settings > Video  (for the stream profile)
  Output (Scaled) Resolution ... 1920x1080     # do not stream 4K to Twitch
  Common FPS Value ............. 60

Common Pitfalls (and the Fixes)

Nearly every capture failure is one of these six, and they are so consistent that you can diagnose most "my card is broken" posts from the title alone. Learn them once and stop losing evenings.

The signal-path pitfalls

• HDCP left enabled → audio, black video. The classic. You hear the game, you see nothing. Fix: Settings > System > HDMI > Enable HDCP > Off, then reconnect the source in OBS. If you were watching Netflix earlier, this is almost certainly it.
• USB 2.0 port masquerading as 3.0 → 1080p cap or dropped frames. Front-panel and hub ports lie. Fix: move the card to a rear-panel port wired directly to the chipset (blue / SS), and verify the negotiated speed in Device Manager or with the vendor app.
• A marginal or non-certified HDMI cable → intermittent 4K30 or signal dropouts. Cheap cables pass 4K60 cold and fail once warm. Fix: use certified Premium High Speed (18 Gbps) for 4K60 or Ultra High Speed (48 Gbps) for 4K120, and swap the cable before you swap anything expensive.

The configuration pitfalls

• HDR on into a non-HDR card → washed-out grey footage. The PS5 sends a PQ signal the card cannot interpret. Fix: turn HDR Off on the PS5 unless the card is explicitly HDR10-certified (HD60 X, 4K S, GC553G2), in which case set OBS to P010 / Rec. 2100.
• Double-captured audio → hollow echo or phasing. Game audio taken via both HDMI and a Desktop Audio source. Fix: use only the capture device's audio track and remove the duplicate source.
• Recording to a mechanical HDD → periodic stutters. Seek stalls cannot keep up with 4K60 writes. Fix: record to an SSD, ideally NVMe; move the finished file to bulk storage afterward.

Troubleshooting Table

Symptom-first, because that is how the problem actually presents itself at your desk. Work top to bottom; the causes are ordered by how often they are the real culprit.

Advanced: VRR, HDR, and Dual-PC

Once the basic chain records clean 4K60, these are the refinements that separate a functional setup from a professional one. None are necessary; each solves a specific real problem.

VRR and 4K120 passthrough on HDMI 2.1

If you own a PS5 Pro, an HDMI 2.1 card (Elgato 4K X or AVerMedia GC553G2), a 4K120 display, and two 48 Gbps cables, you can play at 4K120 with VRR on the passthrough while OBS records the down-converted 4K60 feed. The card captures 4K60 while forwarding the full 4K120/VRR signal to your TV untouched — you lose nothing on the screen you play on and record the platform-legal 60 fps. This is the only scenario where the "two certified HDMI 2.1 cables" advice is load-bearing rather than upsell; on a 4K60 chain it is neither here nor there.

HDR10 capture and tone-mapping

Only three cards here capture true HDR10 — HD60 X, 4K S, and GC553G2. If you capture HDR, capture it in 10-bit (P010, Rec. 2100 PQ) and grade later; do not let OBS crush it to SDR on the way in. For SDR delivery to platforms that mishandle HDR metadata, tone-map on export rather than at capture, so you keep the HDR master:

# Tone-map an HDR10 capture down to clean SDR (Rec.709) for upload
ffmpeg -i capture_hdr.mp4 -vf \
  "zscale=t=linear:npl=100,tonemap=hable,zscale=t=bt709:m=bt709:r=tv,format=yuv420p" \
  -c:v libx265 -crf 18 -c:a copy capture_sdr.mp4

# Linux: confirm the card enumerated as a UVC device before any of this
v4l2-ctl --list-devices
ffmpeg -f v4l2 -list_formats all -i /dev/video0

Dual-PC and low-latency monitoring

Serious streamers split the load: the PS5 feeds a capture card in a second PC that does nothing but encode and stream, leaving the gaming machine — or in this case the console — completely unburdened. The GC553G2 and the internal 4K Pro are the usual choices for the encode box because of their clean UVC output and low passthrough latency. Even single-PC, always monitor gameplay on the passthrough TV, never the OBS preview: the preview's added latency is fine for framing a scene and fatal for actually playing.

The Complete Working Configuration

Here is the entire chain in one place — console, source, encoder, and the two FFmpeg commands that verify and repair your output. This is the reference to save alongside your OBS profile so a firmware update never costs you more than a minute.

# ---------- PS5 (console output) ----------
Settings > Screen and Video > Video Output
  Resolution ............. Automatic (2160p)
  HDR .................... Off        # On + HDR10 card only
  RGB Range .............. Full
  4K Video Transfer Rate . Automatic  # -40Gbps- only on full HDMI 2.1 chain
Settings > System > HDMI
  Enable HDCP ............ OFF

# ---------- OBS 31.x (source) ----------
Video Capture Device
  Resolution ............. 3840x2160   FPS: 60   Format: NV12
Settings > Video
  Base / Output .......... 3840x2160 / 3840x2160
  Downscale Filter ....... Lanczos     Common FPS: 60

# ---------- OBS (recording encoder) ----------
Output (Advanced) > Recording
  Encoder ................ NVIDIA NVENC HEVC (H.265)
  Rate Control / Bitrate . CBR / 80000 Kbps
  Keyframe Interval ...... 2 s   Preset: P5 Slow   Tuning: High Quality
  Format ................. fragmented MP4

# ---------- Verify, then remux to a portable MP4 ----------
ffprobe -hide_banner capture.mp4          # expect 3840x2160, 60 fps, hevc
ffmpeg -i capture.mp4 -c copy -movflags +faststart final.mp4

The FFprobe line should report 3840x2160, 60 fps, hevc (Main) with a bitrate near 80,000 kb/s. The FFmpeg remux rewrites the container without re-encoding — instant, lossless, and it repairs the fragmented-MP4 header into a standard MP4 that every editor and platform accepts. If both commands succeed and report the expected numbers, your chain is correct and reproducible.

The Verdict: What to Actually Buy in 2026

You came for a "PS5 capture card" and you are leaving with a general-purpose 4K60 HDMI capture device and the knowledge to configure it, which is a strictly better outcome. Here is who should buy what, stripped of the passthrough theater.

If you just want clean 4K60 clips

Buy the Elgato 4K S at $159.99. It genuinely captures 4K60 on an ordinary HDMI 2.0 chain, it launched in August 2025 so it is current, and it is the cheapest honest 4K60 recorder on the list. PC Gamer said it "would be the top of the pile, if it weren't for a recent AverMedia stunner" — which tells you both that it is excellent and what beats it. The much-recommended HD60 X ($179.99) is a fine card, but remember it captures 4K30 and merely passes 4K60; buy it for its price and passthrough, not for 4K60 recording it does not do.

If you have a PS5 Pro and a 4K120 display

Buy the AVerMedia GC553G2 (~$199 street, $299.99 MSRP) or the Elgato 4K X (~$230). Both are HDMI 2.1, both pass 4K120/VRR to your TV while capturing a platform-legal 4K60, and both need two 48 Gbps cables to do it. Windows Central on the GC553G2: "True 4K/60 FPS recording on consoles and PC, but the software needs work" — buy it for the hardware and tolerate the software, or buy the Elgato and tolerate the price. And ignore the "GC553Pro": it is a SKU that does not exist, no matter how many AI-written listings insist otherwise.

If you are on a budget or want zero USB clutter

The Asus TUF CU4K30 at ~$120 is the budget answer — "brilliant external video capture on a budget," per Windows Central — capturing 4K30 and passing 4K60, which is plenty for 1080p60 streaming with a 4K passthrough on the TV. And if you have a spare PCIe slot and a capable PC, the internal Elgato Game Capture 4K Pro ($279.99) removes the USB question entirely, passes 8K60, and is, in Windows Central's words, "the only capture card you'll ever need (if your PC can handle it)," or as GamesRadar puts it, "an internal capture card with some future-proofing." Whichever you choose, the setup above is identical — because, one last time, none of these cards has ever known or cared that the box on the other end of the cable says PlayStation.