Webcam Not Working in Chrome: How to Fix Permissions, Hardware Acceleration, and Camera Conflicts

Published on 2026-11-08 ยท 7 min read ยท By MiniTestLab Engineering Team ยท Category: Video

Launch Companion Diagnostic Tool

Test your hardware right now in your browser with zero install:

Open Webcam Test

Chrome is almost always the problem, not your webcam hardware. The three failure modes that account for roughly 90 percent of cases are a blocked site-level permission stored in Chrome's origin database, hardware acceleration forcing the video pipeline through a GPU path that drops the camera claim, and a second application holding an exclusive lock on the UVC device so Chrome never gets a handle. Your sensor, lens, and USB controller are almost certainly fine.

Confirm the Camera Hardware Is Actually Working

Before touching Chrome, verify the device is alive at the OS level. A bad assumption here wastes 30 minutes. Run Webcam Test in a different browser, Firefox or Edge, using the same URL. If the feed appears there, your hardware is healthy and Chrome is the culprit. If nothing appears in any browser, open Device Manager on Windows (Win + X, then M), expand Imaging Devices, and check for a yellow exclamation on your camera node. On macOS, go to Apple menu, About This Mac, System Report, Camera, and confirm your device is listed with a valid Vendor ID.

USB webcams enumerate as UVC class devices. If Device Manager shows error code 43, the firmware handshake failed, usually from a bad cable or a hub without enough power. Move the cable to a rear USB-A port directly on the motherboard, not through a hub. If the camera has a physical privacy shutter, confirm it is fully open. Some Logitech models like the C920 and C922 have a firmware-level shutter state that persists across reboots.

Also check the Mic Test tool while you are here. Webcams with integrated microphones often share a USB composite descriptor, and if the audio interface is also blocked you have a permission problem at the OS level, not just Chrome.

Fix Chrome Camera Permission at the Site and Global Level

Chrome stores camera permissions per origin in its SQLite preferences database. A single mis-click on the lock icon sets that origin to Block permanently and the browser never prompts again. Here is the exact path to clear it.

  1. Open Chrome and navigate to the site where the camera is not working.
  2. Click the lock icon or the tune icon to the left of the address bar.
  3. Click Site Settings.
  4. Under Permissions, find Camera and set it to Ask or Allow.
  5. Hard-reload the page with Ctrl + Shift + R (Cmd + Shift + R on Mac).

If that origin does not appear in the dropdown, the global camera permission may be off. Go to chrome://settings/content/camera. Confirm that Sites can ask to use your camera is selected, not Don't allow sites to use your camera. Below that, check the Blocked list and remove any entry matching your site's domain.

On Windows 10 and 11, Chrome also inherits the OS-level camera toggle. Go to Settings, Privacy and Security, Camera, and confirm both Let apps access your camera and Let desktop apps access your camera are enabled. Chrome is a desktop app in Microsoft's classification, so the second toggle is the one that matters. On macOS, go to System Settings, Privacy and Security, Camera, and make sure Google Chrome has a checkmark.

Disable Hardware Acceleration to Release the GPU Camera Path

Chrome's hardware acceleration routes the video decode pipeline through the GPU process. On some systems, particularly those with Intel Iris Xe or AMD integrated graphics sharing system memory, this causes the camera capture session to conflict with the display compositor. The symptom is a black frame or a frozen first frame, not an error message, which makes it look like a hardware fault.

Navigate to chrome://settings/system. Toggle off Use graphics acceleration when available. Chrome will ask you to relaunch. After relaunch, test again with Webcam Test. If the feed now appears, the GPU path was the issue. You can leave hardware acceleration off permanently or try re-enabling it after updating your GPU driver.

For Intel graphics, the correct driver path is Intel's own Driver and Support Assistant, not Windows Update. For NVIDIA, use GeForce Experience or the NVIDIA driver download page filtered to your GPU model and OS. AMD users should use the Auto-Detect tool from AMD's support site. A driver that is more than six months old on an integrated GPU is a real suspect here.

Resolve Multiple Application Camera Claim Conflicts

Windows handles UVC camera access through the Media Foundation pipeline. Unlike macOS, which can multiplex some camera streams, Windows before version 22H2 gives exclusive access to whichever process opens the device handle first. If Teams, Zoom, OBS, Discord, or even the Windows Camera app is running in the background with the camera initialized, Chrome gets a MEDIA_DEVICE_FAILED_DUE_TO_SHUTDOWN error internally and shows a generic permission denial to the page.

Application Where to Fully Close Camera Notes
Microsoft Teams Right-click system tray icon, Quit Minimizing does not release the camera handle
Zoom End meeting, then File, Exit Background blur keeps the camera open after calls
OBS Studio Stop Virtual Camera, then close OBS Virtual camera driver claims the physical device
Discord User Settings, Voice and Video, set camera to None, then close app Discord pre-initializes camera on login if video was active last session
Windows Camera Close the app window fully UWP apps release handle on window close, not on minimize

After closing all competing apps, open Task Manager (Ctrl + Shift + Esc), go to the Details tab, and confirm no process named Teams.exe, Zoom.exe, obs64.exe, or Update.exe from those vendors is still running. Then reload Chrome and test.

If you want to check whether your full input chain is healthy after resolving the camera, the Meeting Check tool runs camera, microphone, and speaker in one session, which is useful before a call.

Frequently Asked Questions

Why does my camera work in Edge but not in Chrome?

Edge and Chrome use the same Chromium engine but maintain separate permission databases and separate GPU process instances. A blocked permission in Chrome does not affect Edge. Clear the Chrome origin permission at chrome://settings/content/camera and reload the site.

Chrome shows a camera icon with a red X in the address bar. What does that mean?

That icon means Chrome attempted to access the camera and was blocked, either by the site permission set to Block or by the OS-level toggle. Click the icon directly to open the permission panel for that origin and switch it to Allow, then reload with Ctrl + Shift + R.

My camera worked yesterday in Chrome and stopped today. What changed?

The most common overnight change is a background app update. Teams, Zoom, and Discord all auto-update and sometimes restart background services that pre-initialize the camera. Check Task Manager for those processes. A Chrome update can also reset hardware acceleration behavior, so check chrome://settings/system as well.

Does incognito mode affect camera permissions?

Yes. Incognito mode does not inherit site permissions from the normal profile. When you visit a site in incognito, Chrome prompts for camera access fresh every session and does not save the answer. If the camera works in incognito but not in a normal window, a corrupted permission entry in your normal profile is the cause. Go to chrome://settings/content/camera, remove the blocked entry for that site, and re-allow it.

Can a Chrome extension block my camera?

Yes. Extensions with the webRequest or declarativeNetRequest permission can intercept the getUserMedia call or block the domain the site uses for video. Open a new Chrome profile with no extensions (chrome://settings/people, Add profile) and test the camera there. If it works in a clean profile, disable extensions one at a time in your main profile to find the offender.

How do I know if my webcam is physically damaged versus a software issue?

Run Webcam Test in Firefox or Edge without changing any settings. If the live feed appears there, the hardware is fine and the fault is entirely in Chrome's configuration. If no browser shows a feed and Device Manager shows error code 43 or the device does not appear at all, the USB controller, cable, or image sensor has a hardware fault that software cannot fix.

Launch Companion Diagnostic Tool

Test your hardware right now in your browser with zero install:

Open Webcam Test