Fix Discord Mic Not Working: Complete 2026 Guide

A microphone that works everywhere except Discord is telling you something useful. It means the hardware is fine and the fault sits in a Discord setting, a permission, or the way Discord picks its input device. This guide explains how to fix Discord mic not working by checking the exact places where Discord and the system can disagree, so you can stop reinstalling the app and start changing the one setting that actually matters.

Discord has its own input selector, its own volume controls, and its own voice processing, and any one of them can override what the system is doing correctly. That is why a mic can sound perfect in a voice recorder and stay silent in a voice channel. Working through the app settings before touching drivers keeps the fix small and the side effects smaller.

What Usually Causes This

Before the steps, it helps to know that this fault rarely has a single cause, and the table below separates the likely causes by the sign you actually see, so you can start at the row that matches your situation rather than at the top of a generic list. Working out how to fix Discord mic not working starts with that match, because the right first step depends on the symptom in front of you.

Likely cause	Sign you will see	First check
Wrong input device	Meter moves for another mic	Select the exact mic in Voice and Video
Muted or deafened	Mic icon shows a slash	Unmute and undeafen in Discord
System permission off	Mic works elsewhere but not Discord	Check system microphone privacy
Push to Talk keybind fault	Voice works only with a key held	Check Input Mode and keybind
Server mute	Mic icon cannot be unmuted	Ask a server moderator
Driver or hardware fault	Mic fails in every app	Update drivers and test hardware

Note what changed before the fault began, what still works, and what you have already tried, because those three facts turn a frustrating afternoon into a short sequence of tests. A short note on those points, written before you start, also makes any later conversation with support far shorter, since you can describe what you have ruled out instead of repeating the symptom.

Before You Reinstall Anything

Read the whole guide once before changing anything, because the order matters, and a step skipped early often returns as a larger problem later. Where a price or a feature is given, check it on the vendor page before you commit, since pricing and features change, and the right choice depends on your situation and your existing setup.

When you approach fix Discord mic not working, keep a simple log of each test and its result, even a few lines on paper. Change one thing, test, and note the result before moving on, because changing three things at once and seeing an improvement leaves you unsure which change helped, and the fault returns when the unhelpful changes are undone.

Back up anything important before the later steps, even if you do not expect to reach them. A backup made while the device still works is worth far more than a backup attempted after a destructive step, and it removes the fear that keeps people from taking a legitimate last resort step. Check that the backup completed, rather than assuming it did, since a backup that never finished offers no protection at all.

Discord microphone visual tied to the Before You Reinstall Anything section of this guide

How to fix Discord mic not working in the Right Order

Working through fix Discord mic not working in this order keeps the least disruptive tests first, so a simple settings fault is found before anyone considers a reinstall, a replacement, or a repair booking, and each step below ends with what a success looks like, so you know when to stop.

