Discord Microphone Not Working: Windows Test, Input Mode and Call Checks

Step 1｜Check whether Windows receives the same microphone

Start outside Discord so you know which layer needs attention.

Time: A few minutes; compare one change

1. Check the headset’s physical mute and detachable microphone connection. Reconnect an external USB/audio plug safely, and confirm which microphone you intend to use. Do not change several devices at once.
2. In Windows 11, open Settings → System → Sound → Input and select that microphone. Use its microphone test, speak a short harmless sentence and stop. Listen to a sample if your version offers playback.
3. On Windows 10, select the input under Settings → System → Sound and observe the microphone test indicator while speaking. Keep the selected device name in your record.
4. If input reacts, continue to STEP 2. Otherwise check input volume and compare a direct USB connection rather than a hub, another port, or another available microphone. Keep the comparison narrow.
5. If the device is absent, follow the PC or microphone maker’s detection guidance. If another microphone works, investigate the original connection/device; if neither works, also check access settings in STEP 2. Record the result instead of assuming hardware failure.

No Windows input can reflect selection, mute, access or connection. For Bluetooth-only failures, a wired/USB comparison can help without proving the cause.

Step 2｜Match microphone access, input and playback output

A silent test can also be an output problem.

Time: A few minutes; compare one change

1. Open Windows 11 Settings → Privacy & security → Microphone; on Windows 10 use Settings → Privacy → Microphone. On a managed PC, ask the administrator if access is restricted.
2. For a microphone you intend Discord to use, check Microphone access and the desktop-app access setting. Desktop Discord may not have an individual toggle in the app list. Browser use also needs permission for the actual Discord website.
3. Open Discord User Settings using the cogwheel, then Voice & Video and its voice controls. Choose the microphone that reacted in Windows by name instead of relying on Default. Check that input volume is not zero.
4. Select your current headphones as the output device. Start the Mic Test, say the same short sentence and check whether you hear the playback. Do not use private conversations as test material.
5. If input reacts but playback is silent, check headphones and output volume. If playback works, stop the test and continue to STEP 3. If only Windows works, fully exit/reopen Discord after the settings change and repeat once.

Discord’s official mic-test guide says a test during a call automatically mutes and deafens you. Stop it before asking a caller whether your voice is arriving.

Step 3｜Check mute, input mode and the speech threshold

Voice Activity and Push to Talk determine when audio is transmitted; sensitivity is not voice loudness.

Time: A few minutes; compare one change

1. Stop Mic Test and return to the call. Check your microphone/headphone icons and remove only a mute/deafen state you set yourself. A server-imposed restriction requires the administrator.
2. Check Input Mode in Voice & Video. For Push to Talk, hold the assigned key while speaking. If others hear you only while holding it, that is expected behavior.
3. If you want transmission without a key, choose Voice Activity. If automatic sensitivity cuts off quiet speech, record the current setting before comparing a manual threshold.
4. Compare the level in silence with quiet speech. Adjust the threshold so room noise does not trigger transmission but quiet words do. Use the actual indicator, not a universal numeric recommendation.
5. For illustration, noise around −60 dB and quiet speech around −40 dB might justify comparing a threshold between them. These are example values only. Ask a willing caller whether sentence endings arrive; readjust if background sound is continuously sent.
6. If the key works only when Discord is focused, compare key conflicts with game controls. Record whether this occurs only in an elevated game; consult the relevant official guidance rather than making administrator launch a default fix.

A sensitivity threshold does not increase the microphone’s actual loudness. Keep “too quiet”, “cutting out” and “no audio” separate in the support record.

Step 4｜Locate a channel or listener-specific restriction

Keep your working input settings while comparing the destination.

Time: A few minutes; compare one change

1. With a willing contact and an authorized test location, compare the same short sentence in a DM call and the affected server voice channel. Do not use another destination to bypass a restriction.
2. If the DM works but the channel does not, ask an administrator to check server mute and the effective Speak permission. Joining a voice channel does not guarantee permission to speak there.
3. If just one listener cannot hear you, compare another willing listener. Ask the affected person to check their individual mute and volume for your user, as well as their playback device.
4. If nobody hears you and the call is stuck connecting or disconnects, record that connection state. Repeated sensitivity changes are not a repair for an unresolved connection failure; use official connection support.

Step 5｜Compare the browser before a documented settings reset

Record settings so an unhelpful reset does not erase your troubleshooting history.

Time: A few minutes; compare one change

1. End the desktop call. Open discord.com/app in a supported browser and use the same input, allowing microphone access only for the intended site. Repeat the local test and, with consent, the short call.
2. If only the browser works, record desktop input/output devices, input mode, sensitivity and key assignments before changing them. Do not post private screenshots publicly.
3. Restart the desktop app to apply available updates. If it still fails, consider the documented Reset Voice and Video Settings control under the Debugging tab of Voice & Video. Placement can vary; do not reset unrelated account settings.
4. Reselect the intended microphone and output afterward. Test, stop the test, then compare the actual call. If unchanged, restore your recorded preferences and send official support the Windows/test/DM/channel/browser results without raw voice recordings.