You're on a Zoom call and someone types "you're cutting out" in the chat. Or maybe the feedback is blunter: "Can you speak up? We can barely hear you." You unmute, you talk louder, nothing changes. The instinct is to blame the microphone and go shopping for a new one. Don't do that yet. In the vast majority of cases the mic itself is fine — the problem is somewhere between the mic hardware and the meeting platform, and the fix takes under two minutes once you know where to look.

This guide walks every layer of the audio stack in order of how often each layer is actually the culprit. Before you buy anything, run through this list. After each fix, use Clipy's free mic and webcam test to confirm you actually got louder — your ears on a live call are a bad judge.

If you're also having camera trouble alongside the mic issue, the complete webcam and mic test guide covers both devices together.

Why your mic sounds quiet: a map of the actual culprits

Your voice travels through six distinct layers before the other person hears it. A problem at any one layer produces the same symptom — "you sound quiet" — so blaming the mic without checking the others is a coin flip. Here's the stack:

  1. Wrong device selected. Your OS or app switched to a different mic (built-in instead of headset, or vice versa) without telling you. This is the single most common cause.
  2. OS input volume slider. macOS and Windows both have a global input level that most users set once and forget. It can drift to 50% or lower after an OS update or device reconnect.
  3. App-level gain. Zoom, Google Meet, and Microsoft Teams each have their own audio processing layer — auto gain control, noise suppression, and a separate volume slider — that can override the OS level.
  4. Bluetooth mic switching. Wireless headsets and AirPods silently swap between a high-quality audio profile (HFP/SCO for mic use) and a lower-quality one, often cutting apparent volume.
  5. Hidden gain controls. Windows has a "Microphone Boost" slider that adds up to +30 dB and is disabled by default. Most people don't know it exists.
  6. Noise reduction overcooking. macOS ambient noise reduction and app-level suppression can be so aggressive they suppress the voice itself, making it sound thin or far away.

Hardware failure — a broken capsule, fraying cable, or defective USB port — is genuinely rare. It belongs at the bottom of the list, not the top.

TL;DR — 6-step checklist

  • Check the right mic is selected in your OS sound settings AND in your meeting app. They can disagree.
  • Drag the OS input volume to 80–100%. Mac: System Settings → Sound → Input → Input volume. Windows: Sound → Recording → Properties → Levels.
  • Turn off "Auto adjust microphone volume" in Zoom and set the level manually. Same for Meet and Teams.
  • On Windows, check Microphone Boost — it's a second gain slider under the same Levels tab, set to 0 dB by default. Try +10 dB.
  • On Mac, turn off Ambient Noise Reduction under System Settings → Sound → Input → Input options.
  • After each change, test your mic level at clipy.online/mic-webcam-test to see a real meter before rejoining the call.

Step 0: Verify the mic is actually quiet — see a real level meter

Before you change anything, confirm you have a real problem. Perceptions on calls are unreliable — the listener's speaker volume, their internet codec, and the room they're in all affect how loud you sound to them. A level meter doesn't lie.

Open clipy.online/tools/mic-test or the mic and webcam test page, allow microphone access when prompted, and speak at your normal call volume. Watch the input level bar. A healthy mic should be hitting 60–80% of the bar on normal speech — peaks touching the yellow zone, never clipping into red. If the bar is barely moving, you have a confirmed problem. If the bar is moving fine but people still say you're quiet, the issue is in the app or the meeting platform, not the OS level.

Keep this tab open. After each fix below, come back and re-test before rejoining a real call.

Fix 1: Wrong mic selected (default device drift)

This is the most likely cause. Every time you plug in headphones or install an audio driver update, your OS may silently reassign the default input device. Your meeting app then picks up whatever the OS says is default — which might be the quiet laptop mic instead of the headset mic you intended.

On Mac: Open System Settings → Sound → Input. You'll see a list of available input devices. Click the one you actually want to use. The input level meter below the list updates in real time — speak and watch it move to confirm you picked the right one.

