Discord Mic Not Working? 13 Fixes That Actually Work

You've joined a voice channel, other people can hear each other fine, and your green mic ring never lights up — Discord just isn't picking up anything. A broken microphone is one of the most common complaints in Discord's own support forums, and it affects gamers, streamers, remote workers, and Discord-based communities equally. The good news: in the overwhelming majority of cases, the microphone hardware itself is completely fine. The problem is almost always a setting — either inside Discord, inside your operating system, or a conflict with another app that's quietly grabbing the mic first.

This guide walks through all 13 fixes, ranked from the fastest and most common (wrong input device selected) to the more involved hardware and driver-level causes. We cover Windows 10/11, macOS, and mobile, and explain exactly why each fix works so you can diagnose the real cause instead of guessing.

Diagnose the Cause in 30 Seconds

Symptom	Likely Cause	Jump To
Green input bar never moves, at all	Wrong input device selected, or OS permission blocked	Fix 1, Fix 2
Bar moves but others can't hear you	Server mute, muted mic icon, or Input Volume near zero	Fix 4, Fix 5
Worked yesterday, broken today with no changes	Another app (Zoom, Teams, OBS) is holding exclusive mic access	Fix 6
Mic cuts in and out, or only picks up loud sounds	Input Sensitivity threshold set too high	Fix 3
Voice sounds robotic, clipped, or partially muted	Krisp / Noise Suppression over-filtering	Fix 9
Works in every other app except Discord	Corrupted Discord voice cache — needs reset	Fix 10, Fix 13

13 Fixes for a Discord Mic That Isn't Working

Discord Mic Not Working on iPhone or Android

Mobile mic issues follow a different diagnostic path than desktop, mostly because there's no visible input meter to test with the way there is on Windows or Mac. On both iOS and Android, the starting point is always the same: the operating system's own app-level microphone permission, which is separate from any in-app Discord setting.

On iPhone: go to Settings > Discord and confirm the Microphone toggle is on. If Discord isn't listed under Settings at all, it means iOS has never registered a permission request from it — open Discord, join a voice channel, and iOS should prompt you; if it doesn't, force-close Discord (swipe up from the app switcher) and relaunch. Also check Settings > Screen Time > Content & Privacy Restrictions > Microphone isn't blocking app-level access, which is common on shared or managed family devices.

On Android: go to Settings > Apps > Discord > Permissions > Microphone and confirm it's set to "Allow." Android manufacturers layer their own permission systems on top of stock Android (Samsung's "Auto permission removal" is a frequent culprit) — if Discord hasn't been opened in a while, some Android skins silently revoke microphone access to save battery. Reopen Discord, and if the permission was auto-revoked, you'll need to re-grant it manually rather than expecting a prompt to reappear automatically.

A second common mobile-specific cause: Bluetooth headset routing. If you're using AirPods, a Bluetooth gaming headset, or a car Bluetooth connection, the phone's OS sometimes keeps routing audio through the wrong Bluetooth profile (media-only, not hands-free/mic-enabled). Disconnect and reconnect the Bluetooth device from your phone's Bluetooth settings menu, not from within Discord, to force the OS to renegotiate the correct audio profile that includes microphone input.

How Long Does This Usually Take to Fix?

Based on the remote troubleshooting sessions we run for Discord audio issues, most cases resolve within the first three fixes on this list. Wrong Input Device selection (Fix 1) accounts for the largest single share of reports and typically takes under a minute to diagnose and fix once you know where to look. OS-level permission blocks (Fix 2) are the second most common, and usually add only another minute or two, since the fix is just a toggle switch once you find the correct settings page.

Cases that require driver reinstalls (Fix 8), a full Discord reinstall (Fix 13), or hardware-specific companion software troubleshooting (the headset-specific section below) are less common but take meaningfully longer — typically 10-20 minutes including a restart. If you've worked through the first six fixes without success, it's a reasonable point to consider whether the remaining, more time-intensive fixes are worth attempting yourself versus getting a technician to diagnose it directly over a screen share, which usually narrows the cause down in a few minutes just by watching your exact settings live.

Test Your Mic Outside Discord First

Before working through the numbered fixes, it's worth spending 30 seconds confirming whether the problem is Discord-specific or system-wide — this alone tells you which half of the troubleshooting list to focus on. On Windows, right-click the speaker icon in the taskbar > Sound settings > scroll to Input > you'll see a live blue volume bar under your selected microphone as you speak. On Mac, go to System Settings > Sound > Input, and you'll see the same kind of live level indicator.

