Two gates control microphone access: the operating system's permission for the browser, and the browser's permission for the site. Both must be open.
Last reviewed on August 26, 2026
Allowing microphone access takes about thirty seconds once you know where the setting lives. Browsers ask for microphone permission once and then 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.
chrome://settings/content/microphone).The same panel exposes a default behaviour at the bottom: When visiting other websites. Set it to Ask or Allow as you prefer.
Edge uses the same engine as Chrome, so the steps mirror Chrome closely.
Visit edge://settings/content/microphone to manage the default and review allow/block lists.
Sometimes a browser refuses to re-prompt even after you change the saved decision. The fastest reliable reset:
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.
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.
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.
Granting a website permission achieves nothing if the operating system is blocking the browser itself, and this is the single most common reason a "fixed" permission still produces silence. There are always two gates:
| Layer | Windows | macOS |
|---|---|---|
| System allows the browser | Settings › Privacy & security › Microphone — including Let desktop apps access your microphone | System Settings › Privacy & Security › Microphone, then fully quit and reopen the browser |
| Browser allows the site | Per-site permission in the address bar or the browser's content settings | |
Test the system layer by opening a non-browser recorder — Windows Voice Recorder or macOS QuickTime. If that hears you and the browser does not, the system gate is open and the browser gate is closed.
On a corporate laptop, a policy can remove the prompt entirely, and no setting you can reach will restore it.
chrome://policy or edge://policy and look for AudioCaptureAllowed. If it is set to false, only IT can change it.Permissions granted to a site persist until you remove them. If you would rather not leave standing access:
Our tools release the microphone as soon as you press stop or leave the page, and never transmit audio anywhere — see the privacy policy for the details.
Click the icon at the left of the address bar, open Site settings, set Microphone to Allow, then reload the page. Globally, visit chrome://settings/content/microphone.
Remove the site from the browser's blocked list, then reload the page so the prompt appears again. Browsers never re-ask on their own once a decision is remembered.
Usually a remembered Block, a page not served over HTTPS, a cross-origin iframe without the right permissions policy, private browsing mode, an enterprise policy, or a privacy extension auto-denying the request.
Yes. Permissions are read when the page loads, so an already-open tab keeps the old state.
Because the operating system layer is separate. On Windows, 'Let desktop apps access your microphone' governs browsers; on macOS you must enable the browser in Privacy & Security and then fully quit and reopen it.
No. Access is released when the tab is closed or the stream is stopped, and both the browser and the operating system show an indicator whenever a microphone is live.