That difference is useful evidence. If one app receives the processed video, at least one working path exists from the face-swap software to a receiving app. The next thing to investigate is where the second app gets its camera input.

Keep the working app’s settings handy as a reference, then check the failing path one boundary at a time.

Separate the preview from the outgoing camera

There are three distinct stages:

Physical webcam → face-swap processing → virtual camera → receiving app

A successful preview confirms that the software can capture and process your face. It does not, by itself, confirm that another application can receive that result.

The browser experience in LiveFaceSwap AI is a live webcam preview; opening it does not automatically make the processed image available in Zoom, Meet, or OBS. On a compatible Windows desktop setup, the virtual device named LiveFaceSwap Camera can send the processed AI output to applications that support video capture devices.

Before changing settings in the receiving app, confirm that your desktop setup provides that virtual device. If you only have the browser preview running, repeatedly switching cameras in a meeting app will not create the missing output path.

Cloud inference may also need loading time. Wait until the processed desktop preview is moving before using a blank receiving-app preview as evidence of a separate problem.

Check which device the failing app actually selected

Open the failing app’s video settings and inspect its selected camera. Device names matter more than whether the preview looks healthy.

If you see your normal face, the app may simply be using the physical webcam. Select the virtual camera explicitly, then check the preview again. Automatic camera selection can choose a different device from the one you intended.

Use a quick, visible check: turn your head and open your mouth. You want to confirm that the receiving app shows the moving, processed face rather than a frozen frame.

For a browser-based call, camera access involves both the browser and the website. Check that the site has permission to use a camera and that its selected input is the virtual device. A permission grant alone does not establish which camera the call uses.

Avoid changing the Halloween reference image during this check. A new face introduces another variable while you are trying to isolate camera routing.

If the virtual camera is missing, check permissions and restart the receiver

A missing device and a listed device with a black preview are different symptoms. Start with the missing-device case:

1. Confirm that the desktop face-swap software is running and its processed preview is active.
2. Check Windows camera privacy settings for the relevant application category. Browser calls may also need site-level permission.
3. Fully quit the receiving app, then reopen it with the desktop output already running. Closing a call window may leave the application running in the background.
4. Return to video settings and inspect the camera list again.

Some applications may need to reopen before they recognize an available device. A restart is a useful diagnostic step, but it does not guarantee support.

If the device remains absent in one app while another can receive it, check whether the failing app supports virtual video capture devices in your setup. Where available, its documentation or administrator settings may explain restrictions. Do not assume every desktop client and browser version exposes the same inputs.

If the device is listed but black, reduce the moving parts

Keep the virtual camera selected and return to the source preview. Is the processed face still moving there?

If it is not, investigate capture or processing first. If it is, leave that setup alone and close other camera-using apps and unused browser tabs. Then retry with only the face-swap software and the failing receiver open. Competing camera use can cause capture problems in some setups.

Next, try the physical webcam in the failing app:

• If that is also black, investigate the app’s camera access and general video setup.
• If the physical webcam works but the virtual camera stays black, focus on the virtual-device connection or compatibility.

Change one thing per attempt. Reinstalling software, changing permissions, and switching browsers together makes any improvement difficult to explain.

Choose a fallback before the party starts

Once the intended app shows your moving monster face, verify it through a short call with another participant, or a short recording if recording is the intended workflow. A local preview does not confirm what the audience receives.

If that path still fails, use an app you have verified works, or switch to the physical webcam and practical Halloween props. If you use OBS, verify its capture of the virtual device separately before relying on it for a stream.

Keep the costume expectation realistic, too: real-time face swapping mainly replaces the face. Voice, clothing, horns, capes, and backgrounds need their own treatment. A working camera route gets the processed face into the call; the rest of the costume is a separate decision.