On Windows: Right-click the speaker icon in the taskbar → Sound settings → scroll to Input → click the dropdown under "Choose your input device" and select the correct mic. Alternatively go to Control Panel → Sound → Recording, right-click your preferred mic, and choose Set as Default Device.

In Chrome (for web apps like Meet): Chrome has its own device permission layer. Click the lock icon in the address bar → Site settings → Microphone and check which device is selected. Chrome can override the OS default per-site.

In Zoom: Settings → Audio → Microphone dropdown. Make sure "Same as System" actually means what you think — if the system default recently changed, this will have followed it silently.

After selecting the right device, re-test your level at clipy.online/mic-webcam-test before assuming it's fixed.

Fix 2: OS input level slider too low

Both macOS and Windows expose a global input sensitivity slider. This is the baseline gain applied to every app. If it's sitting at 50% or below, no amount of app-level tweaking will compensate cleanly.

Mac (macOS Ventura / Sonoma / Sequoia): System Settings → Sound → Input. You'll see an "Input volume" slider at the bottom. Drag it to 80–100%. The change takes effect immediately — speak into the mic and watch the level indicator to confirm.

Mac (macOS Monterey and earlier): System Preferences → Sound → Input. Same slider, different path.

Windows 10 / 11: Settings → System → Sound → Input, click your mic device → Device properties. The Volume slider here is the OS-level gain. Set it to 80–100. Or take the classic path: Control Panel → Sound → Recording tab, double-click your mic → Levels tab. The top slider is input volume. Set it to 80 or higher.

A common trap: you push the slider to 100, get background noise, and pull it back. The right move is to fix the noise at the source — not run the input gain low. A weak input signal makes noise suppression work harder and sometimes distort the voice.

Fix 3: App-level gain low — Zoom, Meet, Teams

Each major meeting platform applies its own processing on top of the OS input level. Getting the OS slider right is not enough if the app has its own gain set low, or if auto-level controls are fighting your settings.

Zoom: Settings → Audio. There's a microphone volume slider and a checkbox: "Automatically adjust microphone volume." That auto-adjust is well-intentioned but it can clamp your level when it thinks you're too loud — and the detection is imperfect. Try turning it off, then dragging the volume slider to 70–80% and testing. Also check Suppress background noise — if it's on "Auto" or "High," try dropping it to "Low" or off; aggressive suppression can make your voice sound thin.

Google Meet: During a call, click the three-dot menu → Settings → Audio. Meet's interface is minimal but there's a microphone selector. Separately, Meet uses Chrome's getUserMedia constraints including auto gain control (AGC) — if you're recording with a browser-based tool on the same tab, the AGC can interfere. More on that in Fix 7.

Microsoft Teams: Click your profile picture → Settings → Devices. There's a microphone selector and a "Make a test call" button. Teams also runs its own noise suppression — under Settings → Devices → Noise suppression, try switching from "Auto" to "Low" if you're on a quiet background already.

Fix 4: Built-in mic vs. headset switching — Bluetooth handoff

Bluetooth headsets and AirPods use two different audio profiles depending on what the OS thinks you're doing. For music playback they use A2DP (high quality, stereo). When a mic stream is active, they switch to HFP/SCO — a narrower, lower-fidelity profile — to handle two-way audio. This switch sometimes fails silently, leaving your system using the laptop's built-in mic instead of the headset mic, or switching back mid-call.

Signs this is your problem: your voice sounds fine at the start of a call and then gets quiet after a few minutes, or the issue started right after you connected AirPods or a Bluetooth headset.

Fixes:

  • Explicitly select the headset mic in your OS and app settings (see Fix 1) rather than relying on "auto."
  • On Mac, if AirPods are connected, the mic can switch profiles when you start a video call. Go to System Settings → Sound → Input and manually re-select the AirPods after the call starts.
  • On Windows, in the Recording tab of Sound settings, you may see both a "Headset Microphone" and a "Microphone" entry for the same Bluetooth device. The "Headset Microphone" is the HFP profile — make sure that's set as default, not the "Stereo Mix" or built-in mic.
  • For important calls, a wired headset sidesteps this entirely. USB or 3.5mm doesn't negotiate profiles.

