Zoom echo or feedback during calls — where participants hear their own voice back, or where there’s a high-pitched squeal — is almost always a speaker-to-microphone path: the microphone is picking up sound from the speakers. The fix is breaking that path. You’ll find the complete rundown in our Complete Guide to Fixing Windows, Browser, and Software Errors.
The fastest diagnostic: ask whether everyone hears the echo or just specific people. If only one person hears echo: the echo is on the others’ side — someone else’s audio setup is creating it. If everyone hears it: it’s usually the person who joined most recently, whose microphone is picking up the meeting audio and rebroadcasting it.
The fastest fix: mute one participant at a time until the echo stops. The person whose mute kills the echo is the source.
The physical cause — and why settings alone don’t always fix it
Echo happens when microphone → audio output → back into microphone creates a loop. Software echo cancellation (which Zoom includes) is supposed to prevent this, but it has limits: very loud speaker output, microphone and speaker physically close together, or the speaker and mic running through different latency paths can overwhelm the cancellation algorithm.
Physical fixes first, before any settings:
- Reduce speaker volume — lower physical output = less sound reaching the microphone
- Use headphones — the most reliable echo fix available. Sound goes into ears, not into the room, so the mic can’t pick it up. External speakers feeding back into a laptop mic is the single most common setup that causes persistent echo despite all software fixes.
- Move microphone away from speakers — physical separation matters
Zoom echo cancellation settings
Zoom has its own echo cancellation that runs independently from the OS. Settings → Audio → Suppress background noise → “High” or “Medium.” Also: Settings → Audio → check “Suppress intermittent background noise.” These settings apply Krisp-based noise suppression that also handles echo components.
But also: Settings → Audio → look for “Echo cancellation” if it appears as a separate toggle in older Zoom versions — ensure it’s enabled.
Multiple audio devices creating a feedback loop
A specific scenario: the computer has speakers active, the person also has a Bluetooth headset connected, and Zoom is set to use the speakers for output while the headset mic captures the speaker sound. The headset mic picks up the laptop speakers, creating echo even though the person is wearing headphones — because they’re wearing headphones for mic input while the audio comes out of a different speaker.
Zoom Settings → Audio → confirm the Speaker and Microphone are from the same device. Both should say “Headset” or both “Laptop speakers/microphone” — not a mix. A mismatched pair is the most common cause of echo that headphones don’t solve.
Bluetooth headsets and codec switching
Bluetooth headsets use two profiles: A2DP (high-quality stereo) for output and HFP (headset) for microphone + lower-quality output. When a communication app like Zoom activates the microphone, the headset switches to HFP mode — which uses lower-quality audio for both input and output. This audio mode switch can cause a brief feedback loop during the transition, or ongoing echo if the headset’s internal hardware echo cancellation isn’t working correctly in HFP mode.
Try: use a wired connection if the headset supports it. Or in Zoom Settings → Audio → Speaker → explicitly select the headset as “Headphones” (A2DP) rather than “Headset” (HFP). Some headsets allow both mic and high-quality audio simultaneously through proprietary audio drivers — check the headset manufacturer’s app for this option.
Virtual audio devices and OBS
If OBS, Voicemeeter, or another audio routing tool is installed: virtual audio devices sometimes create routing loops where audio circulates between virtual inputs and outputs. Zoom receiving audio from a virtual device that receives its input from Zoom’s output creates a digital echo loop.
Test: Settings → Audio → select the physical microphone directly (not a virtual device) → set the speaker to the physical audio output (not a virtual output). If echo stops with direct devices: the virtual audio routing was creating the loop.
When it’s another participant’s issue
If the echo source is another participant who isn’t aware their audio is creating the issue: the host can mute them directly from the participant list. In the meeting: Participants panel → find the echoing participant → mute them → send them a private message explaining to mute and check their audio setup.
Most hosts don’t realise they can mute individual participants without ending the meeting or removing them. The mute is temporary — the participant can unmute themselves — but it stops the echo immediately while they fix their setup.
Recording echo vs live echo
Echo in the Zoom recording that wasn’t present in the live call: Zoom may have recorded from a system audio source that included the meeting audio alongside the microphone — creating a double-track effect that sounds like echo in the recording. Zoom recording settings → ensure “Record computer audio” is set appropriately. For local recordings, using “Separate audio files for each participant” (available in Zoom Pro+) eliminates the mixing issue entirely.
Our guide on Discord audio issues covers the audio subsystem and exclusive control settings that affect Zoom audio in the same way — particularly the Windows sound settings for exclusive device control. For Teams audio echo specifically (slightly different software handling), our Teams microphone guide covers the similar echo cancellation and device routing settings. Zoom’s audio troubleshooting documentation covers the real-time audio statistics (three-dot menu → Audio Statistics during a call) which show whether echo is being detected and suppressed by Zoom’s engine, and at what level.
Room acoustics and acoustic echo
A bare-walled room with hard surfaces (concrete, glass, tiles) creates acoustic reflections. The microphone picks up not just the direct speaker output but also reflections bouncing off walls — delayed versions of the same sound that arrive at the mic at different times. Zoom’s echo cancellation handles direct speaker-to-mic feedback well but can struggle with highly reflective rooms where the echo arrives from multiple directions at different delays.
Practical fixes: add soft furnishings (cushions, curtains, carpets) to the room, position the microphone to face away from reflective walls, or use a directional microphone that picks up sound primarily from one direction (the speaker’s face) rather than omnidirectionally.
Zoom test meeting before calls
zoom.us/test opens a test meeting specifically for checking audio setup before real calls. This test lets you record a message and play it back — hearing exactly what your microphone captures, including any echo from your setup. Testing before important calls takes two minutes and identifies echo problems while there’s still time to fix them rather than during the call itself.
HDMI audio routing creating a loop
A specific and easy-to-miss scenario: the laptop is connected to an external monitor via HDMI, the monitor has speakers, and those speakers are set as the default Windows audio output. The microphone (on the laptop, facing the monitor’s speakers) picks up the monitor speaker output and rebroadcasts it. The physical arrangement — laptop mic facing monitor speakers — creates an echo path that software cancellation handles poorly because the delay is long enough to confuse the echo cancellation algorithm.
Fix: Sound settings → Playback → set the laptop’s internal speakers (not the HDMI monitor) as the default output → reduce speaker volume → use headphones. Alternatively, adjust the monitor position so the speaker faces away from the laptop’s microphone array location (usually near the webcam or keyboard).
Headphone echo from open-back headphones
Open-back headphones allow sound to pass through the ear cups in both directions. In a quiet room, this is usually fine. In a meeting where others are speaking, the audio from other participants can leak out of open-back headphones and be picked up by the microphone as echo. This is an acoustic problem, not a software one.
If using open-back headphones for Zoom calls: switch to closed-back headphones that seal around the ear, preventing audio leakage. Alternatively, reduce the headphone volume enough that the leakage is below the microphone’s sensitivity threshold. Open-back headphones are excellent for music listening but are generally not suited for voice communication in shared spaces or where room acoustics create significant reflections.
TV or external display’s built-in microphone
Many modern TVs and external monitors have built-in microphones (for smart TV functions or video conferencing features). Windows sometimes lists these as available audio input devices. If Zoom selects one of these as the microphone — particularly a TV’s microphone that’s in the same room as speakers — echo is virtually guaranteed because the TV mic is designed to pick up room audio, not suppress nearby speaker sound.
Zoom Settings → Audio → Microphone → confirm it’s set to the laptop’s microphone or a dedicated headset microphone, not a TV or monitor microphone. TV/monitor microphones appear in the dropdown and have similar names to the display (“Dell Monitor Microphone” or “LG TV Audio Input”). Deselecting them from Zoom ensures Zoom uses a more appropriate microphone source.
Multiple Zoom instances
Running Zoom twice — as sometimes happens when clicking a meeting link while already in another meeting — creates two audio pipelines. The second instance receives audio from the first instance’s speakers and re-transmits it, creating a perfect software echo loop. Check whether two Zoom windows are open in Task Manager → look for multiple Zoom.exe processes. Close the additional instance and the echo stops.
Meeting room hardware echo
Conference rooms with dedicated hardware (Poly, Jabra, EPOS, Logitech conference room systems) handle echo cancellation in hardware rather than relying on Zoom’s software cancellation. When a hardware conference room device is used alongside a laptop also running Zoom (two audio devices in the same room both active), the hardware device’s microphone picks up the laptop’s audio output, and the laptop’s Zoom instance picks up the room’s audio — creating a loop between two active Zoom endpoints in the same space.
Only one audio source should be active per physical room. Either: everyone in the room uses the conference room hardware system (laptop participants mute themselves and use the room system), or the room system is disconnected and the laptop handles everything. Two active Zoom audio instances in one room always creates echo — it’s a fundamental audio routing conflict, not a fixable software setting.
The core principle to remember when troubleshooting echo: software echo cancellation is a mitigation, not a solution. It works when the speaker-to-microphone path is manageable (low volume, reasonable distance, clean audio routing). When the path is strong — laptop speakers at high volume with the laptop microphone nearby — no amount of software setting changes fully eliminates the feedback. The right fix in that case is always physical: use headphones, reduce speaker volume, or use a dedicated headset that captures only the speaker’s voice. Chasing software settings for echo problems that have a physical cause leads to partial improvements that degrade as soon as audio levels change.
Audio driver sample rate and latency
When the audio driver’s sample rate is set incorrectly — or when different audio devices on the same system use different sample rates — the echo cancellation algorithm, which depends on precise timing to identify and subtract the echo signal, can fail to cancel properly. A speaker sample rate of 48000 Hz and a microphone sample rate of 44100 Hz means the cancellation algorithm is comparing signals that aren’t temporally aligned.
Right-click speaker icon → Sound settings → More sound settings → Playback tab → right-click your speakers → Properties → Advanced → Default Format → set to 1 channel, 16-bit, 48000 Hz. Do the same in the Recording tab for the microphone. Matching sample rates between input and output devices ensures the echo cancellation algorithm has consistent timing reference data to work with.
Persistent echo after all fixes — Zoom audio debug
When all the above has been tried and echo persists: enable Zoom’s audio debug log. Zoom → Settings → General → “Send diagnostic reports automatically” → also enable the audio debug logging if available in your Zoom version. Then reproduce the echo → email logs to Zoom support with a description. Zoom’s engineering team has seen thousands of echo configurations and can often identify the specific audio routing issue from the logs that isn’t obvious from user settings.
The audio statistics available during a call (three-dot menu → Audio Statistics) show real-time values for echo detection levels — a persistently high echo level in the statistics confirms Zoom is detecting echo but failing to cancel it, which narrows the diagnosis to audio path strength rather than configuration issues.
One final thought on the social dynamics of echo: the person causing the echo rarely hears it themselves. The echo loop sends their own voice back to everyone else but not back to themselves (because Zoom, like all video calling software, suppresses the local participant’s own audio from their own output). If no one can identify the echo source and you’re the most recently joined participant, muting yourself and asking whether the echo stopped is the quickest way to confirm whether you’re the source — even if you can’t hear the echo from your own perspective. If this sounds familiar, Zoom Not Connecting is worth a look.
