Microphone Not Working in Google Chrome: How to Fix It

A microphone not working in Chrome often passes every desktop test, then falls silent the moment a web page asks to listen. That contradiction is the signature of Chrome's design. The browser sits behind two separate permission gates, and both must open. The operating system decides whether Chrome may reach the microphone at all. Chrome then decides, one website at a time, which pages may listen. Close either gate and the page hears nothing, with no error to explain it. The model is deliberate: it stops sites from recording you without consent. It also applies identically on Windows, macOS, Linux, and ChromeOS. This guide opens both gates in order. Confirm a signal first with our microphone test. Then check the per-site permission, which causes most failures, before moving out to the operating-system gate, interfering extensions, and the reset that revives a blocked site.

Chrome Microphone Not Working: Quick Fix Checklist

✓	Test with our microphone test and click Allow.
✓	Allow the site (padlock/tune icon › Microphone) or fix it in chrome://settings/content/microphone.
✓	Grant the operating-system permission for Chrome (Windows or macOS).
✓	Select the correct input device in Chrome’s site settings.
✓	Reset a blocked site, reload, or test in a Guest window.

Test your microphone in Chrome in under a minute

Confirm that Chrome captures sound before you change any setting. The fix for "no signal" differs from the fix for "signal, but the call is silent." A live input meter gives the fastest honest answer. It responds to your voice in real time. A record-and-replay loop hides device-selection mistakes, so avoid it here. Open our online microphone test and watch for the permission prompt. Click Allow when Chrome asks. This single click opens the per-site gate for the page. Now speak normally. If the meter moves as you talk, both gates are already open for this site. The hardware and drivers are then fine, and any remaining fault sits in another app. If no prompt appears and the meter stays flat, one gate is closed. The sections below show which one, and how to open it.

Test Your Microphone →

Chrome exposes the microphone through two distinct controls, and it helps to keep them separate. The operating-system gate governs Chrome as a whole application. The per-site gate governs individual websites. A third control, easily missed, chooses which physical microphone Chrome uses. The table below maps all three. It states where each one lives and what it governs. Keep it beside you as you work through the fixes.

Control	Where it lives	What it governs
Operating-system gate	Windows: Settings › Privacy & security › Microphone. macOS: System Settings › Privacy & Security › Microphone	Whether Chrome, as an app, may use the microphone
Per-site gate	Tune icon at the left of the address bar, or chrome://settings/content/microphone	Which individual websites Chrome permits to listen
Default input device	The dropdown at chrome://settings/content/microphone	Which connected microphone Chrome sends to every site

Why Chrome silences a microphone that works elsewhere

The operating-system gate stays closed

The operating system holds the outer gate. It decides whether Chrome, as an installed program, may touch the microphone. When this gate is shut, no website can reach the input, and no in-browser prompt will help. The block is silent and easy to miss. On Windows, the relevant switch lives under Settings › Privacy & security › Microphone. Two toggles matter there. Microphone access must be on, and Let desktop apps access your microphone must also be on. Chrome counts as a desktop app, so the second toggle is the one people overlook. On macOS, the equivalent lives under System Settings › Privacy & Security › Microphone. Google Chrome must appear in that list with its switch turned on. A Windows or macOS update can reset either setting without warning. This gate is the first thing to check when every website fails at once. When only one site fails, the outer gate is open and the fault lies deeper.

The per-site gate is set to block

Chrome remembers a microphone decision for every site you visit. That memory is the inner gate. Once you block a site, Chrome keeps blocking it silently on every return visit. No prompt appears, because the browser believes the question is already answered. This is the most frequent cause of a dead microphone inside Chrome. A single accidental click on Block during a past visit is enough. You inspect the current site's decision through the tune icon at the left of the address bar. Older Chrome versions show a padlock in the same place. Clicking it reveals a Microphone row with Allow and Block options. The full list of remembered decisions lives at chrome://settings/content/microphone. That page shows the default behaviour for new sites, plus separate Allowed and Blocked lists. A site stuck in the Blocked list will never prompt again until you remove it.

The wrong input, a busy app, or a rogue extension

Three quieter faults remain once both gates are open. The first is device selection. Chrome keeps its own default-microphone dropdown at chrome://settings/content/microphone. It may point at an unplugged headset or a silent virtual device while you speak into the built-in mic. The second is exclusive access. On some systems, another program can seize the microphone and lock Chrome out. A desktop conferencing app left running in the background is the usual offender. Close it fully, then reload the page. The third is extensions. A privacy, ad-blocking, or audio extension can intercept the microphone stream before the page receives it. The quickest test is a Guest or Incognito window, where extensions are disabled by default. If the microphone works there, an extension is the cause.

Fixing it, from the most common cause down

Work through these fixes in order. The sequence resolves the most cases first, with the least disruption. The inner per-site gate accounts for most Chrome microphone failures, so it comes first. The outer operating-system gate follows. Extensions and updates come last. After each change, return to the microphone test and re-check for a signal. That way you always know which step made the difference.

Allow the site, then reset one that is blocked

Start at the address bar. Click the tune icon on its left edge. Find the Microphone row and set it to Allow. Reload the page, because Chrome applies the new decision only on a fresh load. Suppose the site already sits in the Blocked list. Open chrome://settings/content/microphone and locate it under Blocked. Remove the entry, or open it and switch the permission to Allow. Then reload the page so Chrome prompts you again. Check the default behaviour on the same page while you are there. Sites can ask to use your microphone is the setting that lets prompts appear at all. If it instead reads Don't allow sites to use your microphone, no site will ever request access.

Open the operating-system gate for Chrome

Move outward when the site gate reads Allow but the meter stays flat. The operating system is then blocking Chrome as a whole. On Windows 11, open Settings › Privacy & security › Microphone and enable both Microphone access and Let desktop apps access your microphone. Our guide to a microphone not working on Windows 11 covers the deeper Windows layers, and the Windows 10 guide mirrors it for the older release. On a Mac, open System Settings › Privacy & Security › Microphone and switch on Google Chrome. Our Mac microphone guide explains Apple's privacy layer in full. Restart Chrome completely after changing an operating-system setting. The browser reads this permission only at launch.

Isolate extensions, then update Chrome

Open a Guest window from the profile menu and run the microphone test again. Guest mode loads no extensions and no saved site permissions. A working microphone there points squarely at an extension. Return to your normal window and disable audio, privacy, and ad-blocking extensions one by one. Retest after each. A background desktop app can also hold the microphone, so close any conferencing software fully and reload. When every gate is open and the fault persists, update the browser. Open chrome://settings/help, let Chrome download any pending update, and relaunch. A stale build occasionally breaks microphone capture, and the update restores it. The matrix below distils the common symptoms into a single cause and fix for each.

Symptom	Likely cause	Fix
No permission prompt appears	The site sits in Chrome's Blocked list	Remove it at chrome://settings/content/microphone, then reload
Every website fails at once	The operating-system gate is closed for Chrome	Enable Chrome in Windows or macOS microphone privacy settings
Meter moves in the tester, but the call is silent	Wrong input device, or the app has its own selector	Set the device at chrome://settings/content/microphone and in the app
The microphone works in Guest mode only	An extension is intercepting the stream	Disable audio, privacy, and ad-blocking extensions
Nothing works after a recent update	A stale or wedged Chrome build	Update at chrome://settings/help and relaunch

Keeping Chrome's microphone reliable

A few habits keep the microphone dependable in Chrome. Review your site permissions from time to time at chrome://settings/content/microphone. Remove sites from the Allowed list that no longer need to listen. This tightens privacy and stops a forgotten tab from grabbing the input during a call. Prefer Sites can ask over a blanket Allow, so each new site must request access explicitly. Keep Chrome current through chrome://settings/help, since audio fixes ship regularly. Re-check both gates after any Windows or macOS update, because upgrades are the most common moment for a permission to reset. When your calls run through a browser, test the microphone inside the actual service too. Our guides for Google Meet and Zoom cover their in-app audio panels. A Chromebook manages microphone permission differently, at the system level; our Chromebook guide explains that model. A microphone that is flawless in one app can still be blocked one gate up.

Frequently Asked Questions

Why does Chrome not ask for microphone permission?

Chrome only prompts when a site is allowed to ask. If the page sits in the Blocked list, no prompt appears. Open chrome://settings/content/microphone and remove the site from Blocked. Confirm the default reads Sites can ask to use your microphone, then reload the page.

How do I unblock the microphone for one website in Chrome?

Click the tune icon at the left of the address bar. Find the Microphone row and set it to Allow. Reload the page so the change takes effect. You can also manage the site under the Blocked list at chrome://settings/content/microphone.

My microphone works in other apps but not in Chrome. Why?

The operating-system gate for Chrome is probably closed. Enable Chrome under Settings › Privacy & security › Microphone on Windows, or System Settings › Privacy & Security › Microphone on macOS. Restart Chrome afterward, because it reads this permission only at launch.

Can a Chrome extension block my microphone?

Yes. Privacy, ad-blocking, and audio extensions can intercept the microphone stream. Test in a Guest window, where extensions are disabled by default. If the microphone works there, disable your extensions one by one to find the culprit.

How do I change which microphone Chrome uses?

Open chrome://settings/content/microphone and use the input-device dropdown at the top. Select the microphone you intend to use. Chrome then sends that device to every site. Many web apps also keep their own device selector, so set it there as well.