Fix 5: Microphone Boost on Windows (the hidden +20 dB slider)

This one surprises most Windows users. Many audio drivers expose a "Microphone Boost" setting that adds up to +30 dB of gain. It defaults to 0 dB and sits on a separate slider directly below the main volume slider — most people walk right past it.

To find it: Control Panel → Sound → Recording, double-click your microphone → Levels tab. You'll see two sliders. The top one is "Microphone" (volume, 0–100). The bottom one is "Microphone Boost" — it defaults to 0.0 dB. Try setting it to +10.0 dB. If that's still not enough, go to +20.0 dB. Be careful: +30 dB on a poor-quality mic will amplify background noise badly. Start conservative.

Note: This slider only appears if your audio driver supports it. Some USB mics and many modern Realtek drivers don't expose it. If you don't see a second slider, your driver doesn't offer this option — move to the next fix.

Fix 6: macOS "Ambient noise reduction" suppressing your voice

macOS has a built-in ambient noise reduction filter that can be applied to microphone input at the OS level — before the audio even reaches your meeting app. On paper this is useful. In practice, if it's tuned too aggressively or if you're using a headset where the voice profile doesn't match what the algorithm expects, it can suppress your voice along with the background noise.

To check: System Settings → Sound → Input, then click "Input options..." (or the dropdown next to your selected mic on older macOS). You'll see an "Ambient noise reduction" toggle. Try turning it off. Now speak into your mic and check the level meter — if it jumped noticeably, the noise reduction was eating your signal.

If you turn it off and the call becomes too noisy, consider moving the noise suppression to the app level (Zoom or Teams can handle it more reliably than the OS-level filter) rather than running both stacked, which tends to make voices sound robotic.

Fix 7: Browser auto-gain control disabled — getUserMedia constraints

Web apps (Meet, browser-based Zoom, web recorders) access your mic via the browser's getUserMedia API. Chrome applies three audio processing layers by default: echo cancellation, noise suppression, and auto gain control (AGC). AGC automatically adjusts your microphone volume in real time based on signal level.

The problem: some web-based tools deliberately disable AGC to get a cleaner signal. If the site set autoGainControl: false, Chrome won't boost your mic automatically — and if your OS input level is low, you'll record quietly with no visible warning.

The fix is straightforward: keep your OS input level (Fix 2) high enough that you don't need browser AGC to compensate. A healthy base level makes AGC irrelevant either way.

To confirm: open chrome://webrtc-internals/ during a call, find the audio track, and check the constraints. If autoGainControl shows false, the site opted out and you're getting raw input.

Hardware-side fixes (last resort)

If you've worked through all the software layers and the mic is still quiet, it's time to look at the physical connection. These issues are genuinely uncommon but they do happen:

  • USB port quality. Some USB ports — especially on hubs, docks, or front-panel connectors — deliver insufficient or noisy power. Try plugging a USB mic directly into a rear motherboard port or a MacBook's USB-C port. The difference can be 6–10 dB.
  • Cable condition. A partially damaged or oxidized cable introduces resistance that drops the signal. With a USB mic, try a different cable. With an analog mic on a 3.5mm jack, clean the connector and try a different port.
  • Mic placement. The inverse-square law is brutal at short distances — moving a mic from 12 inches to 6 inches away roughly quadruples the perceived volume. A headset mic slipping off your cheek and dangling near your chest will sound dramatically quieter than the same mic positioned correctly.
  • Shock mount and acoustic isolation. This matters less for volume than for clarity, but a mic vibrating on a hard desk surface can color the sound in ways that make voices harder to understand — which gets reported as "you sound quiet" even when the level is technically fine.