**Check mute and deafen first.** Look at the microphone and headphones icons beside your username in Discord, and click to unmute and undeafen if either shows a slash. Deafen also mutes your microphone, so a deafened state silences you even when the mic icon looks normal. Test in a voice channel after changing both, since the icons alone do not confirm audio. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
**Select the exact input device.** Open User Settings, Voice and Video, and choose your actual microphone from the Input Device dropdown instead of leaving it on Default. Laptops often list a built in mic, a headset mic, and a monitor mic, and Discord may default to the wrong one. Speak and watch the input meter, since a moving meter confirms the choice immediately. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
**Raise input volume and test with Lets Check.** In the same Voice and Video panel, raise Input Volume to a high level for the test, and use the Lets Check feature to hear your own microphone. A volume set too low can make a working mic sound silent to others, while a meter that never moves points back at device selection or permission. Adjust volume down again once the mic is confirmed working. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
**Check Input Mode and sensitivity.** Confirm Input Mode is set to Voice Activity unless you intend Push to Talk, and check the sensitivity slider. With Voice Activity, the bar should light up when you speak and stay dark for background noise. With Push to Talk, confirm the keybind works and does not clash with a game key, since a clashing keybind can block transmission entirely. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
**Test the mic outside Discord.** Open the system sound settings or another voice app and test the same microphone. A mic that works elsewhere points at Discord settings or permission, while a mic that fails everywhere points at the system, the driver, or the hardware. This test decides whether the remaining steps should focus on Discord or the device. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
**Check system microphone privacy.** On Windows, open Settings, Privacy and security, Microphone, and confirm microphone access and desktop app access are on. On macOS, open System Settings, Privacy and Security, Microphone, and confirm Discord is allowed. A system block overrides Discord settings, so Discord cannot receive audio until the system allows it. At this stage of fix Discord mic not working, a success here is especially valuable, because it proves the fault sat in the middle of the sequence rather than at either end. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
**Restart Discord fully.** Quit Discord completely, including from the system tray, and relaunch it. A Discord process left running in the tray can hold an old audio route after a device change. Test in a voice channel after relaunch, before opening other audio apps, so a fresh app cannot seize the microphone first. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
**Check for a server mute.** Look for a muted mic icon that you cannot turn off, or a message saying you are muted by the server. A server mute is set by a moderator and cannot be cleared from your settings, so contact a moderator and ask them to unmute you. Testing in a direct call or another server confirms a server mute, since the mic will work there. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
**Reset voice settings.** In Voice and Video settings, scroll down and choose Reset Voice Settings, then test again. A reset clears a stuck routing path or a conflicting custom setting, including sensitivity, attenuation, and processing options. Note your custom settings first, since the reset returns them to defaults and you may want to restore some of them. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
**Disable audio processing for a test.** Temporarily turn off noise suppression, echo cancellation, and attenuation in Voice and Video settings, then test. Processing features can suppress a quiet voice or a non standard microphone to silence, especially on headsets with their own processing. If the mic works with processing off, re-enable features one at a time. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
**Update audio drivers.** On Windows, update the microphone or headset driver through Device Manager, and install Windows updates. On macOS, install system updates. Restart after updating, then test the mic outside Discord first, so a system fault is proven fixed before Discord is tested again. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
**Reinstall Discord as a last resort.** Uninstall Discord, restart, and install a fresh copy from the official Discord site, then sign in and test before restoring custom settings. A reinstall clears corrupted app files and forces a fresh permission request. Test in a voice channel immediately after reinstall, so a restored setting cannot reintroduce the fault. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.

Discord microphone visual tied to the How to fix Discord mic not working in the Right Order section of this guide

Details People Often Miss

Discord mic faults are usually routing faults rather than broken microphones, because Discord sits behind several layers of device selection. The system default, the Discord input device, the input mode, and the server state must all agree, and any one mismatch silences you while the microphone itself works perfectly. Checking the layers in order, from mute to device to permission to server, finds the mismatch quickly. This distinction shapes how you should approach fix Discord mic not working.

The input meter in Voice and Video settings is the most honest test in Discord, because it shows what Discord receives before any server, channel, or processing setting takes effect. A meter that moves while others cannot hear you points at mute, server mute, or output routing on their side, while a meter that never moves points at device or permission. Use the meter after every change.

Push to Talk deserves a specific check, because it changes the meaning of every other test. A mic that works only while a key is held is not broken, it is in Push to Talk mode with a keybind that may clash with a game. Owners often switch modes by accident through a shortcut, then test with Voice Activity expectations and conclude the mic has failed.

The checks that matter most, in brief, are the first five steps of the sequence, and they deserve a second pass if the fault survives them.

Check mute and deafen first
Select the exact input device
Raise input volume and test with Lets Check
Check Input Mode and sensitivity
Test the mic outside Discord

Discord publishes voice and microphone guidance through its official support pages, and the Voice and Video paths in this guide follow those pages. See the official Discord support site for the current voice settings steps for your platform.

Testing one change at a time is the habit that separates a quick repair from a long afternoon of guessing. Change a single setting, run the same test you ran at the start, and write down the result before you touch anything else. When a later step appears to work, that note tells you whether the improvement came from the latest change or from an earlier one that only needed time to take effect. Support teams ask for the same log, so the habit pays twice.

A short note made before you start will save time later, especially if the fault returns or if someone else has to finish the job. Record what changed just before the fault appeared, which tests you have already run, and what each test showed. A fault that began after an update, a new accessory, or a move points in a different direction from a fault that appeared out of nowhere, and that single detail often narrows the search more than any single setting.

