sodcalculator

10 Tech How-To

Discord Error 3002 Mic Not Detecting Input? Fix

Guide 10-54323 · Updated · Step by step

Discord error 3002 means the app cannot detect any audio from your microphone, so your voice never reaches the call. The fix is usually a quick permission or input-device setting change, not a hardware failure. Below are the exact steps to resolve it on Windows, macOS, and mobile, plus what causes the error in the first place.

What Error 3002 Actually Means

Discord uses error codes to describe why an action failed. Error 3002 specifically appears when the client tries to read audio from your mic but gets no signal. It is not a ban, not a server outage, and not a network problem. The error typically shows as a red banner inside the voice channel or in the user settings, often accompanied by “No input detected” or “Mic not working.”

The underlying cause is almost always one of these three:

  • Your OS or browser is blocking Discord from accessing the mic.
  • Discord is set to the wrong input device (e.g., a webcam mic instead of your headset).
  • The mic itself is muted, at zero volume, or disabled in system sound settings.

Less common but possible: outdated audio drivers, a corrupted Discord cache, or a third-party app (like a voice changer) holding exclusive control of the mic. The steps below cover all of these in order of likelihood.

Quick Fix: Check Permissions First

On Windows 10 and 11, Discord needs both the system microphone permission and, if you use the browser version, the browser’s own permission. If either is off, you get error 3002.

  1. Open Windows Settings → Privacy & security → Microphone.
  2. Make sure “Microphone access” is turned On.
  3. Scroll down to “Let apps access your microphone” and ensure it is On.
  4. Find Discord in the list of apps and toggle it to On. If you use the web app, also check the browser’s site permissions (the lock icon in the address bar).
  5. Restart Discord completely (right-click the tray icon → Quit, then reopen).

On macOS, go to System Settings → Privacy & Security → Microphone and make sure Discord is checked. On mobile (iOS/Android), go to the OS settings for Discord and enable the microphone permission. If you recently updated the OS or reinstalled Discord, permissions often reset to off, which is why this is the first thing to check.

Select the Correct Input Device in Discord

Even with permissions granted, Discord may be listening to the wrong device. This happens frequently when you plug in a USB headset after launching Discord, or when a monitor with a built-in mic becomes the default.

  1. Open Discord → User Settings (gear icon) → Voice & Video.
  2. Under “Input Device,” click the dropdown and select your actual microphone. If you are not sure which one it is, say something and watch the “Input Sensitivity” bar—it should move.
  3. If the bar does not move, try each device in the list until one responds.
  4. Set “Input Volume” to at least 80–100%.
  5. Scroll to “Input Sensitivity” and choose “Automatically determine input sensitivity” unless you have a specific reason not to.

Also check the “Voice Processing” section: if “Krisp” noise suppression is on, it can sometimes mute very quiet mics. Try turning it off temporarily to see if that fixes detection. If your mic is a wireless headset, make sure it is paired and selected as the default communication device in Windows Sound settings (Control Panel → Sound → Recording tab → right-click your mic → Set as Default Device and Default Communication Device).

Check System Sound Settings and Drivers

If Discord still shows no input, the problem may be at the OS level. Open your system sound settings and verify the mic is not disabled or muted.

  • Windows: Right-click the speaker icon → Sound settings → Input. Look at the “Test your microphone” bar. If it doesn’t move, the mic is not reaching Windows at all.
  • macOS: System Settings → Sound → Input. Select your mic and speak; the input level should rise.
  • If the mic is disabled, right-click it in the Recording tab (Windows) and choose “Enable.”
  • Check the mic’s physical mute switch (many headsets have one on the cable or earcup).
  • Update or reinstall the audio driver. In Windows, open Device Manager → Audio inputs and outputs → right-click your mic → Update driver. If that fails, uninstall the device and restart the PC—Windows will reinstall it.

For USB mics, try a different USB port (preferably directly on the motherboard, not a hub). For 3.5mm mics, ensure the plug is fully inserted into the pink jack. Laptops with combo jacks often need a TRRS headset, not a separate mic plug.