Actual capsule failure is very rare on mics less than five years old. If you've cleared every software and connection variable and the meter still shows a flat line, that's when to suspect the capsule.

Verify the fix — record 10 seconds and listen back

The best final confirmation isn't a level meter — it's a recording that matches what the other person hears. Open clipy.online or the Clipy voice recorder tool, record ten seconds of yourself speaking at normal call volume, and play it back. You're listening for:

  • Volume: does it sound like a normal conversation, or do you have to crank your speakers to hear it?
  • Clarity: is your voice clear, or thin and over-processed?
  • Background noise: now that gain is higher, is the room too noisy? If so, use app-level noise suppression (not OS-level) to clean it up.

If the playback sounds good to you, it will sound good to the other person. Share the link with a colleague for a second opinion if you're still uncertain.

For a live check before a call, the Clipy mic and webcam test gives you both a level meter and a short recording preview without installing anything.

FAQ

Why do I sound quiet on Zoom but loud on Google Meet?

Each app applies its own audio processing pipeline independently of the OS. Zoom's auto-adjust mic volume may be overcorrecting — try disabling it in Zoom settings and setting the level manually. Meet relies more heavily on Chrome's built-in AGC, which can make the same mic sound louder. The fix is to set a consistent, high OS input level (Fix 2) and then disable auto-adjustment in each app so you control the gain rather than each app guessing at it separately.

Why does my AirPods mic sound bad or quiet on calls?

AirPods switch to a lower-quality Bluetooth profile (HFP/SCO) when a mic stream activates — the same connection can't carry high-quality stereo audio and a full-quality mic stream simultaneously. You can't fully fix this without switching to a wired option, but you can improve it: select AirPods explicitly as the mic device (not "auto"), keep them charged, and stay within three feet of your device.

Should I disable noise suppression to sound louder?

Maybe. If the suppression is actively eating your voice — you sound thin, robotic, or inconsistent — yes, turn it down or off. But noise suppression doesn't actually reduce volume; it removes noise between words. What makes you sound quiet is low gain. If you sound quiet and robotic, fix the gain first, then decide whether suppression is still needed. If you sound quiet but clear, skip the suppression settings and go straight to Fix 2 and Fix 5.

What's a "noise gate" and is it making me sound quiet?

A noise gate cuts the audio signal below a set volume threshold — essentially silence below a floor level to reduce background noise. If the threshold is set too high, the gate clips the beginning and end of your words, making you sound like you're cutting in and out. This is usually a deliberate setting in tools like OBS, audio interfaces, or professional podcast software — it's unlikely to be on by default in Zoom or Meet. If you use any audio processing middleware (Voicemeeter, Krisp, NVIDIA RTX Voice, or an audio interface with DSP), check whether it has a gate enabled and what the threshold is set to.

Will a USB mic automatically fix a quiet microphone problem?

Not automatically. A USB mic with a built-in audio interface typically has better gain and a higher quality capsule than a laptop's built-in mic, so the ceiling is higher. But if you set the OS input slider to 40%, put the mic two feet away, and leave Zoom on auto-gain, a USB mic will still sound quiet. The fixes in this guide apply to any mic — USB, analog, or built-in. Fix the software stack first. If you've done that and the laptop's built-in mic is still producing a thin, noisy signal that no amount of gain fixes cleanly, that's when a dedicated USB mic is a worthwhile upgrade.

Bottom line

"We can barely hear you" is almost never a dead microphone. It's almost always a wrong device selection, a forgotten OS slider, an app that thinks it's helping by adjusting your level automatically, or a hidden gain control you didn't know existed. Work through the list above in order — most people find their fix by step 3 or 4.

The habit that eliminates this problem entirely: run a quick level check before every important call. Open clipy.online/mic-webcam-test, speak for five seconds, confirm the meter is moving, and close the tab. It takes less time than the awkward first two minutes of any call where someone has to tell you that you're quiet again.