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

Type ps5 capture card into any search bar and you have already made a small category error, because the PlayStation 5 is not a capture card and no company on earth manufactures a capture card that is uniquely, exclusively a PS5 device. What people mean when they type that phrase is: a general-purpose HDMI capture card that I intend to aim at a PS5. The distinction is not pedantry. It is the single fact that explains why the 2025-2026 market has produced no PlayStation-branded capture silicon, no proprietary PS5 capture version numbers, and no console-specific launch prices - only the same lineup of Elgato, AVerMedia, NearStream, Asus, and ClonerAlliance boxes that will happily digitize an Xbox, a Switch 2, or a DSLR with equal indifference.

This guide is the setup nobody else writes correctly. We will wire the thing, kill the copy protection that stops it working, and configure OBS to record a clean 4K60 master and stream a 1080p60 that does not look like a fax. Along the way we will correct the wreckage: at least four widely-syndicated buyer's guides in circulation right now list a capture card SKU that does not exist, quote a $249 price for a $120 box, and claim a 1080p device records in 4K. We checked every number against the manufacturer spec sheets. You are welcome.

There Is No 'PS5 Capture Card'

Before you spend money, understand what you are actually buying and why the marketing language around it is a minefield. A capture card is a passive interceptor. It sits in the HDMI path between your console and your screen, mirrors the video signal to a computer, and - critically - is allowed to do so only when the console permits it.

The Category Error, Stated Plainly

A capture card captures a signal from a source. The PS5 is the source. It emits an HDMI 2.1 signal from a single HDMI-out port, and that signal is identical in kind to what an Xbox Series X or a Blu-ray player emits. There is nothing in that signal that requires PlayStation-specific hardware to receive. That is why, across all of 2025 and into 2026, there have been zero new product launches for capture hardware built specifically for the PS5. The market runs entirely on existing general-purpose HDMI cards whose specifications, prices, and version numbers largely predate 2025. The only genuinely new hardware worth noting is Elgato's Game Capture 4K S, which arrived in August 2025 at $159.99, and AVerMedia's Live Gamer Ultra 2.1 (GC553G2) - and neither is a PS5 device. They are HDMI 2.1 cards that a PS5 owner might reasonably buy. IGN's own 2026 roundup, The Best Capture Card for PS5 and PS5 Pro Streaming, lists six devices, and every one of them is a general capture card.

What the Card Actually Sees (and the Law)

When your PS5 sends video over HDMI, it can flag that stream with HDCP - High-bandwidth Digital Content Protection - an encryption layer designed to stop the signal being recorded. A capture card cannot decode an HDCP-protected stream; it is not permitted to. This is where people who skipped the manual meet a black screen. Sony, sensibly, lets you switch HDCP off for gameplay, because your own game footage is yours to record. The legal line, for those who care about it and you should, is drawn at circumvention: toggling the console's own HDCP switch to record your own play is exactly what the switch is for, while stripping HDCP to rip a purchased 4K Blu-ray or a Netflix stream is the kind of thing the DMCA's anti-circumvention clause was written to punish. The card behaves accordingly - kill HDCP and your game passes through; the console re-asserts HDCP the instant you open a protected video app, and the capture goes black. That is not a bug. That is the system working.

Internal vs External, and the No-Card Alternative

Capture cards come in two physical forms. External boxes connect to your PC over USB and are the default for ninety-five percent of people - portable, driver-light, and dual-PC friendly. Internal cards slot into a PCIe lane inside a desktop, eliminating a USB cable and, in the case of Elgato's Game Capture 4K Pro, adding 8K60 passthrough headroom. Internal cards are lower-latency and higher-bandwidth but chain you to one tower. Worth saying out loud before you spend anything: if your only goal is playing your own PS5 on a laptop in another room, you may not want a capture card at all - PS Remote Play streams 1080p over your network with no capture hardware, no HDCP dance, and no $150 outlay. A capture card is for broadcasting and for pristine local recording, not for casual couch relocation.

Prerequisites & Versions

A capture rig is a chain, and a chain fails at whichever link you cheaped out on. Here is the full bill of materials with the versions that matter, because a $300 card behind a USB 2.0 port and a five-dollar cable will still hand you a stutter-fest.

The Hardware You Actually Need

You need five things: a PS5 or PS5 Pro, one capture card, a host PC that can encode video in real time, two good HDMI cables, and a display to watch while you play. That last item trips people up - the whole point of passthrough is that you look at a real screen, never at the laggy software preview. Here is the shopping list in reference form:

