The two-minute Discord check
Discord problems fall into two piles, and they need opposite fixes. The first pile is nothing arrives: your friends hear silence, the green ring never appears around your avatar. The second is something arrives and it is bad: you are quiet, robotic, cutting out, or accompanied by a fan. Playing a clip back on this page sorts them in about ninety seconds, because it removes Discord from the chain entirely.
If the recorder above captures your voice and plays it back cleanly, your microphone, your cable, your operating system and your browser are all fine. Whatever is wrong is inside the Discord client, and there are only about six settings it can be. If the recorder captures nothing, stop reading about Discord — the problem is upstream, and the Windows 11 microphone page takes it from there.
Every microphone control in Discord, and what it maps to
The path is User Settings (the cogwheel in the lower-left corner) → Voice & Video → the Voice section. The table lists each control by the name Discord’s own documentation uses, and — where one exists — the browser constraint that does the equivalent job, so you can reproduce the setting on this page before you change it in the client.
| Control | Where | What it does | Browser equivalent |
|---|---|---|---|
| Input Device | Voice & Video → Voice | Chooses which microphone Discord opens. | deviceId |
| Input Volume | Voice & Video → Voice | Scales the captured signal before it is sent. | none |
| Mic Test → Let’s Check | Voice & Video → Voice | Plays your voice back through the selected output device. Discord’s own article notes it is desktop and browser only, and that running it while connected to a voice channel mutes and deafens you until the test ends. | none |
| Input Mode: Voice Activity or Push to Talk | Voice & Video → Voice | Decides whether the microphone opens on sound or on a key. Silence in a call with a working mic is very often this. | none |
| Noise Suppression | Voice & Video → Voice | Discord’s troubleshooting guide names this as Krisp noise suppression and lists disabling it as an advanced step when audio quality is poor. | noiseSuppression |
| Audio Subsystem: Standard or Legacy | Voice & Video, at the bottom | Switches the capture backend. Both Discord articles reach for this when a microphone is not detected at all. | none |
| Reset Voice and Video Settings | Voice & Video → Debugging | Puts every control above back to default in one action. | none |
Silence, in order of likelihood
1. You are muted in a way you did not do
Discord’s guide puts this first for a reason. A slash through the mic or headset icon means voice is disabled, and a server administrator can apply that at the server level — in which case no amount of device fiddling will help and you need an admin to lift it. Before that, check the channel permissions: Connect lets you join a voice channel and Speak is a separate permission that enables your microphone in it. A role can grant one and withhold the other.
2. Input Mode is Push to Talk
The single most common self-inflicted silence. Voice Activity opens the microphone when you make noise; Push to Talk opens it only while a key is held. Someone who set a keybind six months ago and then rebound that key in a game will be inaudible with a perfectly working microphone. Discord’s troubleshooting guide lists verifying the Input Mode before it lists anything about devices.
3. The wrong Input Device
Laptops make this easy: the lid array and a headset boom both appear, and Windows changes the default when you plug something in. Use the Input device tab on this page to see the exact device names your browser reports, then pick the matching entry in Discord’s Input Device dropdown. The names are the same because they come from the same operating system.
4. Discord cannot see the device at all
If the dropdown is empty or the device is missing while this page lists it, that is the case for the Audio Subsystem switch at the bottom of Voice & Video. Both Discord articles that deal with a missing microphone end up there, and the accompanying advice is to disable Quality of Service high packet priority at the same time.
Bad audio, and the setting behind each symptom
- The first word of every sentence is missing. Voice Activity’s threshold is set above your normal speech, so the gate opens late. Speak up, move closer, or lower the sensitivity.
- You sound underwater or clipped when quiet. Noise suppression. Toggle it here to hear the same effect, then turn Discord’s off.
- Your volume swells and fades. Gain control chasing a changing room. Turn the automatic gain switch off on this page — if the swelling stops, that is your culprit.
- Everyone hears themselves echoing back through you. You are on speakers with echo cancellation off or overwhelmed. A headset ends it at the source, because your speakers stop feeding the microphone at all; the headset mic test checks that the headset is the device actually in use.
- You are simply too quiet. Raise the gain at the device before you touch Input Volume in the client — why that order matters.
A headset Discord could not find
A common shape, and one this page resolves quickly. Someone plugs in a USB headset, joins a voice channel and is inaudible. On this page they press start, the waveform moves, the recorder plays their voice back clearly, and the Input device tab lists the headset with a groupId shared by its earpieces. That is proof the whole chain up to the browser works.
So the fault is inside Discord, and the table above narrows it: device selected but silent points at Input Mode or a server mute; device absent from the dropdown points at the Audio Subsystem switch. Neither of those would ever have been found by unplugging the headset and trying another cable, which is what most of an hour usually goes on.