How to Fix Discord Error 3002 (No Microphone) – Windows, Mac & Linux [2026]

If you’re seeing a red banner inside Discord that says “It looks like Discord is not detecting any input from your mic,” you’re dealing with Discord Error 3002 — one of the most common microphone issues on the platform. The error doesn’t mean your mic is broken. It means Discord can see your microphone is connected, but it’s receiving zero audio from it. The cause is almost always a permissions block, a wrong input device, outdated drivers, or a software conflict — all of which are fixable without reinstalling your OS or buying new hardware. Here’s every working fix for Windows, Mac, and Linux in 2026.

What Is Discord Error 3002?

Discord Error 3002 is a microphone input detection error. It’s different from cases where your mic is completely missing — here, Discord recognizes the device but receives no audio signal from it, so your voice never transmits during calls or in voice channels. Discord uses a technology called WebRTC to handle voice communication, and any break in the path between your microphone, your operating system’s audio stack, and Discord’s voice service can trigger this error.

The red banner looks like this: “Well, it looks like Discord is not detecting any input from your mic. Let’s fix that! (Error: 3002)”

It can show up in the Discord desktop app on Windows, Mac, and Linux, as well as in the browser version on Chrome or Edge.

Fix 1: Select the Correct Input Device in Discord

The most common cause of Error 3002 in 2026 is Discord defaulting to the wrong microphone — especially if you have multiple audio devices connected (a webcam mic, a headset, a USB mic, and a built-in laptop mic can all appear at once). Discord doesn’t always pick the right one automatically.

1. Open Discord and click the gear icon next to your username to open User Settings.
2. In the left sidebar, click Voice & Video.
3. Under Input Device, click the dropdown and manually select your actual microphone.
4. Speak into your mic and watch the Input Volume bar below — if it moves and turns green, Discord is now detecting your voice.
5. Click Let’s Check under the Mic Test section to confirm audio is coming through correctly.

If the green bar moves after switching the input device, you’re done. If nothing happens regardless of which device you select, continue to the next fix.

Fix 2: Check Microphone Permissions (Windows)

Windows 10 and Windows 11 have privacy settings that control which apps can access your microphone. A Windows update can silently reset these permissions, which would explain why Discord suddenly shows Error 3002 even though everything worked fine before.

1. Press Windows + I to open Settings.
2. Go to Privacy & Security > Microphone.
3. Make sure Microphone access is toggled On.
4. Make sure Let apps access your microphone is also toggled On.
5. Scroll down and find Discord in the app list — make sure its toggle is On.
6. Close Settings and restart Discord.

Pro tip: If Discord is already enabled but the error persists, try toggling the microphone access Off, waiting 5 seconds, then turning it back On. This forces Windows to refresh the permission for Discord.

Fix 3: Check Microphone Permissions (Mac)

On macOS, Discord needs explicit permission to access the microphone through System Settings. If this was denied at any point — even accidentally — Discord will be completely blocked from receiving audio, which directly causes Error 3002.

1. Click the Apple menu and open System Settings (or System Preferences on older macOS versions).
2. Go to Privacy & Security > Microphone.
3. Find Discord in the list and make sure the toggle next to it is turned On.
4. If Discord isn’t in the list at all, open Discord and it should prompt you to grant microphone access. Accept the prompt.
5. Quit Discord fully (Command + Q) and reopen it.

Fix 4: Check Microphone Permissions (Linux)

On Linux, microphone access for Discord depends on your audio system — whether you’re using PulseAudio or PipeWire — and whether your desktop environment has any privacy controls active. Here’s what to check:

1. Open pavucontrol (PulseAudio Volume Control) from your applications menu or by running pavucontrol in the terminal.
2. Go to the Recording tab.
3. Start a voice call or open the Mic Test in Discord, then look for a Discord entry in the Recording tab. Make sure it’s connected to your actual microphone and not a null or monitor device.
4. If you’re using PipeWire, run pw-top in the terminal to see active audio streams and confirm Discord is routing to the correct input device.
5. If you’re on a GNOME desktop, check Settings > Privacy > Microphone and make sure microphone access is enabled.

On Flatpak installations of Discord on Linux, microphone access is additionally sandboxed. Run this command to grant mic access to the Flatpak version:

flatpak override --user --device=all com.discordapp.Discord