BILL OF MATERIALS - PS5 capture rig (2026)
------------------------------------------
Console      : PS5 or PS5 Pro (single HDMI 2.1 out)
Capture card : HDMI 2.0 for a 4K60 stream
             : HDMI 2.1 only if you want 4K120/VRR on your own monitor
Host PC      : 6-core CPU, 16 GB RAM, one free USB 3.0 (5 Gbps) port
             : GPU with a hardware encoder -
               NVIDIA NVENC / Intel QuickSync / AMD VCN
HDMI cables  : 2x - use 48 Gbps 'Ultra High Speed' for 4K120
               18 Gbps 'Premium High Speed' is fine for 4K60
Display      : 1x monitor or TV on the card's HDMI OUT (passthrough)
Software     : OBS Studio 31.x, card firmware current, GPU driver current

PC and USB Requirements

The host PC does the heavy lifting the card cannot: compressing raw video into a streamable H.264, HEVC, or AV1 bitstream. Do this in software on the CPU and you will pin a six-core chip to the wall the moment you ask for 4K. Do it on the GPU's dedicated encoder - NVENC on NVIDIA, QuickSync on Intel, VCN on AMD - and the cost is nearly free. A modern GPU or an Intel CPU with integrated graphics from the last several generations covers it. Sixteen gigabytes of RAM is the sane floor. The port matters as much as the silicon: a USB 3.0 port delivers 5 Gbps, and an uncompressed or lightly-compressed 4K60 stream needs most of it. Plug a high-bandwidth card into a USB 2.0 port or a cheap unpowered hub and you will drop frames until you find the real port - a rear-panel connector wired straight to the motherboard, usually the blue one.

Software and Versions

Install OBS Studio - the free, open-source, industry-standard broadcaster maintained on GitHub. As of mid-2026 the current line is OBS Studio 31.x; use it. You do not strictly need the manufacturer's app - Elgato's 4K Capture Utility, AVerMedia's Streaming Center, or the older RECentral - because every card here is UVC-class (USB Video Class), meaning Windows, macOS, and Linux see it as a plug-and-play webcam with no driver install. The vendor apps are useful for firmware updates and standalone recording, and firmware updates matter: an out-of-date card can refuse a PS5 Pro's higher-bandwidth modes outright. Update the card firmware once, update your GPU driver, and then leave the vendor app closed while OBS runs, because two applications cannot hold the same capture device at once.

The Cards Worth Buying in 2026

Here is the lineup that a PS5 owner is realistically choosing between in 2026, grouped by what actually distinguishes them - the HDMI generation - with the prices and SKUs corrected against the manufacturers' own pages. Read the corrections. The syndicated guides are wrong more often than they are right.

HDMI 2.0 Cards: The 4K60 Mainstream

These cap passthrough at 4K60 and are all any streamer needs, because your broadcast is 60fps regardless. The Elgato HD60 X ($179.99) is the long-running external default: it captures 4K30 or 1080p60 HDR10, passes through 4K60 with VRR, and connects over USB-C 3.0. It replaced the older HD60 S+ years ago. The genuinely new option, and the one the syndicated 2026 guides keep omitting, is the Elgato 4K S ($159.99, August 2025): still HDMI 2.0, but it captures a true 2160p60, plus 1440p144 and 1080p120, in a 90-gram brick that also works off an iPad. PC Gamer's review summed it up with the year's most backhanded compliment: it 'would be the top of the pile, if it weren't for a recent AverMedia stunner.' The value pick is the Asus TUF Gaming Capture Box CU4K30. Half the guides in circulation list this at $249; the actual price is around $120. It captures 4K30, 1440p60, or 1080p120 and passes through 4K60, and Windows Central called it, correctly, 'brilliant external video capture on a budget.'

HDMI 2.1 Cards: The 4K120/VRR Tier

