In-game voice chat: teammates hear your own voice — telling sidetone, crosstalk and echo cancellation apart

Key takeaways: When teammates hear your own voice back in game voice chat, the fault is a loop, not a broken microphone: sound from your speakers, a monitoring switch, or a second voice app is being picked up again and sent back. Find who hears the echo, switch to headphones, then turn monitoring and echo cancellation off one at a time.
You say one sentence in game voice chat, and a moment later you hear it again — not from your own headphones, but from a teammate, who hears your words twice: once live, and once delayed, or mixed in with the game sound coming back through their speakers. Or a teammate tells you that every time you speak, your voice comes back to them, quieter and a fraction of a second late, sometimes with the game's music and effects riding along with it. That combination — your own voice, heard by someone else, overlapping or delayed — is the whole problem this guide addresses, and the combination itself is the first piece of evidence.
The instinct is to blame the microphone, to buy a new headset, or to turn the microphone volume down and hope the problem goes away. All three are premature. An echo is a loop, not a broken part: sound is leaving somewhere it should not leave, being picked up again, and being sent back around the same path a second time. Replacing the microphone does not stop sound leaking from a speaker into a microphone, and turning the gain down only makes the echo quieter while also making your real voice quieter. The first job is to define the shape precisely, then to find who hears the echo, then to test the speaker path, the monitoring path, the echo-cancellation path, the gain path, and the dual-application path, one change at a time.
This guide covers only a narrow shape, and four conditions must all be present. First, the echo happens in live voice chat: in-game voice, Discord, or a platform voice service. The point is that it is live, two-way speech, not a recorded file. An echo heard only when playing back a recording is a recording problem, and it belongs to a different guide. Second, a teammate hears your voice back: you speak, and the teammate hears your words overlapping or delayed. If only you hear your own voice in your own headphones, and no teammate hears it, that is sidetone or monitoring — a design feature of many headsets, not this guide's shape — and the steps below do not apply in the same way. Third, the microphone itself works normally: the Windows microphone test meter moves when you speak, and teammates can hear you clearly when there is no echo. A microphone that picks up nothing at all is a different shape, the input-silence shape, where the fault is in the input path rather than in a loop. Fourth, the game sound itself is normal: you hear the game effects, the music, and your teammates' voices. A game with no sound at all is a playback-chain problem, not this guide's shape.
Sidetone is not an echo
The first distinction to make is between hearing yourself and being heard twice by someone else. Sidetone is the small amount of your own voice that many headsets deliberately feed back into your ears so that you know you are speaking and do not shout. It is a design choice, not a fault: it is there so that your own voice does not sound muffled or absent while you wear sealed headphones. Monitoring is similar in purpose but different in scope. "Listen to this device" in Windows, an in-game monitoring switch, or a monitoring option in Discord takes the microphone signal and sends it to the speakers or headphones in real time, so the speaker can hear themselves. Used on its own, with headphones, monitoring is usually harmless. Used while speakers are on, or used twice at once, it becomes a loop.
The difference matters because the fix is different. Sidetone heard only by you needs no fix at all, and in many headsets it can be turned down or off in the manufacturer's software if it is distracting. An echo heard by a teammate needs the loop to be found and broken. The diagnostic question that separates them is simple, and it should be asked before anything is changed: who hears the echo? If the answer is "only me, in my own headphones," stop and check the sidetone and monitoring settings on your own machine. If the answer is "my teammate hears my voice back," your machine is the source, and the rest of this guide applies. If the answer is "I hear my teammate's voice back," the source is on their side, not yours, and the same tests need to be run on their machine instead.
How the sound gets around the loop: six layers
An echo needs three things: a sound source, a path back into the microphone, and a second transmission of that picked-up sound to the other person. Every layer in this guide is one version of that path.
1. Speaker leakage: acoustic crosstalk
Game sound comes out of the speakers, travels through the air, and is picked up by the microphone, which sends it back into the voice chat along with your voice. The teammate then hears the game sound mixed with your voice, and, if the timing lines up, your own words a second time. The louder the speakers, the closer the microphone is to the speakers, and the higher the microphone gain, the stronger the leakage. This layer has a clear signature: the echo follows the game sound. When the game is quiet, there is no echo; when the game gets loud, the echo gets loud. A teammate who hears game music and effects coming from your side, even when you are not speaking, is hearing speaker leakage.
The output device matters here, and it must be asked about explicitly, not assumed. Game sound can come out of desktop speakers, a television, or a soundbar connected over HDMI, and each of those is a speaker as far as the microphone is concerned. A television in particular is easy to miss: the player is wearing a headset for voice, but the game sound is still going to the television speakers, and the microphone is picking the television up. The diagnostic question is not only "headphones or speakers?" but "where does the sound actually come out?" — and the answer has to be checked in Windows and in the game, not guessed.
2. The monitoring loop: electronic crosstalk
Monitoring takes the microphone signal and sends it straight to the output. If that output is a speaker, the microphone picks it up again, and the cycle repeats: microphone to speaker, speaker to microphone, microphone to speaker again. Unlike speaker leakage, this loop does not need air at all. It can happen with headphones on, because the loop is electronic: the monitored signal is sent to the headphones, and if the monitoring path is doubled — for example, Windows "Listen to this device" and the game's own monitoring both turned on — the signal can be fed back into the voice stream a second time. The signature of this layer is that the echo survives the switch to headphones. Speaker leakage almost disappears on headphones, because the sound no longer travels through the room; a monitoring loop does not, because it never travelled through the room in the first place.
There are three places monitoring can be turned on, and each must be checked separately: the Windows Sound settings, under the microphone's Listen tab, where "Listen to this device" sends the microphone to the selected playback device; the game's own voice settings, where a monitoring or sidetone option may be present; and Discord or the platform voice application, where a monitoring or input-monitoring option may be present. Any one of them can create the loop, and two of them together make it worse.
3. Echo cancellation: missing, off, or overwhelmed
Echo cancellation, usually shortened to AEC, is the software that is supposed to prevent exactly this problem. Its principle is straightforward: the system knows what sound it is sending to the speakers, so it uses that output signal as a reference and subtracts the matching part from what the microphone picks up. If the microphone hears the game sound coming from the speakers, AEC recognises it as the same sound it just sent out and removes it before the voice is transmitted.
AEC is not present in every combination, and it is not always on. Some in-game voice systems have no echo cancellation at all. Some have it as a setting that must be turned on by hand. Discord and some platform voice services have their own echo cancellation, which may be on by default or may need to be enabled in the voice settings. Windows also has audio processing that can include echo cancellation on some devices, depending on the driver. The reader must check each application in use, not assume that turning it on in one place covers the others.
AEC is also not unlimited, and this must be stated plainly, because the most common mistake in this shape is to treat it as a cure-all. AEC cannot remove leakage that is much louder than the voice itself, because the subtraction is never perfect and a loud leaked signal leaves a residue. It cannot cope well with long delays between the speaker output and the microphone pickup, and it cannot cope with two monitoring loops running at once, because the reference signal no longer matches what the microphone is actually hearing. An echo that remains after AEC is turned on is therefore not proof that the setting is wrong. It is evidence in its own right: it points at leakage that is too loud for AEC to remove, or at a second loop that AEC was never designed to cancel. Turning AEC on and off, and writing down the result each time, is a test, not a repair.
4. Microphone gain and open microphone
Microphone gain decides how much sound the microphone picks up, including sound that is not your voice. With the gain set high, the microphone hears the room: the speakers, the keyboard, the fan, and the echo of your own voice off the walls. With open-microphone mode, the microphone is live the whole time, so any sound in the room is transmitted the moment it happens. Push-to-talk breaks this path, because the microphone only transmits while the key is held, but it is a comparison test, not a repair: it proves that the echo follows the microphone being open, and it does not fix the underlying loop. If the echo follows the gain — quieter when the gain is lowered, louder when it is raised — the gain and open-microphone layer is involved. If the echo does not change at all when the gain is lowered, that layer is not the main cause, and the fault sits elsewhere. Lowering the gain too far is a trade-off, not a fix: the echo gets quieter, but so does your voice, and teammates will then struggle to hear you at all.
5. Television and soundbar output
Game sound sent over HDMI to a television or a soundbar follows the same speaker-leakage mechanism as desktop speakers, but it is easier to miss, because the player may think of the television as a screen rather than as a speaker. The microphone picks up the television sound, sends it back, and the teammate hears the game twice. The diagnostic point is the same as in the speaker layer, but the question must be asked in full: which device is producing the sound — headphones, desktop speakers, television speakers, or a soundbar? The answer decides which output has to be turned down or switched. If the game sound is going to the television while voice goes to the headset, the two paths are split, and the television path is the one leaking.
6. Dual monitoring and dual sending
Two voice applications can be running at once: the game's own voice chat and Discord, for example, both transmitting the same microphone. Each may have its own monitoring and its own echo cancellation, and the two loops stack: the microphone signal is monitored twice, sent twice, and echo-cancelled — if at all — against a reference that no longer matches either path. The signature of this layer is that the echo appears only when both applications are running together. Either one on its own is clean; the two together produce the echo. The test is to stop one application at a time and ask the teammate after each stop. Whichever stop makes the echo disappear identifies the combination that creates it.
The six suspect layers
| Layer | What it means | Decisive comparison |
|---|---|---|
| Speaker leakage | Game sound from speakers, television, or soundbar picked up by the microphone through the air | Headphones versus speakers comparison |
| Monitoring loop | "Listen to this device", in-game monitoring, or Discord monitoring feeding the microphone back to the output | Monitoring switches off one at a time |
| Echo cancellation | AEC missing, off, or overwhelmed by loud leakage or a second loop | AEC on and off comparison in each application |
| Gain and open microphone | High gain and always-on microphone transmitting room sound continuously | Gain lowered, and push-to-talk comparison |
| Television and soundbar output | Game sound leaving through a television or soundbar instead of headphones | Output-device check: where the sound actually comes out |
| Dual monitoring and dual sending | Game voice and Discord, or two voice applications, both transmitting and monitoring the same microphone | One application stopped at a time |
Each layer has its own comparison, and no single comparison covers all six. The order in the six steps below is the order that wastes the least time.
Six diagnostic steps
Step 1 — Find the direction
Before changing anything, ask the teammate two questions and write the answers down. First: "The echo you hear — is it my voice, or the game sound?" Second: "Do you hear it, or do I hear it too?" If the teammate hears your voice back, your side is the source, and the rest of the steps apply to your machine. If you also hear your own voice, check your own sidetone and monitoring first, because the loop may be on your side in a different form. If you hear the teammate's voice back, the source is on their side, and the same steps need to be run there. This step proves nothing by itself, but if the direction is wrong, every test after it is aimed at the wrong machine.
Step 2 — Compare headphones with speakers
Switch from speakers to headphones, and ask the teammate whether the echo is still there. If the echo disappears the moment the headphones go on, the fault is in the speaker-leakage layer: game sound was travelling through the air from the speakers into the microphone, and the headphones have broken that path. The follow-up is to keep the game sound on the headphones, or to turn the speakers down, and to check whether the game sound is also going to a television or soundbar that is still on. If the echo is still there with headphones on, speaker leakage is not the main cause, and the fault sits in the monitoring or echo-cancellation layer: move to Step 3. Headphones are a comparison test, not a repair in themselves — they prove where the sound is travelling, and the real handling is to remove the path that should not exist.
Step 3 — Switch monitoring off, one switch at a time
Turn off "Listen to this device" in the Windows microphone properties, then ask the teammate. If the echo disappears, that switch was the loop. If it is still there, turn off the in-game monitoring option, and ask again. Then turn off monitoring in Discord or the platform voice application, and ask again. Only one switch should be changed at a time, and the teammate should be asked after each change, because two monitoring switches together can hide each other: turning one off may leave the echo in place while the second is still running, and the reader who changes both at once will never know which one was responsible. If all three are off and the echo is gone, the fault was in the monitoring layer. If all three are off and the echo remains, move to Step 4.
Step 4 — Compare echo cancellation on and off
In Discord or the platform voice application, and in the game if it has its own setting, try echo cancellation on, then off, and ask the teammate after each change. Write down both results. If the echo disappears with AEC on, the fault was that AEC was off, and it can be left on. If the echo is still there with AEC on, that result is itself evidence: the leakage may be too loud for AEC to remove, or there may be a second loop running, and the next step is to lower the speaker volume and re-check the monitoring switches, rather than assuming AEC is broken. AEC on is not a guarantee, and an echo that survives it must not be written off as a settings error.
Step 5 — Compare gain and push-to-talk
Lower the microphone gain by one step, and ask the teammate whether the echo got quieter. Then switch from open microphone to push-to-talk, and ask again. If the echo follows the gain — quieter when the gain is lower, gone when the microphone is only open while the key is held — the gain and open-microphone layer is involved. The handling is a balance, not a single setting: the gain should be high enough for teammates to hear your voice clearly, and low enough that room sound is not picked up, and the choice between open microphone and push-to-talk is a choice about how much room sound is acceptable, not a repair of the loop itself. If the echo does not change at all when the gain is lowered or when push-to-talk is used, that layer is not the cause: move to Step 6.
Step 6 — Stop one voice application at a time
If game voice and Discord, or two voice applications, are both running, stop one of them and test with the teammate, then stop the other and test again. If the echo appears only when both are running together, the fault is in the dual-monitoring and dual-sending layer, and the handling is to use one voice application at a time, with monitoring on in only one place. If the echo is still there with only one application running, go back through Steps 3 and 4 with that single application, because the loop is inside it, not in the combination.
Boundary cases
A teammate who hears nothing at all from you is the input-silence shape, not this guide's shape. In that shape the microphone is not transmitting, and the tests ask which microphone and which input setting is at fault. In this guide the microphone is transmitting — too much, in fact, because it is transmitting your voice twice — and the direction of the fault is the opposite. The two guides must not be mixed: their tests ask opposite questions, and a step from one will not diagnose the other.
A recorded file with an echo is a recording problem, not a live voice-chat problem. In a recording, the echo is baked into the file, and the diagnosis asks which source was recorded and when. In live voice chat, the echo is happening in real time, and the diagnosis asks who hears it and through which path. The two shapes share the word "echo" and little else.
Sound that is distorted, crackling, or cutting in and out during a game is a load or driver problem, not an echo. Its sign is that the sound changes character under load, or breaks up, rather than repeating cleanly. A voice that is too quiet, or dialogue that is too quiet relative to the effects, is a volume-balance problem, not a loop problem: the sound is present but at the wrong level, and there is no repetition. A voice that suddenly makes the whole game go quiet when a call starts is a different mechanism again — the system lowering other sounds while a voice call is active — and it is mentioned here only as a boundary. Its sign is the sudden quieting tied to a call starting, not a persistent echo, and it is not the fault this guide diagnoses. If the symptom is the sudden quieting, the communications setting is the direction to check, and the six steps in this guide do not apply.
Eight common misconceptions
- "An echo means the microphone is broken." Wrong. An echo is a loop: sound leaving somewhere it should not, being picked up again, and being sent back. A broken microphone produces silence, distortion, or noise, not a clean repetition of your own voice. Replacing the microphone does not stop speaker leakage.
- "Turning on echo cancellation fixes everything." Wrong. AEC subtracts the speaker output from the microphone input, but it cannot remove leakage that is much louder than the voice, it cannot cope well with long delays, and it cannot cancel a second monitoring loop. An echo that survives AEC is evidence, not proof that the setting is wrong.
- "Hearing my own voice means there is an echo." Wrong. Hearing your own voice in your own headphones is sidetone, a design feature so you know you are speaking. An echo is when a teammate hears your voice back. The two need different handling, and sidetone alone needs no fix.
- "Turning the microphone gain down fixes it." Wrong. Gain is a comparison test, not a repair. Lowering the gain makes the echo quieter, but it also makes your voice quieter, and teammates will struggle to hear you. The gain should be set so your voice is clear and room sound is not picked up, and the loop itself still needs to be found.
- "Headphones always stop an echo." Wrong. Headphones stop speaker leakage, because the sound no longer travels through the air. They do not stop a monitoring loop, which is electronic and does not need air. An echo that survives the switch to headphones points at monitoring, not at the speakers.
- "Muting myself fixes it." Wrong. Muting yourself only cuts off your side. If the loop is on the teammate's side — their monitoring, their speakers — muting yourself changes nothing for them, and the direction has to be established first.
- "It must be the graphics card or the headset." Wrong. The voice path does not run on the graphics card, and a headset fault does not create a clean, delayed repetition of your voice. The loop is in the speaker, monitoring, echo-cancellation, gain, or dual-application layer, and those must all be tested before hardware is suspected.
- "Two voice apps at once is fine, because they use the same microphone." Wrong. Two applications can each monitor and transmit the same microphone, and the two loops stack. Either one on its own can be clean while the two together produce an echo, which is why they must be tested one at a time.
What is confirmed, what is only a mechanism
The confirmed parts of this guide are the ones that follow from how the pieces are built: speakers send sound through the air and a microphone picks it up; monitoring sends the microphone signal back to the output; echo cancellation works by subtracting the known speaker output from the microphone input; microphone gain decides how much room sound is picked up; and two voice applications can each transmit the same microphone. No figure in percentages, no case count, no success rate, and no fee beyond the site's published three-tier fee appears in this guide, because none is supported by the sources used.
One point must be kept at the level of a mechanism, not a measured rule: the exact volume at which AEC stops being able to remove leakage depends on the device, the driver, and the application, and this guide gives no number for it. The test is the comparison — AEC on against AEC off, gain up against gain down — not a threshold.
Sources and what they do and do not establish
This guide is built from the mechanism of the voice chain itself — speaker to air to microphone, microphone to monitoring to output, output to echo cancellation — and from the settings as they are presented in Windows Sound settings, in-game voice settings, and Discord voice settings. The neighbouring guide on input silence is used here only for the boundary: its own boundary section states that the shape where a teammate hears your own voice back belongs to the monitoring and crosstalk layer, not to input silence, and this guide starts where that one stops. The two guides must not be mixed: silent is not echo, and their tests read in opposite directions even where the same setting appears in both.
A library search found no earlier article covering the core phrases of this guide's shape — game voice chat echo, teammates hearing your own voice, and echo cancellation in live voice chat — which is why the monitoring, crosstalk, and echo-cancellation layers in this guide are new ground rather than a repeat of earlier coverage. Mentions of monitoring elsewhere in the library are in recording and output contexts, not in live voice chat, and this guide does not claim they were never mentioned before, only that the live voice-chat echo shape was absent.
FAQ
My teammate hears my voice back, but I hear nothing wrong. Is the problem on my side?
Yes, most likely. The direction is the first test: if a teammate hears your voice back, your side is the source, because the sound is leaving your machine, being picked up again, and being sent back. Run the six steps on your machine — headphones, monitoring, echo cancellation, gain, and dual applications — and ask the teammate after each change. If you hear the teammate's voice back instead, the source is on their side, and the same steps need to be run there.
I switched to headphones and the echo is still there. Does that rule out speaker leakage?
Yes, it rules out speaker leakage as the main cause. Headphones break the path through the air, so an echo that survives the switch is not travelling through the room. It is almost certainly a monitoring loop, which is electronic and does not need air, or an echo-cancellation gap. Move to the monitoring switches in Step 3, turning each one off and asking the teammate after each change.
Is hearing my own voice in my headphones an echo?
No. That is sidetone, a design feature of many headsets that feeds a small amount of your own voice back so you know you are speaking and do not shout. An echo is when a teammate hears your voice back, overlapping or delayed. Sidetone alone needs no fix, and it can usually be turned down in the manufacturer's software if it is distracting. Do not treat it as the fault this guide diagnoses.
I turned echo cancellation on and the echo is still there. Is the setting broken?
Not necessarily. Echo cancellation subtracts the speaker output from the microphone input, but it cannot remove leakage that is much louder than the voice, it cannot cope well with long delays, and it cannot cancel a second monitoring loop. An echo that survives AEC is evidence in its own right: lower the speaker volume, re-check the monitoring switches one at a time, and check whether two voice applications are running together.
Will turning the microphone gain down fix the echo?
No, not as a repair. Lowering the gain makes the echo quieter, but it also makes your voice quieter, and teammates will struggle to hear you. Gain is a comparison test: if the echo follows the gain, the gain and open-microphone layer is involved, and the handling is a balance — high enough for your voice to be clear, low enough that room sound is not picked up — while the loop itself still needs to be found.
I only get the echo when game voice and Discord are both open. What does that mean?
It means the fault is in the dual-monitoring and dual-sending layer. Either application on its own is clean, but together they each monitor and transmit the same microphone, and the two loops stack. Stop one application at a time and test with the teammate to confirm which combination creates the echo, then use one voice application at a time, with monitoring on in only one place.
If the fault still cannot be divided
Bring the written record described in Step 1 to Room 1209, Dali Plaza, Shek Mun for inspection. The telephone number is 2186 8010 and WhatsApp is 6558 6806. There is no Mong Kok shop, and there is no on-site service. The site's published three-tier fee is HK$400–780, HK$480–1,380, and HK$680–2,800, an overall range of HK$400–2,800, with the actual fee quoted after inspection. Do not change several settings at once before coming in; the record of which comparison produced which result is the comparison material.