A capture card sits between a console (or a second PC) and your streaming machine, copying the HDMI signal so OBS can see it. Without one, there’s no clean way to stream PS5 or Xbox gameplay short of pointing a phone at the TV. The card does two jobs: grabs the HDMI input at 1080p60 or 4K30, and usually passes the signal through to a separate display so you can play on your normal TV without lag.
Setting one up takes about 45 minutes if you’ve never done it before. Expected outcome: console gameplay shows up as a video source in OBS, synced to your microphone, with latency low enough that you don’t feel the delay on the gameplay display (the passthrough handles that). You’ll also configure scene layout, audio routing, and bitrate so the stream looks good and doesn’t desync. This walkthrough uses a USB 3.0 external capture card and OBS Studio. Same logic applies to internal PCIe cards.
What you’ll need
A USB 3.0 (or higher) capture card. Budget options run $15 to $35 and handle 1080p60. Mid-range Elgato HD60 X or AVerMedia GC551G2 at $150 to $200 handle 4K30 passthrough with 1080p60 recording, plus VRR passthrough for PS5/Xbox Series X.
Two HDMI cables: one from the console to the card’s INPUT, one from the card’s OUTPUT (passthrough) to the gameplay display. HDMI 2.0 for 1080p60, HDMI 2.1 for 4K120 or VRR. A USB 3.0 port on your streaming PC: critical. USB 2.0 caps at 480 Mbps and forces the card to drop to 1080p30. Look for a blue port or one labeled “SS.”
OBS Studio installed. A microphone or headset. A second monitor or window arrangement so you can see OBS while playing on the gameplay display. Optional: an HDMI splitter for copy-protected sources, but HDCP-stripping splitters exist in a legal gray area.
Step 1: Connect the hardware in the right order
Connection order matters because HDCP (the copy protection on console outputs) handshakes between devices at boot. Get the order wrong and the card might not see the signal, or your display will show a blank screen with “HDCP error.”
Power everything off first. Console off, capture card unplugged from USB, gameplay display off. Now connect the console’s HDMI OUT to the capture card’s INPUT. Then connect the capture card’s OUTPUT to the gameplay display’s HDMI IN. Finally plug the USB cable from the capture card into a USB 3.0 port on the streaming PC.
Power on in this order: streaming PC first (so the card gets recognized), then the gameplay display, then the console. This sequence lets the card establish the HDCP handshake correctly. If you skip ahead and turn on the console before the PC sees the card, the passthrough sometimes fails until you reboot the console.
On Windows, open Device Manager and confirm the capture card shows up under “Cameras” or “Imaging devices” without a yellow warning triangle. If there’s a triangle, the driver didn’t load. Install the manufacturer’s driver from their support page. Elgato uses 4K Capture Utility, AVerMedia uses RECentral. Both register the card with Windows and OBS.
If your PS5 won’t output to the card (gameplay screen black), disable HDCP in PS5 system settings: Settings, System, HDMI, turn off Enable HDCP. Xbox doesn’t have that toggle and uses HDCP only for protected media, not games.
Step 2: Add the capture card as a source in OBS
Open OBS Studio. In the Sources panel (bottom-left), click + and select Video Capture Device. Name it something like “PS5” or “Capture Card.” Click OK.
In the device dropdown, pick your capture card by name. If you see two entries (some cards register twice), pick the one with “MJPEG” or “YUY2” in the description. These are uncompressed or lightly compressed formats that give the cleanest signal.
Set Resolution/FPS Type to Custom. Resolution: 1920×1080 for HD streaming, 3840×2160 if you’ve got a 4K card and are recording locally. FPS: 60 for fast-paced games (shooters, fighting), 30 if your card or PC can’t handle 60.
Video Format: NV12 if available, or MJPEG. Avoid YUY2 unless those two don’t work since it uses more USB bandwidth. Color Space: 709 for 1080p, 2020 for 4K HDR sources. Color Range: Limited for console output, Full only if you’ve forced full RGB on the console.
Click OK and you should see live console video in the OBS preview. If the preview’s black, the most common cause is HDCP not disabled on PS5. The second most common is a wrong resolution or framerate. Try 1080p30 first to confirm signal, then bump up.
Step 3: Set up audio routing
Console audio comes through the HDMI signal that the capture card sees. By default, OBS treats this audio as part of the video source, but you’ll need to configure it so your mic, game audio, and any music or alerts mix correctly.
In OBS, right-click the capture card source, Properties, scroll to “Audio Output Mode.” Set it to “Output desktop audio (WaveOut)” if you want game audio to play through your PC speakers/headphones as well as the stream. Set it to “Capture audio only” if you’ll listen to game audio through the gameplay display.
In Audio Mixer (bottom-center of OBS), you’ll see the capture card audio. Set its level so peaks hit -12 dB to -6 dB on the meter. Your microphone should hit the same range. Don’t let either clip at 0 dB. Compression and limiters can be added via filters if you want polish, but at minimum get both sources to similar levels.
For console party chat (PS5/Xbox), route through your headset using a TRRS splitter on the controller’s 3.5mm jack: one cable to your mic, the other to headphones. Capture card grabs game audio from HDMI; mic captures your voice on the PC. Party chat routes to your ears via the controller, not the stream unless you add a separate audio capture. Mixers like the GoXLR or RodeCaster route everything cleaner but aren’t required to start.
Pros
- Plug-and-play USB 3.0 setup, no driver install required on Windows, macOS, or Linux.
- 4K 30/60Hz input with 1080P 60FPS capture covers current-gen consoles and modern cameras.
- HDMI loop-out enables zero-delay local monitoring while capturing simultaneously.
- 3.5mm TRS mic input adds commentary capability without extra hardware.
Cons
- Output tops out at 1080P 60FPS, no 1440P or 4K capture path despite 4K input support.
- Captures only MJPEG and MJPG formats, no YUV output, which limits color accuracy in post-production.
- Brand has limited independent third-party review coverage, owner feedback is the primary performance signal.
The vixlw capture card is a budget-tier external USB 3.0 capture device targeting casual streamers and content creators who need a no-fuss way to record or broadcast from a Nintendo Switch, PS5, Xbox, or HDMI camera source. It sits firmly in the entry-level segment alongside a crowded field of similar anonymous-brand dongles.
The most practical feature is the HDMI loop-out port, which passes the source signal to a monitor or TV at full quality while the card simultaneously captures to a PC. Based on owner reports, latency on the loop-out path is negligible, which is critical for console gaming. The USB 3.0 connection handles the 1080P 60FPS capture stream without dropping frames under normal conditions.
The honest trade-off is the output ceiling. Despite accepting 4K 30/60Hz input, the card encodes and outputs at 1080P 60FPS maximum using only MJPEG compression, not YUV. That compression choice is typical at this price tier, but it does affect color fidelity compared to YUV-capable cards costing more. Independent benchmark data for this specific unit is sparse, so claims of zero CPU impact should be treated as approximate.
Buy this if you stream at 1080P 60FPS from a console or camera and want a driver-free solution that works immediately with OBS or VLC. Skip this if you need 1440P or 4K capture output, require YUV color space for professional post-production, or are sensitive to the limited third-party validation behind this brand.
Input and Output: HDMI input accepts up to 4K 30Hz and 4K 60Hz signals as well as 1080P up to 120/144Hz. Maximum capture output is 1080P 60FPS over USB 3.0. The card does not support 4K 120Hz or 4K 144Hz input, and output does not exceed 1080P 60FPS under any configuration.
Encoding Format: Captured video is encoded in MJPEG and MJPG only. YUV output is not supported on this model, which is a relevant constraint for editors who rely on YUV color space in DaVinci Resolve or Premiere for accurate color grading at 1080P.
Connectivity and Audio: USB 3.0 host connection with HDMI loop-out for simultaneous local monitoring. A 3.5mm TRS microphone input is present for commentary. The card is bus-powered with no external supply required, and operates on Windows 7 through 11, macOS 10.9 or later, Linux, and Android 8 or later.
Software Compatibility: Confirmed compatible with OBS, VLC, Amcap, and Potplayer. Plug-and-play enumeration means the device appears as a standard UVC webcam, so any software supporting UVC capture devices should recognize it without additional configuration.
Step 4: Tune latency and verify sync
Capture cards introduce 50 to 150 ms of latency between the console output and what OBS sees. The passthrough port on the card bypasses this, which is why you play on the passthrough-connected display, not on the OBS preview. The OBS preview’s only for monitoring scene layout.
Confirm passthrough’s actually working. Look at the gameplay display (the one connected to the capture card’s OUT port). Move the joystick. The response should feel instant, identical to direct console-to-TV gameplay. If there’s a noticeable delay on the passthrough display, the card’s broken or you’ve accidentally connected things wrong.
Audio-video sync in the stream itself sometimes drifts because capture card video lags slightly behind game audio coming through HDMI. In OBS, right-click the capture card audio in the Audio Mixer, Advanced Audio Properties, and add 80 to 120 ms of Sync Offset to the audio. This delays the audio to match the slightly-delayed video. Stream a 30-second clip with a sharp visual event (a gunshot, a jump) and check that sound and image line up.
Run a stream preview to Twitch or YouTube using the built-in OBS preview button (not a live stream). Watch the preview through the dashboard. If video and audio are off, adjust the sync offset another 20 ms and retry.
Lock the stream at your target bitrate. For 1080p60 on Twitch, 6000 Kbps is the cap. YouTube allows up to 12000 Kbps for 1080p60 and 30000 Kbps for 1440p60. Set the encoder to NVENC (Nvidia GPU) or x264 (CPU) depending on your hardware. NVENC’s the easy choice if you’ve got an RTX 20-series or newer GPU.
Step 5: Build a scene and go live
In OBS, create a scene called “Gameplay.” Add the capture card video, your webcam (if streaming with face cam), and any overlays. Gameplay typically fills the canvas, webcam sits in a bottom corner at 320×240. Add a second “BRB” scene with a static image, social handles, and looping music for breaks. Configure stream key from your platform dashboard (Twitch Creator Dashboard, YouTube Live Control Room), paste it into OBS Settings, Stream, pick the closest server, then hit Start Streaming. Watch the dashboard preview for 60 seconds to confirm video, audio, and overlays show correctly.
Troubleshooting common issues during setup
Black screen in OBS but passthrough display works. Driver loaded but resolution mismatch. In OBS, drop to 1080p30 to confirm signal, then step up. Also check that the capture card source is set to the right video format (NV12 or MJPEG).
Choppy video at 1080p60. USB 2.0 port. Move to a USB 3.0 port (blue inside). If you’ve already done that and it’s still choppy, the USB 3 controller may be shared with another high-bandwidth device. Disconnect external SSDs and webcams from neighboring ports.
Stuttering or dropped frames in OBS but card looks fine. Your CPU or GPU encoder’s overloaded. Drop the stream bitrate to 4500 Kbps, switch encoder to NVENC if you’re using x264, and lower the OBS Preview FPS to 30 (the stream FPS stays at 60).
Audio echo or doubled audio. Game audio coming through both the capture card and your PC speakers. In OBS audio settings, set the capture card’s Audio Output Mode to “Capture audio only” (no desktop output), so game audio only goes to the stream and the gameplay display, not back through your PC speakers.
Before / after metrics or expected outcome
A working setup hits these numbers. OBS shows console video at full 1920×1080 60 fps with no stutter (check the FPS counter at the bottom right of OBS). Capture card encoder uses about 6 to 12% CPU (or 8 to 15% NVENC utilization on a modern RTX GPU). USB bandwidth shows around 300 Mbps for 1080p60 NV12 (roughly 60% of a USB 3.0 port’s effective throughput).
Audio peaks sit at -12 to -6 dB on both the mic and game channels. Sync offset between video and game audio sits around 80 to 120 ms (added to the audio side). The passthrough display shows zero perceptible latency since it’s a hardware split, not software.
Stream output to Twitch at 6000 Kbps 1080p60 should show no dropped frames (Twitch Inspector tool measures this from the receiving side). Stream latency on Twitch Low Latency Mode runs about 2 to 3 seconds between your gameplay and what viewers see. On YouTube Ultra Low Latency, about 1 to 2 seconds.
Variations / advanced setups
Dual-PC streaming uses a capture card to pull gameplay from a gaming PC into a separate streaming PC. The streaming PC handles OBS, encoding, and chat without taxing the game machine. Connect the gaming PC’s HDMI output to the capture card on the streaming PC, same as console capture. Pros use this since it isolates encoding load.
Internal PCIe cards (Elgato 4K Pro, AVerMedia Live Gamer 4K) eliminate USB bandwidth concerns and usually support 4K60 with HDR passthrough. Install into a PCIe x4 slot, run drivers, then configure in OBS the same as a USB card. For 4K HDR passthrough, your card, both HDMI cables, and the gameplay display all need HDMI 2.1 with HDR10 metadata. A single weak link forces HDR off.
Common questions
Can I use a capture card without a passthrough display?
Yes, but you’ll play through the OBS preview, which has 80 to 150 ms latency. That’s playable for slow turn-based games, painful for shooters or fighting games. Always use passthrough if your card supports it.
Do I need 4K capture if I only stream 1080p?
Only if you want your gameplay display to remain 4K via passthrough. A 1080p-only card downscales the passthrough to 1080p too, which is annoying if you’ve got a 4K TV.
Why does my stream look soft compared to my gameplay display?
Bitrate. Twitch’s 6000 Kbps 1080p60 limit’s tight for action games. Use the Twitch broadcaster preview to check actual output sharpness. YouTube allows higher bitrate and usually looks crisper.
Will a capture card add input lag to my game?
Not through the passthrough port. Passthrough’s a hardware split. Through OBS preview, yes, 80 to 150 ms. So always play looking at the passthrough display, never the OBS preview.
