Discord cuts off words on Mac? Check input sensitivity before changing microphones

Documentation-based guide, sources reviewed 12 November 2026. No Discord call, microphone recording or hardware test was performed for this article.
Your friends hear most of a sentence, but the last few quiet words disappear. The microphone you wanted is still selected. Before reconnecting your headphones or buying another mic, inspect how Discord decides when to transmit your voice.
Discord's own documentation identifies sentence endings being cut off as a reason to compare automatic and manual input sensitivity. That gives you a specific setting to investigate, rather than a reason to reset every audio preference.
This guide is for Mac users whose voice is partly audible in Discord. If there is no input at all, start with device selection and permission instead. SoundBuddy is our product; the built-in Discord checks below do not require buying it.
First, name the symptom
Choose the description closest to what you actually hear:
| Observation | First question |
|---|---|
| Quiet endings disappear, but louder words arrive | Does the result change with Discord's input-sensitivity setting? |
| Your voice sounds different after headphones connect | Did either the Mac or Discord select a different microphone? |
| There is no voice at all | Is the intended input available, permitted and unmuted? |
| Words break up unpredictably throughout a sentence | Can you reproduce it in the app's test, or only in a call? |
These are starting points, not diagnoses. A device label cannot establish what someone else hears.
Keep the microphone choice steady
Open System Settings > Sound > Input and note the selected source. Apple's sound-input guide describes this selection separately from input volume. Use the guide's version selector if your Mac's interface differs.
Then open Discord's User Settings > Voice & Video and inspect its Input Device and Output Device. These controls are documented in Discord's troubleshooting guide. Write down an explicit device name or the displayed default choice, rather than assuming the two selectors agree.
If they disagree, resolve that first using our call-app microphone guide. For Discord in a browser, check the browser permission and selection guide if access is missing. Do not grant unrelated permissions to investigate an audio problem.
Once you have the intended source, leave the headphones connected, the microphone in the same position and input volume unchanged during the next comparison. Changing three things at once makes an apparent improvement difficult to explain.
Check the sentence in Discord's own test
On desktop or browser, go to the Voice section of Voice & Video, find Mic Test and select Let's Check. Speak a short, non-sensitive phrase and listen through your selected output. Select Stop Testing when finished. Discord's Mic Testing guide warns that testing while connected to a voice channel automatically mutes and deafens you until the test ends. Do this before joining a conversation you need to hear.
Try an ordinary sentence such as: “The blue notebook is beside the window.” Repeat it at your normal level, then with a naturally quieter ending. Do not shout, whisper unnaturally or turn up your headphones to force a result. Note which words disappear, if any.
This is a screening check. It does not prove that a remote listener receives the same result or isolate every processing stage. If a friend has offered to help, arrange a brief private comparison afterward and ask only whether the same ending arrived. No recording is necessary.
Compare input sensitivity, one setting at a time
Discord's Voice Input Modes guide describes automatic and manual sensitivity in Voice Activity mode. Record your original choice. If automatic sensitivity is on, compare it with a manual threshold that admits quiet speech but excludes ordinary background noise.
Repeat the same phrase without moving the mic. Check the silence between phrases too. Record missing words and unwanted room sound separately. Restore the original choice if the result is worse or unclear; avoid copying someone else's threshold number.
If you use Push to Talk, inspect its release delay instead. Discord documents that this controls the time before transmission ends after key release. Browser Push to Talk also requires the window to be focused.
Compare noise suppression separately
If the input remains steady and sensitivity did not explain the symptom, note the current Noise Suppression choice before comparing it. Discord's Krisp FAQ describes Krisp as background-noise filtering and acknowledges that voice quality can decline in a quiet environment with a good microphone.
Where the option is available, compare Krisp on and off with the same phrase, source and room. Restore the earlier choice if the comparison does not help. Do not switch sensitivity, suppression and input volume together.
An improved result in one room does not establish that suppression should always be disabled. Repeat your check if the environment changes. If the option is absent, record that instead of installing extra software or assuming your client supports it.
Keep a short comparison card
Copy this into a private note. Leave unknown results blank rather than filling in a likely explanation.
| Item | Your observation |
|---|---|
| Mac model and macOS version | |
| Discord desktop version, or browser and version | |
| Microphone and connection type | |
| Mac input / Discord input / Discord output | |
| Initial input mode, sensitivity and suppression | |
| Exact symptom and phrase | |
| One setting changed, original value and test value | |
| App-test result: improved, unchanged, worse or unclear | |
| Quiet words preserved? Unwanted room sound transmitted? | |
| Consenting listener's result, if checked | |
| Original setting restored, or new choice retained |
For example, “the final two words still disappear with manual sensitivity” is a useful unresolved result. “The microphone is broken” goes beyond what that comparison established.
Where SoundBuddy fits
SoundBuddy's Input Lock maintains a preferred macOS default microphone while SoundBuddy is open, with a chosen fallback when that device disconnects. Discord can use its own input selection. Input Lock does not set Discord's transmission threshold, replace Krisp or guarantee that every word reaches another person.
If the selected microphone changes when headphones reconnect, investigate that selection problem. If the selection stays correct while quiet words disappear, keep the Discord controls in view. The two symptoms need different evidence.
Stop with a result you can describe
If a controlled change helps, note the setting and check it before your next important call. If it does not, restore the earlier choice and keep the comparison card for Discord support. Remove private server names, messages and account details from any screenshots before sharing them.
Avoid starting with a full voice-settings reset: it discards the baseline you were trying to compare. A clean app test with a poor remote result is useful information, but it does not prove a network fault or rule out every local cause. Record both observations and continue through Discord's official troubleshooting guide for your client.
Next step: write down the actual input devices, then compare one sentence with one setting changed. Keep the result narrow enough that you can repeat it.