Find where your
camera stops working.

How do you locate a virtual-camera failure?

1. Check the physical webcam

   Close the background utility, select the physical webcam in the meeting app and check its prejoin preview. If it fails here, start with device connection, permissions or another app using the webcam.

2. Check the utility’s own preview

   Close the receiving preview if your webcam cannot be shared, then open the utility and select the physical webcam as its input. If this fails while the direct camera works, check that utility’s camera permission and input selection.

3. Check the virtual camera in the meeting app

   Start the utility’s output, keep it running, and select its virtual camera in the receiving app. A good utility preview with a bad receiving preview points toward output activation, camera selection or client compatibility.

4. Check delivery during a call

   A smooth local preview with poor remote video can involve the meeting app, network or another participant’s connection. Local frame rates alone do not prove remote call quality.

Why is the virtual camera missing from the list?

• Confirm that the utility’s camera component is installed or activated, then start its virtual-camera output.
• Reopen the receiving app’s device settings. If its camera list is still stale, restart the app or refresh the browser tab.
• Check minimum OS requirements and any organizational restrictions on software cameras or extensions.
• Check OS and browser camera permissions for the receiving app as well as the utility.

Why is the output black, frozen or empty?

• Confirm the input and output are different. The utility should capture the physical webcam; the meeting app should receive the virtual camera. Feeding the output back into its own input can create a loop.
• Keep the producer open and running. An installed camera device can remain listed even when no new frames are being produced.
• Inspect the chosen source or scene. In scene-based tools, a hidden, disabled or unconfigured source can leave an empty composition.
• Release competing capture. Temporarily close other camera apps and retry one receiving preview.

Daylight shows a scene but no person

In Windows versions with Background only output, stopping the webcam leaves the scene in the virtual camera. Start the webcam to restore the person. A scene without a person can therefore be an intentional output mode.

Why is video laggy or the cutout rough?

Turn off the receiving app’s own blur or background replacement when testing a separate background utility. This removes a second effect pass and makes it easier to identify which stage causes the defect.

• Uneven edges: light your face and shoulders evenly, reduce strong backlighting, and move slowly while checking hair and hands.
• Lag in the utility preview: try a lower capture or processing resolution and close demanding apps. Retest before changing another setting.
• Smooth local preview, poor meeting video: inspect the client’s send resolution and network diagnostics. More local frames cannot repair a weak connection.
• Mirrored text in self-view: the local preview can be mirrored while participants see the correct orientation. Check the receiving output before reversing a background image.

Google’s camera and video-quality guide explains Meet’s send-resolution controls. Its effects guide describes self-view mirroring and possible performance impact.

What can Daylight’s local checks tell you?

Windows releases with Camera and Call Health offer a 30-second local check. Run it while the receiving client is active and compare capture, processing, rendering and virtual-camera delivery. It diagnoses the local pipeline; it does not measure another participant’s screen or your meeting provider’s network.

Standard mode targets 30 fps. Optional High motion attempts 60 fps when the camera and processing pipeline can sustain it; the meeting client can still use a lower frame rate. No universal 60 fps meeting pass is claimed.

For Windows installation errors, close camera and meeting apps before using the reset or setup action supplied by Daylight. Do not use unrelated driver cleanup tools as the first diagnostic step. Check platform and version limits before assuming the Mac release has newer Windows controls.

Sources and related guides

• Microsoft Teams: device and camera settings
• Google Meet: camera selection and resolution
• Google Meet: effects, performance and mirroring
• OBS: virtual camera output and scene selection
• Daylight camera setup
• Choose a video background utility

Reviewed October 2, 2026. This is a diagnostic guide, not evidence that every client, device or processor architecture has been field-tested.