Chrome Camera Permission Not Working

What this symptom means

A permission failure can block perfectly healthy hardware. DeviceOK separates browser permission from whether the device exists and produces a usable signal.

Diagnostic principleTreat 'not detected', 'permission denied', 'black image', 'frozen image', low resolution and low frame rate as different failures. A single generic webcam fix path wastes time because each state points to a different layer.

Fault tree

Camera fault tree

Use the observation that best matches what you can reproduce. Do not treat every cause as equally likely.

Privacy shutter or permission

Evidence: The camera is listed but video is blocked or black immediately.

Next: Open the physical shutter, check browser permission, then OS camera privacy settings.

Another app owns the camera

Evidence: The camera works after closing Teams/Zoom/OBS or after rebooting.

Next: Close competing apps and retest before touching drivers.

Mode/bandwidth issue

Evidence: Video works at lower resolution/FPS but not at the requested mode.

Next: Reduce resolution/frame rate, connect directly, and remove hubs/capture chains.

Detection or hardware path

Evidence: No camera appears in DeviceOK or another trusted app.

Next: Check cable/USB port, OS recognition, official driver/firmware, then hardware.

Interpret the result

Evidence matrix

A test result is useful only if it changes the next troubleshooting branch.

ObservationWhat it supportsPrioritize next

Live preview worksA camera stream successfully reached the browser.Affected app settings, device selection, virtual camera, permissions or app contention.

Camera listed, preview blackEnumeration succeeded but usable frames are not reaching the preview.Shutter, source selection, capture source, app contention, privacy or camera pipeline.

Preview starts then freezesThe stream opened and then stopped updating.USB stability, bandwidth, driver/firmware, competing apps or power management.

No camera listedThe browser cannot enumerate a camera endpoint.Connection, OS recognition, privacy policy, disabled device or hardware.

Fast baseline

Rule out the simple causes first

1
Allow Camera in the site permission control.
2
Verify Chrome Settings > Privacy and security > Site settings > Camera.
3
Verify operating-system camera access.

Full sequence

Work from reversible checks to invasive ones

Do not reinstall hardware drivers before checking the site/browser and operating-system privacy controls.

1
Allow Camera in the site permission control.
2
Verify Chrome Settings > Privacy and security > Site settings > Camera.
3
Verify operating-system camera access.
4
Reload and retest with DeviceOK.

Platform branches

Where the setting lives

Windows

Settings → Privacy & security → Camera
Open the Windows Camera app for an independent comparison
Use Device Manager only after checking privacy/shutter and external USB path

macOS

System Settings → Privacy & Security → Camera
Quit apps that may be holding the camera
For external cameras, test a direct port/cable before a dock

Browser

Confirm the correct camera in site permissions
Reload after changing permission
Inspect active resolution/FPS separately from simple detection

If it works in DeviceOK

Use the passing DeviceOK test to narrow the problem to the specific app or settings layer.

If it also fails here

If DeviceOK also fails, step back to permissions, connection, OS configuration, and device-level troubleshooting.

Escalation threshold

When software troubleshooting has stopped being high value

No image in DeviceOK and the OS camera app
Repeated disconnect/reconnect with a direct known-good port
Physical shutter/hinge/cable damage
OEM diagnostics or service tools identify a camera module fault

Changed one variable?After permission is granted, rerun the relevant live test and confirm the device produces the expected signal/output. Retest under the same condition so the result is comparable.

Retest Webcam test