Slapback · 2026-09-20
Does Krisp remove echo? What it can and can't do
Short answer: yes — echo removal is a named, documented part of what Krisp does, not a marketing fog around its noise cancellation. Longer answer worth reading before you install anything: Krisp's docs describe two different echo features solving two different problems, and knowing which of the two you have decides whether Krisp is your fix at all. Everything below comes from Krisp's own documentation and announcements, checked 2026-09-20; we haven't run lab tests, and we say so.
Feature one: Acoustic Echo Cancellation
This is the loop-breaker. When you take calls on external speakers — or laptop speakers with the volume up — your mic hears what your speakers play, and the far side gets their own voices mailed back to them. Krisp's Acoustic Echo Cancellation targets exactly that path: in Krisp's words, it works "by not letting the echo captured by your actual microphone reach the other participants on your call." Because Krisp runs as a virtual microphone underneath all your apps, that protection applies to every call in every app, not just the one whose settings you remembered to fix.
Who this is for: the person whose colleagues report hearing themselves, the open-speaker die-hards, the no-headphones crowd. If that's your complaint pattern, this is the relevant half of Krisp.
Feature two: Room Echo Cancellation
Different problem: nobody hears their voice twice, but your voice arrives sounding like it was recorded in a stairwell — hollow, ringing, "empty room" sound. That's your walls reflecting your voice into your own mic a few milliseconds late. Krisp's Room Echo Cancellation targets this reverberant smear, and per Krisp's docs it's built into its bi-directional noise cancellation rather than living behind a separate switch. (Strictly, this problem is reverb rather than echo — the distinction has practical teeth, and we unpack it here.)
Who this is for: the person told they sound distant or boomy in a sparse home office. Note the honest overlap warning: if this is your only problem and you have an RTX GPU on Windows, NVIDIA Broadcast's Room Echo Removal does this half free — the comparison treats both fairly.
The fine print that matters (verified 2026-09-20)
- Free tier: 60 minutes of processed audio per day — a fresh hour daily, roughly 30 hours a month — resetting at midnight GMT. For evaluating echo removal that's genuinely enough: echo either dies on your first test call or it doesn't. Ongoing heavy use is what the paid tier ($8/user/month billed annually, $16 monthly) is for.
- Desktop only. Live cancellation runs in the Windows and macOS apps. Krisp's mobile apps handle recording, transcription and meeting notes — per Krisp's support docs, live noise cancellation isn't available there due to platform limitations. If your echo problem lives on a phone, Krisp is not your fix.
- It's a background processor. Real-time inference costs some CPU — a non-issue on recent machines, worth knowing on old ones.
What no Krisp install can do
Krisp processes audio on your machine. If the echo you hear is your own voice coming back, the loop is running on someone else's device — their speakers, their mic, their missing canceller — and nothing you install locally reaches it. This isn't a Krisp limitation; it's the geometry of the problem, and it's the most common way people buy the right tool for the wrong side of the call. Check whose loop it is first (two-minute logic, group-call version) — then put the canceller on the machine that's actually looping. If that machine is yours, the free hour will tell you today whether it's solved.