Browser Camera and Microphone Permissions Explained — Fix 'Allow Access' Issues
Camera or mic blocked in your browser? This guide explains how permissions work in Chrome, Firefox, Safari, and Edge — and how to fix common issues step by step.
You click "Join call," the site asks for camera and microphone access, and something goes wrong. Maybe you accidentally clicked Block. Maybe nothing happened at all. Maybe the camera feed shows up but there's no audio. Maybe it worked yesterday and doesn't work now.
Browser permissions for camera and microphone have more layers than most people realize. This guide explains how they actually work and how to fix the common problems in Chrome, Firefox, Safari, and Edge.
How Browser Permissions Work
When a website wants access to your camera or microphone, it has to ask — both the browser and you. That request comes from a browser API called getUserMedia, which is part of WebRTC.
The permission system has two levels:
Browser-level permissions are specific to each site. Chrome, Firefox, Edge, and Safari all keep a list of which sites you've allowed or blocked. These settings persist between visits. If you blocked camera access for a site, the browser remembers and won't ask again — it just silently denies requests from that site. Operating system-level permissions sit above the browser. On macOS and Windows, the OS has its own camera and microphone access controls. If the OS hasn't granted camera access to your browser application, the browser cannot access the camera regardless of what you've allowed in browser settings. This trips up a lot of people who have fixed the browser settings but still can't get it to work.Both levels need to be correct for a video call to work.
Chrome
Chrome is the most common browser for web-based video calls, and its permission system is fairly straightforward once you know where to look.
Allowing camera and microphone in Chrome
When a site requests camera or microphone access, Chrome shows a small camera icon in the address bar on the right side. Click it to manage the permission.
If you missed the prompt or previously blocked it:
You can also manage permissions globally for all sites at chrome://settings/content/camera and chrome://settings/content/microphone. These pages show you every site that has been granted or denied access, and let you reset them.
Chrome on macOS
On macOS, Chrome also needs OS-level Screen Recording and Camera/Microphone permissions. If you've allowed the site in Chrome but the camera still won't activate, check:
System Settings > Privacy & Security > Camera — Chrome should have a checkmark. System Settings > Privacy & Security > Microphone — same.If Chrome isn't listed, you may need to trigger a camera request to prompt macOS to ask for permission, then approve it in System Settings.
After changing OS-level permissions, quit and relaunch Chrome. The change doesn't apply to an already-running browser process.
Chrome on Windows
Windows 10 and 11 have app-level camera and microphone settings under Settings > Privacy & Security > Camera and Settings > Privacy & Security > Microphone.
Make sure "Allow apps to access your camera/microphone" is toggled on, and that "Allow desktop apps to access your camera/microphone" is also on (Chrome is a desktop app, not a Store app, so the second toggle is the relevant one).
Firefox
Firefox has a slightly different permission interface but works on the same principle.
Allowing camera and microphone in Firefox
When Firefox asks for permission and you deny it, a crossed-out camera or microphone icon appears in the address bar.
To fix it:
Alternatively, go to: Preferences (or Settings) > Privacy & Security > Permissions. Click Settings next to Camera or Microphone to see a list of all sites with saved permissions and change them individually.
Temporary vs. permanent permissions in Firefox
Firefox gives you two options when granting access: Allow for this visit and Allow (permanent). If you chose "Allow for this visit" in the past, Firefox will ask again the next time. This is intentional privacy behavior, not a bug.
If you want permanent permission, look for that option in the permission prompt and select it.
Firefox on macOS and Windows
The same OS-level permission requirements apply to Firefox as to Chrome. On macOS, check System Settings > Privacy & Security for Camera and Microphone. On Windows, check the Privacy & Security settings as described above. Firefox must be listed and allowed at the OS level.
Safari
Safari has the tightest permission defaults of any major desktop browser. It's designed to ask frequently and grant access narrowly.
Allowing camera and microphone in Safari
Safari also has a global toggle: Settings > Websites > Camera (or Microphone) — at the bottom, "When visiting other websites" controls the default for sites not in your list.
Safari and macOS Screen Recording
For screen sharing specifically (not camera/mic), Safari on macOS also requires the Screen Recording permission in System Settings. Camera and microphone do not require it — but if you've been troubleshooting permissions and read advice about Screen Recording, that applies specifically to screen sharing, not camera access.
Safari quirks to know
Safari re-prompts for camera and microphone access more aggressively than other browsers — sometimes once per session or once per visit even if you've previously allowed it. This is a deliberate privacy choice by Apple, not a malfunction. If you keep getting asked, that's expected Safari behavior.
On iOS, Safari permissions work similarly to macOS but the path is: iOS Settings > Safari > Camera and iOS Settings > Safari > Microphone. Set both to "Ask" or "Allow" rather than "Deny."
Edge
Edge is Chromium-based, so its permission system closely mirrors Chrome's.
Allowing camera and microphone in Edge
Global settings are at edge://settings/content/camera and edge://settings/content/microphone — same structure as Chrome's equivalent pages.
Edge on Windows also relies on the OS-level privacy settings described in the Chrome/Windows section above. Both toggles (apps and desktop apps) need to be on.
Mobile Browsers
Android (Chrome)
Chrome on Android asks for camera and microphone when you first visit a site that needs them. If you denied it:
If the site permission is set to Allow but it's still not working, check Android's app-level permissions: Settings > Apps > Chrome > Permissions. Camera and Microphone both need to be allowed there.
iOS (Safari)
On iOS, Safari's camera and microphone permissions are managed in the iOS Settings app, not in Safari itself.
Go to: Settings > Safari > Camera and set it to "Allow" (or "Ask"). Do the same for Settings > Safari > Microphone.
If you're using a different browser on iOS (Chrome, Firefox, Edge), each has its own entry in the iOS Settings app under its app name. Find the browser, tap it, and you'll see Camera and Microphone toggles.
Advanced Fixes
If you've gone through all the browser and OS settings and the camera or microphone still won't work, here are the less obvious things to check.
OS-level permissions aren't saving
On macOS, if you grant permission in System Settings but it reverts or doesn't stick, try this: quit the browser, remove it from the Privacy & Security list by clicking the minus button, then relaunch the browser and trigger the permission request again. macOS will re-add it and prompt you to allow it fresh.
Outdated browser
Browsers update frequently, and older versions sometimes have broken or incomplete getUserMedia implementations. If you haven't updated your browser in several months, update it. Check chrome://settings/help in Chrome or about:support in Firefox to see your current version and trigger an update.
Conflicting extensions
Browser extensions — particularly privacy extensions, ad blockers, and VPN extensions — can interfere with camera and microphone access. Some block getUserMedia requests as a privacy measure.
To test: open the browser in its private/incognito mode (which disables most extensions by default) and try the video call again. If it works in private mode but not normal mode, an extension is the cause. Disable extensions one by one to find the culprit.
Another application is using the camera
On Windows and some Linux setups, only one application can use the camera at a time. If another app (Teams, Zoom, OBS, a second browser window) has claimed the camera, the browser's request will fail silently. Close other applications that might be accessing the camera and try again.
On macOS, multiple applications can share camera access in recent OS versions, so this is less of an issue — but it can still occur with older camera drivers.
Hardware driver issues (Windows)
On Windows, camera driver problems are more common than people expect. Open Device Manager, find your camera under "Cameras" or "Imaging Devices," right-click it, and select Update driver. If that doesn't help, try Uninstall device, restart Windows, and let it reinstall the driver automatically.
Test Before Your Call
The worst time to discover a permissions problem is when you're supposed to be on a call.
videocalling.app lets you test camera and microphone access without needing anyone else to be online. Open a room, let the browser ask for permissions, and confirm that your camera and microphone work before your actual meeting. The site uses the samegetUserMedia API that every other browser-based video call tool uses, so if it works there, it'll work everywhere that uses the same approach.
For more on how browser media permissions connect to the broader video calling stack, see our WebRTC glossary page and the guide on fixing video call quality issues.