Fix a webcam that is not working in Citrix

The essential answer

A webcam that fails inside Citrix is almost always blocked in one of three places: the local computer has not given Citrix Workspace permission to use the camera, Citrix is not redirecting that camera into the remote session, or the app inside the session has not selected it as the active video input. A working microphone does not mean the camera is available. Webcam video and microphone audio travel on separate Citrix paths, so you can have clear call audio and still get a black preview, a missing camera list, or a permission error for video.

The right next step depends on where you are testing. If the camera already fails in a local app outside Citrix, fix the local device first; Citrix settings will not restore a camera the endpoint cannot open. If video is handled by a meeting-app optimization feature (common with Microsoft Teams or Zoom in a virtual desktop), capture can stay on your computer instead of appearing as a camera inside the remote desktop, so you check that meeting app’s device settings and local camera permission for Workspace, not only tools inside the session. If you use a published desktop, look at the Desktop Viewer device controls; if you use a published application with no desktop toolbar, use Workspace device access and the in-app camera list. A Citrix administrator can disable webcam or USB redirection for the whole site. That policy cannot be turned on from your session alone.

Checks that narrow the cause

Work through the layers below in order. Each test answers a limited question. A pass only supports the components that test actually uses; it is not proof that later layers are healthy. Close other camera apps before you start so an exclusive lock does not look like a Citrix failure.

• Confirm the camera is connected, uncovered, and powered. If it has a hardware shutter or a privacy LED, note whether the LED turns on when a local app opens the camera. This only tests physical presence and basic power, not Citrix.

Use a local camera app on the same computer that runs Citrix Workspace (the Windows Camera app, macOS Photo Booth, or an equivalent). Do this while disconnected from the Citrix session or with no in-session app holding the device.

• If the local preview is black, frozen, or missing, the fault is on the endpoint: connection, cover, local privacy for that app, a driver the operating system cannot open, or another process holding the camera. Stop Citrix troubleshooting until that local preview works. This test does not check Workspace permission or session redirection.
• If the local preview works, hardware and the local stack for that test app are good enough to capture. Next you must still prove that Citrix Workspace is allowed to open the same camera.
• On Windows, open the camera privacy settings and confirm camera access is on for the device, then that Citrix Workspace (and any listed Citrix helper) is allowed. On macOS, open Privacy & Security camera settings and confirm Citrix Workspace or Citrix Viewer is allowed. Turning this on only authorizes Workspace to request the camera; it does not prove the remote app received a device.
• Quit every local app that might hold the camera, including browsers with video sites, meeting clients, and the OS camera app. Then fully quit Workspace, start it again, and reconnect. A camera held locally often never appears in the session, or it appears with a black preview. This check does not distinguish HDX webcam redirection from generic USB redirection.
• In the Citrix session, open the same meeting or capture app that failed and look at its camera list and preview. Note whether any camera is listed, whether a specific local camera or a virtual name is listed, and whether the preview is live, black, or frozen. A missing list points at detection or redirection. A listed camera with a black preview points at capture, exclusive use, or a stalled video stream. A listed camera with a live preview that the app still does not send points at that app’s selected input or its own permission prompt.
• If the meeting product uses Citrix optimization, also open that product’s device settings as they run for the call. Optimized video can use the local camera even when Device Manager or a generic in-session camera tool shows nothing. A result there does not prove non-optimized apps in the same session can capture.
• If you have Desktop Viewer, open its device controls and see whether the webcam is allowed or connected for this session. Allowing it here only affects device mapping for that connection. It does not grant Windows or macOS privacy permission, and it does not choose the camera inside Teams, Zoom, a browser, or a line-of-business app.

What the results support