If the OS-level meter moves normally but Discord's doesn't, the problem is isolated to Discord — focus on Fixes 1, 3, 9, and 10, which deal with Discord's own input selection, sensitivity, and cached voice configuration. If the OS-level meter also doesn't move, the problem is upstream of Discord entirely — a hardware fault, a driver issue, or an OS permission block — and Fixes 2, 7, 8, and 12 (permissions, exclusive mode, drivers, and physical connections) are the more productive starting points. This single check can save you from working through Discord-specific settings when the actual fault is a loose USB connection or a muted OS-level input.

A quick way to test the mic completely independently of both Discord and the OS settings panel: open the Windows Voice Recorder app (search "Voice Recorder" in the Start menu) or macOS's QuickTime Player (File > New Audio Recording), record a few seconds of speech, and play it back. If it records silence or nothing at all, you've confirmed the issue sits below the application layer — most likely a driver, permission, or physical hardware problem rather than anything inside Discord.

Headset-Specific Quirks: HyperX, Razer, Logitech G, SteelSeries, Corsair

Gaming headset brands ship their own companion software — HyperX NGENUITY, Razer Synapse, Logitech G HUB, SteelSeries GG (Sonar), and Corsair iCUE — and each of these can independently intercept audio routing before it ever reaches Discord. If you have any of these installed, they're worth checking specifically, because they behave differently from a generic Windows driver conflict.

SteelSeries GG / Sonar installs its own virtual audio devices (things like "SteelSeries Sonar - Microphone") that sit between your physical mic and every app, including Discord. If Sonar's own input/output routing is misconfigured, Discord can end up listening to a virtual device that's receiving no signal, even though your headset's actual hardware mic is working fine. Open GG, go to Sonar, and confirm the "Chat Mic" or "Streaming" input is correctly routed to your physical headset mic, not muted at the software mixer level.

Razer Synapse and Logitech G HUB both have their own per-app volume and mic gain controls that operate independently of Windows' native mixer — a muted or zeroed slider inside these apps won't show up as muted anywhere in Windows or Discord, it just silently drops the signal. Open the companion app, find your headset's audio profile, and check the mic gain/mute state directly inside that software, not just in Windows Sound settings.

Corsair iCUE and HyperX NGENUITY are less likely to intercept audio routing directly, but both are known to conflict with exclusive mode settings (Fix 7 above) when their own "enhanced audio" features are toggled on. If you've tried every Discord and Windows-level fix with no luck and one of these apps is installed, try fully closing it (not just minimizing to tray) and testing Discord's mic again before assuming a deeper hardware problem.

Discord Audio Settings Glossary

A few of the settings referenced throughout this guide aren't self-explanatory. Here's what each one actually controls:

• Input Sensitivity: the volume threshold your voice needs to cross before Discord treats it as "you're talking" and transmits audio. Too high a threshold silently drops quiet speech.
• Automatic Gain Control (AGC): automatically raises or lowers your mic's volume in real time to keep it consistent. Occasionally causes pumping or cutting artifacts on sensitive mics — worth disabling to test if voice sounds unstable.
• Echo Cancellation: removes your own voice from being picked back up through your speakers if you're not using headphones. Rarely the cause of "not working," but can make voice sound muffled if misconfigured.
• Krisp Noise Suppression: Discord's built-in AI noise filter, licensed from Krisp.ai. Extremely effective at removing background noise but occasionally treats quiet or accented speech as noise to be removed.
• Exclusive Mode (Windows): a Windows audio setting that allows one single application to take full, locked control of an audio device, blocking every other app — including Discord — from accessing it simultaneously.
• Push to Talk vs. Voice Activity: two different input modes. Voice Activity transmits automatically once your volume crosses the Input Sensitivity threshold; Push to Talk only transmits while a specific bound key is physically held down.

Preventing Discord Mic Problems From Coming Back

Once your mic is working again, a few habits significantly reduce the odds of it breaking the next time you update Windows, macOS, or Discord itself:

• Always select your mic by name, never "Default." The Default option is what silently breaks after Windows reassigns device priority following a driver update or a new USB device being plugged in anywhere on the system — not just your mic.
• Keep Discord and your audio drivers updated together. A large share of "it worked yesterday" reports we see trace back to a Windows Update or a Discord auto-update landing between sessions. Checking both after any mic issue appears helps you catch the actual trigger instead of guessing.
• Avoid using more than one voice/communication app at a time when possible, especially ones that request exclusive audio device access (older versions of OBS and some VOIP-based games are the most common offenders).
• If you use Push to Talk, memorize the key. A surprising number of "mic randomly stopped working" tickets turn out to be Push to Talk mode toggled on accidentally, with the user not realizing it and holding nothing.

