Discord Microphone Not Working? Input Device, Permissions, and OS Fixes

Discord microphone not working is usually routing, not a dead headset. On desk tickets we see the wrong input device, OS mic privacy off, Voice Activity thresholds set like a fortress, or Windows exclusive mode locking the endpoint. Fix those before you nuke the Discord install.

Same diagnostic family as Zoom no microphone sound and broader Windows 11 no sound — prove the OS hears you, then prove Discord uses that device.

Symptom map

What happens	Likely cause	First check
Mic test flatlined	Wrong device / OS permission	Input device + privacy
Meter moves, friends hear nothing	Sensitivity / filters / server mute	Sensitivity + server status
Works in Notepad voice typing, not Discord	Discord-specific device selection	Voice & Video settings
Breaks when a game launches	Exclusive mode	Disable exclusive mode
Bluetooth robotic mic	Hands-Free profile	Wired test / BT stereo vs HFP
All apps silent	Driver / service failure	OS audio repair

Webcam-only failures are a different stack (webcam not working on Windows); do not reinstall camera drivers for a mic ticket unless the endpoint is a combo USB UVC device that enumerates both.

1. Set Discord’s input explicitly

Discord → User Settings → Voice & Video:

1. Input Device = your headset/mic (not “Default” if Default is wrong)
2. Speak and watch the Mic Test
3. Temporarily set Output to the same headset so you can hear sidetone/test

If the list is empty, Discord cannot see OS endpoints — jump to OS permissions and drivers.

2. Unlock OS microphone privacy

Windows 11: Settings → Privacy & security → Microphone → Microphone access on, and Discord allowed.
macOS: System Settings → Privacy & Security → Microphone → enable Discord; restart Discord after granting.

After OS updates, privacy toggles silently reset more often than vendors admit.

3. Voice Activity, PTT, and processing

Still in Voice & Video:

• Lower Input Sensitivity or uncheck automatic sensitivity so quiet mics pass
• Try Push to Talk with a known key to rule out gating
• Disable Noise Suppression / Echo Cancellation / Automatic Gain briefly for a clean test
• Turn off Debug Logging experiments you do not need

Friends “hearing typing but not voice” is almost always a gate or PTT bind issue, not magnetism in the cable.

4. Fix Windows input defaults

1. Settings → System → Sound → Input → choose the correct mic
2. Device properties → disable audio enhancements for testing
3. Additional device properties → Allow applications to take exclusive control → off
4. Confirm the mic is not muted on a hardware boom-arm mute or inline switch

Bluetooth headsets that flip to Hands-Free when Discord requests mic access need the Bluetooth headphones on Windows treatment — or a cheap USB mic for Discord duty.

If the whole PC lost audio after an update, stabilize that first; Discord cannot outroute a broken stack. Black screens and stuck updates also interrupt USB audio enumeration (Windows 11 black screen).

5. Discord cache and clean reinstall (last software steps)

Only after OS routing works in Voice Recorder / another call app:

1. Fully quit Discord (tray too)
2. Clear %AppData%\discord\Cache and Code Cache (leave Local Storage if you want to keep login when possible)
3. Reinstall from Discord’s site if the app package itself is corrupted

Admin overlays and “hardware acceleration” toggles can be tested next; they are more often FPS cures than mic cures.

6. Hardware prove-out

• Try a second known-good USB headset
• Avoid unpowered hubs
• On desktops, verify the rear case mic jack is actually connected to the header
• Rule out Discord server mute / category permissions with a private DM call

Security software that blocks av devices after a scareware event deserves a look if everything audio-related died the same day (remove malware on Windows).

Do / Don’t

Do	Don’t
Match Discord input to the live OS mic	Assume “Default” is correct
Allow OS microphone privacy	Reinstall Windows for one app’s mute
Test with filters off once	Max noise suppression on a quiet dynamic mic
Disable exclusive mode for call apps	Ignore a glowing hardware mute LED
Prove another app can record	Blame Discord when Audacity is also silent

Quick channel permissions check

Before deep OS work, confirm social/admin state:

• You are not server muted or deafened (server shield icons)
• The voice channel allows Speak for your role
• You are not in a stage channel with invite-only speak
• Discord overlay is not binding a mute key you accidentally tap

Join a private DM voice call with a second account or a friend. If DM works but a guild fails, it is permissions — not your Realtek driver.

Packetizer and QoS notes

Discord voice uses UDP. Aggressive “game boosters,” QoS packs, and some router Smart QoS modes drop or delay that traffic while HTTPS pages still load. Symptoms: you sound robotic, cut out, or fail to connect to voice while text chat works.

Mitigations to try:

• Disable VPN UDP blocking / switch VPN protocol
• Pause network “optimizers”
• Test phone hotspot voice

If hotspot voice is perfect, your PC audio stack is fine and the LAN path is guilty.

Observability inside Discord

Voice & Video → Mic Test is mandatory. Also open the voice connected screen’s Call Stats / debugging views when available to see if Discord is capturing frames. No capture frames + OS privacy on = wrong device. Capture frames + friends hear silence = processing gate, mute state, or their output — have them check their own headphones before you rebuild Windows Audio.

Bottom line

Discord mic failures are device selection + permissions + gating until an OS-wide recording test fails. Set the input explicitly, allow privacy access, calm Voice Activity, and fix Windows exclusive mode. Reach for drivers and hardware only when every app is mute — that is the technician order that closes tickets fast.