Microphone not working or not detected: how to fix it
A flat waveform almost never means broken hardware. Six checks, ordered by how often each one turns out to be the cause.
Last reviewed on August 26, 2026
A flat waveform almost never means broken hardware. Six checks, ordered by how often each one turns out to be the cause.
Last reviewed on August 26, 2026
If our microphone test shows a flat waveform or a level meter that never moves, the cause is almost always one of four things: the wrong device is selected at the operating-system level, another app is holding the microphone, the browser does not have permission, or the OS audio stack has muted the input. None of these require new hardware. This guide walks through them in the order most likely to find your fix fastest.
If the microphone is missing from your sound settings altogether, you have a different failure on your hands — detection rather than permission — and no browser setting will fix it. Start with the dedicated guide to resolving microphone detection problems instead. If the device is listed but silent, carry on below.
Two-minute version: close every other app that uses audio, plug the microphone in directly (not through a hub), reload the page, allow the permission prompt, then re-run the test. That sequence resolves the majority of "no input" reports we see.
The six steps below work in order, but if your symptom is already specific you can skip straight to the right guide.
| Symptom | Most likely layer | Go to |
|---|---|---|
| Microphone missing from sound settings entirely | Hardware or driver | Microphone not detected |
| Crossed-out microphone icon in the address bar | Browser permission | Blocked in browser |
| Silent everywhere on a Windows PC | Windows privacy or levels | Windows 11 and 10 |
| Silent everywhere on a Mac | macOS permission or input | macOS |
| Works in some apps, not others | Per-app permission or device choice | Zoom, Teams, Discord |
| Headset audio works, microphone does not | Boom mute, plug type, or USB power | Headset microphones |
| Works, but sounds thin or muffled | Bluetooth profile or room acoustics | Bluetooth audio quality |
Before changing settings, isolate where the chain breaks. Open a different application that uses the same microphone — your operating system's voice recorder, a meeting app, or any video site that has a "test your microphone" button. If input works there, the problem is browser-specific and the fixes below will help. If the microphone is silent everywhere, skip ahead to the OS-level checks further down.
Browsers cache the choice you made the first time a site asked for the microphone. If you accidentally clicked "Block" or used "Remember", that decision sticks until you reset it.
For a fully illustrated walk-through with screenshots and the matching steps on mobile, our dedicated microphone permissions guide covers each browser in more depth.
Most laptops surface several "microphones": the built-in array, an attached headset, a webcam mic, and sometimes a virtual device created by a meeting app. Choosing the wrong one is the second-most-common cause of silent inputs.
Some applications hold the microphone exclusively. While they are open, the browser cannot read input even with permission granted. The usual suspects are video-meeting apps left running in the background, voice-to-text utilities, recording software, and game launchers with a built-in voice chat.
Quit those applications fully — closing the window is sometimes not enough — then reload the test page.
If you use an external microphone:
Both Windows and macOS, and several driver utilities, ship with noise reduction or "voice enhancement" features enabled by default. They can be aggressive enough to flatten the waveform under quiet conditions. Try turning them off temporarily and rerun the test.
If you have worked through every step in two different browsers, on a freshly rebooted machine, and the input is still silent, the microphone or its cable is the most likely culprit. Test it on a second computer or phone. Many phones can act as a USB-C microphone over a meeting app, which is a quick way to confirm a laptop-side issue.
Once you confirm the microphone works elsewhere, return to the laptop and check Device Manager (Windows) or System Information (macOS) for missing or warning-flagged audio devices. A driver reinstall is the usual next step.
| Message | Meaning | Fix |
|---|---|---|
| "Permission denied" / NotAllowedError | The browser blocked access, usually from a remembered decision | Clear the block and reload |
| "Requested device not found" / NotFoundError | The operating system reports no input device | Detection guide |
| "Could not start audio source" / NotReadableError | Another application holds the device exclusively | Quit meeting, recording, and voice apps completely |
| "Can't find microphone. Make sure it's connected" | The app remembers a device that no longer exists | Reselect the device inside that application |
| "Didn't hear that, tap the microphone to try again" | Device works but no usable speech arrived | Raise input level, reduce noise suppression, get closer |
| Nothing at all, no error | Device is open but silent — usually mute or level | Steps 3 and 6 below |
The most common mistake in microphone troubleshooting is changing five things and then testing once. If it works you do not know why, and if it fails you have introduced new variables. Change one thing, then run the microphone test and watch the level meter — it reacts within a second, so a full cycle takes under ten seconds.
Once you have signal, check quality separately. A microphone can be working perfectly and still sound wrong to other people because of distance, room reverberation, noise suppression, or a Bluetooth profile switch. Record five seconds with the record and playback tool and listen back before declaring the problem solved.
The steps above cover the causes shared by every system. Each platform then has its own set of traps:
tccutil resets, stale aggregate devices, Continuity handing your microphone to an iPhone, and restarting coreaudiod.For background on what the test is actually measuring, see our notes on audio latency and the about page. If a result still seems wrong after all this, please contact us with the browser, OS, and microphone you used so we can reproduce it.
In order of likelihood: the browser permission is blocked, the wrong input device is selected at the operating-system level, another application is holding the microphone exclusively, a hardware mute is engaged, or noise suppression is flattening a quiet signal. Hardware failure is last, not first.
Run our microphone test and watch the level meter as you speak. It reacts within a second, so you can verify each change immediately instead of stacking fixes and testing once at the end.
Each application stores its own device preference and needs its own operating-system permission. An app pointing at a headset you have since unplugged stays silent while everything else works.
That is a quality problem, not a connectivity one. The usual causes are distance from the microphone, room reverberation, aggressive noise suppression, or a Bluetooth headset that has switched to its narrowband calling profile.
Only after ruling out permissions, device selection, mute, and exclusive locks. Avoid third-party driver updater tools, which frequently break laptop microphone arrays by replacing a working configuration with a generic one.
When the microphone is silent in two different browsers, on a freshly rebooted machine, and on a second computer. Test it elsewhere before buying a replacement.