Fix 5: Raise the Input Volume and Unmute in System Settings

Even if the correct microphone is selected in Discord and permissions are allowed, Error 3002 can still appear if the microphone’s volume is set to zero at the operating system level. Discord reads from the OS audio stack — so if the mic is muted or at 0% in your system settings, Discord receives silence and throws the error.

On Windows:

1. Right-click the speaker icon in your taskbar and select Sounds.
2. Go to the Recording tab.
3. Right-click your microphone and select Set as Default Device.
4. Double-click the microphone to open its Properties.
5. Go to the Levels tab and drag the volume slider to 100. Make sure it’s not muted.
6. Click OK, then restart Discord.

On Mac:

1. Open System Settings > Sound.
2. Click the Input tab.
3. Select your microphone and make sure the Input Volume slider is not at zero.

Fix 6: Disable Noise Suppression and Third-Party Audio Software

Discord’s built-in noise suppression (powered by Krisp) can sometimes interfere with low-volume microphone inputs and block audio from being detected entirely. Third-party apps like VoiceMeeter, Realtek Audio Manager, NVIDIA RTX Voice, or OBS virtual audio devices can also grab exclusive control of the mic and cut Discord off.

1. Open Discord Settings > Voice & Video.
2. Scroll down to the Advanced section.
3. Set Noise Suppression to None.
4. Also disable Echo Cancellation and Noise Reduction temporarily to rule them out.
5. If you have VoiceMeeter, OBS, or any virtual audio router running, close them completely.
6. Restart Discord and test the microphone.

Disable Exclusive Mode on Windows (Important)

Windows allows apps to take “exclusive control” of a microphone, which locks other apps — including Discord — out. Disabling this setting is one of the most overlooked fixes for persistent Error 3002 cases:

1. Right-click the speaker icon in the taskbar > Sounds > Recording tab.
2. Double-click your microphone > go to the Advanced tab.
3. Uncheck “Allow applications to take exclusive control of this device.”
4. Click OK and restart Discord.

Fix 7: Reset Discord Voice Settings

If you’ve changed Discord’s voice settings before — adjusted audio subsystems, switched input modes, or tweaked advanced options — a bad saved configuration can cause Discord to fail at mic detection even when everything else is correct. Resetting the voice settings wipes that configuration back to default.

1. Open Discord Settings > Voice & Video.
2. Scroll all the way to the bottom of the page.
3. Click Reset Voice Settings.
4. Confirm the reset.
5. Restart Discord and test your microphone.

Fix 8: Clear the Discord Cache and Update Drivers

Corrupted Discord cache files can interfere with microphone detection by feeding the app bad configuration data. Clearing the cache forces Discord to rebuild fresh files from scratch.

Clear Discord Cache on Windows:

1. Fully close Discord (right-click the system tray icon and select Quit Discord).
2. Press Windows + R, type %appdata%\Discord, and press Enter.
3. Delete the Cache, Code Cache, and GPUCache folders.
4. Reopen Discord and log back in.

Clear Discord Cache on Mac:

1. Quit Discord completely.
2. Open Finder > Go > Go to Folder and type: ~/Library/Application Support/discord
3. Delete the Cache folder inside.
4. Reopen Discord.

Update Audio Drivers (Windows):

1. Right-click the Start button and open Device Manager.
2. Expand Sound, video and game controllers.
3. Right-click your audio device and select Update driver > Search automatically for drivers.
4. If Windows finds nothing, visit your PC manufacturer’s website (or your motherboard manufacturer’s site) and download the latest audio driver manually.
5. Restart your PC and test Discord.

Still Broken? Try These Additional Steps

If you’ve gone through every fix above and Discord still shows Error 3002, here are a few final options worth trying. First, check whether your mic works in a completely different app — like the Windows Voice Recorder, the Mac Voice Memos app, or any online mic tester. If it fails there too, the issue is with your hardware or system drivers, not Discord. Second, try using Discord in your browser (Chrome or Edge) instead of the desktop app — browser versions handle audio permissions differently and can help isolate where the problem is. If the browser version works but the desktop app doesn’t, reinstalling Discord is the next step. Finally, for USB microphones like the Blue Yeti or HyperX Quadcast, visit the manufacturer’s website and check for firmware updates or dedicated driver software that may be needed for full compatibility.

Frequently Asked Questions