Do not judge a fix by the first few seconds after you apply it. Some settings need a restart, some connections need a fresh pairing attempt, and some apps need a full close before a change takes effect. Run the same real world test you used at the start, such as opening the feature, making a test call, or playing a short clip, and give the result a full minute before you declare the step a failure and move on.

If the same fault has appeared before, look for the pattern rather than treating each occurrence as new. A fault that returns after every update, every long trip, or every period of heavy use usually has a trigger that the ordered steps can expose. Fixing the trigger, such as a worn cable, a full storage, or an app that hogs resources, prevents the next occurrence far better than repeating the same quick fix.

Keep the accessories you use for testing in a known good state. A spare cable, a charged spare remote battery, or a second pair of earbuds turns a vague suspicion into a clear answer in under a minute. When the fault follows the accessory to another device, the accessory is the problem. When the fault stays with the original device, the device or its settings deserve the attention.

Before any step that erases data or resets settings, confirm where your important content lives. Photos, messages, and documents that sync to a cloud account usually return after a reinstall, while local downloads and unsaved work may not. A quick backup takes a few minutes and turns a last resort step from a risk into a routine procedure.

When a fault may end in a warranty claim, preserve evidence as you go rather than reconstructing it later. Keep dated notes, keep the original accessory that failed, and avoid opening a sealed device, since an opened device can complicate a claim even when the fault is genuine. A repair centre that receives a clear timeline and untouched hardware can usually decide faster than one that receives only a description.

After any system or app update, retest the feature that previously failed, even if the update notes do not mention it. Updates change drivers, permissions, and background behaviour in ways that release notes rarely capture fully, and a fault that an update quietly fixed can return with the next update just as quietly. A two minute retest after each update turns that uncertainty into a known result.

Discord microphone visual tied to the Details People Often Miss section of this guide

Mistakes That Make It Worse

The following errors do not cause the original fault, but they regularly turn a short repair into a long one, and they are worth naming before you start.

Reinstalling Discord before checking mute and input device, which replaces working software for a settings fault.
Leaving Input Device on Default after plugging in a headset, which lets Discord switch microphones silently.
Testing only in one server, which leaves a server mute disguised as a mic fault.
Setting sensitivity so high that background noise transmits constantly, which leads others to mute you.
Ignoring system privacy settings, which override every Discord setting when they block the mic.

Avoiding those errors keeps fix Discord mic not working short and calm, because every wasted reset or repeated test adds frustration without adding evidence, and a calm repair is a faster repair.

Discord microphone visual tied to the Mistakes That Make It Worse section of this guide

When to Stop and Get Help

Contact a server moderator when the mic works in direct calls and other servers but not in one server, since that pattern proves a server mute. Contact Discord support or seek hardware help when the mic fails in every app after a driver update and a permission check. Take notes on input device, meter behaviour, and the outside Discord test, since those three facts decide the next step.

Take your notes with you when you seek help, including which tests passed and which failed, and the exact conditions where the fault appears. Support moves faster with ruled out causes than with a repeated symptom description, and a clear log often leads to a faster repair or a correct replacement part on the first visit.

Discord microphone visual tied to the When to Stop and Get Help section of this guide

How to Prevent a Repeat

Choose the exact input device after connecting any new headset, and review Input Mode and sensitivity after any Discord update. Test the meter before an important call, and keep system microphone permission reviewed after operating system updates. A short pre call check of mute state, input device, and meter prevents most Discord mic faults.

A ten minute monthly check of updates, storage, cables, and permissions catches most problems while they are still small, and it builds a baseline so a future change stands out immediately. Prevention is not extra work on top of the repair, it is the same discipline applied before the fault appears, and it pays for itself the first time it saves a repeat repair.

Discord microphone visual tied to the How to Prevent a Repeat section of this guide

Going One Layer Deeper

A second pass is not a repeat of the first pass, it is a different kind of test. The first pass rules out the common causes in order, while the second pass looks for a cause that was masked during the first, such as a second device interfering, a setting that reverted after a restart, or a fault that only appears under load. Work the second pass slowly, and change only one variable at a time, since a second pass done hastily produces the same confusion as the first pass done at random.

