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

Here is the joke at the center of every PlayStation capture guide, and almost nobody tells it to you straight: the single most consequential step in recording your PS5 is a toggle that Sony itself built, labeled in plain English, and buried four menus deep precisely so you would not find it by accident. You are not hacking anything. You are not voiding a warranty. You are switching off a feature whose entire purpose is to stop you from doing the thing the console manufacturer is, by shipping the off switch, quietly admitting you are allowed to do. Welcome to capture cards, where the hardware is the easy part and the legal theater is the obstacle.

This is a tutorial, not a sales brochure. By the end you will have a PS5 outputting a clean signal, a capture card passing it to both your television and your PC, and OBS Studio rendering it at the highest resolution your card and your USB bus can honestly sustain. We are going to do it in fourteen numbered steps and roughly forty minutes, most of which is driver installs and one trip into a settings menu Sony hopes you ignore. Everything here is grounded in 2025–2026 hardware, current OBS, and the unglamorous physics of how many gigabits actually fit down a cable.

Why the PS5 Fights Your Capture Card

Before you spend $210, understand the adversary, because three quarters of "my capture card doesn't work" posts are not hardware failures. They are content protection doing exactly what it was designed to do, and a user who never disabled it.

HDCP Is a Lock You Already Own the Key To

High-bandwidth Digital Content Protection is a copy-protection handshake that rides along the HDMI cable between source and display. It was developed by Intel and is administered by Digital Content Protection, LLC; the master key leaked publicly in September 2010, which tells you everything about how durable the scheme really is. The PS5 applies HDCP across its entire HDMI output by default, which is why your brand-new capture card shows a black rectangle the first time you plug it in. The card receives the video, sees a protected stream it is not licensed to decrypt and re-transmit, and refuses. That is not a bug. That is the card obeying the law.

The relevant law, for the curious, is the anti-circumvention clause of the Digital Millennium Copyright Act — 17 U.S.C. § 1201 — which makes defeating a protection measure a problem. The elegant part of the PS5 workflow is that you never defeat anything. You ask Sony to stop applying the protection, and Sony complies, because Sony is a content company that also sells a games console and has correctly concluded that people streaming Astro Bot to ninety viewers sells more hardware than a stray DRM lawsuit ever could. The off switch exists because the people who make movies and the people who make consoles are, occasionally, the same people, and the console side won the argument.

Capture vs. Passthrough: They Are Not the Same Number

The most expensive misunderstanding in this hobby is reading a box that says "4K60" and assuming it means the card records 4K60. Often it means the card passes 4K60 to your TV while recording something lower. Passthrough is a wire that splits the signal toward your display; capture is the data the card digitizes and hands to your PC. A card can do 4K120 passthrough so your television stays gorgeous while it only captures 1080p60, because capture is bottlenecked by the USB bus and the onboard chip, not by the HDMI input. Every spec line you read in the next section needs to be parsed as two separate numbers, and the smaller one is the one you actually stream.

What "Works With PS5" Actually Means in 2026

The PS5 and PS5 Pro output up to 4K120 and, on the Pro, flirt with 8K signaling over HDMI 2.1. According to IGN's 2025 capture-card guide, full 4K60 compatibility with the PS5 Pro is gated on the card supporting HDMI 2.1. That is true for the passthrough leg in the strict sense — a 4K60 SDR capture signal at 4:4:4 lands around 17.8 Gbps and squeezes inside HDMI 2.0's 18 Gbps envelope, but the moment you want 4K120, VRR, or the Pro's richer HDR pushed through to your screen, you are over budget and need 2.1's 48 Gbps headroom. "Works with PS5" therefore means three things at once: it disables cleanly via HDCP-off, it captures a resolution you can live with, and it passes through whatever your television deserves. Miss any one and the card is wallpaper.

Prerequisites: What You Actually Need

Read this list before you buy anything. The cable section in particular is where people who spent $210 on a card then sabotage it with a $4 cable from a gas station.

Hardware Checklist

