To use XSplit Broadcaster as a webcam, add your camera to a scene, then choose XSplit Broadcaster as the camera in your video-call app. You do not need a separate webcam if your computer already has a usable built-in camera or another connected camera.
The basic route is camera source → scene → call app. You can also send a particular scene through Playout → Virtual Camera; that is an optional way to choose what the call receives, not a requirement for the basic setup.
Check your camera and Windows setup
XSplit Broadcaster is a Windows application. XSplit’s current system-requirements page lists Windows 10 or 11, 64-bit, and says earlier versions are no longer supported by the current Broadcaster release. It also lists minimum processor, memory, graphics, storage and internet requirements. Treat these as the vendor’s published requirements, not a guarantee that every scene will run smoothly on every qualifying PC. Check XSplit’s current requirements before installing, especially on an older computer.
Before opening Broadcaster, connect the camera you intend to use and check that Windows can see it. A laptop’s built-in camera is enough for a straightforward talking-head call. A USB webcam or a camera connected through a capture card can also be used if it appears as a device Broadcaster can select. An external camera is an option when you need a different position or image; it is not a prerequisite.
If another application is already using the camera, close that application before troubleshooting XSplit. Some cameras or drivers do not make the device available to two applications at once. Also check any physical privacy shutter, camera privacy setting or USB connection. A camera that is unavailable to Broadcaster cannot be passed on to the call app.
Have the conferencing app installed and know where its video settings are. The labels vary: you may see “Camera”, “Video”, or a device list in a preview or meeting settings panel. XSplit names Google Meet, Zoom and Microsoft Teams as examples, and also identifies Discord for this use. That does not mean every call app supports virtual cameras; verify that your own app offers a camera-device selector.
If you are setting up a video loop for a YouTube channel rather than a live camera feed for calls, the workflow is different. Our guide to looping a video on YouTube with OBS covers that separate use case. Here, Broadcaster is producing a camera feed for a video-call application.
Add a camera source in XSplit Broadcaster
Open Broadcaster and create or choose the scene you want to use. From the source controls, select Add Source → Camera / Capture Card, then choose your connected webcam or camera device. XSplit’s camera-as-a-source guide explains the source category and available device settings. Menu wording can change between releases, so if it differs on your screen, consult the current guide rather than relying on an older screenshot.
When the device is selected, its image should appear on the scene canvas. If the canvas remains blank, check whether the camera is listed in the source menu, whether another application is holding it, and whether the selected device is the right one. Remove and re-add the source only after checking those basics; changing several settings at once makes it harder to identify the cause.
A camera source is the image input. The scene is the composition Broadcaster sends onward. That distinction matters: adding the camera does not itself select the virtual camera in your call app, and the call app does not control how sources are arranged in Broadcaster. You set up the source and scene first, then choose Broadcaster as a device in the app.
If you need more than the built-in camera, XSplit’s advice on adding a camera and adjusting its controls describes options that may be exposed for a particular device. The exact controls depend on its hardware and driver. You can start with the default picture and make adjustments only when you can identify a problem, such as exposure changing abruptly when room lighting shifts.
Arrange the camera and optional visuals
Size and position the camera image on the canvas. For a basic call, keep the picture large enough to see your face and avoid placing text or graphics over important parts of the image. If you use a logo, nameplate or presentation visual, check the composition in the preview before joining a meeting. What looks tidy on a full desktop canvas can become difficult to read in a smaller call window.
You can keep the scene simple. A camera alone is often the clearest choice for a conversation. If you want a different background, XSplit documents automatic background removal under Camera Source Settings → Background Removal, with quality and hardware-acceleration options. You can then add a Background source for replacement imagery. Test the result with your actual lighting and clothing: hair edges, movement and similarly coloured backgrounds can make separation less convincing. Do not assume that adding a background source automatically removes the real one; configure and preview the camera’s removal settings.
The virtual camera uses Broadcaster’s current canvas resolution, up to 1080p, according to XSplit’s setup documentation. A call application may impose a lower resolution or downscale the image, so a high canvas setting does not guarantee that other participants receive that same resolution. If the call looks soft, compare the canvas, source quality and app’s video settings before changing equipment. For a YouTube stream, resolution and encoding choices are a different topic; see our guide to 1080p YouTube live-loop settings.
Some cameras expose controls such as image size, frame rate, brightness, gain, contrast, zoom, tilt, focus or saturation. Not every camera supports every control. XSplit notes that disabling auto-white balance or auto-exposure may help when sudden lighting changes cause flicker. Make one adjustment at a time and check the image in the scene; aggressive manual settings can make a picture worse when the room or daylight changes.
Before using the scene in a real call, look at the preview for framing, unwanted sources and background artefacts. If you added a graphic or desktop capture for a presentation, confirm that it does not reveal a private notification or unrelated window. A short test call or app preview is a better check than discovering a layout problem after other participants have joined.
Select XSplit Broadcaster in your call app
Once the scene looks right, open the video or camera settings in your meeting application. Find its camera selector and choose XSplit Broadcaster. The app may show a preview; check that it displays the same camera and scene you arranged in Broadcaster. If the device is not listed, confirm that Broadcaster is open and the virtual camera is available, then close and reopen the call app so it refreshes its device list.
The selector’s location is app-specific and can change after updates. For example, a call app may let you select a camera before joining, in a meeting’s settings, or through a video menu. XSplit’s instructions for using Broadcaster as a camera include examples for common call apps. Use your app’s current help page if its controls do not match the examples.
Do a quick check before a meeting: confirm the correct camera is active, that the scene is not showing a blank source, and that the app is not using a different camera than the one selected. The local preview is useful, but it is not a substitute for checking what the app is sending. If possible, join a test call or ask a trusted participant to confirm the image and sound.
A mirrored self-view is not necessarily a fault. XSplit explains that Google Meet mirrors the local preview by default, while participants see the video in the correct orientation. That detail applies to Google Meet’s preview behaviour, not every video-call app. If text or gestures appear reversed only in your own preview, check the app’s mirroring behaviour before rearranging the scene.
Send a different scene with Virtual Camera
For the simplest setup, the call app uses the current Live Scene. If you need to send a scene other than the one currently live, XSplit’s documented route is Playout → Virtual Camera, where you choose the scene to send. This lets you prepare a separate composition for the call without changing the general idea of adding a camera source and selecting Broadcaster in the app.
A second scene can be useful if one layout is for a presentation and another is for a face-to-face discussion. For example, you might prepare a camera-and-title scene for an introduction and a camera-plus-slides scene for a walkthrough. Select and preview the intended scene before switching to the call app, then confirm the app preview has changed. A scene choice in Broadcaster is easy to miss if you are accustomed to working only with the Live Scene.
This route is optional. You do not need extra hardware to choose a different scene, and a second scene does not create a second camera. It changes the composition being sent. If your call app does not show the desired picture, check the selected scene in Broadcaster, the camera-device selection in the app, and whether the source is visible in that scene.
Configure audio separately
Video selection and microphone selection are separate settings. If you want the call to receive audio from Broadcaster, choose XSplit Audio (Broadcaster) as the microphone in the meeting app. If the call should use your headset or another microphone directly, select that device in the app instead. Check which path you intend to use; otherwise, you can end up with a silent call or more than one active microphone route.
Broadcaster’s microphone setup depends on its audio capture mode. In Presentation Sources mode, XSplit’s instructions say to add the microphone or headset as an Audio Device source or as a Global Recording Device in the Audio Mixer. In System Devices mode, configure the default microphone in Audio Settings. Adding the same microphone again in System Devices mode can cause echo, so avoid duplicating a source without a reason.
Test sound before a call. Speak at a normal distance, watch the app’s audio meter if it has one, and listen for echo or clipping. If you hear your voice twice, check whether the call app is receiving both a direct microphone and XSplit Audio, or whether Broadcaster has the microphone added twice. Muting one route at a time is a practical way to isolate the duplicate.
You can use the virtual camera for video without routing scene audio through Broadcaster. Keep the microphone choice simple unless you specifically need audio sources mixed in the scene. The image path and the audio path can fail independently, so test both rather than assuming a working picture means the microphone is also configured.
Know the workflow’s limits
Broadcaster is Windows-only according to XSplit’s current support information, and the documented current requirements specify 64-bit Windows 10 or 11. Do not assume the same instructions apply on macOS or another operating system. Hardware and app support also vary: a source can work in Broadcaster while a particular call app does not offer or recognise its virtual camera.
The canvas resolution ceiling and the call app’s own limits are separate constraints. XSplit documents output up to 1080p from Broadcaster’s current canvas, but the conferencing app may lower or resize it. Network conditions, camera capability and computer load can also affect what you see. If video quality matters, test in the same app and connection you plan to use rather than treating the canvas setting as a promise about the received feed.
XSplit’s FAQ says its free licence includes a watermarked virtual-camera feature and notes other free-tier restrictions. Licence terms can change, so check the current XSplit FAQ and its latest licence comparison before choosing a plan. This is a product limitation to account for, not a reason to assume a particular paid feature or price without checking the current terms.
You also do not need a camera purchase to follow this guide if an existing camera gives an acceptable image. An external USB webcam can make sense if the built-in camera is poorly positioned, unavailable or not suitable for the image you need. A capture card, microphone, lighting and tripod are similarly optional choices based on the specific problem you are solving, not mandatory parts of the basic virtual-camera workflow.
This guide is for a camera feed in calls, not an always-on YouTube broadcast. For a prerecorded channel that should keep running after your own computer is off, the requirements and trade-offs are different; our overview of cloud-based 24/7 YouTube streaming without OBS explains that separate workflow. StreamNeo turns an uploaded video into a YouTube live stream, which removes the need to leave your own computer running for that particular broadcast workflow; it does not provide a virtual camera for calls.
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
How do I use XSplit as a webcam?
Add your camera through Add Source → Camera / Capture Card, arrange the scene, and select XSplit Broadcaster in the video settings of a compatible call app. Check the app’s preview before joining. The exact menu names can vary by app and update.
How do I select XSplit Broadcaster in Zoom?
Open Zoom’s video settings and choose XSplit Broadcaster from its camera list, then check the preview. If it is missing, make sure Broadcaster is open and the virtual camera is available, then reopen Zoom to refresh its device list. Refer to Zoom’s current help if its menu differs.
Why is my XSplit camera mirrored?
The local preview may be mirrored by the call app even when other participants see the correct orientation. XSplit documents this behaviour for Google Meet; do not assume another app handles its preview the same way. Check the app’s mirroring settings or ask someone on a test call what they see.
Do I need to buy a webcam?
No, not if your existing built-in or connected camera works for your needs and Broadcaster can select it. A separate camera is an optional upgrade for a particular image or positioning need, not a requirement for this setup.