Quick answer
What this guide helps you determine
Resolve blocked permission, insecure pages, busy devices, missing cameras and privacy controls in a sensible order.
Begin with the observable browser result, repeat it under the same conditions, and change one connection, setting or application at a time. A browser result narrows likely causes but does not certify hardware or decide a repair.
Scope of this check
A browser camera failure usually falls into one of five layers: insecure page, missing browser capability, site permission, operating-system privacy, or unavailable hardware. Reading the exact error and checking those layers in order avoids repeatedly toggling the same permission.
Step-by-step method
- Confirm the page uses a valid HTTPS connection and that the browser reports MediaDevices support. Click Start and read whether the result says blocked, not found, already in use or unsupported rather than treating every failure as “permission denied.”
- Open the address-bar site controls and the operating-system camera privacy panel. Both must allow the browser. Close conferencing, recording and virtual-camera applications that may hold the device, then reload and request access again.
- Reconnect an external camera directly and compare the operating-system camera app. If no application can see it, the browser is not the only failing layer; check the cable, port, driver and manufacturer support.
What to check first
Use these checkpoints to keep the comparison focused. Record the visible behavior rather than assigning a fault label too early.
- Confirm HTTPS and MediaDevices support
- Close apps already using the camera
- Review browser and operating-system privacy settings
How to read what you see
| Observation | What it can suggest | Useful next check |
|---|---|---|
| Permission is explicitly denied | The site or OS privacy choice blocked access. | Allow this origin and the browser application, then reload. |
| No camera is found | The OS exposed no eligible video input to the browser. | Reconnect, enable or test the camera in the system app. |
| The camera is already in use | Another application or tab may hold an exclusive stream. | Stop other previews and try again. |
Common mistakes to avoid
- Do not disable security software broadly for a camera check.
- Do not install an unrelated driver package.
- Do not reset every browser permission before noting the specific error.
Build evidence another person can use
Write down the exact action, visible result and whether it repeats. Include the browser family, operating-system family, connection type and the single comparison that changed the result. Quote the observation directly—for example, “Permission is explicitly denied”—then add where it occurred and which comparison changed it.
Change one condition per comparison and return settings that have no effect. Follow model-specific manufacturer instructions before firmware changes, cleaning, disassembly or warranty action.
When to seek qualified support
If the same problem remains in multiple applications and on another compatible connection or computer, collect the repeatable observations and contact the manufacturer or a qualified technician. Stop using equipment that is physically damaged, unusually hot, wet, sparking or unsafe. Device Test Bench cannot inspect electrical condition or make a repair decision.
Privacy during testing
Our public tests process key events, pointer values, media streams and controller input locally. Do not send private recordings, complete typed text or device identifiers when asking for help. A short description of the behavior, browser and page URL is normally enough.
Questions readers ask
Why does Allow still fail?
Operating-system privacy or another application can block the camera even when the browser site setting says Allow.
Can HTTP pages use a webcam?
Camera access generally requires a secure context such as HTTPS; localhost is a special development exception in many browsers.
Primary technical references
The following specifications define the browser APIs discussed in this guide. They are primary web-platform references, not product repair manuals.