Why Does Discord Say My Mic Works in Settings, But No One Can Hear Me?

This is one of the most confusing scenarios users report: the green meter in Voice & Video settings moves perfectly when you talk, proving the mic hardware, driver, and OS permission are all fine — yet in an actual voice channel, other members say they hear nothing. Here's what's actually happening: the settings page only tests local audio capture. It does not simulate the full pipeline Discord uses once you're in a real voice channel — including Input Sensitivity gating, Push to Talk key state, Krisp noise suppression, and server-level mute flags.

Work through this checklist specifically for the "works in settings but not live" scenario: confirm Input Mode is set to Voice Activity (not Push to Talk, unless you're actually holding the bound key); confirm you aren't server-muted (check the member list for a muted icon next to your name); confirm Input Sensitivity isn't gating out normal speech; and try temporarily disabling Krisp. In our experience fixing this remotely, roughly half of these cases turn out to be an accidentally-enabled Push to Talk mode with a key the user isn't pressing.

Common Mistakes That Waste Time Troubleshooting This

After fixing hundreds of Discord audio issues remotely, a handful of mistakes come up repeatedly and consistently delay finding the real cause:

• Restarting the PC before checking Input Device selection. A restart fixes almost nothing here, since it's a settings issue in the vast majority of cases, not a system-state issue. Check Fix 1 before doing anything more drastic.
• Reinstalling Discord immediately. This is the very last fix on this list for a reason — it clears your local settings and cache, meaning if the actual problem was a simple wrong-device selection, you'll have wiped useful diagnostic information (like which device Discord had selected) without fixing anything.
• Assuming a new headset is defective because it doesn't work in Discord immediately after plugging it in, without first checking whether it works in the OS-level sound test described above. New hardware is far more likely to be a driver or default-device issue than an actual defect.
• Not checking companion software (Fix: Headset-Specific Quirks section) when troubleshooting a gaming headset specifically — Windows and Discord can both report everything as correctly configured while a brand's own audio software is silently muting or misrouting the signal underneath.
• Testing only in the Voice & Video settings page and assuming that's proof the mic works everywhere, when in fact it only tests local capture — see the section above on why the settings test can pass while live voice channels still fail.

Frequently Asked Questions

Why does my mic work in Windows but not in Discord?

This almost always means Discord has the wrong Input Device selected, or the mic is set to "exclusive mode" by another app. Manually select your microphone from the Input Device dropdown in Voice & Video settings instead of leaving it on "Default," and check Windows Sound Settings > Input > Device Properties > Advanced to uncheck exclusive mode.

How do I give Discord microphone permission on Windows 11?

Go to Windows Settings > Privacy & security > Microphone. Turn on "Microphone access" and "Let apps access your microphone," then confirm Discord is toggled on in the app list below. If Discord isn't listed, fully quit and reopen it, then join a voice channel to trigger the permission prompt.

Why does Discord say my mic is working in the settings test but other users can't hear me?

The settings page only tests local capture, not the full live pipeline. Check that Input Mode is set to Voice Activity (not an unpressed Push to Talk key), you aren't server-muted, Input Sensitivity isn't gating your voice, and Krisp noise suppression isn't over-filtering.

Does closing Zoom or Teams fix Discord mic issues?

Often yes. Many mics only support one app accessing them at a time. If Zoom, Teams, or OBS is still running in the background with the mic open, Discord may show "no input detected." Fully quit other audio apps, including in the system tray, before retesting.

How do I fix Discord mic not working on Mac?

Go to System Settings > Privacy & Security > Microphone and confirm Discord is toggled on. If never prompted, quit Discord fully with Cmd+Q, reopen, and join a voice channel to trigger the permission dialog. Also confirm the correct mic is set as the system default in Sound settings.

Why did my Discord mic stop working after a Windows Update?

Windows Updates frequently reset default audio device priority or reinstall generic audio drivers over your headset's dedicated driver. Reopen Discord Settings > Voice & Video and re-select your mic by name from the Input Device dropdown, since it may have silently reverted to "Default" or switched to your laptop's built-in mic. If the mic is missing from the dropdown entirely, update its driver via Device Manager.

How do I fix Discord mic issues on iPhone or Android?

Check the OS-level microphone permission first: Settings > Discord > Microphone on iPhone, or Settings > Apps > Discord > Permissions > Microphone on Android. If using a Bluetooth headset, disconnect and reconnect it from your phone's Bluetooth settings (not inside Discord) to force the correct hands-free audio profile with mic support to load.