Pay the premium here only if you want 4K120 or VRR on your own monitor. The headline device is the AVerMedia Live Gamer Ultra 2.1, and its real model number is GC553G2 - not 'GC553Pro', which is a SKU that does not exist and which several guides have copied from each other. At an MSRP of $299.99 it is AVerMedia's most premium external box: HDMI 2.1, a true 4K60 capture (its '4K144' figure is a Windows-only software mode in the Streaming Center app, encoded as MJPEG), and passthrough up to 4K144, 1440p240, and 1080p360 with HDR and VRR over USB 3.2 Gen 2. Windows Central's verdict was 'true 4K/60 FPS recording on consoles and PC, but the software needs work.' Elgato's external HDMI 2.1 answer is the 4K X (around $230), which captures up to 4K144 and passes 4K144, dropping to 4K120 on displays that use Display Stream Compression. If you own a desktop and hate USB clutter, the internal Elgato Game Capture 4K Pro ($279.99) is a PCIe 2.0 x4 card with 8K60 passthrough and 4K60 HDR10 capture; GamesRadar called it 'an internal capture card with some future-proofing,' and Windows Central, more bluntly, 'the only capture card you'll ever need (if your PC can handle it).'

Budget, Standalone, and the Traps

Below the flagships sit the honest cheap cards and a couple of oddballs. The NearStream CCD30 (about $135) is a USB-C 3.1 card that records a real 4K60 HDR10 - not a downscaled 1080p - with a built-in audio mixer, and NearStream's own beginner's guide is a decent primer on the HDCP step. The AVerMedia Live Gamer Mini (GC311), near $100, does a clean 1080p60 over USB 2.0 - and yes, USB 2.0 is fine here, because the card encodes to H.264 onboard and never needs the bandwidth. That is the nuance the 'never buy USB 2.0' crowd misses. The Live Gamer Portable 2 Plus (GC513), roughly $150, is widely and wrongly listed as a '4K30 capture' device; it is not. It records 1080p60 and merely passes 4K through - the 4K in its marketing is a passthrough figure. Its real trick is standalone recording to a microSD card with no PC attached. ClonerAlliance's UHD Pro and UHD Halo occupy the same standalone niche, recording 4K at 24-30fps to internal storage; the '2K120 / 1080p240' capture specs attributed to them in one tier list are fabricated. When in doubt, read the spec table below, not the blurb.

The HDMI 2.1 Passthrough Math

This is the section that saves you a hundred and fifty dollars, or spends it well. The confusion at the heart of every capture-card purchase is that a card does two different jobs with two different ceilings, and the marketing quotes whichever number is bigger.

Passthrough Is Not Capture

A capture card runs two pipelines at once. Passthrough takes the console's HDMI-in and mirrors it straight out to your screen, ideally with zero added latency, so you can play normally. Capture is the copy sent over USB to your PC. These have separate limits. The Elgato 4K Pro passes through 8K60 but captures 4K60 - the 8K figure describes what it can hand to your monitor untouched, not what it can record. The AVerMedia GC553G2 passes 4K144 but its honest capture is 4K60. When a box advertises '4K144', read it as a passthrough or software-assisted number every single time, and assume the recording is 4K60 until the spec sheet says otherwise in plain language.

The 60fps Ceiling Nobody Mentions

Here is the fact that makes the whole HDMI 2.1 premium optional for most people: your broadcast is capped at 60fps no matter what you own. Twitch and YouTube ingest are, in practice, universally limited to 60fps. So even if your card could capture 4K144 - and only in a niche local-recording mode can any of them - your audience would see 60. The high-refresh numbers only benefit you, on your passthrough monitor, in the moment you play. That is a real benefit for a competitive player who wants 120Hz feel while they stream, but it is a personal luxury, not a broadcast feature. If you have ever read our breakdown of the 240fps-vs-120fps ceilings across PC and console, the same logic applies downstream: the frame rate you feel and the frame rate you deliver are different numbers, and the delivery number is lower.

Cables, Bandwidth, and the PS5 Pro

To pass a 4K120 or VRR signal through the card to your monitor, three things must all be HDMI 2.1: the card, and both cables. VRR is an HDMI 2.1 forum feature; an HDMI 2.0 card cannot pass it, full stop. A 4K60 signal fits inside 18 Gbps 'Premium High Speed' cable, but 4K120 needs the full 48 Gbps of a certified 'Ultra High Speed' cable, and on some displays the link uses Display Stream Compression to hold 4K120 within budget. Both the PS5 and the PS5 Pro, with its faster GPU, output HDMI 2.1 from a single port, so the console side is never your bottleneck - the card and the cheaper of your two cables are. HDMI 2.1 cards cost roughly $100 to $150 more than their 2.0 siblings. Buy that gap only if 120Hz passthrough is a feature you will actually use.

The 12-Step Setup

