Why Your Microphone Sounds Too Quiet: Gain, Input Levels, and OS Limits
"Can you hear me? You're really faint" sends most people hunting for one volume slider — but the slider they find is only one of four places where the level gets decided. Here is an order of operations that finds the culprit.
The short version
Your level is set by a chain of stages, and any one of them can be the limit: the physical path (cable, jack, hub, selected device), the OS input volume and gain, the processing inside the meeting or recording app, then your distance and aim.
Work through them in that order, one variable at a time. Turning the volume up first usually gives a louder version of the same bad signal.
- Gain amplifies the signal. More gain makes a weak microphone louder, and its noise louder at the same rate.
- Input level is what the meter shows: how much signal arrives after whatever gain has been applied.
- Clipping is what happens when the signal exceeds what a stage can carry. The peaks flatten and the audio crackles. It cannot be undone afterwards.
Stage 1: confirm the physical path
Before touching a setting, prove the signal arrives at all. Three checks cover most cases:
- Is the right device selected? Laptops have a built-in mic and headsets add a second input with a similar name, so the system may be capturing the built-in microphone while you speak into one on the desk.
- Is a hardware mute engaged? A mute button, a mute LED, or a dial on an inline cable produces a silent meter with healthy-looking settings.
- Does the connection match the microphone? A USB microphone needs a data-capable port; some hubs and charge-only cables enumerate it without audio, and an analogue condenser expecting phantom power gives little signal from a jack that does not supply it.
A Bluetooth headset used as the microphone also falls back to its hands-free profile, which is a likelier cause of "you sound thin" than your input level.
Stage 2: set the operating system input level
macOS
Open the Sound settings, select the Input tab, then speak and watch the level indicator. Apple's guide to sound input settings documents the input volume control and notes that it is unavailable for some devices. A greyed-out control means the device exposes no gain the system can change — set the level on the microphone or interface instead.
Windows
Go to Settings > System > Sound, find the Input section, and open the properties of the selected microphone to reach its volume. The classic sound control panel's Recording tab adds a Levels page, where built-in drivers often expose a boost control; boost raises the noise floor along with your voice, so use the smallest value that gives a healthy meter. If the microphone is missing or silent in every app, work through Microsoft's audio troubleshooting guide first, because a driver or permission fault looks identical to a level fault.
Check the app permission too
Both systems can deny one app microphone access while leaving the device healthy for everything else. If a single app is silent, check the permission before you touch gain.
Stage 3: the app is not a passive pipe
Meeting software processes what it receives rather than what your microphone produced:
- Automatic gain control raises quiet voices and lowers loud ones. It is why a badly set-up microphone sounds passable on a call but noisy once someone records it.
- Noise suppression subtracts steady-state sound; aggressive settings clip consonants, which people describe as "too quiet".
- Compression and normalising narrow the dynamic range so your level sits in a small band.
The useful technique: disable automatic gain while you measure, set the OS and hardware level until a normal voice gives a healthy, unclipped meter, then re-enable it and listen. If the level only looked fine because software was rescuing you, you now hear the noise floor it was lifting. Recording apps such as OBS add their own per-source gain — see our OBS Studio guide.
Stage 4: distance and polar pattern
If gain is adequate and processing is sane, the remaining cause is physics. Every step the microphone moves away from your mouth asks the later stages for more gain, which adds room noise and more chance of clipping. Moving it closer beats turning it up.
| Pattern | What it hears | Effect on your level |
|---|---|---|
| Cardioid | Front, rejects rear | Must face your mouth; drops off when you turn away |
| Supercardioid / hypercardioid | Tighter front, some rear | More isolation, less forgiveness |
| Omnidirectional | All directions equally | Consistent as you move — and it hears the keyboard |
| Figure-8 | Front and back, rejects sides | Two people facing each other, not a conference call |
A level that swings as you move is a pattern-and-aim problem: adding gain to compensate for a cardioid microphone pointing past your mouth amplifies the wrong thing.
Common mistakes that make it worse
- Stacking gain in two places. Hardware boost plus maximum OS input volume plus app gain gives distortion no single control can fix.
- Treating distortion as low level. A clipped signal can sound thin, so people add more gain. If the meter pegs and the audio crackles, turn something down.
- Judging by other people's sliders. Gain that suits a dynamic microphone can be far too much for a condenser two centimetres from your mouth.
- Testing only in the meeting app. Automatic gain hides level problems, so check a system input meter or a bare recording first.
A five-minute check you can repeat
- Select the device at the system level and confirm its name matches the hardware.
- Turn off automatic gain and noise suppression in the app you are testing.
- Speak at normal call volume and watch a system input meter; adjust one control until peaks are present but never pinned.
- Say something loud, then lean back. If the loud pass clips or the distant pass disappears, fix distance and aim before gain.
- Re-enable processing, record a short clip and play it back rather than trusting the live meter.
Where the hardware still sets the ceiling
Software cannot recover a signal that never arrived. A genuinely quiet source — a dynamic microphone on a low-output interface — needs gain from hardware that suits it, so choosing a microphone whose output and pattern fit your distance is usually easier than amplifying one that does not. Our picks for best USB microphones and podcast microphones separate the ones that need a lot of gain from those that do not. Platforms also differ in how much processing they impose — see Microsoft Teams vs Zoom and Zoom vs Google Meet.
Two limits. Gain does not distinguish voice from hiss, fan, or keyboard, so a quiet room is a prerequisite. And if you monitor through headphones, raise the level gradually: feedback and a sudden peak at high monitoring gain can hurt.
Frequently asked questions
What input level should my microphone be set to?
There is no single correct number that applies to every microphone, room, and app. The goal is relative: your voice moves the meter clearly and consistently at normal speech, peaks do not sit flat against the top, and the setting still sounds right when you lean back or talk louder.
Why does my microphone volume slider look greyed out or missing?
Some devices do not expose input gain to the operating system, so the control is shown disabled or omitted entirely. Set the level with a dial or pad switch on the microphone, on the interface, in the device driver panel, or with the input volume inside your app.
Is distorted microphone audio always caused by gain being too high?
Usually, but the overdriven stage may be the capsule because the source is too close, the interface gain, the OS input volume, or software effects applied afterwards. Change one control at a time and listen for the point where the harshness goes away.
Should I turn off automatic gain control?
Turn it off while diagnosing, then decide. It hides the real level by pushing quiet voices up and loud ones down. Measure with it disabled to confirm your hardware is genuinely healthy; many people leave it on for calls and off for recording.