During the second pass, test under the exact conditions where the fault originally appeared, with the same app, the same accessory, and the same network or location. A fault that cannot be reproduced under test conditions has not necessarily been fixed, it may simply be waiting for its trigger. If the second pass still fails, the notes from both passes together give support a far stronger starting point than either pass alone, and they often reveal a pattern that a single pass hides.

Making Sure the Fix Sticks

Return to the first step and confirm it properly before moving on, because a step that was rushed the first time often looks like a failure when it was really an incomplete test. Give it the full time it needs, watch for the result described in the main sequence, and only then move to the next step. This habit of retesting the early steps, rather than jumping to the later and more disruptive ones, saves most of the time that troubleshooting usually wastes.

The diagnosis table at the start deserves a second look once the main steps are done, because a cause that seemed unlikely at the start can become the leading explanation once the obvious ones are ruled out. Compare what you observed with the sign described for each row, and if your observation matches a row you dismissed earlier, work that row again with fresh attention. Diagnosis improves when the table is treated as a checklist to revisit, not as an introduction to skip.

Test again the next day under normal use, not just in the moment after the fix. Some faults return when the device warms up, when a background app updates, or when the original trigger recurs, and a next day test catches those returns while the repair is still fresh in your mind. If the fault returns, note exactly what changed since the fix, since that change is the most likely trigger.

Frequently Asked Questions

Why did this problem start suddenly?

The commonest trigger is a change just before the fault, such as an update, a new accessory, a move, or a period without use. Tracing that change usually points at the cause faster than testing parts at random. Note the last change first, then work through the ordered steps, because a fault with a clear trigger often has a short fix and a fault without one needs the full sequence. Retest the exact action that failed before, not an easier one.

How long should each fix take before I move on?

Give each simple step a proper test rather than a glance, because a restart, a cable swap, or a permission change needs a minute or two to show its result, while a reinstall or a restore needs longer. If a step shows no change after a fair test, move on and note the result, because the log of failed steps is what narrows the remaining causes for the steps that follow. Retest the exact action that failed before, not an easier one.

Will clearing data or resetting settings delete my content?

Clearing a cache removes temporary files only, while clearing data or storage signs you out and removes local settings, so check where your content lives before the stronger step. Content that syncs to a cloud account usually returns after a reinstall, while local downloads and unsaved work need a backup first. Never take a destructive step on a device that holds the only copy of something important. Retest the exact action that failed before, not an easier one.

What if the fault affects only one app, one device, or one connection?

That pattern is useful evidence, because a fault tied to one app points at that app and its permissions, while a fault that follows the device points at the device itself. The ordered guide for fix Discord mic not working helps separate those two cases before you change settings everywhere, and testing with a second app, a second device, or a second connection is the fastest way to draw that line. Retest the exact action that failed before, not an easier one.

When should I contact support instead of trying more fixes?

Contact support after the ordered steps fail, or immediately if you see danger signs such as heat, swelling, liquid damage, or a burning smell, and take your notes on what you tried. Support moves faster when you can list the causes you have ruled out, and continuing to guess after that point risks making a repairable fault worse or turning a warranty claim into a dispute. Retest the exact action that failed before, not an easier one.

How do I stop this happening again?

Keep updates current, keep comfortable free storage, check cables and permissions monthly, and note any change before a fault appears, because most repeats come from the same neglected basics. A ten minute monthly check is cheaper than another afternoon of troubleshooting, and it builds a baseline that makes future changes obvious before they become faults. Retest the exact action that failed before, not an easier one.

The Bottom Line for This Fault

Work through fix Discord mic not working in order, stop at the step that works, and keep the notes on what you tried, because that discipline turns a frustrating fault into a short sequence of tests, and it also means the next fault starts from a known baseline instead of from scratch.

Start with the first step today, test one change at a time, and let the result of each test decide the next move, because a calm ordered approach beats a fast random one, and the time saved by not repeating failed steps is time you get back for the work itself.

Discord Mic Not Working? Fixes in Order (Input Device, Permission, Server)