Skip to main content
fixmic

Discord Microphone Not Working

Last reviewed · fixmic team

Discord shows you connected to the voice channel, but no one can hear you — or your voice is choppy, robotic, or cutting in and out. Discord has its own audio stack on top of the OS, with several settings that silently mute you. This page walks through the six causes behind nearly every Discord mic failure, in the order most likely to fix it.

Try this first — Reset Voice Settings

Open User Settings (gear icon, bottom-left next to your name) → Voice & Video → scroll to the very bottom → 'Reset Voice Settings'. This reverts input device, sensitivity, codec, and processing to defaults. It fixes a large share of Discord mic problems in one click and takes 5 seconds.

1. Pick the right input device and run the Mic Test

Discord remembers a device even after you unplug it, and 'Default' often points at the wrong one. Verify which device Discord is actually listening to.

  1. User Settings → App Settings → Voice & Video

    At the top, set 'Input Device' to your actual microphone by name — not 'Default'. Do the same for Output Device so test playback comes through the right speakers.

  2. Use the built-in Mic Test

    Below the device dropdowns, find the 'MIC TEST' block and click 'Let's Check'. Speak — Discord records a short clip and plays it back. If you hear yourself clearly, Discord can hear you. If you hear nothing, the problem is upstream of Discord (OS permission or hardware) — jump to step 6.

  3. Watch the green bar under Input Sensitivity

    Scroll to 'Input Sensitivity'. Speak normally — the bar should fill green well past the threshold marker. If it barely moves, raise the Input Volume slider at the top to about 80%.

2. Turn off 'Automatically determine input sensitivity'

This is the single most common Discord mic problem. The auto-sensitivity feature is meant to ignore background noise, but on quieter voices and lower-output mics it drifts upward over time until your normal speaking voice falls below the threshold. The result: you sound completely silent to others, even though Discord recognises the input.

  1. Find the toggle under Input Sensitivity

    Voice & Video → Input Mode set to 'Voice Activity' → there's a toggle labelled 'Automatically determine input sensitivity'. Switch it OFF.

  2. Set the threshold manually

    A slider appears. Speak normally — the green bar shows your live input level. Drag the slider to roughly the point where the green bar starts lighting up. Anything below that level is treated as silence.

  3. Verify

    Stop speaking. The bar should drop into the grey/inactive zone. Speak again — the bar should turn green and Discord should activate the mic. If the threshold is too high, your voice still cuts; too low, and you transmit room noise.

3. Fix push-to-talk: keybind, release delay, and focus

Push to Talk is the most reliable input mode for noisy environments — but it has three failure points that look identical to a dead microphone.

  1. Set Input Mode to Push to Talk and bind a key

    Voice & Video → Input Mode → Push to Talk. A 'Shortcut' field appears. Click 'Edit Keybind' → 'Record Keybind', press the key (or combination) you want, and click 'Stop Recording'. Discord saves it as a global keybind.

  2. Raise the Push to Talk Release Delay

    Below the keybind, you'll see 'Push to Talk Release Delay' (default 20 ms). At 20 ms, the end of every word gets clipped — listeners hear your sentence cut off mid-syllable. Raise it to 100–200 ms. Most users settle around 100 ms.

  3. Discord needs to receive the keypress

    On Windows, a full-screen game running as administrator (or with anti-cheat) can capture your keys before Discord sees them. Two fixes: right-click Discord → 'Run as administrator' so it has equal priority, or play the game in borderless windowed mode. On macOS, grant Discord 'Accessibility' permission (System Settings → Privacy & Security → Accessibility) — without it, Discord cannot read global keypresses.

  4. Check for keybind conflicts

    If your PTT key is something the game also uses (e.g. mouse-button-4), the game may eat the press. Pick a key the game never uses — many people use a side mouse button or a function key.

4. Turn off Krisp and voice processing (a temporary test)

