The short answer
If your own voice returns, ask the other person to mute only their microphone and repeat the same short phrase. If that stops the return, inspect their playback/input path. If you still hear yourself after leaving the call, inspect local monitoring on your PC or headset.
Different symptom or still not fixed? Find the next check →Key facts
- Identify both people
- Whose voice is duplicated, and who hears it?
- Mic mute is the comparison
- Mute one participant’s microphone, not the entire output
- After leaving the call
- A remaining self-voice suggests inspecting local monitoring
Find your symptom
Start with your symptom. Skip steps that do not apply to your setup.
| What you see | What to check | Go to |
|---|---|---|
| A hears their own voice; muting B’s mic stops it | Have B compare headphones, then unmute and retest. | Step 2 |
| A still hears their own voice after leaving the call | Check A’s mic test and Windows/device monitoring. | Step 3 |
| B hears A twice, but A cannot hear the duplication | Compare another recipient and stop extra playback paths. | Step 4 |
| Self-voice occurs only during Discord Mic Test | Stop Testing; playback during that test is intentional. | Step 1 |
| The return appears with more participants | Compare the non-speaking participants’ mic mutes one at a time. | Step 1 |
Fixes, in order
Continue this issue
Private notes stay in this browser. Nothing is sent automatically. Back up important notes on My Page. PC settings are never changed by this site.
Step 1｜Mute one participant’s microphone at a time to trace the return
Your own returning voice can originate at someone else’s speakers and microphone.
Time: Compare one change at a time
- Open Discord User Settings → Voice & Video and stop Mic Test if it is running. The test deliberately plays your voice through the selected output; finish it before comparing a real call.
- Let A, the person hearing their own return, say a short phrase once, such as “Audio check, one, two, three.” Have B mute only their microphone using Discord’s mic icon, rather than the headphone/deafen control.
- Have A repeat the same phrase. If the return stops only while B is mic-muted, ask B to perform Step 2.
- With three or more participants, repeat one person at a time. If unclear, have everyone except A mute their mic, then unmute one at a time and repeat the phrase.
- If the return persists with the other microphones muted, have A leave the call and repeat the phrase. If still audible, use Step 3; if limited to calls/streams, use Step 4.
A mute comparison narrows the returning path but does not distinguish speaker pickup from a virtual-audio mix. Lower playback volume immediately if loud feedback occurs.
Results that did not fix the problem help the next reader too.
Step 2｜When muting one person helps, inspect that person’s playback
If A’s voice returns through B, B makes this comparison. A wearing headphones does not remove B’s speaker pickup.
Time: Compare one change at a time
- Have B stop PC speaker playback and use available earphones or headphones.
- In B’s Discord Voice & Video, select those headphones as Output Device and the actual microphone as Input Device.
- Have B unmute the microphone and A repeat the same phrase once. If A no longer hears the return, verify both people can converse with that setup.
- If unchanged, check whether another phone or PC in the room is also playing the call. If B uses a virtual mixer or loopback input, continue to Step 4.
Results that did not fix the problem help the next reader too.
Step 3｜If self-voice remains after leaving, inspect local monitoring
Windows, recording software and a headset/interface can each play your microphone back locally.
Time: Compare one change at a time
- Press Windows+R, enter mmsys.cpl and open the Sound dialog. Under Recording, select the microphone in use and open Properties.
- If a Listen tab offers Listen to this device, record its state, clear it and apply. Repeat the phrase to check whether the local return stops; restore an unhelpful change.
- If the control is absent or unhelpful, inspect the headset/interface’s sidetone or Direct Monitor feature. Use its own manual to compare it temporarily off, keeping the original setting recorded.
- Compare with recording/streaming software closed too. After improvement, return to Discord and separately confirm that you no longer hear the return and the other person still hears your microphone.
Monitoring can be intentional. Record needed settings before changing them; disabling local playback is different from disabling the microphone or muting its Discord input.
Results that did not fix the problem help the next reader too.
Step 4｜For duplicate voice, separate playback and virtual input
A recipient may hear both a call and a stream, or the same signal may enter a mixer twice. Merely having OBS open does not establish the cause.
Time: Compare one change at a time
- Have B, who hears the duplicate, keep the Discord call but stop watching a stream or using another call app one at a time. Have A repeat the same phrase and check whether call-only playback produces one copy.
- If only B hears two copies while another participant hears one, inspect B’s playback paths. If everyone hears A twice, compare A’s input path.
- Have A record the current Input Device in Voice & Video, select the physical microphone directly instead of a virtual cable/mixer, and compare with OBS/voice-changing software closed.
- If direct physical input helps, restore the removed software one at a time. At the step where duplication returns, inspect input, monitoring and loopback routing. If unchanged, restore the original setup and compare another existing mic if available.
Results that did not fix the problem help the next reader too.
Avoid
- Do not assume the person hearing their own voice is the person who must change settings.
- Do not use delay length alone to diagnose the cause or leave loud feedback playing while testing.
Important cautions
- Record whose voice returns to whom, whose mic mute stops it, whether it persists after leaving and whether direct physical input changes it.
- Include microphone/headset models, Discord input/output names and virtual-audio software when seeking help. Use willing participants and do not record private calls merely for this test.
FAQ
Is hearing myself during Mic Test abnormal?
The test intentionally returns your voice through the selected output. If Stop Testing ends it, that is expected. Finish the test before comparing an actual call.
Why does my voice return when I already use headphones?
Another participant’s speakers may feed your voice into their microphone. Compare their microphone mute, then their output and input path.
Can noise suppression or echo cancellation solve everything?
Processing may help, but a second playback device or duplicated route can remain. First narrow the return using mic mutes and headphones, then compare processing settings individually.
Will stopping my local monitor stop others hearing me?
Local Listen/sidetone monitoring is distinct from disabling the mic or muting Discord input. After changing it, verify both your local sound and the recipient’s hearing.
Sources
English adaptation of the existing Japanese guide with corresponding steps and official sources. Comparisons and example outcomes are editorial guidance, not measured results. Record original settings, change one condition at a time and leave comparisons you cannot perform marked as untested.
Discord: voice and video troubleshootingDiscord: mic-test playback and stopping the testFocusrite: direct/software monitoring and Windows Listen settingsDiscordJapanese version of this page