← Back to the FAQ

Hardware & System Errors

How to unblock camera permissions in Chrome, Edge, and Safari

Quick answer: Browsers remember a camera denial per site and never ask again. Reset it from the icon left of the address bar, change Camera from Block to Allow, then reload the page. Confirm the operating system also permits the browser itself to use the camera.

Browsers block camera access per-site once you have denied it once, and they will not ask again automatically — you have to reset it manually.

There are two independent layers involved: the browser's permission for that specific site, and the operating system's permission for the browser itself. Both must be granted, and fixing one while the other is blocked looks like nothing happened.

Try It Yourself

Check whether the permission actually took effect

Requests the camera the same way any site would, so you can confirm a permission change worked without joining a real call.

Run the free online webcam test

Chrome — reset the permission for one site

Click the icon to the left of the address bar — a padlock, a tune icon, or a camera with a slash — find Camera in the permissions list, and change it from Block to Allow or Ask.

  1. Click the site-information icon left of the URL.
  2. Set Camera to Allow, or use Reset permission to return to being asked.
  3. Reload the page afterwards; the change does not apply to the already-loaded page.
Chrome site settings permissions panel showing camera, microphone, location and notification dropdowns, with the camera permission set to block and highlightedChrome — Site settingsCookiesSite settingsPermissionsPrivacySecurityPermissions for this siteCameraBlockMicrophoneAllowLocationAskNotificationsBlock!Change Camera from Block to Allow, then reload. The change does not apply untilthe page reloads.
Chrome → site-information icon → Camera. A denial is remembered per site indefinitely, which is why the browser stops prompting.

Chrome — review every site you have blocked

Open chrome://settings/content/camera to see every site you have ever blocked or allowed, and to set the default behaviour for new sites.

This page is the fastest way to find a site you blocked long ago and have since forgotten about, and to confirm the global default is still Sites can ask rather than blocked outright.

Confirm a permission change worked with the free online webcam test before joining a real call.

Edge — the same pattern as Chrome

Edge uses an almost identical flow: click the site-information icon in the address bar, find Camera, and switch it to Allow. The global list lives at edge://settings/content/camera.

Because both browsers share the same engine, a fix that works in one applies unchanged in the other.

Safari — permissions are managed centrally

Go to Safari → Settings → Websites → Camera to see and change permissions for every site at once, and to set what Safari does by default for sites you have not visited.

Safari differs from Chrome here: rather than a per-page control, it presents one list covering currently open sites and previously configured ones together.

If permissions look correct but the camera still fails, the OS Permission Doctor checks each layer in turn.

Confirm the OS-level permission for the browser itself

All three browsers depend on the operating system permitting camera access to the browser. On Windows check Settings → Privacy & Security → Camera; on Mac check System Settings → Privacy & Security → Camera.

On macOS a browser only appears in that list after it has requested the camera once, so open a camera-using site first if yours is missing.

If it is still blocked, test with extensions disabled

Some browser extensions, especially privacy and ad-blocking ones, intercept media permissions before the page ever sees them.

Try in an incognito or private window with extensions disabled. Working there and failing in a normal window isolates the cause to an extension, which you can then re-enable one at a time.

To find out whether something else is intercepting the request, run the Camera Block Detector.

Exact permission paths in Chrome, Edge, Safari and Firefox

Each browser stores camera permissions differently, and the global page is usually faster than the per-site control.

Google Chrome

chrome://settings/content/camera

The site-information icon handles one site; this page lists every decision you have ever made.

Microsoft Edge

edge://settings/content/camera

Identical behaviour to Chrome, since both are built on the same engine.

Safari

Safari → Settings → Websites → Camera

Safari also honours a separate per-profile setting on iOS and iPadOS, which does not sync from the desktop.

Firefox

about:preferences#privacy → Permissions → Camera

Firefox offers a Block new requests checkbox that silently denies every site, which is worth confirming is unticked.

The table below shows where each browser stores its camera permission and how much control it gives you over it:

Practical ceiling and manual control available per app
AppPractical ceilingManual control
Google ChromePer-site allow, block or askPer-site and global default
Microsoft EdgePer-site allow, block or askPer-site and global default
SafariPer-site allow, ask or denyPer-site and default for other sites
FirefoxPer-site allow or blockPer-site, plus a global block-all option

Troubleshooting checklist: camera blocked in the browser

Two layers to clear. Start with the browser, then confirm the operating system.

  1. Click the site-information icon left of the address bar and set Camera to Allow.
  2. Reload the page, since permission changes do not apply to an already-loaded page.
  3. Open your browser's global camera settings page and check the site is not listed as blocked.
  4. Confirm the global default is set to ask rather than block for new sites.
  5. Check the operating system permits the browser itself to use the camera.
  6. On macOS, open a camera-using site once so the browser appears in the privacy list.
  7. Retry in an incognito or private window with extensions disabled.
  8. Re-enable extensions one at a time to identify which one intercepts the permission.

Related Guides

Go Further

On a school or work Chromebook the block is often administrator policy rather than a browser setting, which the Chromebook guide explains.