Blocking a website’s access to your Chrome microphone or camera is a sensible step — especially for sites that shouldn’t need these permissions in the first place. News sites, shopping pages, and random web services have no legitimate need for your camera or microphone, yet many include the necessary JavaScript to request them opportunistically. This fits into the wider topic we cover in our Chrome How-To Guides.
The quickest way to see what you’ve already allowed: chrome://settings/content/camera and chrome://settings/content/microphone. Scroll through the “Allowed” sections. If anything appears that surprises you — a site you don’t use for video calls, or a site you visited once and clicked “Allow” without thinking — remove it now.
Blocking camera and microphone globally
You have three options for the global default for each permission:
- Sites can ask (default): Chrome shows a prompt each time a new site requests access. You decide per-site. This is the right choice for most people — it doesn’t lock you out of video calls but keeps you in control of what gets access.
- Don’t allow sites to use your camera/microphone: blocks all sites by default. Prompts never appear. Video calls in the browser (Google Meet, Zoom web, Teams web) stop working unless you specifically add exceptions for those sites.
- Custom exceptions: the most granular option — block by default, but add specific allowed sites (meet.google.com, zoom.us, etc.) so those work while everything else is blocked.
To set up the third option (block by default with specific exceptions): change the global default to “Don’t allow” → then use the “Add” button under “Allowed to use your microphone” to add the specific sites you trust. This is the most privacy-protective configuration that still allows legitimate use.
Blocking for a specific site you’re currently visiting
If a site is prompting for camera or microphone access and you want to deny it permanently: click the camera/microphone icon that appears in the address bar during the prompt → select “Always block [camera/microphone] for [site].” This adds the site to the blocked list without going into settings.
If you’ve already allowed a site and want to revoke it: while on the site, click the lock icon in the address bar → Permissions → find Camera or Microphone → change from “Allow” to “Block.” The change takes effect immediately; you don’t need to refresh.
System-level controls in Windows 11
Chrome’s browser-level permissions work alongside Windows’ own privacy settings. Windows 11 has a system-level toggle that controls whether any application — including Chrome — can access the camera or microphone.
Settings → Privacy & security → Camera → “Let apps access your camera” must be On for Chrome to access the camera at all. The individual app toggle for “Google Chrome” below that must also be On. If either is Off: Chrome sees no camera, regardless of what Chrome’s own permission settings say.
This is the reason “I allowed the camera in Chrome but it still doesn’t work in Google Meet.” The Windows permission was either off for Chrome or off globally. Check both levels: Windows privacy settings first, then Chrome’s own settings.
Disabling microphone access specifically for a video call app
A nuance: if you want video but not microphone access for a specific site — or microphone but not camera — you can set these independently. The lock icon → Permissions shows Camera and Microphone as separate entries. You can allow one while blocking the other for any given site.
Practical use: a site where you want to watch a livestream via camera but don’t want the site to access your microphone. Allow Camera → Block Microphone → the site sees your video but can’t hear you. Or for a site where you want to dial in but not be on camera: allow Microphone → Block Camera.
Our guide on Chrome site permissions overview covers all permission types together, and our article on Chrome privacy settings covers the broader picture. For Chrome’s official documentation on camera and microphone permissions, Google’s Chrome Help covers device permission behaviour across different operating systems.
Checking if a site is currently using your camera or microphone
Chrome shows a red dot on the browser favicon when a tab is actively recording. The tab that’s using camera or microphone shows the icon in use. Click the red dot/camera icon in the browser’s tab area → it shows which permissions are active and offers a quick “Stop” button to revoke access without going into settings.
This real-time indicator is more reliable than memory — you can forget you gave permission to a site, then see the indicator and know something is currently active. The indicator appears for any active recording session, whether or not you’re currently looking at that tab. If you notice the indicator on a tab you’re not actively using: that site may be doing background recording. Clicking Stop ends the session and effectively revokes access until the next time you visit and re-allow.
| Goal | Where to change it |
| Block camera/mic on one specific site | Lock icon in address bar → Permissions |
| Block camera/mic on all sites by default | chrome://settings/content/camera (or /microphone) |
| Allow only specific sites with camera/mic | Block globally → add exceptions via “Add” button |
| Stop an active camera/mic session | Click the recording indicator icon in the tab |
| Chrome can’t access camera at all | Windows Settings → Privacy → Camera → allow Chrome |
Managing camera and microphone access in Chrome is more layered than most users expect — browser permission, per-site permission, and OS-level permission all interact. Understanding these three layers means you can fix problems (camera not working in Meet) and configure protection (all non-video sites blocked) without needing to guess what’s wrong when something doesn’t behave as expected.
macOS camera and microphone controls for Chrome
On macOS: the equivalent system-level controls are in System Preferences → Security & Privacy → Privacy → Camera (and Microphone). Chrome must be listed and checked here for any camera or microphone access to work. If Chrome isn’t in the list: open Chrome → visit a site that requests camera → macOS prompts to add Chrome to the allowed applications. If Chrome is in the list but unchecked: check the box.
macOS also shows the microphone and camera status indicators in the menu bar (green dot for camera in use, orange dot for microphone). These system-level indicators are separate from Chrome’s browser tab indicators — you can see both when a browser tab is actively using these devices.
Hardware-level camera disable
For maximum assurance that no software can access the camera: a physical webcam cover or privacy shutter (available on most modern laptops as a built-in feature, or as a £2 adhesive cover for webcams without one) provides hardware-level protection that no permission system can override. Software can’t see through tape.
This approach is common in high-security environments and for users who want certainty beyond what software settings provide. A permission system can theoretically be bypassed by malicious software; a physical cover cannot. For camera specifically — where the concern is visual surveillance — hardware protection gives certainty that software settings don’t.
The microphone equivalent is harder to implement physically, since microphone holes on laptops are small and multiple. Some users put a small piece of tape over microphone openings, though this can muffle but not completely block audio capture on most hardware designs. A hardware microphone killswitch (available on some privacy-focused laptops) is the more thorough physical approach.
Extensions that affect camera and microphone access
Some Chrome extensions claim to provide additional camera and microphone privacy controls. These are worth treating with skepticism: an extension that intercepts camera access has itself been granted broad permissions to see your media streams. You’d be replacing a website’s camera access with an extension’s camera access, which isn’t obviously better.
Chrome’s built-in permission system is sufficient for managing which sites get camera and microphone access. The system-level OS controls provide an additional layer. Third-party extensions aren’t necessary and introduce their own trust considerations — an extension that claims to block camera access needs camera access itself to intercept and block it, which gives it the same access you’re trying to prevent others from having.
Stick to Chrome’s native permission controls and the OS-level privacy settings. They’re adequate for the threat model most users face (websites requesting inappropriate permissions) without introducing additional layers of software that you’d need to trust just as much as the websites you’re trying to protect against.
What happens when you deny camera or microphone access
When you deny camera or microphone access on a site, Chrome adds it to the blocked list — and importantly, the site cannot re-prompt you. The browser silently returns an error to the site indicating the device is unavailable. Sites handle this differently: video conferencing tools typically show an error message explaining that camera access was denied; less transparent sites may just show nothing or behave incorrectly without explaining why.
If you previously blocked a site and now want to grant access: the site won’t prompt you again automatically. You need to manually update the permission. The address bar lock icon method is fastest: navigate to the site → click the lock icon → Camera or Microphone → change from “Block” to “Allow” → reload the page. The site can then access the device on the next load.
Camera access in embedded iframes
Some websites embed video conferencing tools or camera-using features in iframes — a frame inside the main page that loads a different domain’s content. The camera permission for an iframe can differ from the permission for the main site.
If you’ve allowed camera access for website A, but website A embeds a video tool from website B inside it: website B may also need camera permission. Chrome may show a separate permission prompt for the embedded content, or it may inherit the permission from the parent site depending on how the site is coded. If camera access isn’t working on an embedded tool despite having granted permission for the main site: check if there’s a separate permission entry for the embedded tool’s domain in chrome://settings/content/camera.
Reviewing access after meetings
A practical habit: after video calls, close the tab and confirm the recording indicator in other tabs is gone. Some video call services continue to hold camera and microphone access even after the call ends, until the tab is closed or you manually revoke access. This isn’t malicious — it’s usually because the page doesn’t properly release device access when the call ends — but it means your camera is technically “in use” to software on that page while the tab remains open.
The red dot indicator on the tab gives you visibility of this. If a call has ended but the indicator is still showing: either refresh the page (which releases the devices on most services) or close the tab. From a privacy perspective: getting in the habit of closing video call tabs after meetings rather than leaving them open is a minor but sensible practice.
Chrome’s camera and microphone permission management is well-designed when you understand its layers. The address bar is your fastest access point for per-site control. The settings pages give you the complete view of what’s been allowed. And the recording indicator tells you in real time when something is actively using your devices. These three tools together give you practical, effective control without needing to turn off camera and microphone access globally and lose the ability to do video calls. If this sounds familiar, How to Clear Chrome Cache Safely is worth a look.
One useful context for why this matters: camera and microphone access are among the most privacy-sensitive capabilities a browser can grant. Most other browser permissions (location, notifications, clipboard) are less immediately personal. Camera and microphone access, if granted to the wrong site, allows visual and audio capture of your environment. Understanding exactly how to control these permissions — and verifying what currently has access — is more valuable than knowing how to configure any other browser permission type. Our guide on Chrome Dark Mode covers an adjacent issue.
For anyone who finds they’re regularly managing these permissions: adding the shortcuts to your browser toolbar makes the process faster. The address bar lock icon is always available — it’s the most accessible entry point for permission management on any site. Combined with the knowledge of where to find the global settings (chrome://settings/content/camera) and the OS-level controls (Windows Privacy Settings or macOS System Preferences), you have complete, layered control over one of the most sensitive capabilities your browser exposes. See also Disable Chrome Notifications for a related case.
