Troubleshooting audio issues

What is going wrong

Most “no sound” problems are not a broken microphone. They are one of three separate failures: the system never detected the device, the browser or app was never granted microphone access, or the wrong input is selected. Video from a webcam can work while audio fails, because camera capture and microphone capture are independent.

Start by naming the symptom. No input at all, input from the wrong mic, sound that is too quiet, sound that is distorted, echo, or audio that works in one app and not another each point to a different step. Do not skip permission and input selection just because the device appears in a list.

Separate detection, permission, and selection

Device detection means the operating system can see a microphone and assign it a name. Access permission means the browser, meeting app, or recorder is allowed to use that microphone. Active input selection means the app is actually listening to that device rather than another mic, a virtual cable, or the system default.

• If the microphone is missing from the system sound settings, treat it as a detection or hardware problem. Permission screens will not help until the OS lists the device.
• If the system lists the mic but the browser or app shows a blocked or denied microphone icon, treat it as a permission problem. Grant access for that site or application, then reload.
• If permission is allowed and the device is listed, open the app’s audio or input menu and confirm the selected microphone. A detected, permitted mic is silent if another input is active.

A webcam with a built-in mic is two devices. The camera can be selected and working while the associated microphone is unused, muted, or never permitted.

Check the hardware path first

Confirm the microphone is the one you intend to use. Unplug unused USB mics and disable Bluetooth headsets you are not speaking into, so the system default cannot jump to a quiet or muted device.

• USB microphones and headsets: try a different port, avoid unpowered hubs when the device needs more power, and wait a few seconds after plugging in before opening the app.
• 3.5 mm headsets: confirm the plug is fully seated. Combo headset jacks and separate mic jacks are easy to mismatch on desktops.
• Laptop arrays and webcam mics: keep the mic unobstructed. A closed laptop lid, a webcam cover that fouls the capsule, or a case over the grille can starve the signal.
• Mute switches: hardware mute on the mic, headset inline control, or a red LED on a USB device overrides software gain. Unmute at the hardware first.

If the same microphone works in the operating system’s sound test or in a second app, the hardware is likely fine and the original app’s permission or input selection is the issue.

Windows

On Windows, open Settings, then System, then Sound. Under input, select the microphone and watch the volume meter while you speak. No meter movement means the OS is not receiving a signal from that device. Meter movement with silence in one app means that app is not using this input.

• Set the intended microphone as the default input if apps are left on “system default.”
• Open the device’s properties and confirm it is not disabled. Raise the input level; a level near zero can look like a dead mic.
• Turn off exclusive mode if an app grabs the device and other programs then go silent. Exclusive mode is a per-device option in the recording device properties.
• In Privacy settings, allow desktop apps and, separately, allow the specific app to use the microphone. Windows can list the device and still block a store or desktop app.
• Bluetooth headsets often expose both a hands-free profile (narrow, call-quality audio) and a stereo headset profile. If voice sounds thin or the mic disappears when media is playing, re-select the hands-free or communications input in the app.

macOS

On macOS, open System Settings, then Sound, then Input. Select the microphone and watch the input level while you speak. Use the Input volume slider if the meter is weak. Mute on the menu bar or on a connected headset still applies even when the correct device is selected.

• In Privacy & Security, open Microphone and enable the browser or meeting app. A newly installed app stays silent until this toggle is on.
• After changing permission, quit and reopen the app. Permission granted while the app is running may not take effect until relaunch.
• External USB and Bluetooth devices appear as separate inputs from the built-in microphone. Select the one you are speaking into.
• On Apple silicon Macs, some USB audio devices need the maker’s driver or firmware. If the device never appears in Sound settings, detection has failed at the OS layer.

Browsers and websites

Sites that record or call through the browser request microphone permission separately from the operating system. Chrome, Edge, Firefox, and Safari each keep a per-site permission. A site that was denied once will stay silent until you change that site’s microphone setting and reload the page.

• Look at the address bar or site controls for a microphone icon. Allow the site, then reload.
• In the site’s in-page settings, choose the same microphone you selected in the OS. Browser menus can list every detected device; the OS default is not always the one the page uses.
• If the page never prompts, the browser may have a global block on microphone access, or the page may be serving from an insecure context that cannot open the mic. Use a current browser build and a context the browser treats as capable of media capture.
• Close other tabs and apps that might already hold the microphone. Some drivers allow only one capture client at a time.

Camera permission does not grant microphone permission. A working webcam preview with no voice is expected if only the camera was allowed.

Meeting and recording apps

Zoom, Teams, Meet, Discord, and similar apps keep their own input device, level, and mute. The app mute button, a push-to-talk bind, and “automatically adjust microphone volume” can hide a working device.

• Open the app’s audio settings and pick the microphone by name. Avoid “Default” while you are diagnosing.
• Speak and watch the app’s input meter. If the OS meter moves and the app meter does not, the app is on a different device.
• Turn off automatic gain if your voice pumps, clips, or fades. Set a stable input level instead.
• Disable noise suppression, echo cancellation, or “original sound” experiments one at a time if the voice sounds gated, watery, or delayed. These filters can make a quiet mic seem dead.
• If you use a virtual audio device, cable, or multi-output aggregate, confirm that chain is still running. A broken virtual device selected as input produces silence even when the physical mic works.

Quiet, distorted, or echoing audio

When the meter moves but the result is unusable, treat it as a levels and path problem rather than a missing device.

• Too quiet: raise input level in the OS, then in the app. Move closer to the mic. Disable mute and any “listen to this device” monitoring that you do not need.
• Clipping or harsh peaks: lower input gain, turn off automatic gain, and reduce analog gain on USB mixers or interfaces. Distortion at the first stage cannot be repaired later.
• Echo or you hear yourself: speakers and an open mic are feeding back. Use headphones, lower speaker volume, and keep echo cancellation on unless you are using a dedicated interface that already handles it.
• Wrong room sound or keyboard noise: you may be on the laptop array or webcam mic instead of a headset boom. Reselect the boom mic.
• One-way audio in a call: your output (speakers or headphones) is a different setting from input. Confirm both the speaker and the microphone in the same app panel.

When the microphone never appears

If the operating system never lists the device, skip app settings. Reseat the cable, try another port, power-cycle USB devices, and toggle Bluetooth off and on for wireless headsets. On Windows, open Device Manager and look under Audio inputs and outputs for a disabled or error-flagged device. On macOS, check Sound settings and, for class-compliant USB mics, whether the device enumerates after a fresh plug-in.

A device that appears and vanishes often points to a loose connector, an underpowered USB hub, or a Bluetooth range or battery issue. Those are detection failures. Reinstalling an app will not make an undetected microphone show up.

What to do next

Work in this order: confirm the physical mute and connection, confirm the OS can see the microphone and that its meter moves, grant microphone permission to the exact app or site, then select that same device inside the app. Only after those four checks should you change drivers, filters, or hardware.

If the OS meter never moves on any port or cable, the microphone or its interface needs repair or replacement. If the OS meter moves and one app is still silent after permission and selection are confirmed, the remaining issue is inside that app’s audio settings or a single-client driver lock. This guide does not include measured sensitivity figures, compatibility lists, or vendor-specific driver versions; use the device maker’s current instructions when a driver install is required.