Why Does a Video Call Echo for Only One Participant?

A video call can echo for only one participant because the problem is often in one person’s audio path or room, not in the call as a whole. A speaker may send another person’s voice back into a microphone; two devices in the same room may be connected at once; or the affected listener may hear a local monitoring loop that nobody else hears. The key clue is not just who reports the echo. Ask whose voice repeats and which people can hear it.

Start with two questions: who hears it, and whose voice repeats?

“Only one person has an echo” can describe different problems. If several people hear their own words repeated whenever one participant speaks, that participant’s device or nearby room is a likely place to test first. If only one person hears an echo of their own voice, the sound may be looping locally through their headset monitoring, operating system, recording software, or a second audio connection. If one person hears another participant repeat but nobody else does, inspect the listener’s own output and connected devices as well as the other person’s setup; the report alone does not identify the source.

How a one-person echo happens

During a call, the app sends microphone audio to other participants and plays their audio through speakers or headphones. With speakers, some of that played sound can travel back into the microphone. The app’s acoustic echo cancellation tries to recognize and remove that return path. If the speakers are loud, the microphone is close, the room is reflective, or the cancellation system cannot handle the device setup, a copy can be sent back into the meeting. The person whose device creates the loop may not hear the echo themselves; other participants hear their own words return from that room.

A second common cause is joining the same meeting on more than one device with audio active. For example, someone may join on a laptop and also dial in on a phone, or a meeting-room computer and a personal laptop may both play call audio. Muting one microphone may not be enough if its speakers remain on. Zoom’s echo guidance specifically identifies computer-and-phone audio active together, nearby speakers, and multiple active computers in one room. Microsoft similarly warns that a personal device can cause echo if its audio stays on after joining a Teams Room.

Echo can also be limited to a particular headset, speakerphone, monitor, soundbar, microphone, or software route. Mismatching a microphone and external speaker can matter, and some Bluetooth headsets behave differently across meeting apps. Google Meet advises checking the selected microphone and speaker, trying a headset, lowering speaker volume, and checking headset compatibility. These are sensible first tests; they do not prove a device is defective.

Run a quick isolation test before changing settings

1. Ask the group for a precise description. Is the repeated sound the speaker’s own voice or the listener’s voice? Does one person hear it, or do several? Does it start when one person unmutes or joins from another device?
2. Mute likely sources one at a time. If the echo stops when a participant mutes, their outgoing audio path is implicated. Unmute and have them switch to headphones or reduce speaker volume to see whether that changes it. In a large meeting, the host can mute everyone and unmute people one at a time. Treat this as a clue, not a final diagnosis.
3. Remove duplicate audio connections. If someone joined from a phone and computer, keep audio connected on only one. If their video must stay on a second device, use that device’s “no audio” or “don’t use audio” option when available. In a shared room, leave computer audio connected on one system only. Muting a mic does not necessarily turn off its speaker.
4. Try a headset and reduce speaker volume. A headset usually keeps call playback closer to the listener and farther from the microphone. If the echo disappears, the room-speaker path was likely involved. If it remains, verify which microphone and output device the app selected; the built-in laptop mic may still be active even when headphones are connected.
5. Test another route. Rejoin with one device, use another headset or a wired connection if available, or test in a different app. If the issue follows one accessory across calls, check that accessory’s firmware and device settings. If it occurs only in one app, update the app or browser and check that app’s audio setup.

When is it an app setting or a network problem?

Meeting apps include echo cancellation, but the control names and available options change. Start with the app’s normal or automatic setting rather than switching off audio processing at random. Zoom describes its advanced echo-cancellation controls as an option for technical troubleshooting and notes that settings can affect audio quality or system behavior. Change an advanced control only for a specific test, record what you changed, and restore the previous value if sound gets worse.

Network trouble more often presents as lag, gaps, or choppy or robotic speech than a clean copy of the same words. If the “echo” is really a long delay, test a stable connection, move closer to Wi-Fi, or temporarily try another network. Google Meet’s current guidance separates its echo tips—headphones, lower speaker volume, and muting when not speaking—from its network-quality suggestions. On Meet, its current help page also offers “Troubleshooting & help” recommendations when it detects a quality issue.

Use the platform documentation that matches the call. See Google Meet’s troubleshooting steps for echo and call quality, Google Meet’s microphone and speaker selection guide, and Zoom’s instructions for isolating an echoing attendee. For a Teams Room, check Microsoft’s room-joining audio instructions. Menus and features can vary by app version, device, and organization settings.

What to do if the echo keeps coming back

Keep a short note of the pattern: which participant unmutes, whose voice repeats, whether a second device is present, and which headset or app was used. That record helps separate a room feedback loop from a local monitoring setting or an app-specific fault. Ask the participant to test a different microphone and output device, and update the meeting app, browser, operating system, and headset firmware where the manufacturer recommends it.

If one participant hears the echo even when everyone else confirms the call is clear, focus first on that participant’s local audio routing and any recording, streaming, or accessibility software that could monitor the microphone. If everyone hears their own voice return from one person’s room, focus first on that room’s speakers and duplicate connections. If the echo persists across devices and apps after these checks, the app provider or device manufacturer can help investigate an audio-processing or hardware issue. A single person reporting echo is a useful clue, but it is not enough by itself to prove whose device is at fault.

Sources checked October 1, 2026. Menu labels and available audio controls can change; follow the current instructions for your app and device.