You need a PS5 or PS5 Pro, a capture card (model choices below), a Windows PC with a real USB 3.0 port, a television or monitor for passthrough, and two HDMI cables that are not lying about their bandwidth. On the PC side, capturing 4K60 is not free: budget for a six-core CPU from the last few years and, ideally, a discrete GPU with a hardware encoder — NVIDIA NVENC on RTX cards, AMD's VCN, or Intel Quick Sync — so your processor is not simultaneously playing nothing and encoding everything. Per NearStream's own 2025 setup guide, the CCD30 specifically wants a Windows PC and warns that Macs may hit driver limitations, which is the polite way of saying do not do this on a MacBook and then file a support ticket.

Software and Versions

Install OBS Studio 31.x — the 2025 release line — or newer; we walk the full broadcaster build in our companion piece on why Twitch Studio is dead and OBS v31 is the replacement. Run Windows 11 24H2 or newer, or Windows 10 22H2 if you are stubborn. Install the manufacturer's current capture driver and, optionally, FFmpeg 7.x for diagnostics, because when OBS lies to you, FFmpeg tells the truth. Update the PS5 to Sony's latest 2026 system software before you start; an out-of-date console occasionally renegotiates HDMI in ways that strand the card.

Cables: The Part Everyone Cheaps Out On

The CCD30 ships with one certified HDMI 2.1 cable and, per NearStream, expects two certified 2.1 cables in the chain — one PS5-to-card, one card-to-display. "Certified 48 Gbps Ultra High Speed" is a real certification with a real hologram label, not marketing vapor. A cable that physically fits and carries 1080p fine will silently drop to a lower link rate at 4K60 and hand you sparkles, dropouts, or a blank screen that you will spend an hour blaming on software. Here is the bill of materials as a config you can shop against:

# PS5 4K60 CAPTURE — BILL OF MATERIALS
console          = PS5 / PS5 Pro (latest 2026 firmware)
capture_card     = 4K60 class (e.g. NearStream CCD30, $210)
host_pc          = Windows 11 24H2+ , 6-core CPU , dGPU w/ HW encoder
host_port        = USB 3.0 (5 Gbps) min ; USB 3.2 Gen2 (10 Gbps) better
display          = TV / monitor for passthrough leg
cable_1          = HDMI 2.1 Ultra High Speed, 48 Gbps  (PS5 OUT -> card IN)
cable_2          = HDMI 2.1 Ultra High Speed, 48 Gbps  (card OUT -> display)
usb_cable        = USB 3.x data cable (NOT a charge-only cable)
software         = OBS Studio 31.x+ , vendor driver , FFmpeg 7.x (optional)

Picking the Card: 2026 Models by Reality

There is no single best capture card, only the best card for your resolution ceiling, your budget, and your tolerance for marketing. The market in 2026 sorts cleanly into three tiers. If 1080p60 is genuinely your ceiling — and for most streamers on most platforms, it is — read our focused 1080p60 capture card walkthrough and save yourself a hundred dollars.

The 4K60 Tier

This is where the CCD30 lives. NearStream's card runs $210, captures and passes 4K60, and is HDMI 2.1 native, which is the cleanest single answer to "what do I buy" in 2025–2026. The MidnightMan "Ultimate Capture Card Tier List (2026)" on YouTube, which ranks eighteen cards by price-to-performance to seventy-five thousand viewers, lands the CCD30 at $210 in its top bracket alongside the AVerMedia Live Gamer 3 Extreme at $147–$200. The Elgato HD60 X — listed in 2025 at roughly €175–€220, about $190–$240 — is the only Elgato worth your money for PS5 specifically, owing to its 4K60 capture and a price barely above the older HD60 S+. IGN's 2025 top-six also names the Asus TUF CU4K30 (4K60 passthrough; the "30" in the name is the capture ceiling, so read it as 4K30 capture, 4K60 to your TV), the EVGA XR1 Pro for 4K HDR recording, and the AVerMedia GC513 Live Gamer Portable 2 Plus, a USB 3.0 portable rated for 4K60 HDR capture.

The 1440p / 4K30 Middle

The AVerMedia Live Gamer 3 Extreme is the versatile pick here: it records at 1440p60 or 4K30 while passing 4K60 or 2K144 to your display, at €150–€200 (about $165–$220). That split — 1440p60 capture, 4K60 passthrough — is the honest sweet spot for high-resolution streaming, because 1440p60 is a genuinely great stream and 4K30 is a slideshow nobody asked for. The late-2025 Elgato 4K X belongs in this conversation with an asterisk the size of a billboard: it passes through 4K60, 2K144, and even 1080p240, but it does not capture 4K120, because it is HDMI 2.0, not 2.1. If you bought a PS5 Pro to push 4K120 and assumed any "4K X" card would record it, that asterisk just cost you the upgrade.