Thirty minutes, start to finish, if the software is already downloaded. Each step has a reason attached, because a step you perform without understanding is a step you will perform wrong. Do them in order - the HDCP toggle before OBS, the wiring before the HDCP toggle.

1. Position the card between console and screen. The card is an interceptor; it must physically sit in the HDMI path, not off to the side. Everything downstream depends on this topology.
2. Run PS5 HDMI OUT to the card's HDMI IN. Use a certified cable rated for your target - 48 Gbps if you want 4K120 passthrough, 18 Gbps if 4K60 is enough. This is the source feed.
3. Run the card's HDMI OUT to your monitor or TV. This is passthrough, the screen you will actually watch while playing. Skip it and you are forced to play off the laggy preview, which is unplayable for anything fast.
4. Connect the card to the PC over USB. Use a rear USB 3.0 port wired to the motherboard, not a front-panel jack or a hub. Bandwidth-starved USB is the number-one cause of stutter.
5. Boot the PS5 and open Settings. You need to change two menus before the card will see a usable signal. Do it now, before you touch OBS, so you are debugging one variable at a time.
6. Disable HDCP. Settings, System, HDMI, then switch off Enable HDCP and reboot when prompted. Without this the card receives an encrypted stream it is not allowed to decode, and you get a black screen. This is the step people forget and then blame the cable for.
7. Set the video output. In Screen and Video, confirm 2160p resolution and set HDR to 'On When Supported' only if your card lists HDR10 passthrough; otherwise leave HDR off to avoid a washed-out capture. Set VRR to Automatic on an HDMI 2.1 card, off on a 2.0 card.
8. Open OBS Studio and add a source. In the Sources panel, click the plus, choose Video Capture Device, and name it something you will recognize, like 'PS5'. This is the object that pulls the card's feed into your scene.
9. Select the card and force the format. Pick your card from the Device dropdown, set Resolution/FPS to Custom, and specify 3840x2160 at 60fps. Leaving it on 'Preset' lets OBS negotiate a lazy 1080p30. Force what you paid for.
10. Set the video format and color range. Choose NV12 for 8-bit SDR, or P010 for HDR10. Set Color Range to Limited (Partial) to match the console's limited-range HDMI output - mismatch this and your blacks turn grey.
11. Disable source buffering. In the device properties, turn Buffering off for the lowest possible preview latency. You still will not play off the preview, but lower latency makes monitoring and sync saner.
12. Confirm the passthrough screen, then verify in OBS. Your TV should show the game live with no perceptible lag; the OBS preview will trail it by a few frames, which is normal. If both show the game, you are capturing. Configure encoder settings next, then hit Start Recording or Start Streaming.

Wiring: Get the Topology Right (Steps 1-4)

The mechanical part is trivial and the place people still get it wrong. In-out-out-out: the console goes in to the card, and the card sends signal out to your display and out to your PC. If your passthrough TV is black but the capture works, you connected only the IN - or, on some cards, the box needs USB power attached before the passthrough circuit activates. Cheap cables are false economy here; a marginal 4K120 cable will hand you intermittent signal dropouts that look exactly like a dying card.

HDCP and PS5 Settings (Steps 5-7)

These are the exact menu paths, in reference form, so you are not squinting at a video tutorial:

PS5 > Settings > System > HDMI
  Enable HDCP ............ OFF     # cards cannot decode an HDCP-locked signal
  (reboot when the console prompts you)

PS5 > Settings > Screen and Video > Video Output
  Resolution ............. 2160p (Automatic)
  HDR .................... On When Supported   # only if the card passes HDR10
  4K Video Transfer Rate . Automatic            # drop to -1/-2 if signal drops
  VRR ................... Automatic              # HDMI 2.1 cards; Off for 2.0

The one consequence worth repeating: with HDCP off, the console blocks Netflix, Disney+, and purchased 4K movie playback, because those apps demand HDCP and the console honors the demand. Toggle it back on to watch a film, off again to capture games. Sony's own 4K resolution guide documents the video-output side of these menus.

OBS Source Configuration (Steps 8-12)

The Video Capture Device properties are where a $300 card gets quietly throttled to 1080p by a default nobody changed. Set these explicitly:

OBS Studio > Sources > + > Video Capture Device
  Device ............. AVerMedia Live Gamer ULTRA 2.1   # your card
  Resolution/FPS ..... Custom
  Resolution ......... 3840x2160
  FPS ................ 60  (Highest FPS)
  Video Format ....... NV12   (8-bit SDR)  |  P010 for HDR10
  Color Space ........ Rec. 709   |  Rec. 2100 (PQ) for HDR
  Color Range ........ Limited (Partial)
  Buffering .......... Disable

