Microphone Not Working in Chrome — How to Fix It

Chrome runs more video calls than any other browser, so when its mic stops working the whole day stalls. The cause is almost always one of five things: site permission, the wrong device selected at the OS level, Chrome's global permission, a Bluetooth headset on the wrong audio profile, or an extension interfering. Below is each one in order — start at the top, stop when your mic picks up sound.

1. Check the site permission (the tune icon in the address bar)

In Chrome 124 and later (current 2026 builds are around 145), the icon at the left of the address bar is a small sliders / tune icon, not the older lock. Click it and choose "Site settings" — a panel opens listing Camera, Microphone, Location, Notifications, etc. Each has Allow / Block / Ask. If Microphone shows Block, change to Allow and reload the page. If it shows Ask, it means the site never got permission — refresh, click Allow when prompted, and try again. A gotcha worth knowing: Chrome 121+ expires permission grants after 90 days of inactivity on that site. So if a site you used six months ago suddenly forgot — that's why. Just allow it again.

2. Check Chrome's global microphone settings

Open chrome://settings/content/microphone in your address bar (paste it as-is, including the colons). This page controls Chrome's microphone behavior across all sites. Three things to confirm: • The dropdown at the top shows the correct microphone — Chrome may default to a USB or Bluetooth device that's no longer connected. Pick the one you actually want. • "Sites can ask to use your microphone" is on. If it's off, no site will be able to request permission at all. • The site you need is not in the "Not allowed" list. Remove it from there if it is.

3. Check OS-level permission for Chrome itself

Even if Chrome's settings are right, the operating system must let Chrome touch the microphone. This catches many people after OS updates. Windows 10/11. Settings → Privacy & security → Microphone. Turn on "Microphone access", "Let apps access your microphone", and scroll down to "Let desktop apps access your microphone" — Chrome counts as a desktop app, so this last toggle is the one that often matters. macOS (Sequoia, Tahoe 26). System Settings → Privacy & Security → Microphone. Google Chrome should appear in the list with the toggle ON. If Chrome isn't there at all, launch a site that requests mic access (like check-camera.com) and macOS will prompt you the first time. After granting, fully quit Chrome (⌘Q) and reopen — running apps don't pick up new permissions. macOS Tahoe added a Privacy Dashboard showing which apps recently accessed your mic — useful for spotting an app that's hogging it.

4. The Bluetooth headset profile trap

If you're on AirPods, a Sony / Bose / Jabra Bluetooth headset, or any wireless earbuds, this is the single most common reason "the mic doesn't work" in Chrome. Bluetooth audio has two main profiles. A2DP is high-quality stereo audio output, but microphone-only. HFP (or HSP, the older variant) supports microphone input but downgrades output to mono and lower bitrate. When Chrome enables the mic, the headset has to switch from A2DP to HFP — and some headsets either don't switch cleanly, switch silently and stay there, or only support one profile at a time. What to do: • Check Chrome's microphone dropdown (chrome://settings/content/microphone). If your headset appears twice — once as "Headset" and once as "Headphones" — pick the "Headset" version. The other one is output-only. • On Windows, check the speaker icon dropdown. After a call, Windows sometimes leaves the headset stuck in mono HFP mode. Disconnect and reconnect the headset to reset. • If audio sounds tinny or robotic during a call, that's the HFP profile — there's no fix in the browser; it's a hardware limitation. A wired headset or a separate USB mic + Bluetooth headphones (output only) avoids it.

5. Verify the mic actually works in Chrome

Open check-camera.com in Chrome. Allow microphone access when prompted. Speak — the audio level bars should react to your voice within a second or two. This test isolates the problem. If the bars move here: • Your mic works in Chrome — the problem is on the specific site that's failing. Go back to that site, click the tune icon, and verify Microphone is set to Allow for it. If the bars don't move here: • The mic doesn't work in Chrome at all. The fix is somewhere in steps 1-4 (site permission, global setting, OS permission, or Bluetooth profile).

6. If nothing above works

A short list of fixes for edge cases: Incognito mode test. Open the failing site in an incognito window. Extensions are disabled by default in incognito, so if the mic works there, an extension is the culprit. Disable extensions one by one — privacy blockers, script blockers, and "webcam protection" antivirus extensions are the usual suspects. Clear site data for the failing site. Settings → Privacy and security → Site Settings → View permissions and data → find the site → Reset permissions. This often fixes stuck "Block" decisions that didn't seem to update. Update Chrome. Chrome → About Google Chrome forces an update check. Old builds (older than Chrome 130) had a few mic regressions that newer versions fixed. Restart the computer. Last resort, but a stuck audio driver after sleep or hibernation is real and a reboot clears it.

Ready to check your devices?

Test Camera & Microphone

FAQ

All articles