How to Set Up Push to Talk in Discord

Push-to-talk has no default keybinding in Discord — it must be manually configured under User Settings > Voice & Video before it does anything at all, distinguishing it from most of the other voice-related shortcuts covered on this page, which come with sensible defaults already assigned. **What push-to-talk actually changes**: by default, Discord's Voice Activity mode transmits your microphone audio automatically whenever it detects sound above a certain sensitivity threshold, continuously, without requiring any key to be held down. Switching to push-to-talk mode changes this fundamentally — your microphone only transmits while a specifically assigned key or button is physically held down, staying silent the rest of the time regardless of background noise or sound picked up by the microphone. **Common key choices**: because there's no universal default, users commonly bind push-to-talk to a key that's comfortably reachable without disrupting other activity — the backtick key (`) is a frequent choice on a standard keyboard since it sits in an easily reachable corner rarely used for anything else, and many gaming mice and keyboards include a dedicated spare button specifically marketed toward this exact binding, letting a thumb or pinky trigger it without taking a hand fully off other controls during active gameplay. **Why this matters disproportionately for gaming-oriented users**: Discord's substantial base of gaming communities relies on push-to-talk considerably more heavily than its more general-purpose or professional-community users, since Voice Activity mode's automatic sound-triggered transmission can pick up keyboard clatter, controller sounds, or general background noise during intense gameplay and broadcast it to the whole call — push-to-talk gives explicit, deliberate control over exactly when the microphone transmits, avoiding that unwanted noise entirely. **Adjusting sensitivity for Voice Activity mode instead**: for anyone who prefers not to use push-to-talk at all, Discord's Voice Activity mode includes an adjustable sensitivity slider that controls how much sound is required before the microphone activates automatically — raising this threshold reduces false triggers from quiet background noise without requiring a manually held key, a middle-ground option between the two extremes of always-on transmission and fully manual push-to-talk. **Related shortcuts**: Ctrl+Shift+M toggles a persistent mute state independent of whichever transmission mode (Voice Activity or push-to-talk) is currently configured — even with push-to-talk enabled, toggling the separate mute shortcut still fully silences the microphone regardless of whether the push-to-talk key is being held. **Mistake to avoid**: binding push-to-talk to a key that's already used by another frequently-run application, particularly a game, which can cause the two applications to conflict or for Discord to unreliably detect the key press when the other application has captured it first — checking for binding conflicts with whatever else runs alongside Discord regularly, especially games, avoids the frustrating experience of a push-to-talk key that seems to work only inconsistently. **Configuring a release delay**: alongside the basic push-to-talk binding, Discord's Voice & Video settings also offer a small configurable delay between releasing the key and the microphone actually cutting off, useful for someone whose natural speech has brief pauses that would otherwise get clipped by an instantaneous cutoff — a short release delay smooths this out without requiring the key to be held through every brief pause in speech. **Using push-to-talk with a mouse button versus a keyboard key**: binding push-to-talk to a mouse button (common on gaming mice with programmable side buttons) rather than a keyboard key can be genuinely more ergonomic for someone whose hands are occupied with a controller or otherwise away from the keyboard during the activity they're voice-chatting about — the underlying mechanic is identical regardless of which physical input is bound, since Discord doesn't distinguish between keyboard and mouse bindings for this specific setting. **Global versus Discord-focused push-to-talk**: like the mute and deafen shortcuts covered elsewhere on this page, push-to-talk can be configured to register globally (working even while Discord isn't the focused application) under the same Keybinds settings section, which is essential for its most common actual use case — transmitting voice while a game, not Discord itself, has active window focus. **Related shortcuts**: Ctrl+Shift+M's persistent mute toggle remains fully independent of and compatible with push-to-talk mode — even with push-to-talk configured and actively in use, toggling mute separately still fully silences the microphone regardless of whether the push-to-talk key happens to be held down at that moment.