Microphone Not Working? How to Troubleshoot Common Mic Problems
If your microphone is not working, first find out where the signal stops: the device, operating system, browser or application. A microphone that fails everywhere needs a different fix from one that works in a recording but stays silent in Teams. Work through the checks below in order and change one setting at a time.
Start with the symptom, not a driver reinstall
| What you observe | What it suggests | First check |
|---|---|---|
| No microphone in the operating system | Connection, device support or hardware detection | Cable, port, interface power and device list |
| Device listed, but the system input meter stays flat | Mute, wrong input or insufficient signal | Hardware mute, selected input and gain |
| System meter moves, but the website is blocked | Browser or operating-system permission | Both permission layers, then reload |
| Browser recording works, but one app fails | App-specific selection, permission or routing | The app’s microphone selector and mute state |
| Meter moves, but playback is silent | Possibly an output problem | Headphone/speaker selection and playback volume |
| Sound is present but noisy or distorted | A sound-quality problem rather than complete failure | Gain, distance and a recorded comparison |
These observations narrow the investigation; they do not prove a component is faulty. If the operating system detects your device, use our browser microphone test to check whether sound reaches the browser and make a short recording. Select the input explicitly instead of relying on “Default,” and listen with headphones.
1. Check whether the computer detects the microphone
In Windows 11, open Settings → System → Sound and inspect the Input devices. On recent macOS versions, open System Settings → Sound → Input. Choose the intended device and speak while watching the input indicator. An XLR microphone generally appears under the audio interface’s name rather than the microphone’s brand.
If the device is absent, reconnect it and try a known working port. For a detachable USB cable, check that it supports data; a charging-only cable can supply power without carrying audio. Test directly on the computer to isolate a hub or dock. A microphone’s power light alone does not establish a working audio connection.
For an analog headset, confirm that the computer has a compatible headset socket. A combined TRRS headset plug and separate headphone/microphone sockets may need the correct adapter; an ordinary headphone splitter is not equivalent. For XLR equipment, check interface power, input selection, cable seating and the microphone’s specified power requirements.
2. If the device is listed but receives no sound
Inspect the physical mute button, inline cable switch, headset boom position and interface gain. Some headsets mute when their boom is raised. Next, choose the microphone by name in the system input list. A webcam, monitor or Bluetooth headset may have taken over as the default input when it connected.
Speak toward the correct face of the microphone, then raise input gain gradually while monitoring the meter. Do not raise headphone output volume and expect the microphone to become louder: input and output are separate controls. If the microphone has several channels through an interface, make sure the app receives the channel carrying your microphone rather than an unused input or loopback channel.
3. Check Windows or macOS permission before browser permission
On Windows 11, open Settings → Privacy & security → Microphone. Microphone access must be enabled. Microsoft Store apps may have individual permission switches, while traditional desktop apps and browsers depend on “Let desktop apps access your microphone.” A desktop browser may not have its own individual switch in the Store-app list. Microsoft’s microphone permission instructions explain these controls.
On macOS, open System Settings → Privacy & Security → Microphone and check permission for the actual browser or calling app. Follow any prompt to quit and reopen it after a permission change. On a managed work or school computer, an administrator policy may override your choice; ask the administrator rather than disabling security protections.
For detailed Windows device and input-level checks, follow our Windows 11 microphone settings guide.
4. Resolve a blocked browser microphone request
A website needs its own microphone permission in addition to operating-system access. Open the site controls beside the address bar and inspect microphone permissions. If access was blocked, change or reset the decision, reload the page and start the test again. Browser labels differ; Chrome and Edge use site controls, Firefox shows remembered permissions, and Safari provides website microphone settings.
An empty device list before permission is granted is not proof that the hardware is missing. Browsers can restrict device details for privacy. A permission-denied message points first to access settings; a device-not-found message suggests checking available inputs; a device-in-use or read error can have several causes, including a disconnected device or another application holding it.
Close other recording applications temporarily if access fails, then retry. If a fresh browser profile works, investigate the original profile’s remembered permission or extensions. Do not grant microphone access to unrelated sites as part of the test.
5. If it works in the browser but fails in a meeting app
A successful browser recording establishes that one capture path works at that moment. It does not certify every application, channel or processing mode. Open the failing app’s audio settings and select the same microphone explicitly. Check both the app’s mute button and the meeting’s microphone controls; host restrictions or organization policies can also limit participation.
Zoom provides microphone settings and a test in its Audio section. Teams provides device/audio settings and may offer a test call depending on the client and account. Google Meet lets you choose the microphone in the pre-join settings. Exact controls can change, so use the device name and input indicator to confirm the selection rather than relying on an old screenshot.
For OBS or recording software, check that an input source exists, its channel is active, and it is routed to the recorded track. A moving meter with a silent exported file can be a track-routing problem. Reinstalling the microphone driver is unlikely to fix an app that is recording the wrong source.
6. Separate microphone silence from playback silence
If the recording meter responds but you cannot hear playback, test a known audio file through the same headphones. Check operating-system output, browser tab mute, player volume and the output chosen inside the meeting app. Bluetooth devices and monitors can change the output when they connect. Ask another person whether they hear you before assuming a missing local monitor means the microphone is broken.
7. Investigate dropouts, Bluetooth changes and delay
For USB dropouts, compare another port and compatible data cable, bypass a dock temporarily, and note whether the device disappears from system settings. If the failure follows a particular cable or port, that comparison is more useful than changing several unrelated audio options. Obtain drivers or firmware from the computer, interface or microphone manufacturer.
A Bluetooth headset may change audio modes when its microphone activates, affecting listening quality depending on the hardware and system. Compare a wired input to isolate the wireless path. Check pairing, charge and distance for intermittent disconnects; low battery does not necessarily explain every poor-quality recording.
A delayed copy of your own voice may come from software monitoring rather than network delay or a defective microphone. Disable unnecessary monitoring, including “Listen to this device” or a browser’s hear-yourself option, and compare. Use headphones when monitoring. A browser’s reported device latency is not a measurement of round-trip meeting delay.
8. Decide when hardware replacement is justified
Use a known working microphone on the same computer, then test the suspect microphone on another compatible device if possible. Keep the cable and adapter changes documented. If the failure consistently follows one microphone across otherwise working setups, hardware service becomes more reasonable. If both microphones fail only in one app, continue investigating that app.
When capture works but speech is muffled, noisy or distorted, move to the audio-quality troubleshooting workflow. Restoring a signal and improving its sound are separate tasks. After a fix, repeat the original failing scenario for long enough to check reliability, then verify a short call in the application you actually need.
