Browser Microphone Permission Blocked
Last reviewed · fixmic team
The browser is the gatekeeper to your microphone. If you clicked Block once, dismissed the popup, or landed on a site that never asked, no page on the web can record audio until you fix the permission. This guide walks through the three states a permission can be in, how to identify which one is yours, and the exact path to grant access — for every major browser.
Try this first
Look at the left side of your address bar. If you see a tune/sliders icon (Chrome, Edge, Brave, Arc, Opera) or a lock/permissions icon (Firefox, Safari), click it, find Microphone, set it to Allow, and reload the page. This fixes most permission problems in 5 seconds.
1. First — which permission state are you in?
Browser microphone permission has three states, and the fix differs for each. Identify yours before you start clicking.
State A — 'Asked once, you (or someone) clicked Block'
The popup appeared, the choice was Block. The site stays blocked. No popup will appear again until you reset it manually. The visual cue: a small microphone icon with a red strike-through appears near the address bar after you try to use the mic.
State B — 'Never asked'
The browser has not requested permission on this site yet. Click the test/microphone button on the page; the popup should appear automatically. If it doesn't, see section 5 — something is suppressing the request.
State C — 'Asked, you closed the popup'
You hit Escape or clicked outside the popup. Browsers treat this as a soft denial (different from explicit Block). Reload the page and click the mic button again — the popup will reappear. No settings to change.
2. Chrome family (Chrome, Edge, Brave, Arc, Opera)
All Chromium-based browsers share the same permission UI. Since Chrome 117 (September 2023), the padlock icon was replaced with a 'tune' icon (sliders). The functionality is the same — it opens site information and permissions.
Click the tune icon, then 'Site settings'
The tune icon is on the left of the URL. Click it, then pick 'Site settings' (or 'Permissions' on some versions). A new tab opens with all permissions for this site.
Set Microphone to Allow
Find the Microphone row. Use the dropdown on the right to switch it from Ask / Block to Allow. Then return to the original tab and reload.
Or if a popup appeared earlier — grant it directly
When the popup is on-screen, the only correct click is the blue 'Allow' button on the right. Don't click outside the popup or hit Escape — that counts as a soft denial.
Power-user shortcut
Paste chrome://settings/content/microphone (Edge: edge://settings/content/microphone, Brave: brave://settings/content/microphone) in the address bar to jump straight to the global microphone settings list. Find the site under 'Not allowed to use your microphone', click the trash/remove icon, reload.
How to spot a blocked site
After you try to use the mic on a blocked site, a small microphone icon with a red strike-through appears in the address bar (near the right edge). Click that icon to get the inline 'Always allow' option without leaving the page.
3. Firefox
Firefox handles permissions differently — instead of changing the URL bar icon, it shows a small permission glyph to the left of the URL whenever a site has any active permission (granted or blocked).
If the permission popup is currently showing
Pick your microphone from the dropdown (Firefox lists all available devices by name — useful when several are connected). Tick 'Remember this decision' so you only do this once. Click 'Allow'.
If you already blocked the site
Click the permissions icon to the left of the URL (looks like a small mic or camera glyph with a red dot for blocked). In the dropdown that opens, click the X next to 'Use the Microphone — Blocked Temporarily' or 'Blocked'. Reload the page — the popup will reappear, and this time pick Allow.
Global permissions: about:preferences#privacy
Paste about:preferences#privacy in the URL bar, scroll to Permissions → Microphone → 'Settings…'. Find the site in the list, change its status, or remove it entirely.
4. Safari (macOS and iOS)
Safari handles permissions through Settings rather than an inline UI. The flow differs between Mac and iPhone/iPad — and Safari Private Browsing windows reset permissions every time they close.
Mac: Safari → Settings → Websites → Microphone
Open Safari. Top menu bar: Safari → Settings (formerly Preferences) → Websites tab → Microphone in the left sidebar. Find the site under 'Currently open websites' or 'Configured websites'. Switch its dropdown to Allow.
Mac: the per-site shortcut
In the address bar, click the 'AA' menu (left side of the URL) → 'Website Settings…'. The same Microphone dropdown is here without leaving the page.
iOS / iPadOS: Settings app → Safari → Microphone
Open the Settings app (the gear icon on your home screen). Scroll to Safari → Microphone. Set the default to Ask, then revisit the site — the popup will appear. Per-site overrides are managed under Settings → Safari → 'Settings for Websites' on newer iOS versions.
Private Browsing caveat
Safari Private Browsing windows do not persist microphone permissions. If you're testing in a private window, the grant disappears the moment you close the window. Use a regular window for permanent grants.
5. The popup never appears at all
You click the mic button. Nothing happens — no popup, no error, just silence. This is not a permission problem. Something is preventing the browser from even reaching the permission system.
HTTPS is required
Modern browsers only allow getUserMedia (microphone access) on HTTPS pages — and localhost as a developer exception. If the page URL starts with http:// (no 's'), the browser silently refuses the request and shows no popup. Force https:// in the URL, or contact the site owner.
iframes need allow="microphone"
If the page runs inside an iframe (embedded inside another page), the outer page must add allow="microphone" to the iframe tag. Without it, browsers reject the request silently. View the page source to check — if you see an iframe wrapping the test, this may be why.
Permissions-Policy header
Sites can send a Permissions-Policy: microphone=() HTTP header that disables microphone for the entire page. Open the browser's developer tools → Network tab → click the page request → Response Headers — search for 'Permissions-Policy'. If you find it disabling microphone, the page itself blocks the feature.
A previous permanent Block
State A above. Once permanently blocked, the popup intentionally never reappears. The browser is doing what you told it to. Use sections 2–4 to unblock the site explicitly.
Browser extensions intercepting media
Privacy-focused extensions (uBlock Origin in advanced/Medium mode, NoScript, Privacy Badger, some VPN/anti-tracker extensions) can intercept getUserMedia before the browser shows the prompt. Open an incognito/private window with extensions disabled and try again. If the popup appears there, an extension was the cause.
6. Permission granted, but the browser still sees no microphone
You allowed permission. The page is HTTPS. The popup appeared. But the microphone dropdown is empty, or the test reports 'no device detected'. The browser has permission — it just has nothing to expose. This is an OS-level block, one layer below the browser.
Windows: 'Let desktop apps access your microphone'
Settings → Privacy & security → Microphone. Confirm all three toggles are on: 'Microphone access', 'Let apps access your microphone', and especially 'Let desktop apps access your microphone'. Chrome, Firefox, and Edge all count as desktop apps — without the third toggle, no per-site grant works.
macOS: System Settings → Privacy & Security → Microphone
Toggle your browser ON in the list (Chrome, Safari, Firefox, Brave — each one separately). Then fully quit the browser (Cmd + Q, not just close the window) and reopen it. macOS only applies the change on relaunch.
Linux: PulseAudio / PipeWire input routing
Open pavucontrol (PulseAudio) or pwvucontrol (PipeWire) → Recording tab. While the browser is asking for audio, an entry for the browser should appear here. Pick the right input source from its dropdown.
Still no microphone in the browser?
If permission is granted at both the browser and OS level and the device still does not appear, the cause is usually one of these:
- Private / Incognito windows treat permissions as ephemeral. Your grant disappears when the window closes. Use a regular window.
- Corporate-managed browsers may block microphone permission via admin policy. Look for a 'Managed by your organization' label in the browser's settings — ask IT to lift the policy.
- A VPN or interception proxy that re-signs HTTPS can strip the secure context flag, silently disabling microphone APIs. Disable the VPN to test.
- Browser updates occasionally regress permissions. If everything worked yesterday and breaks today, restart the browser and re-grant the permission once.
- Run the live test on the fixmic homepage — it gives a specific error message (permission denied, no device, busy) that pinpoints which of the three states you're actually in.
Related guides
- Google Meet microphone not working — Same browser permission flow, applied to Meet specifically.
- Zoom microphone not working — For Zoom-on-the-web (the desktop app uses OS permission instead).
- Fix the microphone on Windows — The OS-level "Let desktop apps access" toggle that gates every browser.
- Fix the microphone on Mac — macOS Privacy & Security per-browser permission grants.
- Discord microphone not working — Discord-in-browser uses the same permission system; the desktop app does not.
- Microphone troubleshooting guide — Top-to-bottom diagnostic if permissions are not the cause.
Test your microphone now
The live diagnostic on the homepage tells you in one click whether the browser can see the mic, whether the OS is blocking it, or whether the hardware is the problem.
Run the microphone test