Discord ships Krisp noise suppression on by default. Krisp is excellent — but on quiet voices, headset mics with low output, or certain accents, it can misread your speech as background noise and silence you completely. The same applies to Echo Cancellation, Noise Reduction, and Automatic Gain Control.

  1. Voice & Video → Voice Processing

    Find the 'Noise Suppression' option. Switch it from 'Krisp' to 'Standard' (or off entirely).

  2. Toggle off the other processing options

    In the same section, turn OFF Echo Cancellation, Noise Reduction, and Automatic Gain Control — one at a time. Test in a voice channel between each toggle. The one that brings your voice back is the culprit.

  3. If turning everything off fixes it

    Re-enable them one by one in this order: Echo Cancellation → Automatic Gain Control → Standard Noise Suppression. Leave Krisp off if it was the one cutting you. The exact combination depends on your mic and room.

5. Switch the Audio Subsystem (the hidden fix)

Deep in Voice & Video → Advanced, Discord has a setting called 'Audio Subsystem' with options Standard, Legacy, and Experimental. This is the actual audio engine Discord uses to talk to your OS. On a stubborn mic that refuses to work despite correct settings, switching subsystems is the fix.

  1. Voice & Video → Advanced → Audio Subsystem

    If you're on 'Standard', switch to 'Legacy'. Discord prompts you to reload — click 'Okay'. The client restarts. After reload, run the Mic Test again.

  2. Try 'Experimental' next

    If Legacy does not help, switch to Experimental and reload. Some USB and Bluetooth mics work only on one of the three subsystems.

  3. Also check Quality of Service

    In the same Advanced section, toggle 'Enable Quality of Service High Packet Priority' OFF. On home routers with aggressive traffic shaping, this flag can cause Discord packets to be deprioritised, producing choppy voice.

6. Discord doesn't see the microphone at all

If the Input Device dropdown is empty, greyed out, or only shows 'Default', the problem is between Windows/macOS and Discord — not inside Discord itself.

  1. Windows: turn off exclusive mode

    Right-click the speaker icon (taskbar) → Sound settings → More sound settings → Recording tab → right-click your mic → Properties → Advanced tab. Uncheck 'Allow applications to take exclusive control of this device'. If another app (e.g. Zoom, OBS) grabbed the mic with exclusive control, Discord gets silence until you close that app.

  2. Windows: grant desktop app access to the mic

    Settings → Privacy & security → Microphone → enable 'Microphone access', 'Let apps access your microphone', and 'Let desktop apps access your microphone'. Discord installs as a desktop app, so the third toggle is the one that matters most.

  3. macOS: System Settings → Privacy & Security → Microphone

    Toggle Discord on. Then fully quit Discord (Cmd + Q — not just close the window) and reopen it. macOS only applies the permission change on relaunch.

  4. Browser Discord (discord.com/app) is a separate permission

    If the desktop client refuses to see the mic, log in at discord.com/app as a sanity check. Click the site-info icon in the address bar → Microphone → Allow → reload. If browser Discord hears you, the desktop client is the problem — reinstall, or use the browser version in the meantime.

Still silent in Discord?

If you've reset Voice Settings, fixed sensitivity, tested all three audio subsystems, and confirmed OS permissions — a few more things to check:

  • Run the live test on the fixmic homepage. If the meter moves there but Discord stays silent, the problem is definitively inside Discord — try a clean reinstall, deleting %appdata%\discord on Windows or ~/Library/Application Support/discord on macOS before reinstalling.
  • Streamer Mode (User Settings → Streamer Mode) can interfere with input on some setups. Turn it off temporarily to confirm.
  • If you only fail on one specific server, the server may have channel-level permission overrides that block voice for your role — ask a moderator.
  • On a Bluetooth headset, the mic drops to mono 16 kHz (HFP) the moment Discord opens. That's a Bluetooth Classic limitation, not Discord. See the AirPods/Bluetooth guide for the input-swap workaround.
  • Discord's status page (discordstatus.com) sometimes confirms voice-server outages in specific regions — worth a glance if everyone in your call has the same issue.

Related guides

Confirm your mic works outside Discord

Run the live test in your browser before changing more settings. If our test hears you, the problem is inside Discord — and the steps above will fix it.

Run the microphone test