Vipin PG 
When Discord hits you with error code 3002, it’s usually telling you one thing: your mic is plugged in, but Discord isn’t actually hearing anything from it. This can happen even when your mic works perfectly fine everywhere else in Windows or macOS, which is exactly why this error feels so frustrating.
Here’s the thing though — 3002 is actually one of the simpler Discord voice errors to track down once you stop thinking of it as some mysterious app crash. Most of the time, you’re dealing with a muted input, blocked mic permissions, Discord listening to the wrong device, or the desktop client just being stuck. Work through the right checks and you can typically sort it out pretty quickly.
What error code 3002 is really telling you
According to Discord’s audio error guide, error 3002 means “Microphone not picking up sound.” That’s important because it tells you this isn’t the same kind of problem as connection drops, server outages, or login issues. Discord can see that a microphone exists somewhere in the chain — it’s just not getting any actual voice data from it.
So you’re looking at one of four culprits: your headset or mic is muted somewhere, your operating system is blocking access, Discord is pointed at the wrong input device, or the desktop app itself has gotten stuck. And if you’re running virtual audio tools, voice changers, or multiple USB headsets, the chances of a device mismatch go up even more. If you want to double-check how Discord’s input selection actually works, this Discord input setup guide walks through the exact settings path.
Start with these checks before you change anything major
Data last verified: April 2026
| What you notice | Most likely cause | What to do first | Where to check |
|---|---|---|---|
| Discord shows 3002 and nobody can hear you | Mic muted or input level too low | Unmute the headset or inline switch and raise input volume | Headset controls and OS sound settings |
| Mic works in another app but not Discord desktop | Discord is using the wrong input device | Select the correct microphone manually in Voice & Video | Discord Settings > Voice & Video |
| Mic fails in Discord and browser apps too | OS microphone permission is blocked | Re-enable microphone access for apps | Windows Privacy & Security or macOS Privacy & Security |
| Browser Discord works but desktop Discord does not | Desktop client glitch or corrupted local state | Fully quit Discord and relaunch, then reinstall if needed | Task Manager / Activity Monitor |
| Input meter moves sometimes, then drops to zero | Driver, audio utility, or virtual device conflict | Disable extra audio tools and test with one mic only | Device Manager / audio utility / background apps |
The fix path that works most of the time
1. Make sure your mic isn’t muted outside Discord
I know this sounds basic, but it catches way more 3002 cases than you’d think. Check the physical mute switch on your headset, any inline mute button on the cable, and the microphone level in your OS sound settings. Windows users have also run into situations where the input volume mysteriously dropped to zero after an update or device swap, which makes Discord think the mic is there but completely silent.
2. Double-check microphone permissions at the OS level
On Windows, Microsoft’s microphone permission steps say you need to verify both the main microphone access toggle and individual app access under Privacy & Security. If desktop apps are blocked at that level, Discord will fail even though your mic works fine elsewhere. One extra step that’s helped people: turn microphone access off, wait a few seconds, then flip it back on before you reopen Discord.
On Mac, Apple’s Mac microphone controls live under System Settings > Privacy & Security > Microphone. If Discord isn’t showing up in that list or it’s toggled off, the app won’t be able to capture any input. Worth checking if you’re testing Discord in a browser too, because the browser itself needs mic permission separately.
3. Manually pick the right input device in Discord
Open Discord, head to Settings > Voice & Video, and stop using “Default” if you’ve got more than one mic path available. Choose the exact device you want to use. USB headsets, webcam mics, laptop mic arrays, Bluetooth headsets, and virtual devices from tools like Voicemod or similar audio software can all show up at once, and Discord doesn’t always pick the one you’re expecting.
This is where mixed-audio setups tend to break down. And if you sometimes use a browser-based workflow, it’s also worth reviewing your browser permission settings so Chrome, Edge, or Firefox aren’t still pointed at an old device.
4. Run Discord’s mic test before you join a call
Stay in Voice & Video and use Discord’s built-in input test. Watch whether the input meter moves when you talk. If it never moves, the problem is still happening below the app layer. If it does move but other people still can’t hear you, you’re probably dealing with sensitivity settings, push-to-talk config, or a channel-specific permission issue instead of 3002.
5. Test the browser version of Discord
This is one of the cleanest ways to isolate the problem. Sign into Discord in your browser and test the same mic there. If the browser version works but the desktop app still throws 3002, your mic and OS permissions are probably fine — the desktop client is what’s broken. That usually points to a stuck process, corrupted cached state, or a bad device handoff after an update.
6. Fully quit Discord, then reopen it
Don’t just close the window. Actually quit Discord from the system tray on Windows or the menu bar on macOS, then confirm the process is gone in Task Manager or Activity Monitor. Open it fresh and test again. Community reports from recent Discord updates show this can clear device-detection problems that survive a normal window close.
7. Strip out extra audio layers for one test
If you’re running voice changers, virtual cables, motherboard audio utilities, streaming overlays, or vendor headset software, disable them temporarily and test with one simple microphone path. This single change often tells you whether the issue is Discord or an audio-routing conflict caused by third-party software.
Platform-specific fixes
Windows
- Go to Settings > Privacy & Security > Microphone.
- Turn on Microphone access.
- Turn on Let apps access your microphone.
- Make sure Discord, or desktop app access in general, isn’t blocked.
- Go to System > Sound > Input and confirm the right mic is selected and the input volume isn’t sitting near zero.
- Open Discord and manually select that same mic in Voice & Video.
If Windows privacy settings keep breaking mic access across multiple apps, it’s also worth reviewing your broader app permission habits so Discord isn’t getting caught in a blanket privacy block.
macOS
- Open System Settings > Privacy & Security > Microphone.
- Make sure Discord is allowed to use the microphone.
- Open System Settings > Sound > Input and confirm the right device is active.
- Reopen Discord after you change permissions.
- If you’re using Discord in a browser, confirm Safari, Chrome, or Edge also has microphone permission.
Browser Discord
If the web version also fails, clear the browser’s site permission for Discord and allow mic access again when it prompts you. Browser-side audio problems usually come from stored site permissions, stale cached state, or the browser remembering an older mic. If you need a quick cleanup path, TechRounder’s cache clearing guide is helpful for the browser side of things.
When reinstalling Discord actually makes sense
Reinstalling shouldn’t be your first move. It’s only worth doing after you’ve confirmed three things: the mic works in another app, OS permission is enabled, and the browser version of Discord works. At that point, reinstalling the desktop app makes sense because you’re fixing a client-specific problem instead of just guessing.
Before you reinstall, fully quit Discord and kill any background processes. After reinstalling, open Discord and set the input device manually instead of leaving it on Default. That keeps it from pulling the same bad device choice back in on first launch.
What to do next
If 3002 keeps coming back after all this, stop treating it like a Discord-only problem and test your mic in another voice app right away. If the mic fails there too, you’re looking at a system, driver, or hardware issue. If it only fails in Discord desktop, keep the browser version as your temporary backup and watch for client updates from Discord.