OBS Encoder & Bitrate

Capturing the signal is half the job. Turning it into a stream that does not smear on motion, or a recording you would archive, is the other half, and it lives entirely in OBS's Output settings. Switch OBS to Advanced output mode first; Simple mode hides the controls that matter.

Choosing an Encoder

Never encode 4K in software. The x264 CPU encoder produces marginally better quality per bit but will overload a six-core chip the instant you feed it 4K60, and 'Encoding overloaded' in red is the result. Use your GPU's hardware encoder: NVENC on NVIDIA (HEVC or the newer AV1 on 40- and 50-series), QuickSync on Intel, VCN on AMD. The quality gap between modern NVENC HEVC and x264 is now small enough that no streamer should be pinning a CPU for it. Configure the streaming and recording encoders separately - you want a constrained bitrate for the platform and a near-lossless one for your local master:

OBS Studio > Settings > Output  (Advanced mode)
[Streaming]
  Encoder ............ NVIDIA NVENC HEVC   (H.264 for Twitch compatibility)
  Rate Control ....... CBR
  Bitrate ............ 8000 Kbps  (1080p60)  |  12000-15000 (1440p60)
  Keyframe Interval .. 2 s
  Preset ............. P5: Quality
  Profile ............ high
  Psycho Visual Tuning true

[Recording]
  Type ............... Standard
  Format ............. hybrid MP4  (or MKV for crash safety)
  Encoder ............ NVIDIA NVENC HEVC
  Rate Control ....... CQP
  CQ Level ........... 18            # visually lossless-ish local master

Bitrate, Canvas, and Downscale

Set your base (canvas) resolution to 3840x2160 to match the capture, and your output (scaled) resolution to 1920x1080 for the stream, using Lanczos as the downscale filter for the sharpest result. Downscaling a clean 4K capture to 1080p looks dramatically better than capturing 1080p natively, because you are supersampling. For bitrate, 8000 Kbps is the comfortable 1080p60 figure on both Twitch and YouTube; push 12000-15000 for 1440p60 on YouTube, which is more generous than Twitch. When the device initializes correctly, the OBS log confirms it - this is the expected output you want to see:

info: [DShow Device: 'PS5'] settings updated:
    video device: AVerMedia Live Gamer ULTRA 2.1
    resolution: 3840x2160
    fps: 60.00 (interval: 166666)
    format: NV12
    color space: 709
    color range: partial
info: Video output info reset:
    base resolution:   3840x2160
    output resolution: 1920x1080
    fps:               60.00

If that log shows 1920x1080 as the base resolution or 30.00 fps, your source is misconfigured - go back to step 9 and force the custom resolution.

The Preview-Latency Trap

Say it with me: you never play off the OBS preview. That preview window carries 30 to 70 milliseconds of processing and USB latency - fatal for anything with a reaction component and merely annoying for everything else. The passthrough HDMI out exists precisely so you can watch a real, near-instant screen while OBS quietly captures a delayed copy. The delay in the preview is not a fault to fix; it is physics. Play from your TV or monitor, let OBS lag behind, and stop trying to reconcile the two. This single misunderstanding produces more 'my capture card adds input lag' complaints than any hardware defect ever has.

Five Common Pitfalls

These are the conceptual mistakes - the ones that are not a single broken setting but a wrong mental model. Fix the model and the settings follow.

Buying and Bandwidth Mistakes

Pitfall 1: Paying the HDMI 2.1 premium for a 60fps broadcast. Spending $299 on a GC553G2 when a $120 CU4K30 or $160 4K S would deliver an identical-looking stream is the most common money mistake. The fix: buy HDMI 2.1 only if you personally play on a 120Hz or VRR monitor and want that feel preserved while you stream. Otherwise the money is wasted on a passthrough spec your audience never sees.

Pitfall 2: Starving a fast card on slow USB. A high-bandwidth 4K60 card behind a USB 2.0 port, a front-panel header, or an unpowered hub will drop frames endlessly. The fix: rear-panel USB 3.0 (blue), straight to the motherboard. The exception - and it is a real one - is the onboard-encoder cards like the GC311 and GC513, which are designed for USB 2.0 because they compress before the cable and never need the bandwidth.

Signal and Color Mistakes

