Microphone permissions in Chrome, Firefox, Safari, and Edge
Last reviewed on April 25, 2026
Browsers ask for microphone permission once and remember the answer. If a site that should be able to hear you suddenly cannot, the cached answer is almost always the reason. This guide shows where each major browser stores that answer, how to change it, and how to recover from the most common dead ends — including the cases where the operating system itself is blocking the browser.
Two-layer model. A site needs permission from the browser, and the browser needs permission from the operating system. If either layer says no, the microphone is silent. Always rule out the OS layer before reinstalling drivers or blaming hardware.
Operating system check first
Windows 10 and 11
- Open Settings → Privacy & security → Microphone.
- Confirm Microphone access is on.
- Under Let apps access your microphone, make sure it is on.
- Scroll to the desktop apps list and confirm your browser is allowed.
macOS
- Open System Settings → Privacy & Security → Microphone.
- Find your browser in the list and turn the toggle on.
- If the browser is missing from the list, the prompt has not yet been triggered. Open any tab that uses the microphone, accept the prompt, and check the list again.
Desktop browsers, step by step
Google Chrome
For a single site
- Click the lock icon to the left of the address bar.
- Choose Site settings.
- Under Microphone, set the value to Allow or Ask (default).
- Reload the tab.
For all sites
- Open Settings → Privacy and security → Site settings → Microphone (or visit
chrome://settings/content/microphone). - Choose the default behaviour and review the Allowed and Blocked lists.
Mozilla Firefox
For a single site
- Click the small icon to the left of the address bar.
- If the site has a "Microphone — Blocked Temporarily" or "Allowed" entry, click the small × next to it to clear the saved answer.
- Reload the page; the prompt should reappear.
For all sites
- Open Settings → Privacy & Security → Permissions → Microphone → Settings.
- Review the saved decisions and remove any that should be re-prompted.
- The "Block new requests asking to access your microphone" checkbox is off by default; enabling it stops Firefox from asking on any site, which is sometimes the silent culprit.
Safari (macOS)
For a single site
- Open the site.
- Choose Safari → Settings (or Preferences) → Websites → Microphone.
- Find the site under Currently Open Websites and set the dropdown to Allow.
- Reload.
For all sites
The same panel exposes a default behaviour at the bottom: When visiting other websites. Set it to Ask or Allow as you prefer.
Microsoft Edge
Edge uses the same engine as Chrome, so the steps mirror Chrome closely.
For a single site
- Click the lock icon.
- Choose Permissions for this site.
- Set Microphone to Allow.
- Reload.
For all sites
Visit edge://settings/content/microphone to manage the default and review allow/block lists.
Mobile browsers
Safari on iOS and iPadOS
- Open Settings → Safari → Microphone on the device and confirm Safari is allowed to ask.
- While on the site, tap the aA button in the address bar and choose Website Settings.
- Set Microphone to Allow.
Chrome on Android
- Open the site, tap the lock icon, then Permissions.
- Toggle Microphone on.
- If no toggle appears, Android has not seen a request yet — reload the page so the prompt fires.
Resetting a stuck "blocked" state
Sometimes a browser refuses to re-prompt even after you change the saved decision. The fastest reliable reset:
- Close every tab that has the site open.
- Clear cookies and site data for that single site (most browsers expose this in the same site-info panel where the lock icon lives).
- Quit and relaunch the browser.
- Reopen the site. The prompt should appear on first interaction.
If the prompt still does not appear, check the OS-level settings again. Privacy preferences updated by an OS update or third-party security tool sometimes flip themselves off.
Why the prompt is sometimes invisible
Browsers tie microphone access to user interaction. The prompt appears when a page calls getUserMedia, which usually happens after a click. If the call runs immediately on page load — for example, due to a lingering test that auto-starts — some browsers refuse to show the prompt at all and block silently. Reloading and clicking a clearly labelled button is the most reliable way to surface the request.
Browser extensions can also intercept the call. If you have a privacy extension that blocks media access, allow the site explicitly in the extension's settings, then reload.
Common mistakes to avoid
- Switching to private/incognito mode "just in case". Private windows often default microphone permission to ask-every-time, and any earlier denial is preserved.
- Allowing the site at the OS level only. The browser-level permission is a separate decision, and vice versa.
- Granting "Always allow" on a public computer. Permissions persist across sessions; reset them when you are done.
- Assuming the device picker is the same as the permission switch. Selecting a microphone in a meeting app does not grant the browser permission to use it.
- Trusting a denied prompt as a bug. Most "the site does not work" reports trace back to a saved Block decision from an earlier visit.
For a wider walk-through of why a microphone test might still fail after permissions are correct, see our microphone troubleshooting guide. For the underlying numbers, see audio latency explained. Run the microphone test when you are ready to verify the fix.
← Back to audio tests