Clear Discord Cache and Reset Voice Settings

Corrupted cache files can cause erratic behavior, including error 3002. Resetting the cache is safe and does not delete your messages or servers.

  1. Close Discord completely (right-click the tray icon → Quit).
  2. Press Win+R, type %appdata%, and press Enter.
  3. Open the discord folder, then the Cache, Code Cache, and GPUCache subfolders, and delete everything inside them.
  4. Restart Discord. It will rebuild the cache.

If the error persists, reset Discord’s voice settings to default. In Voice & Video, scroll to the bottom and click “Reset Voice Settings.” This clears any bad input-device selection, sensitivity, or processing toggles. You will need to re-select your mic after, but it often resolves the error.

When the Problem Is a Third-Party App

Some applications take exclusive control of a microphone, preventing Discord from reading it. This includes voice changers, recording software (OBS, Audacity), and even some game overlays. If you use any such tool, close it completely and test Discord again. If the error disappears, the app was the culprit.

On Windows, you can also disable “Allow applications to take exclusive control of this device” for your mic:

  1. Right-click the speaker icon → Sound settings → More sound settings (or Control Panel → Sound).
  2. Go to the Recording tab, right-click your mic, and select Properties.
  3. On the Advanced tab, uncheck “Allow applications to take exclusive control of this device.”
  4. Click Apply and OK.

This is a common fix for error 3002 when the mic works in other apps but not Discord.

Frequently Asked Questions

Why does Discord say “No input detected” but my mic works in other apps?

This usually means Discord is not getting permission or is set to the wrong device. Check the OS microphone permission for Discord, then in Discord’s Voice & Video settings, manually select your mic from the Input Device dropdown. If it still fails, try resetting voice settings or disabling exclusive control in Windows sound properties.

Can error 3002 be caused by a broken mic?

Yes, but it is less common than permission or settings issues. Test the mic in another app (like the Windows voice recorder or a phone call). If it does not work there either, the mic or its cable/port is faulty. Try a different USB port or another device to confirm.

Does Discord error 3002 happen on mobile too?

Yes, the same error can appear on iOS and Android. The fix is the same: grant microphone permission in the OS settings for Discord, then check the in-app input device (usually under User Settings → Voice). On mobile, also make sure the app is not running in the background with the mic muted.

Will reinstalling Discord fix error 3002?

It can, but only if the issue is a corrupted installation. Before reinstalling, try clearing the cache and resetting voice settings. If you do reinstall, uninstall completely (including the %appdata%\discord folder on Windows) to remove all settings, then install fresh from the official site.

Why does error 3002 appear only in certain servers?

Error 3002 is a client-side mic detection issue, not a server permission. If it only happens in one server, you may have accidentally muted yourself in that server (the mic icon near the channel name). Check the server’s voice channel mute toggle. If other members cannot hear you but you see no error, it may be a different issue like server voice region or your output device.

Is error 3002 the same as “no route” or “RTC connecting”?

No. “No route” and “RTC connecting” are network-related errors that prevent you from joining a voice channel at all. Error 3002 means you are connected but your mic is not producing a signal. The fixes are different: network errors require checking your firewall, VPN, or router, while error 3002 is about audio input.

Still Stuck? Try the Web App or a Clean Boot

If none of the above worked, try the Discord web app (discord.com/app) in Chrome or Edge. If the mic works there, the desktop app has a deeper issue—reinstall it. If the web app also fails, the problem is at the OS or hardware level. A clean boot on Windows (msconfig → Services → hide all Microsoft services → Disable all, then restart) can isolate a background app that is interfering. Remember to re-enable services afterward.

In rare cases, a Windows update or a Discord update introduces a bug that causes error 3002 for a subset of users. Check Discord’s status page and your OS update history. If a recent update coincides with the error, rolling back the driver or waiting for a patch is the only reliable fix. As a last resort, try a different microphone entirely—if a second mic works, the first one is likely faulty at the hardware level.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →