Microphone not working in the browser: a permission checklist
CheckbenchKeyboard, mouse and mic testsOpen
When a website cannot hear you, the browser usually reports why. Run the mic test and read the message under the button. This page lists what each message means and what to do next.
First, the two-second checks
- Is there a mute switch on the headset or cable, and is it off?
- Is the microphone plugged in all the way, or connected if it is Bluetooth?
Then read the message
| The mic test says | What it means | What to do |
|---|---|---|
| Blocked for this site. | The browser is not letting Checkbench use the microphone. A “block” may be saved for it. | Use the lock or settings icon in the address bar, allow the microphone, and press the button again. |
| Blocked by your system settings. | The system is not letting the browser use any microphone. | Allow your browser in the system’s microphone privacy setting (paths below). |
| The permission prompt was closed. | The question was dismissed without an answer. | Press the button again and choose Allow. |
| The browser did not allow it. | The browser refused without saying whether this website is blocked or the prompt was closed. A browser may give the same answer for both. | Press the button again. If no prompt appears, allow the microphone from the lock or settings icon in the address bar. |
| No device was found. | The browser sees no microphone at all. | Plug it in or switch it on. Check that the system lists it as an input device. |
| The device could not be opened. | A microphone exists but could not be started. Another app may be holding it. | Close other apps that use the mic and press the button again. |
| This needs a secure (https) page. | The page was opened without https, so the browser will not offer the microphone. | Open the https address of the site. |
The test builds these messages from the error the browser hands to the page. MDN lists what each error means: MediaDevices.getUserMedia() (checked 2026-10-10).
Where the system setting is
- Windows 11: Settings → Privacy & security → Microphone.
- Mac: System Settings → Privacy & Security → Microphone.
Allow your browser there. If the test still fails, close the browser and open it again. Names vary a little between versions, so if yours looks different, follow the maker’s own steps:
- Microsoft: Turn on app permissions for your microphone in Windows
- Apple: Control access to the microphone on Mac
Links checked 2026-10-10.
The bar moves here, but the call still cannot hear you
Then the microphone and the browser are fine. Two things are left:
- The app is using a different microphone. In the mic test, the Microphone list shows what the browser is using. Pick the same one in your meeting app’s audio settings.
- You are muted in the app, or that site’s own microphone permission is still blocked. Allowing the mic on this page does not allow it on another site.
The bar barely moves
The test says the mic picks up sound once the level passes −45 dBFS (Checkbench’s own line). For scale, a level of −20 dBFS is one tenth of the loudest value digital audio can store. If speaking close to the mic does not get you past the line, raise the input level in the system sound settings or check that the right microphone is selected.
The test asks the browser to switch off noise suppression and automatic volume, and a line under the bar tells you if the browser kept them on. When they are on, a steady sound such as a hum or music can read lower than it is, so test with your voice.
To judge quality rather than just level, record five seconds and play it back. The recording stays in the tab and is never uploaded.
Found a mistake, or a rule that has changed? Email contact@lumenlab.page. We check it, fix it and put the new date on this guide.