Quick answer
What this guide helps you determine
Find site-level permission controls and understand why device labels may remain hidden until access is granted.
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
Camera permission is scoped to a site origin, while operating-system privacy is scoped to the browser application. Granting one does not override the other. A responsible page asks only after a deliberate Start action and provides a visible way to stop the stream.
Step-by-step method
- Verify the address bar shows the correct HTTPS domain. Click Start, read the browser prompt and choose Allow only if you intend to preview the camera on this site. Avoid global “always allow” changes when a per-site decision is available.
- If a previous Block choice suppresses the prompt, open the address-bar site controls, change Camera for this site, and reload. Then check the operating-system privacy panel to ensure the browser itself may access cameras.
- After the preview appears, choose the intended device if several labels are listed. Press Stop, check that the capture indicator disappears and remove the permission afterward if the access was only needed once.
What to check first
Use these checkpoints to keep the comparison focused. Record the visible behavior rather than assigning a fault label too early.
- Use the address-bar site controls
- Select Allow for this site only
- Reload after changing a blocked permission
How to read what you see
| Observation | What it can suggest | Useful next check |
|---|---|---|
| The prompt appears after Start | The browser is asking for an origin-specific decision. | Choose deliberately and verify the preview. |
| No prompt appears and the page says blocked | A stored site or OS decision may be suppressing it. | Open site controls and OS privacy rather than clicking repeatedly. |
| Labels appear only after permission | The browser withheld device-identifying labels before access. | Select the needed camera and avoid sharing the list. |
Common mistakes to avoid
- Do not grant camera access to a misspelled or insecure domain.
- Do not leave a capture indicator active after the test.
- Do not share device labels when reporting a simple permission problem.
Put the guide into practice
Camera access has several gates: the device must be available, the operating system must allow the browser, and the current site must have permission. A permission granted to this tester does not apply to another meeting website.
Find the relevant permission
In Chrome, open Settings → Privacy and security → Site settings → Camera, then inspect the entry for the exact site. Review the selected camera as well. If the browser directs you to system settings, follow that prompt and restart the browser when requested. Labels differ across platforms and versions; use the official Chrome instructions below for the current interface.
If the control cannot be changed
Check whether the browser or computer is managed by work or school. A disabled control can reflect administrator policy. Record the message and site address and ask the administrator about an approved way to use the camera. Changing unrelated browser settings or installing another camera driver does not establish that the policy allows access.
Illustrative examples. These scenarios explain how to compare observations. They are not measured test reports, customer testimonials or confirmed repairs.
The site is blocked; the camera works elsewhere
- Starting observation
- Another permitted application has a picture while this site reports that access was denied.
- Controlled comparison
- Review this site's camera permission and the operating-system permission for the browser.
- How to interpret it
- Success elsewhere makes a missing camera less likely, but does not tell you which permission gate rejected this request.
- Next step
- Change only the relevant permitted setting, reload if required and click Start again.
Permission is allowed but the stream still will not start
- Starting observation
- The site has permission, but the camera is busy, unavailable or the chosen mode cannot start.
- Controlled comparison
- Close competing previews, select another available camera if present, and retry a basic supported mode.
- How to interpret it
- Permission is necessary but does not guarantee an available stream. Keep the exact error rather than calling every failure a blocked permission.
- Next step
- If it persists, test the same camera in the OS camera app and use the manufacturer's guidance.
Your inspection worksheet
Use Observed working, Needs follow-up or Not tested for each item. These labels describe this session, not a hardware certification.
Notes stay in this open page and are not submitted or saved by the site. Print or save as PDF before leaving or reloading. Test links open a separate tab so you can keep this worksheet open.
-
Site permission and selected camera
Record the site setting and exact error, without including private device identifiers.
Open test (new tab) -
OS permission and availability
Check browser access and whether another app is holding the camera.
-
Retry after one change
Record the single change and whether the stream starts and stops correctly.
Continue with a related check
Official setup and troubleshooting instructions
Use the platform or device manufacturer's current instructions when settings differ from this guide.
- Camera and microphone permissions in ChromeGoogle Chrome Help
- Manage camera permissions in WindowsMicrosoft Support
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, “The prompt appears after Start”—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
Can I allow the camera just once?
Browser choices differ, but you can grant for the session and later remove the site permission in the address-bar controls.
Why is the browser missing from OS privacy settings?
The operating system may group desktop applications differently; consult the platform’s current privacy panel and browser documentation.
Primary technical references
The following specifications define the browser APIs discussed in this guide. They are primary web-platform references, not product repair manuals.