Discord produces more “my mic is dead” reports than any other app — not because it’s fragile, but because it layers its own device picker, gain, noise gate and processing on top of the OS, and each layer fails differently. Here’s the order to check them.

First: prove the mic outside Discord

One minute on the mic tester before touching a single Discord setting: if the meter moves and the playback is clean, the hardware + OS + (for Discord-in-browser) the permission layer are all proven — everything left lives inside Discord’s own settings. If the meter is flat, stop here and run the ordered fix checklist instead; Discord can’t fix a dead input.

Voice & Video: the controls that matter

User Settings (the cog, bottom-left) → Voice & Video. In order:

1. Input Device. “Default” follows the OS; a named device is Discord’s own pick — and Discord remembers picks across unplug events, so a headset you removed weeks ago can still be selected. Set it to Default, or explicitly to the mic you mean.
2. Input Volume. Discord’s own gain, multiplied with the OS gain. For “you’re too quiet” reports, this is the first dial.
3. Mic Test — ‘Let’s Check’. Records a few seconds and plays them back. With the live input meter beside it, this answers “does Discord hear me at all” in ten seconds.
4. Input Mode — Voice Activity vs Push to Talk.
   • Voice Activity opens the mic once you pass a sensitivity threshold. With automatic sensitivity on, Discord sets the gate itself; manual mode gives you a slider — set too high and quiet speech never opens the mic, too low and your fans broadcast forever.
   • Push to Talk needs a keybind (Record Keybind) and a short release delay (~20–50 ms) so word-endings aren’t clipped. Reliable in noisy rooms; a liability when you forget you’re unkeyed.
5. Voice Processing. The toggles that shape everything:
   • Echo Cancellation — leave it on with speakers; optional with headphones.
   • Noise Suppression — Krisp / Standard / None. Krisp is the strongest and the most artifact-prone: it eats keyboards and dogs impressively, and it can also eat consonants. If friends say you sound robotic or “underwater,” step down to Standard or None and compare.
   • Automatic Gain Control — keeps your level even as you lean in and out; disable it if you’re riding a hardware gain knob carefully, because AGC pumping is audible.
6. Advanced. Audio Subsystem (Standard / Legacy / Experimental) is the fix of last resort for stubborn USB mics and interfaces — Legacy resolves a real share of “Discord sees the device but gets no signal” cases. Attenuation and packet-priority settings affect what you hear, not your mic.

“You’re too quiet” / “you’re clipping” — the fix paths

Too quiet, in order: Discord Input Volume up → OS input level up → AGC on → move closer (a hand’s width is the baseline — distance beats gain every time). If the tester meter already peaks between −20 and −6 dB, the problem is Discord-side, full stop.

Clipping or distorted: the reverse — Discord Input Volume down → remove any OS-level mic boost (Windows: mic Properties → Levels) → back off the mic or speak slightly off-axis. Two gain stages (OS + Discord) stacked hot is the classic cause; lower the earlier one first.

Robotic, watery, choppy: that’s processing, not level — step Noise Suppression down a level and retest.

Verify after every change

Discord’s own mic test proves what Discord captured; the tester’s recording proves what your raw signal looked like before Discord touched it. A/B the two after each change and you’ll know exactly which layer the fix landed in. If Discord is fine but the meeting apps are the problem, the same layered approach lives in testing your mic in Zoom, Teams & Meet — and if delayed echo of your own voice is the real complaint, that’s monitoring latency, not Discord.

Frequently asked questions

Where is the mic test in Discord?

User Settings (the cog next to your avatar, bottom-left) → Voice & Video → the Mic Test section under the input controls → 'Let's Check'. Discord records a few seconds and plays them back so you hear what it captured. The live input meter in the same section moves as you speak — quicker than the recording for a yes/no check.

What does Krisp do to my microphone quality?

Krisp is Discord's aggressive ML noise suppression — great on keyboards, fans and dogs, but when it's working hard it can make voices sound watery, robotic, or chopped at the start of words. It's under Voice & Video → Noise Suppression: try Standard (milder) or None (quiet room, decent mic) and compare — a recorded clip side by side makes the difference obvious.

Discord says 'no input detected' but my mic works elsewhere — why?

Three usual causes: the Input Device dropdown in Voice & Video points at a different input than the OS default (Discord remembers old picks); input mode is Push to Talk and you're not holding the key; or Voice Activity's sensitivity slider sits too high for the gate to open. Try 'Default' as the device and automatic sensitivity first.

Why am I quiet on Discord when other apps are fine?

Discord has its own Input Volume slider and Automatic Gain Control stacked on top of OS gain — the two multiply. Turn Discord's slider up, confirm AGC is on, and check the OS input level isn't parked low. Then verify the raw signal with the mic tester: if the meter peaks healthy there, Discord's own controls are the fix.

How do I set up push to talk in Discord?

Voice & Video → Input Mode → Push to Talk → Record Keybind, then press the key you want. Set the release delay to ~20–50 ms so the last syllable isn't cut. PTT beats voice activity in loud rooms and with mechanical keyboards — but it makes you inaudible whenever you forget the key, which is most 'dead mic' reports.

Does Discord in a browser have the same audio settings?

Mostly — the device picker, input mode and sensitivity are there, but Krisp and some processing options are desktop-app features, and the browser version sits behind the site's mic permission (lock icon → Allow). If Discord-in-browser fails while the desktop app works, the permission layer is the first suspect.