The Short Answer
Yes, a webcam does work with capture card passthrough, but only if the passthrough is not consuming the USB controller or bandwidth the webcam needs. A capture card’s HDMI passthrough itself does not block a webcam, because the passthrough is a direct HDMI-in to HDMI-out video relay. Problems only occur when the capture card and the webcam compete for the same USB host controller, power budget, or software encoder. If you connect the capture card to a USB 3.0 port on one controller and the webcam to a separate USB 2.0 or USB 3.0 port on a different controller, and you keep them on separate applications or scenes, both will run simultaneously without conflict.
As of early 2026, most modern PCIe and USB 3.0 external capture cards are designed to coexist with USB webcams in OBS Studio, Streamlabs, and Discord, provided you avoid bandwidth saturation and driver collisions.
Compatibility at a Glance
| Factor | Requirement | Notes |
|---|---|---|
| Interface | Capture card on USB 3.0 / PCIe, webcam on separate USB 2.0 or 3.0 port | Do not share the same USB hub or front-panel header. HDMI passthrough does not use USB bandwidth. |
| Power | 5V / 900mA per USB 3.0 port, powered hub if using external card + webcam + mic | Bus-powered capture cards can starve webcams when on same controller. |
| Drivers | UVC-compliant webcam driver, manufacturer driver for capture card | Windows Device Manager should show no yellow warning icons under Cameras and Sound, video and game controllers. |
| Firmware / HDCP | Capture card firmware updated, HDCP disabled for passthrough source | HDCP from consoles blocks passthrough preview; does not affect webcam but prevents capture preview overlay. |
| Form Factor | PCIe internal or external USB 3.0 card with dedicated HDMI Out for passthrough | USB 2.0 capture dongles often lack true passthrough and rely on software preview, which adds latency and USB load. |
| Software | OBS Studio 29+ or equivalent, separate sources for Video Capture Device | Create two distinct Video Capture Device sources; do not nest webcam inside capture card source properties. |
What Determines It
Interface and Signal Path
What causes it: A true HDMI passthrough circuit routes the HDMI input signal directly to the HDMI output without passing through the USB encoder. A webcam uses a completely separate UVC path over USB. Issues happen only when users mistake USB software preview for passthrough, or when both devices are forced onto a single USB 2.0 bus that caps at 480 Mbps total throughput.
How to check: Inspect your capture card. If it has an HDMI In and a separate HDMI Out labeled Passthrough, Out, or Loopout, it has hardware passthrough. If it only has HDMI In and USB Out, it has no hardware passthrough. In Windows, press Win + X and open Device Manager, then expand Universal Serial Bus controllers. Right-click each USB Host Controller and select Properties > Advanced tab to see Bandwidth usage. If both devices list under the same Host Controller, they share bandwidth.
What to do: Connect the HDMI source such as a console or second PC to the capture card HDMI In, connect the HDMI Out to your primary monitor or TV, and connect the capture card’s USB cable to a rear motherboard USB 3.0 port marked SS or with a blue insert. Connect the webcam to a USB 2.0 port on the opposite side of the rear I/O panel or to a different USB header. In OBS Studio, go to Sources > + > Video Capture Device, select the capture card by name, then add a second Video Capture Device source and select the webcam. Set Resolution/FPS Type to Custom and choose 1920×1080 at 30 FPS for the webcam to conserve bandwidth.
How to undo: Disconnect the webcam from the alternate port, remove the second Video Capture Device source in OBS Studio by right-clicking it and selecting Remove, and plug the capture card back into its original USB port. Restart OBS Studio to revert to the previous source layout.
Power Delivery and USB Bandwidth
What causes it: External capture cards in particular the Elgato HD60 S+, EVGA XR1, and generic MS2130-based sticks draw 400 to 650 mA continuously. A 1080p webcam with autofocus and built-in mic draws another 200 to 500 mA. A single unpowered USB hub or a front-panel case header often cannot supply 900 mA per port, causing brownouts where the webcam turns black, flickers, or shows Code 43 in Device Manager.
How to check: Open Device Manager > Universal Serial Bus controllers > USB Root Hub (USB 3.0) > Properties > Power tab. Check Power Required versus Power Available. Also open Settings > Bluetooth & devices > Cameras in Windows 11, or Settings > Devices > Cameras in Windows 10, to see if the webcam preview disappears when the capture card is streaming. Listen for the Windows USB disconnect sound when starting a capture preview.
What to do: Move the webcam to a motherboard USB port directly, not through a hub. If you must use a hub, use a powered hub with a 12V 2A or 12V 3A AC adapter. In Device Manager, right-click the USB Root Hub > Properties > Power Management tab and uncheck Allow the computer to turn off this device to save power. Set the webcam to MJPEG instead of YUY2 in its source properties. In OBS Studio, right-click the webcam source > Properties > Video Format > MJPEG. MJPEG halves bandwidth at 1080p compared to uncompressed YUY2.
How to undo: Re-check Allow the computer to turn off this device to save power on the USB Root Hub, switch the webcam Video Format back to YUY2 or NV12, and remove the powered hub by plugging devices directly back into the original ports.
Drivers and Software Conflicts
What causes it: Webcams use the native Microsoft UVC driver usbvideo.sys. Capture cards use proprietary drivers such as Elgato Game Capture, AVerMedia RECentral, or generic UVC extensions. Conflict arises when two applications try to claim exclusive control of the webcam or when the capture card utility locks the camera pipeline. OBS Studio will display a black screen with the message Device in use by another application.
How to check: Press Win + R, type msinfo32, and navigate to Components > Problem Devices to check for driver conflicts. Open Device Manager > Cameras, right-click your webcam > Properties > Driver tab > Driver Details to confirm driver is usbvideo.sys with a Microsoft provider. Open Device Manager > Sound, video and game controllers, right-click the capture card > Properties > Driver tab and note driver version and date. Close all apps that may hold the camera: Zoom, Teams, Discord, Camera app. Then test the webcam alone in Windows Camera app at path C:\Windows\Camera\ or via Start Menu > Camera.
What to do: Update the capture card driver from the manufacturer’s support page, not through Windows Update. Uninstall conflicting virtual camera drivers. In Device Manager, right-click the capture card > Uninstall device > check Attempt to remove the driver for this device only if you are reinstalling. Reboot, then reinstall the driver package. In OBS Studio, go to Settings > Advanced and uncheck Auto-reconnect for sources if enabled, then under Sources, ensure each Video Capture Device has Deactivate when not showing unchecked for the main scene but checked for background scenes to release the device.
How to undo: In Device Manager, right-click the device > Properties > Driver tab > Roll Back Driver to return to the previous driver version. In OBS Studio, revert Settings > Advanced to its prior state and re-enable any virtual camera utilities you uninstalled by running their installers again.
Firmware and HDCP / EDID
What causes it: Outdated capture card firmware can misreport EDID to the source, causing passthrough to fail or to force a lower resolution that overlaps with webcam resolution handling in the compositor. HDCP encryption from a PS5, Xbox, or streaming stick will black out the capture preview but leave the HDMI passthrough to the TV active. Users often think the webcam failed when the entire OBS canvas is black due to HDCP.
How to check: For HDCP, check the source device settings. On PS5, go to Settings > System > HDMI > Enable HDCP. On Xbox Series X|S, go to Settings > General > TV & display options > Video modes. On the capture software, open the card’s utility such as Elgato 4K Capture Utility > Settings > Device and look at Firmware version and Status. If the preview shows a HDCP error or flashing screen, HDCP is the blocker. Check the capture card firmware file location after download, typically C:\Program Files\Elgato\4KCaptureUtility\Firmware or C:\Program Files\AVerMedia\AVerMedia RECentral\Firmware.
What to do: Disable HDCP on the source when allowed. On PS5 set Enable HDCP to Off. Keep it On for streaming apps that require it, but do not capture that content. Update firmware by running the manufacturer firmware tool as administrator. Right-click the tool > Run as administrator, connect only the capture card, and follow the on-screen progress bar until it shows Update complete. Set EDID mode to Display or Internal if available. In the capture utility, go to Settings > Device > EDID Mode > Display to mirror the passthrough monitor’s native resolution. Set webcam FPS to 30, and capture card to 60 if your monitor supports it; mismatched refresh rates do not conflict.
How to undo: Re-enable HDCP on the source by toggling Enable HDCP back to On. In the firmware utility, use the Restore Default EDID or Revert Firmware option if provided. If not, reinstall the previous firmware version from the archived installer in your Downloads folder.
Form Factor and Physical Passthrough vs USB Loopback
What causes it: PCIe capture cards such as the Elgato 4K60 Pro MK.2 or AVerMedia Live Gamer 4K pass through video via onboard HDMI splitter chips with near zero latency, independent of USB. External USB 2.0 sticks marketed as having passthrough often simply duplicate the USB preview window, which uses CPU and USB bandwidth and will drop frames when a webcam is active.
How to check: Look at the card’s specifications sheet for latency value and passthrough support. True hardware passthrough will list Latency: < 50 ms or Zero latency passthrough and Support resolution: 4K60 HDR passthrough. Open OBS Studio > Tools > Log Files > View Current Log and search for device name. If the log shows using QSV or NVENC overload warnings when both devices are active, you are CPU or encoder limited, not passthrough limited.
What to do: Prefer PCIe for dual-PC streaming with a webcam on the streaming PC. If you own a USB card, place it on a USB 3.1 Gen 1 port with at least 5 Gbps signaling. Keep passthrough HDMI cable length under 10 feet, use Certified Premium High Speed HDMI cables, and avoid HDMI switches between source and capture card. In Windows, go to Settings > System > Display > Advanced display and confirm the passthrough monitor is running at its native refresh rate such as 144 Hz or 60 Hz without dropping to 30 Hz.
How to undo: Reconnect your source directly to the monitor via HDMI, bypassing the capture card. In Device Manager > Device Manager > Sound, video and game controllers, disable the PCIe card by right-clicking > Disable device if you want to test the system without it. Re-enable it afterward.
How to Check Yours
Run this five minute check before buying a new webcam or hub:
1. Identify your ports. Shut down the PC, note which USB ports are blue SS ports and which are black USB 2.0. Boot, press Win + X > Device Manager > View > Devices by connection. Expand the USB controllers tree and plug the webcam in first, note which controller it appears under, then plug in the capture card and see if it appears under a different controller.
2. Test isolation. Open the Windows Camera app and verify the webcam shows video. Open the capture card utility or OBS Studio with a scene that contains only the capture card Video Capture Device. If both previews run at the same time in separate windows, the hardware isolation is sufficient.
3. Check format and load. In OBS Studio, right-click the webcam source > Properties > Resolution. Try 1280×720 at 30 FPS and Video Format MJPEG. Right-click the capture card source > Properties > Configure Video. Observe CPU usage in Task Manager > Performance > CPU, which should stay below 85 percent sustained during preview. If it spikes to 100 percent, lower the webcam to 720p.
4. Verify audio routing. Go to Settings > System > Sound > Input. Ensure the webcam microphone, if present, appears as a separate input from the capture card audio such as Line In or Digital Audio Interface. In OBS Studio, go to Settings > Audio > Global Audio Devices and assign the webcam mic to Mic/Auxiliary Audio and the capture card audio to its own source, then mute the unused desktop audio to prevent echo.
5. Confirm passthrough on the monitor. With the capture preview active in OBS Studio, check the physical monitor connected to the capture card HDMI Out. You should see the console or source video with no delay, even if you close OBS Studio. If the monitor goes black when you close the software, you have software preview only, not hardware passthrough.
If It’s Not Compatible
If your current setup cannot run both reliably, use one of these alternatives without replacing the entire PC:
Use a dedicated USB host card. Install a PCIe USB 3.0 expansion card with a separate Renesas or ASMedia host controller. Models with one controller per two ports are ideal. This gives the capture card and webcam independent 5 Gbps buses. Install the card in a PCIe x1 slot, install its driver from the included CD or the vendor site, then assign the webcam to the new card and keep the capture card on the motherboard controller.
Switch the webcam connection method. Replace a USB webcam with an HDMI camera or camcorder connected to a second cheap HDMI-to-USB dongle, or replace the USB capture stick with a PCIe capture card to free USB bandwidth. NDI or network cameras are another option: use NDI Tools and add an NDI source in OBS Studio instead of a second Video Capture Device, which uses Ethernet or Wi-Fi instead of USB.
Lower the total data rate. Keep the capture card at 1080p60 for passthrough but set its recording resolution to 1080p30 in OBS Studio > Settings > Video > Output Resolution. Set the webcam to 720p30 with MJPEG. This keeps combined USB throughput below 300 MB/s and avoids frame drops without noticeable quality loss for face cam.
Separate workloads across two PCs. Run the game or console capture on a dedicated capture PC with the capture card, and run the webcam, alerts, and encoding on the streaming PC. Connect the capture PC’s OBS preview via Projector Mode over NDI or via HDMI passthrough to the streaming PC’s capture card. This cleanly isolates UVC devices.
FAQ
Can I use the passthrough monitor and still show the webcam overlay in OBS Studio?
Yes. Passthrough is a hardware mirror to your monitor and does not affect the OBS Studio canvas. In OBS Studio, add the capture card as Video Capture Device on the bottom layer and the webcam as Video Capture Device above it, then resize and position the webcam overlay. The monitor will show only the source video, while the OBS canvas and stream will show the composited scene with the webcam.
Why does my webcam go black when I start the capture card?
This is almost always a USB power or bandwidth collision, not a passthrough issue. Check Device Manager > Cameras to see if the webcam shows Error Code 43 or 10. Move the webcam to a USB 2.0 port or a powered hub, change its Video Format to MJPEG at 1280×720 30 FPS, and uncheck Allow the computer to turn off this device to save power on the USB Root Hub properties.
Do I need to install drivers for both devices?
Webcams typically need no extra driver beyond the built-in UVC driver in Windows 10 and Windows 11. Capture cards do need their vendor driver and firmware utility. Install only the vendor driver for the capture card, reboot, then plug in the webcam and let Windows install usbvideo.sys automatically. Avoid installing webcam vendor bloatware that claims exclusive control unless you need its background removal features.
Will a USB 2.0 capture dongle work with a 1080p webcam passthrough setup?
It can, but you will face limitations. USB 2.0 dongles cap at 480 Mbps and have no true hardware passthrough, so they copy the video to the monitor via software preview with added latency of 100 to 300 ms. For reliable use with a webcam, keep both devices at 720p30, use MJPEG for the webcam, and connect them to separate USB controllers. For best results, upgrade the capture device to a USB 3.0 or PCIe model with dedicated HDMI Out.
Related guides
- Is 3.5mm Lavalier Mic Compatible with Dslr? What You Need to Know (2026)
- Is Studio Monitor Compatible with Audio Interface Output? What You Need to Know (2026)
- Does Green Screen Work with Ring Light Setup? What You Need to Know (2026)
- Is Usb C Capture Card Compatible with Ipad Streaming? What You Need to Know (2026)