3 min read
Why Your Mic Isn't Working in the Browser (and How to Fix It)
A systematic fix for browser microphone problems: permissions, OS privacy settings, exclusive-access conflicts, and the wrong-device trap — in the order to check them.
The four failure points
When a website can't hear you, the problem lives in one of four layers: the browser's permission for that site, the operating system's microphone privacy setting, another application holding the mic, or simply the wrong input device being selected. Checking them in that order resolves the overwhelming majority of cases in a couple of minutes.
Start with a ten-second sanity check: open the microphone tester on this site and click start. If the level meter moves when you speak, the mic and browser are fine and the problem is inside the specific app or meeting site. If the browser shows an error or the meter stays flat, work through the layers below.
Layer 1: browser permission
Browsers block microphone access per-site until you explicitly allow it. If you ever clicked 'Block' — even accidentally — the site can't ask again; it just fails. Click the padlock or tune icon in the address bar, find Microphone, and set it to Allow, then reload the page.
In Chrome and Edge you can also review every site's decision under Settings → Privacy and security → Site settings → Microphone. Firefox keeps the same control behind the permissions icon in the address bar. A reload after changing the setting is required — permission changes don't apply to an already-loaded page.
Layer 2 and 3: the OS and other apps
Operating systems have their own kill switch. On Windows: Settings → Privacy & security → Microphone — 'Microphone access' and 'Let desktop apps access your microphone' must both be on, or every browser fails no matter what its own settings say. On macOS: System Settings → Privacy & Security → Microphone, and make sure your browser is checked.
Next, exclusive access: apps like Discord, Zoom, Teams, OBS, and some game launchers can hold the microphone so nothing else can open it (the NotReadableError in browser terms). Close or fully quit those apps — check the system tray, not just the window — and retry.
- 1Open the Microphone Tester and click start — note the exact error if one appears.
- 2'Permission denied' → fix the browser padlock setting and reload.
- 3'Not found' → check the cable/USB port and that the OS lists the device at all.
- 4'In use / not readable' → quit Discord, Zoom, OBS, and similar apps, then retry.
- 5Meter still flat with no error → switch the input device in the tester's dropdown.
Layer 4: the wrong-device trap
Modern machines expose several 'microphones': the laptop's internal array, a webcam mic, a headset, virtual devices from audio software. Browsers use the system default, which is often not the one you're speaking into. If the meter stays flat but there's no error, open the device dropdown in the mic tester and try each entry — one of them will move.
Once you've found the right device, set it as the system default (Windows: Settings → System → Sound → Input; macOS: System Settings → Sound → Input) so every site and app picks it up automatically. And if the level moves but is very low, raise the input volume/gain on that same OS screen — websites can't boost your gain for you.
Frequently asked questions
Why does the site work in one browser but not another?
Permissions are stored per browser. If Chrome works and Edge doesn't, Edge has its own blocked permission or isn't allowed microphone access at the OS level. Fix that browser's padlock setting and the OS privacy list.
Does the mic test record me?
No. The tester analyzes the audio stream locally to draw the level meter — nothing is recorded, stored, or transmitted. Close the tab and the stream ends.
My mic works but people say I'm quiet. What do I adjust?
Raise the input gain in your OS sound settings (not the playback volume), position the mic closer to your mouth, and disable aggressive noise suppression in meeting apps, which can clip quiet voices.
Tools mentioned in this guide
Keep reading