Pitfall 3: Forgetting HDCP and blaming the hardware. A black screen after a flawless wiring job is almost always HDCP still enabled on the PS5. The fix is step 6, every time. Before you RMA a card or swap a cable, check the toggle.

Pitfall 4: Mismatched color range, i.e. grey blacks. The PS5 outputs limited-range HDMI; if OBS is set to Full range, your blacks lift to a washed grey and your highlights clip. The fix: set Color Range to Limited (Partial) in the device properties to match. For HDR content, capturing HDR10 as SDR produces a flat, desaturated image - use the P010 format and Rec. 2100 color space, or simply set the PS5's HDR to Off and capture clean SDR.

Workflow Mistakes

Pitfall 5: Letting the vendor app fight OBS for the device. Elgato's 4K Capture Utility and AVerMedia's Streaming Center each grab exclusive control of the card. Run one alongside OBS and you get 'device in use' or a black source. The fix: close the vendor app entirely before launching OBS; only one application may own a UVC device at a time.

Pitfall 6: Skimping on the cable for a 4K120 dream. A non-certified or 18 Gbps cable on a 4K120 passthrough attempt yields intermittent signal loss that mimics a failing card. The fix: two certified 48 Gbps Ultra High Speed cables for any 4K120/VRR chain. This is a five-minute diagnosis that people spend a week misattributing to the console.

Troubleshooting Table

Symptom-first, because that is how failures actually present. Find your symptom, apply the fix, move on. Twelve of the most common ones:

Black Screens and HDCP

The top three rows of that table are all the same root problem wearing different hats: the card is receiving a signal it is not permitted to show. Full-screen black is global HDCP - fix it in the menu. Black that appears only during a specific game's pre-rendered cutscene is that publisher choosing to flag its own footage, which no setting on your end overrides; you record around it. And the Netflix casualty is the intended, documented consequence of disabling HDCP, not a malfunction. If capture worked yesterday and is black today, the first question is always: did HDCP get re-enabled by a system update or a settings reset?

Stutter and Bandwidth

Dropped frames that appear only in the capture while the passthrough screen stays perfectly smooth are diagnostic gold: the console and card are fine, and the USB path or the encoder is the culprit. Rule out the port first - move to a known-good rear USB 3.0 connector - then the encoder. If OBS reports rendering or encoding lag in its stats dock, you are asking too much of the CPU; move to hardware encoding and, if needed, drop the output to 1080p. Persistent PS5-side hitching that also shows on the passthrough TV is a different animal and points back at the console itself; if that is your situation, a PS5 cache clear from Safe Mode is the cheap first move before you suspect the capture chain at all.

Color, HDR, and Audio

Color problems are almost always a range or format mismatch, not a defective card. Grey, milky blacks mean Full-vs-Limited range disagreement; a green or magenta cast on HDR content means you captured a PQ HDR signal as if it were SDR. The pragmatic answer for most streamers is to leave HDR off on the console and capture clean, predictable SDR, because HDR tone-mapping to an SDR stream is a rabbit hole that rarely survives platform re-encoding anyway. Audio drift, meanwhile, is a buffering artifact: nudge the audio sync offset on the capture source by 30 to 120 milliseconds until lips and words agree.

Advanced Tips

Once the basic chain works, here is where the quality and the resilience live. None of this is required. All of it separates a stream that looks fine from a recording you would keep.

The Dual-PC Rig

The cleanest high-end setup splits the load across two machines: the PS5 feeds a capture card in a dedicated streaming PC that does nothing but encode and broadcast, while your gaming happens elsewhere entirely. Because the encoding box is not also rendering a game, you can run a heavier encoder preset - even x264 slow, or high-bitrate AV1 - without a single dropped frame. An internal card like the Elgato 4K Pro shines here, sitting in the streaming tower with 8K60 passthrough headroom and no USB bottleneck. This is overkill for most, and it is exactly what full-time broadcasters run. If you are building a rig you will sit at for eight-hour streams, the one non-negotiable that is not a computer is the chair - our 2026 gaming chair rundown exists for a reason, and your spine will file a complaint otherwise.

AV1, HEVC, and Local Masters

