Diagnosis before treatment
Why does my mic sound bad? Name the symptom first.
A microphone sounds bad for one of five reasons: the wrong device is listening, the levels are set wrongly, an automatic process is meddling, the signal is being damaged in transit, or there is genuine noise in the room. Each family has its own symptoms and its own software fix — and treating the wrong family is how people end up buying a new microphone to solve a checkbox. Two minutes of diagnosis below, then a direct escort to the correct page.
The three questions that sort everything
Answer these in order. They separate the five families faster than any amount of slider-fiddling.
Does a local recording sound bad too — or only callers complain?
Record thirty seconds in any voice recorder and play it back. If the recording is bad, your problem lives in the capture chain: device choice, gain, processing, or the room. If the recording is fine but callers wince, the damage happens in transit — network, or the call app's own processing — and you should read the robotic voice guide, where transit problems are the lead suspects.
Is it bad in every app, or one app?
Bad everywhere means the problem sits at system level: input device, OS gain, enhancements, drivers. Bad in a single app means that app's private settings are overriding yours — a different device selected, its own auto-gain, its own aggressive suppression. Check the app's audio settings and disable its automatic adjustment before touching anything system-wide.
Is it constant, or intermittent?
Constant faults (always muffled, always quiet) point to settings and device choice — fixable in minutes. Intermittent faults (crackle that comes and goes, voice that drops to walkie-talkie quality mid-call, levels that surge) point to Bluetooth profile switches, CPU load, USB congestion or auto-gain — each covered in its symptom page below.
Find your symptom
| People say… | Most likely cause | Go to |
|---|---|---|
| "You sound muffled / underwater" | Wrong input selected, Bluetooth call profile, covered mic | Mic sounds muffled |
| "You sound robotic / choppy / garbled" | CPU spikes, packet loss, sample-rate mismatch | Mic sounds robotic |
| "You sound far away" | Distant mic listening, auto-gain fighting, low level | Mic sounds far away |
| "Speak up, we can't hear you" | Input level, gain staging, app auto-adjust | Mic too quiet |
| "There's crackling / static" | Sample rates, buffers, drivers, busy USB bus | Static & crackling |
| "You sound boomy / muddy / harsh / tinny" | Tonal balance — an EQ matter | EQ for voice |
| "There's a lot of background noise" | The room, not the mic — suppression territory | Gate vs suppression |
One rude guest, five disguises: Bluetooth
If your headset sounds splendid in music and dreadful the instant a call starts, you have met the hands-free profile. Bluetooth earbuds and headphones use a high-quality codec for listening, but many switch to a narrow, telephony-grade link the moment their microphone engages — taking your voice (and sometimes your audio) down with it. It masquerades as muffle, distance, quiet and even robot. The fixes — all software-side, from choosing a different input to letting the headset stay output-only — are in the muffled guide, because muffle is its favorite costume.
When the recording is fine but callers still complain
A clean local recording acquits your microphone and convicts the journey. Three transit suspects, in order of frequency: your upload bandwidth (other devices and uploads compete with your voice), your machine's CPU (a loaded processor starves real-time audio, and encoding stutters), and the call app's own processing (aggressive suppression or auto-gain chewing consonants). The robotic guide works through all three with software fixes. None of them require new equipment, which is fortunate, because we wouldn't tell you which to buy anyway.
The order of operations, once you know your family
Whatever the diagnosis, the treatment sequence is the same civilized chain: correct device → honest baseline → gain → retire the meddlers → EQ → suppression → pre-call check. It is written out step by step in how to make your mic sound better, and every symptom page slots into it. Do not skip ahead to suppression, however tempting — suppression applied to a mis-set mic is perfume on a fault.
If the diagnosis is simply "the room is loud"
Sometimes the checker ends quickly: your settings are fine and the problem is the world around you. That is the one family software solves by subtraction — Krisp removes background noise across every app, with a 7-day full trial (no card) and a Core plan at $8/month billed annually. Facts checked 20 September 2026.
Quiet the room with Krisp Disclosure, as manners require: this button is an affiliate link, and a subscription through it may pay the desk a fee without adding a penny to your bill. Every diagnostic step on this page is free.Asked at this desk
Why does my mic sound bad all of a sudden?
Sudden decline with no settings change is almost always one of three events: an update reset your defaults or reinstalled a driver, an app re-elected a different input device, or a Bluetooth device re-paired and grabbed the microphone role. Check the input device first — it is the culprit in the majority of "it was fine yesterday" cases.
Why do I sound fine to myself but bad to others?
Because you are not listening to what you transmit. Your sidetone or memory of your voice is not the signal after gain, processing, encoding and network. The only honest referee is a recording — locally first, then, if that is clean, a test call recorded at the far end.
Could it just be a bad microphone?
It could, and the baseline recording will tell you: if every device, setting and app produces the same faithful ugliness, the hardware is the suspect. At that point our advice ends honestly — repair or replacement is a purchase decision, and this desk does not do purchase advice. Run the checker first, though; most "bad mics" are innocent.