The Budget Floor

The AVerMedia Live Gamer Mini does 1080p60 recording and 1080p60 passthrough and nothing more, which is exactly the right card for a streamer who values cost over resolution and would rather spend the difference on a better microphone — a trade that improves the broadcast more than pixels ever will. Here is the tier sheet:

One arithmetic note that governs every "4K60 over USB 3.0" claim above: a 4K60 frame in NV12 is roughly six gigabits per second, and USB 3.0's real-world ceiling is around four. So any 4K60 card on a 5 Gbps bus is compressing the stream before it reaches your PC. That is not an accusation against any specific product; it is arithmetic. Want a pristine, uncompressed feed over plain USB 3.0? Stay at 1080p60, where NV12 is about 1.5 Gbps and fits with room to spare.

Steps 1–4: Disable HDCP, Prep the PS5

Everything that follows assumes the PS5 is on, connected to a working display through your normal HDMI port, and updated. We do the console first because a misconfigured console produces a black screen on the card that looks identical to a dozen unrelated failures.

Step 1: Update the PS5 System Software

Navigate to Settings > System > System Software > System Software Update and Settings, and install whatever Sony's 2026 firmware offers. Rationale: HDMI link negotiation and HDCP behavior have shifted across firmware revisions, and an out-of-date console occasionally renegotiates the link in ways that strand a downstream card. Updating first removes a variable you do not want to debug at 11 p.m. Reboot when prompted; do not skip the reboot.

Step 2: Disable HDCP in Settings > System > HDMI

Go to Settings > System > HDMI and turn off Enable HDCP. The console will warn you, briefly black out, and renegotiate the link. Rationale: this is the entire ballgame. With HDCP on, the card sees a protected stream it cannot legally re-transmit and gives you a black frame. With it off, gameplay flows to the card unprotected. The cost, by design, is that the PS5 will now refuse to play HDCP-protected video — Netflix, Disney+, a 4K Blu-ray — until you switch it back on. Games do not care; protected movies do. That trade is the whole mechanism. Both NearStream's guide and IGN's flag this as mandatory, and it is the first thing to re-check whenever capture goes dark.

Step 3: Set Resolution and HDR Manually

In Settings > Screen and Video > Video Output, set Resolution to match what your card can actually capture — 2160p for a true 4K60 card, 1440p or 1080p otherwise — and set HDR to "On When Supported" or "Off" depending on whether your card and OBS pipeline handle HDR end to end. Rationale: the PS5's automatic negotiation reads the EDID of whatever is downstream and sometimes picks a mode the card passes but cannot capture, or an HDR mode that arrives in OBS as a washed-out, grey-black mess because nothing in the chain tone-maps it. Pinning the output manually removes that guesswork. If you are unsure about HDR, set it Off for your first successful capture and add it back deliberately later.

Step 4: Verify the Output Signal

Settings > Screen and Video > Video Output > View Signal Information shows the exact resolution, frame rate, and color format the console is sending. Rationale: this screen is ground truth. If it reports 2160p 60Hz RGB but OBS later shows 1080p, the bottleneck is the card or the USB bus, not the console — and you have just saved yourself from "upgrading" a cable that was never the problem. Record what it says. Pin these settings as the PS5 half of your configuration:

# PS5 OUTPUT (Settings menus)
System > HDMI > Enable HDCP ............ OFF   # mandatory for capture
Screen and Video > Resolution .......... 2160p (match card capture cap)
Screen and Video > HDR ................. Off  (first run) -> On When Supported
Screen and Video > RGB Range ........... Limited   # match in OBS later
Screen and Video > Deep Color Output ... Automatic
View Signal Information ................. confirm 2160p / 60Hz / RGB before moving on

Steps 5–8: Build the Capture Chain

Now the wires. The order matters less than the orientation: source out to card in, card out to display in, card to PC by USB. Get one of those backwards and you get a black screen that no software setting will fix.

Step 5: Connect PS5 HDMI Out to Capture In

