How to Fix a Microphone That Is Not Working

Start with the Mic Test. If the browser cannot see a signal, there is no point tuning Zoom, Discord, or OBS yet. Your first goal is to separate input failure from app-specific behavior. If the test page stays flat and silent, the issue is usually permission, wrong input selection, mute state, or the connection path — not the calling app itself.

Check browser site permissions, then check the operating system's active input device. Many microphone problems come from the wrong device being selected rather than broken hardware. A webcam mic, laptop mic, headset mic, and USB interface can all exist at once, and the browser may be listening to the wrong one. Correct selection often fixes the problem immediately without touching gain or advanced audio settings.

If the browser sees some movement but the signal is very weak, the microphone may not be dead at all — it may just be too quiet. Use the live meter to see whether gain is too low or whether you are too far from the capsule. If the level slams very high and sounds rough, the problem may be clipping instead of silence. A meter gives you quick evidence about which direction to adjust before you keep guessing.

Once input appears, move to the Recording Test. Playback tells you whether the microphone is merely detected or actually usable. A mic can show a moving meter while still sounding robotic, too quiet, noisy, or distorted. Recording and listening back is the shortest route from “the browser sees something” to “the result is good enough for real calls or recording.”

Bluetooth headsets cause a lot of confusion because they often switch into a lower-bandwidth voice mode when the microphone activates. That can make the mic seem broken or terribly low quality even when it is technically functioning. If you can compare with a wired headset, USB microphone, or direct audio interface, do it. The comparison tells you quickly whether the real issue is the mic itself or the transport mode you are forcing it to use.

If the browser still fails after permission, input selection, gain, and connection-mode checks, then it is time to look at OS privacy settings, exclusive app access, audio interface routing, or actual hardware failure. The key is order. Permission first, selection second, signal third, playback fourth. That sequence solves the most common browser microphone problems fast and keeps you from replacing hardware or reinstalling apps when the real issue was a single stored permission or wrong default device.