Remote Desktop webcam not working

The essential answer

A webcam that works on your local PC often fails in a Remote Desktop session because the remote computer never receives the camera. Windows Remote Desktop does not send webcam video unless camera redirection is turned on at the client, allowed on the remote side, and then chosen as the active camera in the remote app. Microphone audio is a separate path; fixing speakers or a mic will not restore video.

Three conditions change the next step. If the camera already fails on the local PC before you connect, treat it as a local device, driver, or privacy-permission problem. If you are using a product other than Windows Remote Desktop, use that product’s own camera or USB-device sharing controls; the Windows client checkboxes below will not apply. If the remote session is locked down by an administrator, device redirection can be disabled by policy even when the client looks correct, and you will need that policy changed.

Separate detection, permission, and input selection

Webcam video capture is not the same as microphone audio capture. A redirected camera can appear in the remote session while the mic stays local, or the reverse. Diagnose in this order: whether the remote session can see a camera at all (detection), whether the remote operating system and the app are allowed to use it (access permission), and whether the app is pointed at that camera rather than another device (active input selection).

• Detection: in the remote session, open the camera or sound settings and confirm a camera device is listed. If none appears, redirection or a remote policy is blocking the device before any app can use it.
• Access permission: on the remote PC, camera privacy must allow desktop apps and, where the OS offers it, the specific app. A listed camera that still shows a black preview is often a permission block, not a missing device.
• Active input selection: in the remote app (meeting software, browser, recording tool), open video settings and choose the redirected camera by name. Apps keep their last camera choice and will not switch automatically when a Remote Desktop camera appears.

Turn on camera redirection on the client

On a Windows Remote Desktop Connection client, open Show Options, then Local Resources. Use the local devices and resources controls (often under More) and enable cameras or video capture devices before you connect. Apply the change, disconnect if you are already in a session, and connect again. Redirection is decided at logon; toggling the checkbox during an active session does not attach the camera.

If you launch the session from a saved .rdp file, that file can override the client UI. Open the file in a text editor and confirm camera or video-capture redirection is not set to disabled. Reconnect after saving. Documented field names vary by client version; if the file has no camera-related line, the UI setting on the client you used to start the session is what applies.

Microsoft’s Remote Desktop apps on other platforms also expose a cameras or local-devices toggle in connection or session settings. Enable it for that saved PC, then start a new session. The remote host still has to allow redirected cameras; a client-only change is not enough.

Confirm the remote PC allows the camera

On the remote Windows PC, open camera privacy settings and allow camera access for the device, then for desktop apps if that switch exists. If the meeting or browser app has its own camera toggle, turn that on as well. A UWP or Store camera app can have permission while a desktop meeting app does not, so grant access for the app you actually use in the session.

Group Policy and similar management tools can disable Plug and Play device redirection, camera redirection, or both. When those policies are in force, the client checkboxes have no effect and no camera appears in remote Device Manager or camera settings. That is an administrator-controlled condition; there is no supported end-user override on the session host.

Some remote session hosts never supported camera redirection, or support it only for specific session types. Published RemoteApp programs, older session-host roles, and locked-down virtual desktops are common cases. If no camera device is visible after a clean reconnect with client redirection on, the host configuration is the likely limit. This article does not list version-by-version support; check the remote Windows edition and Remote Desktop role documentation for that host.

Select the redirected camera in the remote app

Once a camera is listed on the remote PC, open the remote app’s video or camera settings and pick that device. Redirected cameras often use a generic name rather than the local model name. Preview the feed there. If the preview is black, another process on the remote PC may already hold the camera; close other camera apps in that session and try again.

Browsers in the remote session need their own camera permission in addition to Windows privacy settings. Allow the site when prompted, then choose the redirected camera in the site’s device list. Closing the tab does not always release the camera; quit the browser fully if the device stays busy.

Local camera checks when redirection looks correct

The Remote Desktop client can redirect only a camera the local operating system already exposes. On the local PC, confirm the webcam appears in camera settings, that camera access is allowed, and that a simple local camera app shows a live image. Unplug and replug a USB webcam on the local machine, or disable and re-enable the device, then reconnect the remote session.

Exclusive local use can also block redirection. If a local meeting app, browser tab, or camera utility has the device open, the remote session may get no device or a frozen frame. Close local apps that use the webcam before you connect.

Microphone versus webcam in the same session

Remote Desktop treats recording audio and camera video as different redirected devices. Enabling microphones or audio recording under Local Resources does not enable cameras, and enabling cameras does not enable the mic. If colleagues hear you but see no picture, keep camera redirection, remote camera permission, and app camera selection in scope. If they see you but hear nothing, switch to microphone redirection, remote microphone privacy, and the app’s microphone input instead of repeating camera steps.

When these steps are not enough

Some remote apps use camera interfaces that do not accept a redirected device even when Windows lists it. Virtual cameras, infrared-only sensors, and multi-endpoint USB devices are also uneven; documented behavior is that redirection targets a standard camera endpoint the session host can enumerate, and devices that do not enumerate that way may never appear. There is no supplied test matrix in this brief for specific meeting products, USB models, or Windows builds, so treat app-specific failures as a compatibility question for that app and host rather than a confirmed defect in the steps above.

If detection, permission, and input selection are all correct and the preview is still black, capture whether the camera is missing from remote settings entirely, listed but denied, or listed and selected with no frames. That distinction is the information an administrator or vendor needs next.