Browser-based video calls and camera tools rely on permission: your browser must explicitly allow a website to access your camera. When that permission is missing, denied, or stuck, the camera simply won't appear — even though the hardware is fine. This guide explains how camera permissions work in every major browser and how to fix them when they go wrong.
How Browser Camera Permissions Work
For privacy, browsers never give a website access to your camera automatically. When a site needs the camera, the browser shows a permission prompt. Your choice — Allow or Block — is then remembered for that site. If you blocked it once, the camera will keep failing on that site until you change the setting, with no new prompt appearing.
HTTPS is required: Browsers only grant camera access to secure (HTTPS) sites. A site served over plain HTTP cannot use your camera at all. This is why camera tools always run on secure pages.
Allowing the Camera in Chrome
Click the icon at the left of the address bar (a tune/sliders or lock icon). Find Camera and set it to Allow. Or go to Settings → Privacy and security → Site settings → Camera, locate the site, and change it from Block to Allow. Reload the page afterward.
Allowing the Camera in Firefox
Click the padlock in the address bar, then find the camera permission and clear or change the block. You can also visit Settings → Privacy & Security → Permissions → Camera to review which sites are blocked or allowed. Reload after changing.
Allowing the Camera in Safari
On macOS, open Safari → Settings → Websites → Camera. Find the site in the list and set it to Allow. Safari also asks per-site on first use, so make sure you did not previously choose Deny.
Allowing the Camera in Edge
Edge mirrors Chrome: click the lock/permissions icon in the address bar, set Camera to Allow, or manage it under Settings → Cookies and site permissions → Camera. Reload the page.
Why the Prompt Sometimes Doesn't Appear
If no permission prompt shows up at all, the usual reasons are:
- You previously blocked the site: The browser remembers and won't ask again. You must manually change it in settings.
- System-level block: The operating system is blocking the browser from the camera entirely. Check OS privacy settings too.
- Another app has the camera: If the device is in use elsewhere, the browser can't acquire it.
- Non-secure page: An HTTP page will never get camera access.
Verifying the Fix
After changing permissions, reload and open a camera test. A correct setup will either prompt you to allow the camera or immediately show your live feed. If it works in the test but not in your video app, the app has its own separate permission to grant.
Related Reading
If your camera fails beyond just permissions, work through our full webcam not working fix. To learn the complete testing workflow, see how to test your webcam online. The same permission model applies to audio — our microphone testing guide covers the mic side.
The Permission Model Explained
Every modern browser treats your camera as a protected resource. A website cannot simply turn it on — it must request access, and the browser asks you to approve. Your decision is then stored per site: approve once and the site can use the camera on future visits; deny once and the browser silently refuses without asking again. This persistence is the source of most confusion, because a site you blocked weeks ago will keep failing today with no obvious prompt explaining why.
Permissions are also scoped to the exact origin — the specific site address. Granting access to one site never affects another, and a site served insecurely over HTTP is refused outright regardless of your choice.
Managing Permissions System-Wide
Browser permission is only one layer. Underneath it, your operating system also controls whether the browser itself may access the camera. On both Windows and macOS, you can grant a site permission in the browser and still see a black feed because the OS is blocking the browser entirely. When troubleshooting, always check both layers: the site's permission inside the browser, and the browser's permission inside the operating system's privacy settings.
Clearing a Stuck Permission
Sometimes a permission gets into a confusing state — the site seems allowed but still fails. The cleanest fix is to reset the site's camera permission entirely, then reload and let the browser prompt you fresh. Each browser exposes this differently, but the principle is the same: remove the stored decision so the browser asks again from scratch. This resolves many cases where toggling Allow and Block repeatedly did not help.
Why HTTPS Is Mandatory
Browsers restrict camera and microphone access to secure pages for a clear reason: media streams are sensitive, and an insecure connection could be intercepted or tampered with. As a result, any legitimate camera tool runs over HTTPS. If you ever encounter a page requesting your camera over plain HTTP, the browser will block it — and that block is a protective feature, not a bug.
Privacy Considerations
Granting camera access is a meaningful permission, so it is worth being deliberate about which sites you allow. Reputable camera tools process your video locally and display it back to you without uploading it. Before allowing camera access, make sure you trust the site and understand what it does with the feed. You can always revoke a permission later through the same settings used to grant it, and reviewing your allowed sites periodically is good practice.
Quick Reference: Fixing a Blocked Camera
- Check the address bar icon for a camera or lock symbol and set it to Allow.
- Open site settings and change the camera permission from Block to Allow, then reload.
- Verify OS-level access so the browser itself is permitted to use the camera.
- Confirm no other app is currently holding the camera.
- Reload on a secure (HTTPS) page and let the prompt reappear.
🚀 Try the Tool
The clearest way to test browser camera permissions is to open a page that requests the camera and watch for the prompt. The Camera Test does exactly this — when you open it, your browser should ask for permission, and your feed should appear once granted.