Finding	What it supports	Check next
Local camera app has no picture	Endpoint hardware, cover, local OS privacy for that test app, local driver, or a local process holding the device. It does not test Citrix.	Restore a local preview before changing Workspace or session settings.
Local preview works; Workspace or Citrix Viewer is denied camera access	The session cannot open the webcam until the local OS allows that Citrix process.	Enable camera access for Workspace, fully quit it, reconnect, then retest the original app.
OS allows Workspace; another local app was using the camera	Exclusive capture on the endpoint, not a missing Citrix policy by itself.	Close the local app, reconnect, retest. If the preview returns, the session was starved of the device.
Desktop Viewer or Workspace shows the camera blocked	Device access for this Citrix connection.	Allow the webcam for the session and retest. If the control is missing or greyed out, treat it as a possible admin policy limit.
No camera in the in-session app list (and optimization is not in use)	The app never received a usable video device: redirection not applied, policy blocking webcam or USB mapping, camera plugged in after connect, or a published app that cannot see client cameras.	Reconnect with the camera already attached; then escalate redirection policy if it is still absent.
Camera is listed; preview is black or frozen	Detection succeeded. Capture failed, the stream stalled, or another process still holds the device. This is not proof the camera is unplugged.	Close competing apps, reselect the camera, start a new preview, reconnect. Do not treat this as a microphone problem.
Camera is listed; preview is live; the call still has no video	Active input selection or the meeting app’s own permission, not device detection.	Choose the intended camera in that app, accept any in-app prompt, and confirm the call uses that device.
Microphone works; webcam does not	HDX audio can succeed while webcam redirection fails. Do not use a mic test as evidence the camera path is healthy.	Keep troubleshooting video: permission, redirection, then in-app camera selection.
Optimized meeting app has video; a browser or other in-session app does not	Optimization is using the local camera for that meeting product only.	Treat other apps as a separate redirection problem; do not assume one working call proves all Citrix video works.

What to change, and how you know it worked

Match the change to the finding. Start with reversible steps: close apps that hold the camera, grant permission, allow the device for the session, pick the correct camera, then reconnect. After each change, retest the original symptom in the same app that failed, not only a different camera tester. Success is a live preview and, for a call, outbound video in that app. If the original app still fails, the change did not fix this issue even if another tool now sees a device.

• If the local camera app failed: reconnect the camera, open a hardware shutter, try a different port or cable if you have one, and turn on OS camera access for apps. Retest the local preview. Only when that preview is live should you open Citrix again.
• If Workspace lacked camera permission: enable it in Windows camera privacy settings or macOS camera privacy for Citrix Workspace or Citrix Viewer. Fully quit Workspace so it restarts with the new right, reconnect, and open the original in-session app. Granting this permission lets Workspace request the camera for sessions you launch; it does not by itself publish the camera to every application.
• If a local app was holding the camera: close those apps and browser tabs, then disconnect and reconnect the Citrix session. Plug the camera in before you connect when you can. Retest the original preview. During USB redirection, the session may hold the camera so local apps cannot use it until you disconnect.
• If Desktop Viewer or a Workspace device prompt blocked the webcam: allow the camera for this connection and start a new preview. If you must reconnect for the mapping to apply, do that and retest. This does not override a site policy that forbids webcam or USB redirection.
• If the wrong camera was selected: in the failing app, choose the camera that matches your local device or the Citrix virtual camera name the session shows, apply the setting, and watch the preview. Switch away from any virtual background or “none” camera option the app offers, then confirm outbound video in a test call if that is the real symptom.
• If no camera appears and you are not on an optimized meeting path: reconnect with the camera already attached and with Workspace allowed to use it. User-side toggles stop here. Enabling HDX webcam redirection or generic USB redirection, or choosing one method so the device is not claimed twice, is an administrator change on the Citrix site and the virtual desktop. Those two methods are different: compressed webcam redirection sends a video stream from the endpoint; USB redirection presents the camera as a USB device inside the session. This article cannot state which method your site uses or which product versions your administrator requires.

Do not update camera firmware, replace drivers, or reset the device as a first Citrix fix. Those steps can drop other USB devices and are only appropriate when the local camera app already fails or when your camera vendor and Citrix administrator give you a documented procedure for your model and Workspace version. This guide cannot verify those procedures or name a supported combination.

Stop and escalate to your Citrix administrator or IT support when the local camera preview works, Workspace has camera permission, competing local apps are closed, the session is a fresh reconnect, and the original in-session app still has no device or a black preview. Ask them to confirm whether webcam redirection, USB redirection, or meeting-app optimization is enabled for your delivery group, and whether the Workspace app version they support is what you are running. Remaining causes sit in site policy, the virtual desktop agent, or the published application’s media stack, which you cannot repair from the camera menu alone.