Mic Not Working in Chrome? Here's How to Fix Site Permissions, Flags, and OS-Level Blocks
Launch Companion Diagnostic Tool
Test your hardware right now in your browser with zero install:
Open Mic TestChrome has blocked your microphone at one of three independent layers, and clearing the wrong one leaves the other two intact. The three layers are: the OS audio routing stack, Chrome's internal site permission database, and the experimental flags that override both. A mic that shows green in Windows Sound settings or macOS Audio MIDI Setup can still be dead inside Chrome if the site-level permission was denied once and cached, or if the chrome://flags/#unsafely-treat-insecure-origin-as-secure entry is stripping getUserMedia access on a non-HTTPS page.
Confirm the Mic Is Actually Passing Signal Before Touching Chrome
Before you touch a single Chrome setting, verify the hardware is alive. A USB condenser mic with a broken internal preamp or a TRRS headset plugged into a TRS-only jack will fail at every software layer and waste your time in menus. Open Mic Test in a second browser — Firefox or Edge — and speak. If the level meter moves, the hardware and OS routing are fine and Chrome is the problem. If nothing moves in any browser, stop here and fix the hardware or OS first.
On Windows 11, go to Settings > System > Sound > All sound devices, click your mic, and confirm the input level bar animates when you speak. On Windows 10 the path is Settings > System > Sound > Input > Test your microphone. On macOS 13 Ventura or later go to System Settings > Sound > Input, select the device, and watch the Input level bar. If the bar is dead, check that the mic is not muted at the device itself — many USB mics have a hardware mute button with an LED that goes red when active.
Fix Chrome Site Permissions: The Exact Click Path
Chrome stores a per-origin permission record the first time a site requests getUserMedia. If you clicked Block even by accident, that record persists indefinitely. Here is the exact sequence to clear it.
- In the address bar of the tab where the mic is failing, click the lock icon or the tune icon to the left of the URL. If the site is HTTP-only you will see a circle with an i instead of a lock.
- Click Site settings in the dropdown. This opens
chrome://settings/content/siteDetails?site=https%3A%2F%2Fyoursite.comscoped to that origin. - Find the Microphone row. If it reads Block, open the dropdown and set it to Allow.
- Hard-reload the tab with Ctrl+Shift+R on Windows or Cmd+Shift+R on macOS. A normal reload does not re-trigger the permission prompt.
If you want to audit every site that has a mic permission at once, go to chrome://settings/content/microphone. You will see two lists: sites that are allowed and sites that are blocked. Remove any stale blocked entries for sites you use regularly.
Also confirm the global default at the top of that same page. The toggle should read Sites can ask to use your microphone. If it reads Don't allow sites to use your microphone, Chrome suppresses the permission prompt entirely and the site never gets a chance to ask.
OS-Level Blocks That Survive Chrome Permission Resets
Windows 10 and 11 both have an app-level microphone privacy gate that is completely separate from Chrome's own permission system. Go to Settings > Privacy > Microphone (Windows 10) or Settings > Privacy and security > Microphone (Windows 11). Confirm that Microphone access is On at the top, that Allow apps to access your microphone is On, and that Allow desktop apps to access your microphone is also On. Chrome is a desktop app, not a Store app, so the third toggle is the one that controls it. Many enterprise group policies flip this off and it does not appear greyed out, so you can miss it.
On macOS go to System Settings > Privacy and Security > Microphone. Chrome must appear in the list with its toggle enabled. If Chrome is not in the list at all, it means Chrome has never successfully requested mic access at the OS level — usually because it was blocked at the Chrome permission layer first and the getUserMedia call never reached CoreAudio. Enable the Chrome site permission first, reload, then return to this macOS pane and approve the system prompt that appears.
Chrome Flags and Profile Corruption That Break getUserMedia
Two flags can silently kill microphone access. Open chrome://flags and search for each of these.
| Flag name | Safe value | What goes wrong when set incorrectly |
|---|---|---|
| #unsafely-treat-insecure-origin-as-secure | Disabled unless you specifically need HTTP mic access | If set to a wrong origin string, Chrome may misclassify your target site and deny getUserMedia |
| #enable-webrtc-hide-local-ips-with-mdns | Default | Forcing Enabled can break ICE candidate gathering in WebRTC calls, causing mic to connect then immediately drop |
| #use-fake-ui-for-media-stream | Default | If Enabled, Chrome auto-approves mic requests with a fake stream — real audio never flows, everything looks permitted |
Reset any non-Default flags related to media or WebRTC, then relaunch Chrome using the Relaunch button at the bottom of the flags page. A full relaunch is required — closing the tab is not enough.
If the mic still fails after flags are clean, your Chrome profile may be corrupted. Navigate to chrome://version/ and note the Profile Path. Close Chrome, open that folder, and delete the file named Preferences. Chrome rebuilds it on next launch. You will lose site-level permission records and some settings, but not passwords or bookmarks, which are stored separately.
Once Chrome is relaunched, return to Mic Test and confirm the level meter responds to your voice. If you are troubleshooting a video call setup, also run Webcam Test at the same time — call platforms request camera and mic together, and a failed camera permission can block the entire getUserMedia bundle.
Frequently Asked Questions
Why does my mic work in Zoom but not in Chrome?
Zoom is an Electron or native desktop app that calls the OS audio API directly and bypasses Chrome's site permission layer entirely. Chrome's getUserMedia goes through a separate permission gate. A mic that works in Zoom has OS access confirmed but may still be blocked at the Chrome site or global permission level.
Chrome keeps asking for mic permission every session even though I click Allow. Why?
You are likely in Incognito mode, which discards all site permissions when the window closes. Alternatively, a browser extension is clearing site data on exit. Check chrome://extensions for any privacy or cookie-clearing extensions and whitelist your target site in their settings.
My mic not working in Chrome browser only on one specific site. Other sites work fine.
That site has a blocked permission record scoped to its exact origin. Go to chrome://settings/content/microphone, find the site in the blocked list, remove it, then reload the site and approve the prompt. Also confirm the site is served over HTTPS — Chrome blocks getUserMedia on plain HTTP origins by default since Chrome 86.
The mic permission prompt never appears at all. What is blocking it?
Either the global default in chrome://settings/content/microphone is set to Don't allow sites to use your microphone, or the #use-fake-ui-for-media-stream flag is Enabled and silently auto-approving a fake stream. Check both locations. Enterprise managed Chrome deployments can also push a MicrophoneCapturedAllowedUrls or AudioCaptureAllowed policy that suppresses the prompt — check chrome://policy/ for active audio policies.
I reset everything and the mic still does not work in Chrome on macOS. What is left?
Run sudo killall coreaudiod in Terminal to restart the CoreAudio daemon without rebooting. A hung coreaudiod process passes silence to all apps including Chrome. After the daemon restarts, relaunch Chrome and re-test. If that fails, boot into macOS Safe Mode to rule out third-party kernel extensions intercepting the audio stack.
Does Chrome version matter for mic access?
Yes. Chrome 94 removed the option to allow mic access on HTTP origins through the UI — that path now requires the #unsafely-treat-insecure-origin-as-secure flag. Chrome 112 changed how permission prompts surface in the address bar. Always check chrome://settings/help and update to the current stable release before deep-diving into flags, because several getUserMedia bugs in the 108 to 111 range were patched in subsequent point releases.
Launch Companion Diagnostic Tool
Test your hardware right now in your browser with zero install:
Open Mic Test