Why is my mic blocked?

What a browser mic permission actually is

A microphone permission is a per-site, per-browser flag that says whether a page is allowed to request an audio stream from your hardware. It isn't a system-wide setting — each site you visit gets its own independent yes/no/ask, stored against that site's origin, so granting Zoom access in your browser has no bearing on whether a random web page can also listen in. The browser enforces this deliberately: a microphone is one of the more sensitive things a web page could ask for, so unlike most page content, it requires an explicit, revisitable grant rather than working by default.

Why sites need to ask at all

Before permission APIs existed, there was nothing stopping a page from silently recording audio in the background the moment it loaded. The permission prompt exists specifically to close that gap — a site has to call the browser's media API, which triggers a visible prompt, and only after you click Allow does any audio data become available to the page's code at all. This is also why mic access requires a "secure context" (HTTPS, or localhost during development) — browsers won't even offer the permission prompt on a plain HTTP page, since an unencrypted connection could let the request or the audio itself be intercepted in transit.

Common reasons permission gets stuck denied or blocked

The most common cause is simply having clicked "Block" once, sometimes by accident or sometimes deliberately for a site you didn't trust at the time — that choice is remembered indefinitely until you clear it. Beyond that: some browsers block the prompt entirely if the page isn't served over HTTPS, if the tab lost focus at the exact moment the request fired, or if a browser extension (privacy or ad-blocking tools especially) is intercepting media permissions site-wide. It's also possible for the browser to report a permission as granted while the OS itself is still blocking the hardware — which looks identical from inside the page but needs a completely different fix.

How to reset it, per browser

• Chrome / Edge — click the lock or tune icon at the left of the address bar, find Microphone in the site permissions list, and switch it from Block to Allow (or Ask). A page reload is usually required afterward.
• Firefox— click the lock icon, open "Connection secure" → "More information" → Permissions tab, or simply clear the microphone permission from the padlock dropdown directly and reload.
• Safari — go to Safari → Settings → Websites → Microphone, find the site in the list, and change it to Allow. Safari also has a separate global default at the bottom of that same panel.

OS-level permission layers that can block a mic even when the browser allows it

This is the step people miss most often: the browser can report "permission granted" while the operating system is still refusing the browser itself access to any microphone. On Windows, check Settings → Privacy & security → Microphone, and confirm both the master toggle and the specific entry for your browser are turned on. On macOS, check System Settings → Privacy & Security → Microphone, and make sure your browser is checked in that list — macOS will silently withhold audio from an unchecked app with no error at all. If both layers check out and it's still not working, a stale driver can also be the culprit — see our driver troubleshooting guide — or head back to the main mic test once access is granted to confirm the fix actually worked.