How to fix a microphone that isn't working

Last reviewed on April 25, 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.

Step 1: Confirm the problem is the microphone, not the browser

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.

Step 2: Re-allow microphone access in your browser

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.

Chrome and Edge

1. Click the lock icon next to the address bar.
2. Open Site settings.
3. Find Microphone and set it to Allow or Ask.
4. Reload the tab.

Firefox

1. Click the small icon to the left of the address bar.
2. If a "Microphone Blocked Temporarily" entry appears, click the × next to it.
3. Reload the tab and accept the new prompt.

Safari

1. Open Safari → Settings → Websites → Microphone.
2. Find testmyaudio.com (or "currently open websites") and switch it to Allow.
3. Reload the page.

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.

Step 3: Check the active input device

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.

On Windows

1. Right-click the speaker icon in the taskbar and choose Sound settings.
2. Under Input, pick the device you actually intend to use.
3. Speak into it. The "Test your microphone" bar should react.
4. If the bar moves there but not on our test, return to the browser and reload the page.

On macOS

1. Open System Settings → Sound → Input.
2. Select the right device and confirm Input level reacts when you speak.
3. If it does not, try unplugging and replugging the microphone. macOS occasionally fails to register a hot-swap.

Step 4: Release exclusive locks

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.

Step 5: Investigate cables, hubs, and Bluetooth

If you use an external microphone:

• USB hubs and dongles can drop power or fail to deliver enough current to a microphone. Plug directly into the laptop for testing.
• 3.5 mm jacks on modern laptops are usually combo headset jacks. A microphone-only plug may not connect the input pin correctly. A USB or USB-C adapter often fixes this.
• Bluetooth headsets switch profiles. Many drop sound quality drastically the moment the microphone is enabled. If the test sounds muffled and your level meter is low, that profile switch is likely to blame.

Step 6: Disable noise-suppression and "enhancements"

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.

• Windows: Sound Control Panel → your microphone → Properties → Enhancements. Disable all enhancements and audio effects.
• macOS: on macOS 14 and newer, system-level voice isolation can be set per-app from the Control Center while a call is active.
• Vendor utilities: Realtek, Logitech, NVIDIA Broadcast, Krisp, and similar tools all have a "noise suppression" toggle worth disabling for the duration of the test.

Common mistakes to avoid

• Skipping the permission prompt. If you click anywhere outside the prompt, the browser may treat it as a dismissal and silently block access. Reload, and click Allow directly.
• Testing in private/incognito. Some browsers force microphone permission to "ask every time" in private mode and treat any earlier preference as denied.
• Assuming "no waveform" means the microphone is broken. The most common root cause is permission, not hardware. Always rule out software first.
• Cranking system input gain to 100%. That overdrives the input, clips the signal, and triggers automatic gain control to fight back. Aim for 50–75% and speak at a normal distance.

When to suspect hardware

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.

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.