OBS Studio, XSplit Broadcaster and Streamlabs Desktop document ways to bring capture-card video into a stream. Which one works for you depends on the exact card, operating system, connection, and video format—not just the software’s name.
Before you install drivers or change stream settings, check that your card can accept the source signal and connect to the computer running the broadcast. Then add it as a source in your chosen application and test picture and sound separately.
What a capture card does in a stream setup
A capture card takes a video signal from another device and makes it available to streaming software. For example, you might connect a camera or game console to a card, then add the card to a scene in OBS. A second-computer setup uses the same idea: the gaming computer sends video to the card, while a separate streaming computer runs the software and broadcasts the scene.
The card is a bridge between devices, not a guarantee that the whole setup is compatible. Its input has to accept the source device’s output; its connection has to work with the streaming computer; and the software needs to be able to select the card. Audio may travel through the same connection or follow another route, depending on the equipment and configuration.
This differs from streaming a video file directly. If you are deciding between a physical input and a file-based broadcast, screen recording and streaming software explained can help clarify the distinction. A capture card is useful when the live source is a camera, console or other device whose output you need to include in the scene.
Check the card and system before choosing software
“Supports capture cards” is a starting point, not a compatibility verdict. Check the card maker’s documentation for the exact model and the software vendor’s current guidance for the operating system. OBS’s certified-device list can provide another useful signal, but a listing should not be treated as a promise that every format or configuration will work.
Use this checklist before troubleshooting:
| Check | What to confirm | Why it matters |
|---|---|---|
| Exact card | Model name and revision, if the maker distinguishes them | Similar-looking cards can have different software support or format limits. |
| Operating system | Your computer’s OS and version against both card and application requirements | An application may run on your system while the card’s driver or utility does not. |
| Connection | The card’s connection type and the computer’s available port | A cable or port that fits physically may not provide the connection the device requires. |
| Source output | The camera, console or other source’s output settings | The card must be able to accept the signal being sent. |
| Capture format | Resolution, frame rate and any other format details in both devices’ documentation | A mismatch can result in no picture, an unstable image or a format choice that is unavailable. |
| Audio route | Whether audio is carried with the video or connected separately | A visible picture does not confirm that sound is reaching the software. |
| Workflow | Which machine receives the card and runs the broadcast | A two-computer layout depends on the card being attached to the streaming computer, not merely the source computer. |
| Performance | Computer capability, encoding choice and scene complexity | Recognising a card and handling the intended broadcast workload are separate questions. |
Write down the model and the intended format before opening the software. Compare those details with the manufacturer’s current instructions, including driver or utility requirements. Elgato, for example, notes that using its 4K S with third-party software can have different requirements from using Elgato Studio; its model requirements page is relevant to that specific product, not a universal guide for all cards.
Software requirements are not the same as encoding capacity. OBS cautions that meeting its system requirements does not guarantee that a computer can stream or record every workload. Resolution, frame rate, encoder choice and scene complexity affect the load. If your goal is to keep a broadcast running through the night, factor in that workload and operating pattern; keeping an OBS YouTube stream running overnight on a spare PC covers the broader always-on question.
Add a capture card source in OBS Studio
OBS Studio explicitly describes capture cards as a source type that can be added to scenes. Its current feature page lists Windows, Mac and Linux downloads, but that does not mean every card offers the same driver or format support across those systems. Check the card maker’s compatibility information for the computer you plan to use.
First install OBS on the computer that will handle the broadcast. Follow the card maker’s own setup instructions, connect the source output to the card input, and attach the card to the streaming computer as its manual specifies. Open OBS and choose the relevant scene. Add a video-capture source using the source workflow in the current OBS version, then select the card from the device list if it appears.
The source’s available controls depend on the device and its driver. Where OBS allows a format to be selected, choose a setting the source, card and software all support. Do not assume a higher resolution or frame rate is available simply because the camera or console can output it. If you change a setting and the preview goes blank, return to a known supported format from the card documentation before making other changes.
A recognised device is only one part of the test. Check the preview for a stable image, then check whether sound appears in OBS’s audio controls. If a device is missing, avoid creating several duplicate sources as a first response: another application or an existing source may already be using it. Close other applications that could claim the card, then test one source in one scene.
OBS is a cross-platform choice worth considering when your computer is not running Windows, subject to the current requirements for your OS and card. For a software-based file loop rather than a hardware input, the considerations differ; see the guide to Linux software for looping videos to YouTube Live.
Configure a dual-PC capture workflow in XSplit
XSplit Broadcaster documents a dual-PC workflow in which the streaming computer receives the video from a capture card. Its published requirements describe Broadcaster as Windows-only and list Windows 10/11 64-bit; check the current XSplit system requirements for changes before setting up. That makes it a Windows-specific route, not a general answer for a Mac or Linux streaming computer.
In a dual-PC arrangement, the source or gaming computer produces the video, and the streaming computer runs XSplit. Connect the source computer’s video output to the capture card input, then connect the card to the streaming computer according to the card manual. Install Broadcaster on the streaming computer and follow the card manufacturer’s driver or utility steps there.
XSplit’s documented path is Add Source > Devices > Video. Select the capture card from the device list and inspect the preview. The source machine and streaming machine must agree on a signal the card can accept. If the list is empty, first confirm that the card is attached to the computer running XSplit, not only to the gaming PC, and that the operating system can see it.
A two-PC workflow can keep the capture and broadcast tasks on separate computers, but it adds a connection and another device to verify. It does not remove the need to check format support, audio routing or the streaming computer’s encoding workload. If you are using a Windows virtual machine or hosted computer, startup and session behaviour are separate concerns from the capture card itself; automatic startup for an OBS YouTube stream on a Windows VPS addresses that kind of operating setup.
Set up a card in Streamlabs Desktop
Streamlabs Desktop publishes capture-card setup and troubleshooting guidance, including cases where a device does not appear, another source occupies it, or the card needs device-specific setup. Begin with the card maker’s instructions, then add a video-capture source in Streamlabs Desktop and choose the card if it is available. The precise labels and controls can change between software versions, so use the current application and device documentation rather than relying on an old menu screenshot.
If the card is listed, check its picture before changing unrelated scene settings. Confirm that the selected input and format match what the source device is sending. Then check the audio mixer or the card’s documented audio route. A card can deliver video without the expected sound if the source, connection or software input is configured differently from what you assumed.
If it does not appear, close applications that might already be using it and remove or disable duplicate sources while testing. Streamlabs notes that setup can vary by device, including whether particular software or a generic driver is relevant. Do not install a driver just because a forum post recommends it for a different card; follow the instructions for your model and operating system.
Test picture, sound and broadcast load
Test the chain from source to stream, one piece at a time. Start by checking that the source device is outputting a format the card accepts. Then check that the card is connected to the intended computer and visible to the operating system. In the streaming software, confirm the selected device and preview before adding overlays or other scene sources.
For audio, identify where sound should enter the setup. It may be carried alongside video, or it may require a separate input or configuration. Speak or play a short test through the source and watch the software’s audio meter. A meter that moves confirms that audio reaches the application; it does not by itself confirm that the final YouTube broadcast sounds correct, so monitor the output where practical.
Next test the intended scene and encoding settings. A static preview is not enough to establish that the computer can sustain the broadcast. Watch for dropped or delayed frames and check the software’s status indicators while the scene is active. If the computer struggles, reduce scene complexity or revisit the chosen output format and encoder in light of the current system requirements. Do not promise yourself a particular resolution or frame rate until the source, card, software, computer and network have all been checked.
Keep notes on the configuration that worked: card model, OS, connection, source format, software version and audio route. This makes it easier to restore a known-good setup after a driver or application update. If you are diagnosing a file-based YouTube stream rather than a capture source, common causes of stutter when playing a video file cover a different signal path.
Troubleshoot connection or format issues
When a card is absent from the software, start outside the scene. Verify the cable and port against the card manual, reconnect the device if appropriate, and check whether the operating system recognises it. Follow the manufacturer’s driver or utility instructions for that exact model. A card that is not visible to the computer cannot be fixed by changing a scene layout.
If the OS sees the card but the application does not, close other software that may be using it. Check for a second active source in the same application and test with one source in a simple scene. Then restart the application after confirming the device is connected. These steps help distinguish a device-occupancy issue from a driver or format problem.
If the card appears but the preview is blank, compare the source’s output format with the card’s supported input formats. Check the cable direction and input selection too: video output from the source must reach the card’s input. If the software exposes format controls, choose a documented common format and test again. Avoid changing resolution, frame rate, audio and encoder settings all at once, because you will not know which change affected the result.
If the image works but sound does not, trace the audio route independently. Confirm whether sound is expected through the card or another input, whether the source is sending audio, and whether the right device is selected in the application. If sound is present in the software but absent from the broadcast, inspect the scene’s audio routing and monitor the final output.
For intermittent performance problems, separate capture from encoding. Check whether the preview itself is unstable, then assess whether the computer can handle the selected encoder, output format and other active sources. The OBS system-requirements guidance makes clear that minimum requirements are not a guarantee of performance for every workload. If you run the stream from a remote computer, remember that remote access and process persistence introduce their own issues; keeping an Amazon EC2 YouTube stream running after SSH disconnects is a separate operational topic.
Choose by fit, not by a universal ranking
The documented workflows point to practical differences rather than a single best application. OBS lists capture cards as scene sources and offers downloads for Windows, Mac and Linux. XSplit’s documented dual-PC workflow is for Broadcaster on Windows. Streamlabs Desktop provides capture-card setup and troubleshooting material, including device-specific cases. In each case, the exact model and configuration still need checking.
Choose first by the computer and workflow you already have. For a non-Windows system, verify the card maker’s support and the current OBS requirements before buying anything. For a Windows dual-PC setup, XSplit’s guide is directly relevant to adding a card as a video source. If you already use Streamlabs Desktop, its troubleshooting material can help with source conflicts and model-specific setup. These observations describe documented paths, not a claim that any application is compatible with every card.
Then compare the intended capture format and workload. A card that can show a picture may still not meet your preferred resolution, frame rate, latency or passthrough needs. Verify those details against the exact model’s official documentation and test with the source you will actually use. The OBS certified list and the card manufacturer’s page are useful references, but neither removes the need to check your particular system.
If your channel uses a prerecorded video rather than a camera, console or second computer, a capture card may add equipment without solving a real problem. StreamNeo removes the need to keep a local computer running when your YouTube broadcast is based on an uploaded video file, but it does not take a capture-card input and is YouTube-only. A live camera or console feed still needs a compatible capture and streaming workflow.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
What streaming software works with a capture card?
OBS Studio, XSplit Broadcaster and Streamlabs Desktop document capture-card workflows. Their operating-system support and setup paths differ, and none of those statements means every card or format will work. Check the exact card’s requirements alongside the software guidance.
Can OBS use a capture card?
Yes. OBS describes capture cards as sources that can be added to a scene. Add the device through the video-capture source workflow, then confirm the card is supported on your operating system and select a format accepted by the source and card.
How do I add my capture card as a source?
Connect the source to the card and the card to the computer running the streaming software, following the card’s manual. Add a video-capture source in your application, select the device, and test picture and audio separately. If the device is missing, check the connection, driver instructions and whether another application is using it.
Why is my capture card not appearing in the software?
The computer may not recognise the card, its driver or utility setup may be incomplete, or another application or source may already be using it. Confirm the exact model’s instructions and connection first, then close other applications and test a single source. If the device appears but has no picture, check signal and format compatibility before changing unrelated settings.