If your GPU is an NVIDIA 40- or 50-series or a modern Intel Arc, you have hardware AV1 - roughly 30 percent more efficient than H.264, meaning better image quality at the same bitrate. YouTube ingests AV1; Twitch's support has expanded but H.264 remains the safe default there. For your local recording, forget bitrate ceilings entirely and record HEVC at CQP 18, or lower, to keep a near-lossless master you can edit and re-export. Record to MKV rather than MP4 so a crash mid-stream does not corrupt the whole file - MKV is recoverable, MP4 is not - then remux losslessly to MP4 afterward for editors that demand it. Verify that your 'master' is actually the resolution you think it is, because a silent negotiation to 1080p is common and invisible until you open the file:

# Confirm a recording captured 4K60, not a silent downscale
ffprobe -v error -select_streams v:0 -show_entries stream=width,height,r_frame_rate,codec_name -of default=noprint_wrappers=1 ps5_capture.mp4

# Expected output:
#   codec_name=hevc
#   width=3840
#   height=2160
#   r_frame_rate=60/1

# Remux an MKV master to MP4 with no re-encode (crash-safe workflow):
ffmpeg -i recording.mkv -c copy recording.mp4

Recording Without a PC

Not every capture job needs a computer running. The standalone cards - AVerMedia's GC513 to a microSD card, or ClonerAlliance's UHD Pro and Halo to internal storage - record the PS5 directly to a card with the console as the only other device in the room. It is the right tool for a tournament, a spare-room setup, or anyone who finds OBS more friction than the footage is worth. The tradeoff is obvious: no overlays, no live streaming, no real-time commentary mix, and capture ceilings that top out at 1080p60 (GC513) or 4K30 (ClonerAlliance). For pure archival of your own play with zero PC overhead, it is underrated. For broadcasting, it is a dead end - which is why the standalone niche stays a niche.

The Complete Configuration

Everything above, compressed into one copy-and-keep reference. If you read nothing else, wire it like this, set the console like this, configure OBS like this, and verify like this.

The Reference Rig

=== STARESBACK REFERENCE RIG: PS5 -> Card -> PC -> Twitch/YouTube ===

WIRING
  PS5 HDMI OUT ---[48 Gbps cable]--> Card HDMI IN
  Card HDMI OUT --[48 Gbps cable]--> Monitor/TV   (you watch THIS, never OBS)
  Card USB-C -----[rear USB 3.0 port]--> PC

PS5
  System > HDMI > Enable HDCP ............ OFF
  Screen and Video > Resolution .......... 2160p
  Screen and Video > VRR ................. Automatic (2.1 card) / Off (2.0)

OBS (31.x, Advanced output)
  Source: Video Capture Device @ 3840x2160 / 60 / NV12, Buffering OFF
  Canvas 3840x2160  ->  Output (scaled) 1920x1080, filter = Lanczos
  Stream: NVENC HEVC/H.264, CBR, 8000 Kbps, keyint 2s, P5 Quality
  Record: NVENC HEVC, CQP 18, MKV (remux to MP4 after)
  Settings > Video > FPS: 60 Integer  |  59.94 if mixing NTSC sources

VERIFY
  ffprobe the first recording -> width=3840 height=2160 r_frame_rate=60/1
  Play from the TV, not the preview (30-70 ms card latency is normal)

The Verification Checklist

Run this once and you will never wonder whether it is 'really' working. First, the passthrough TV shows the game live with no perceptible input lag - if it lags, you are somehow watching the preview or the card is in a software-passthrough mode; fix that before anything else. Second, the OBS log reports the source at 3840x2160 and 60.00 fps, not 1080p or 30fps. Third, a five-second test recording, run through ffprobe, returns width=3840, height=2160, and r_frame_rate=60/1. Fourth, HDCP is off and you have accepted that Netflix is temporarily broken as the price of admission. If all four hold, the rig is correct and every remaining problem is a settings tweak, not a wiring fault.

The One-Paragraph Summary

There is no PS5 capture card; there is a general HDMI card you point at a PS5. For a 60fps stream, HDMI 2.0 is all you need, which means the $159.99 Elgato 4K S or the ~$120 Asus CU4K30 does the job the $299.99 GC553G2 does, minus a 120Hz passthrough you will not broadcast. Disable HDCP, force your resolutions in OBS instead of trusting the defaults, encode on the GPU, watch your real screen and not the preview, and keep a CQP-18 HEVC local master alongside the 8000 Kbps stream. Do that and you have a rig that outperforms most of what the syndicated buyer's guides describe - including the ones quoting a SKU that does not exist and a price that is off by a hundred and thirty dollars. Precision is the whole job. The card is the easy part.