Run certified cable one from the PS5's HDMI OUT to the port on the card explicitly labeled IN (sometimes "PS5" or "Console"). Rationale: capture cards have two HDMI ports that look identical and are not. IN takes the source; OUT feeds the display. Reverse them and the card receives nothing while dutifully sending a blank frame to your TV. This single mistake accounts for a startling share of "dead on arrival" returns. Use the cable that shipped with the card for this leg first, since you know it is certified.

Step 6: Run Passthrough to Your Display

Run certified cable two from the card's HDMI OUT to your television or monitor. Rationale: passthrough is what lets you actually play with low latency on your big screen while the card siphons a copy to your PC. Without it you would be staring at the OBS preview, which carries encode-and-display latency measured in tens to hundreds of milliseconds — fine for a cooking stream, fatal for a fighting game. This leg is also where PS5 Pro owners chasing 4K120 or VRR need genuine HDMI 2.1; if your card is 2.0-class here, your TV silently drops to 4K60. Future-proofing this leg is one reason buyers eye what is coming — see our read on the PlayStation 6 release window and its $599 target before sinking money into a chain you will rebuild in three years.

Step 7: Connect the Card to Your PC via USB 3.0

Plug the card into a USB 3.0 (or faster) port on your PC using a data-capable USB cable. Rationale: USB 3.0 ports are usually blue or labeled "SS" for SuperSpeed; USB 2.0 ports next to them will enumerate the card and then refuse to deliver high resolutions, because 480 Mbps does not carry 4K anything. Equally important, many bundled USB-C cables on phones and accessories are charge-only with no data lines — they power the card's LED and transmit zero video, producing a device that lights up and does nothing. Use the cable that came with the card, and prefer a port wired directly to the chipset over a front-panel hub.

Step 8: Install Drivers and Confirm Enumeration

Install the manufacturer's current driver, then confirm Windows sees the card. Rationale: without the driver, the card may appear as a generic, half-working UVC device or not at all. The fastest neutral check is FFmpeg's DirectShow device list, which queries Windows directly and bypasses whatever OBS thinks is true. Run this in a terminal:

ffmpeg -f dshow -list_devices true -i dummy

Expected output — your card listed under both video and audio devices:

[dshow @ ...] DirectShow video devices (some may be both video and audio devices)
[dshow @ ...]  "NearStream CCD30 Video"
[dshow @ ...     Alternative name "@device_pnp_\\?\usb#vid_..."
[dshow @ ...] DirectShow audio devices
[dshow @ ...]  "NearStream CCD30 Audio"
[dshow @ ...     Alternative name "@device_cm_{...}"

If both lines appear, Windows and the driver are healthy and the rest is software. If they do not, stop here and fix enumeration before touching OBS; no amount of OBS configuration resurrects a card the operating system cannot see. FFmpeg's device syntax is documented at the FFmpeg devices reference if you want to script captures later.

Steps 9–14: Configure OBS Studio

OBS is where most of the forty minutes evaporates, not because it is hard but because the defaults are conservative and the menus assume you know what NV12 and Rec.709 mean. You will after this section. OBS's own documentation lives in the OBS Knowledge Base, and the source is open at the OBS Studio GitHub if you ever need to read what a setting truly does.

Step 9: Add a Video Capture Device Source

In the Sources panel, click the plus, choose Video Capture Device, name it something honest like "PS5 Capture," and select your card from the Device dropdown — "CCD30," "Game Capture HD60 X," or whatever the driver registered. Rationale: this is the one step every guide agrees on, including NearStream's, because it is the moment gameplay first appears in the OBS canvas. If the dropdown is empty, the driver failed; go back to Step 8. If the device is greyed out as "in use," another application — the vendor's own capture app, a browser tab, Discord's screen-share, or a second OBS instance — has grabbed it exclusively. Close that application; capture devices generally allow only one consumer at a time.

Step 10: Set Resolution, FPS, and Buffering

In the source's properties, set Resolution/FPS Type to Custom, then set the resolution to your card's real capture ceiling and FPS to "Highest FPS" or an explicit 60. Rationale: left on "Device Default," OBS frequently selects a safe 1080p30 even from a 4K60 card, and you stream a downgrade you paid to avoid. Disable Buffering while you are here unless you have a specific sync reason to keep it; buffering trades latency for smoothness and, on a healthy USB 3.0 chain, you want the latency back. Here is the source configuration as a readable block:

# OBS > Sources > Video Capture Device > Properties
Device ................. NearStream CCD30 (Video)
Resolution/FPS Type .... Custom
Resolution ............. 3840x2160        # or 2560x1440 / 1920x1080
FPS .................... Highest FPS (60)
Video Format ........... NV12             # if NV12 caps at 30, try MJPEG
Color Space ............ 709              # Rec.709
Color Range ............ Partial (Limited) # MUST match PS5 RGB Range
Buffering .............. Disable
Audio Output Mode ...... Output desktop audio (DirectSound)

Step 11: Configure Color Space and Range

Set Color Space to 709 and Color Range to Partial (Limited) — assuming you set the PS5's RGB Range to Limited in Step 3 — or Full if you chose Full there. Rationale: the single most common "my capture looks washed out / crushed / pinkish" complaint is a range mismatch. When the source sends Limited (16–235) and OBS interprets it as Full (0–255), blacks go grey and whites clip; reverse the mismatch and shadows turn to mud. The two ends must agree. If you are unsure, set both to Limited, which is what consoles default to, and your greys will be grey instead of accusatory.

Step 12: Set the Canvas and Output Resolution

In Settings > Video, set Base (Canvas) Resolution to your capture resolution and Output (Scaled) Resolution to what you intend to broadcast — often 1920x1080 even from a 4K capture. Set Common FPS to 60, integer, not 59.94. Rationale: canvas is your editing space; output is what viewers receive. Capturing at 4K and scaling to 1080p in OBS yields a visibly sharper 1080p than capturing at 1080p directly, because downscaling supersamples away aliasing — this is the one place "capture higher than you stream" genuinely pays off. Pick the Lanczos downscale filter for the cleanest result if your GPU can spare it.

Step 13: Tune the Encoder and Bitrate

In Settings > Output, switch to Advanced mode, pick a hardware encoder — NVENC HEVC or AV1 on recent NVIDIA cards, otherwise x264 — set Rate Control to CBR for streaming, and choose a bitrate your platform will accept. Rationale: software x264 on "veryfast" steals CPU from everything else; a hardware encoder offloads that to dedicated silicon and frees your machine. Twitch's traditional ceiling for most channels sits near 6,000–8,000 Kbps; YouTube will accept far more; local recording can run as high as your disk tolerates. Keyframe interval of 2 seconds keeps platforms happy. The encoder block:

# OBS > Settings > Output (Advanced) > Streaming
Encoder ............... NVIDIA NVENC HEVC   # or AV1 / x264
Rate Control .......... CBR
Bitrate ............... 8000 Kbps  (1080p60)  | 12000-25000 (1440p60)
Keyframe Interval ..... 2 s
Preset ................ P5: Quality  (NVENC)  | veryfast (x264)
Profile ............... high
Psycho Visual Tuning .. On
Look-ahead ............ On
Max B-frames .......... 2
# Recording tab: same encoder, much higher bitrate, or use CQP 18-20

Step 14: Add Audio and Test the Full Chain

Confirm the card's audio device feeds OBS — either through the Video Capture Device's audio passthrough or as a separate Audio Input Capture — set all sample rates to 48 kHz, and record a thirty-second clip. Rationale: audio sample-rate mismatches (44.1 kHz somewhere, 48 kHz elsewhere) cause slow drift where lips desync minutes into a stream — invisible in a ten-second test, infuriating in a two-hour one. A short recording validates video, audio, and sync together before you go live. Open OBS's own log afterward; the relevant lines read like this:

info: [Video Capture Device 'PS5 Capture']: Selected device 'NearStream CCD30 Video'
info:   settings:
info:     resolution: 3840x2160
info:     fps: 60.00 (interval: 166666)
info:     format: NV12
info:     color range: Partial, color space: 709
info: ---------------------------------
info: [dshow] settings updated
info: Output 'adv_stream': stopping
info:   Number of dropped frames due to insufficient bandwidth/connection: 0 (0.0%)

That "0 dropped frames" line is the certificate of a healthy chain. If it climbs, your problem is bandwidth or USB, not configuration. When a log baffles you, paste it into the OBS Log Analyzer, which flags the usual suspects automatically.

Five Pitfalls That Eat Your Evening

These are the failures that look like hardware death and are not. Each has a fix that takes seconds once you stop blaming the card.

Signal Pitfalls

Pitfall 1 — Black screen with working audio. You hear the game but see black. HDCP is still on, or a protected app (a streaming service, a Blu-ray) is foregrounded on the PS5. Fix: re-confirm Settings > System > HDMI > Enable HDCP is OFF, and exit any video app back to a game. Games pass; movies do not. Pitfall 2 — Black screen with no audio and the card's light on. The HDMI ports are reversed. Fix: the PS5 must reach the port labeled IN; the display hangs off OUT. Swap the two HDMI cables at the card. This is the number-one cause of "DOA" returns that were never broken.

Color and HDR Pitfalls

Pitfall 3 — Washed-out, grey-black, or pink-tinted picture. A color range or space mismatch between source and OBS. Fix: make the PS5's RGB Range and OBS's Color Range agree (both Limited is the safe default), and set OBS Color Space to 709. Pitfall 4 — Dim, lifeless HDR capture. You left HDR on without a tone-mapping step, so a wide-gamut signal is being displayed as if it were standard. Fix: either disable HDR on the PS5 for SDR streaming, or insert an HDR-to-SDR LUT or OBS's HDR tone-mapping and verify your whole chain — card, OBS, output platform — actually carries HDR. Most viewers watch in SDR; do not ship them grey mud.

USB and Driver Pitfalls

Pitfall 5 — Captures 4K passthrough fine but only records 1080p, or drops frames at 4K60. The USB bus is the bottleneck, not the HDMI input. Fix: move the card to a USB 3.0+ port wired directly to the chipset, off any shared hub, and confirm it negotiated 5 Gbps and not USB 2.0's 480 Mbps. Remember the arithmetic: uncompressed 4K60 wants more than USB 3.0 honestly provides, so if your card lacks hardware compression, 1440p60 or 1080p60 is the real ceiling and no port change will fix physics. Bonus pitfall: a "device in use" error means the vendor's capture app, a browser, or Discord grabbed the card first — close it.

Troubleshooting: The Symptom Table

When the fast fixes above do not land, work the table. Read your symptom, suspect the cause, apply the fix, and change one variable at a time.

How to Read the Logs First

Before you swap anything, open OBS's log via Help > Log Files > View Current Log, or the FFmpeg device list from Step 8. Logs distinguish "OBS never saw the device" from "OBS saw it and chose a bad mode" from "the link dropped frames," and those three point at completely different fixes. Guessing without the log is how you buy a cable you did not need.

The Symptom Table

When to Suspect the Cable

Suspect the cable last, but do suspect it. A cable that carries 1080p flawlessly can silently fail to train a 4K60 link, producing intermittent sparkles, periodic black-outs every few seconds, or a resolution that refuses to climb past 1080p no matter what the menus say. Swap in a known-good certified 48 Gbps cable as a clean test before you conclude the card is defective. The OBS community has seen every variant of this; the OBS forums are searchable and your exact card-plus-symptom string has almost certainly been posted before.

Advanced Tips: Bitrate, Color, Latency

Once the chain works, the difference between an amateur stream and a clean one is three numbers and a couple of habits. None of this is mandatory; all of it is visible.

Bitrate Math That Doesn't Lie

Bitrate is not a vibe; it is bits per second, and resolution and motion set the floor. A fast-moving 1080p60 stream needs meaningfully more bitrate than a static 1080p30 talking-head to avoid the smeared, blocky look in explosions and foliage. As a working baseline at 60 fps: 1080p wants roughly 6,000–8,000 Kbps, 1440p wants roughly 12,000–25,000, and local 4K recording climbs from there. Use CBR for live streaming so the platform's buffer stays fed, and CQP or CRF around 18–20 for local recordings where you want quality over a predictable file size. The table:

Color Space, Range, and the Washed-Out Look

For SDR streaming, keep the entire chain on Rec.709 with matched Limited range and stop touching it; consistency beats cleverness. If you commit to HDR, commit fully — an HDR capture source, OBS configured for HDR with proper tone-mapping for SDR viewers, and an output platform that actually delivers HDR — or you ship the worst of both worlds: a dim SDR picture that paid the HDR bandwidth tax for nothing. The honest move for most 2026 streamers is SDR at 709, because the median viewer is on a phone or a midrange monitor that cannot show HDR anyway.

Latency: Why Your Passthrough Beats Your Preview

Always play off the passthrough display, never the OBS preview. Capture, encode, and re-display add latency that ranges from tolerable to game-losing, and the passthrough leg sidesteps all of it by handing the raw signal straight to your screen. If you must monitor in OBS — for a single-screen setup — enable the preview only when composing scenes, not while playing anything reflex-dependent. And if you find yourself fighting hardware latency at every turn, ask whether you need a capture card at all: PS Remote Play streams the console to a PC with zero capture hardware, and we benchmark that path in our guide to PS Remote Play at 1080p HQ in twelve steps. It re-encodes and adds its own latency, so it is a different tool for a different job — but for a 1080p chat stream, it is free and the card is not.

The Complete Working Configuration

Here is the entire setup in one place — console, cables, USB, and OBS — the configuration this tutorial builds toward. Copy it, adjust the resolution numbers to your card's real ceiling, and you have a reproducible 4K60 (or honest 1440p60) capture rig.

The Full Dump

# ===== PS5 SIDE =====
System > System Software ................ latest 2026 firmware, rebooted
System > HDMI > Enable HDCP ............. OFF
Screen and Video > Resolution .......... 2160p   (= card capture cap)
Screen and Video > HDR ................. Off (SDR) | On When Supported (HDR rig)
Screen and Video > RGB Range ........... Limited
View Signal Information ................ confirm 2160p / 60Hz before trusting OBS

# ===== PHYSICAL CHAIN =====
PS5 HDMI OUT  --[48 Gbps 2.1 cable]-->  CARD IN
CARD OUT      --[48 Gbps 2.1 cable]-->  TV / MONITOR   (play off THIS screen)
CARD USB      --[USB 3.0+ data cable]-> PC (chipset port, not a hub)

# ===== OBS: SOURCE =====
Video Capture Device ... "PS5 Capture"
  Device ............... NearStream CCD30 (Video)
  Res/FPS Type ......... Custom
  Resolution ........... 3840x2160     # 2560x1440 / 1920x1080 if lower card
  FPS .................. 60 (Highest FPS)
  Video Format ......... NV12          # MJPEG only if NV12 caps at 30
  Color Space .......... 709
  Color Range .......... Partial (Limited)   # MATCH the PS5
  Buffering ............ Disable

# ===== OBS: VIDEO =====
Base (Canvas) ........ 3840x2160
Output (Scaled) ...... 1920x1080      # supersamples to a sharp 1080p
Downscale Filter ..... Lanczos
FPS .................. 60 (integer)

# ===== OBS: OUTPUT (Advanced > Streaming) =====
Encoder .............. NVIDIA NVENC HEVC   # AV1 if supported; else x264 veryfast
Rate Control ......... CBR
Bitrate .............. 8000 Kbps          # raise to 12000-25000 for 1440p60
Keyframe Interval .... 2 s
Preset ............... P5: Quality
Profile .............. high
Psycho Visual ........ On
Audio ................ 48 kHz everywhere, 160-256 Kbps AAC

# ===== SANITY CHECK =====
ffmpeg -f dshow -list_devices true -i dummy   # card must list under video AND audio
# OBS log must read: "Number of dropped frames ... 0 (0.0%)"

What to Verify Before Going Live

Run the three-line checklist every session: HDCP is off, View Signal Information matches what OBS reports, and a thirty-second test recording plays back with synced audio and zero dropped frames in the log. Those three confirm the console, the link, and the bus respectively, and a failure in any one points at exactly one subsystem instead of sending you cable-shopping at midnight.

Where This Configuration Lands You

With a $210 NearStream CCD30 — or any honest 4K60-class card — this configuration gives you a genuine 4K60 capture compressed to fit your USB bus, scaled to a razor-clean 1080p or held at native resolution for local recording, with the console untouched and your television still gorgeous on the passthrough leg. It is not magic and it is not marketing; it is one DRM toggle, two certified cables, and a dozen settings that the manufacturers could have defaulted correctly and chose not to. Now you know which dozen. Go record something.