Quick Answer
If you need to remove echo in OBS, the most important thing to know is this: most OBS “echo” is not true room echo. It is usually one of two routing problems:
- Live monitoring delay: only you hear yourself back in headphones or speakers.
- Duplicate audio capture: viewers or recordings hear your mic or desktop audio twice.
Actual room echo is different. That is when the voice is not doubled, but it sounds roomy, reflective, or far away because of the space around the mic.
OBS can help with routing, monitoring, and some background-noise control, but its built-in filters are not true de-reverb tools. In practice, the fastest fix is:
- Make a short local recording.
- Check whether the echo is only in live monitoring, in the recording, or baked into the room sound.
- Fix monitoring or duplicate capture first.
- If the voice still sounds roomy after that, use post-processing rather than stacking more OBS filters.
This saves time because Noise Suppression does not fix duplicate routing, and stacking filters will not solve the wrong problem.
Start Here: Which Type of Echo Do You Actually Have?
Most bad OBS advice starts changing filters before confirming what the listener is hearing. Do this instead.
60-second diagnosis
- Open OBS and record a 20-second local test.
- Say a few words, pause, and also play any desktop or game audio you think may be involved.
- Listen back to the recording.
- Compare the recording with what you heard live while monitoring.
| What you notice | What it usually means | Fastest fix |
|---|---|---|
| You hear yourself delayed live, but the recording sounds clean | Monitoring echo | Turn mic monitoring off in Advanced Audio Properties unless you truly need it |
| The recording has a doubled mic or doubled game/Discord sound | Duplicate audio routing | Capture each source only once |
| The recording has one voice, but it sounds roomy, reflective, or far away | True room echo / reverb | Move closer to the mic, reduce gain, use headphones, then clean the exported track if needed |
This is the key separation many guides skip. Once you know which bucket you are in, the fix gets much shorter.

Problem 1: Only You Hear the Echo in OBS
If you hear yourself back, but the recording is fine, OBS is usually not recording an echo. You are hearing monitoring.
OBS’s Audio Mixer workflow includes Advanced Audio Properties, where monitoring behavior is controlled. If your mic is set to monitor, you may hear a delayed copy of your own voice in headphones or speakers.
How to stop hearing yourself in OBS
- In OBS, go to the Audio Mixer.
- Click the settings gear for your mic.
- Open Advanced Audio Properties.
- Find your microphone under the Audio Monitoring column.
- Set it to Monitor Off unless you specifically need live monitoring.
If you still hear yourself, also check for these common causes:
- Windows “Listen to this device” is enabled for the microphone.
- Speakers are playing back your monitored mic, and the mic is picking that sound up again.
- A hardware interface or headset app is doing direct monitoring outside OBS.
If possible, use headphones instead of speakers while testing. That removes one whole category of confusion fast.
Problem 2: Viewers Hear Your Mic Twice
If your audience hears a doubled voice, or your recording has two copies of your speech, that is usually duplicate mic capture.
This is one of the clearest official warnings from OBS: capturing the same device both globally and again as a source can create an echo effect.
The most common duplicate mic mistake in OBS
You add your microphone in Settings > Audio and also add it again as an Audio Input Capture source.
That means OBS may be hearing the same mic through two different paths.
Fix duplicate mic capture
- Go to Settings > Audio.
- Check whether your microphone is already assigned under the global audio devices.
- Then inspect your scene sources for an Audio Input Capture that uses that same microphone.
- Choose one path only:
- Use the global mic in Settings > Audio, or
- Use an Audio Input Capture source in the scene.
Do not use both for the same device unless you intentionally know why.
Best practice: global vs per-scene mic capture
| Approach | Best for | Main caution |
|---|---|---|
| Global mic in Settings > Audio | Simple single-mic setups | Do not also add the same mic as a separate source |
| Audio Input Capture source | Per-scene control and more complex setups | Make sure the global mic is disabled if this is your chosen path |
If you are unsure, the safest troubleshooting move is to disable one route, record another short test, and listen again.
Problem 3: Discord, Game, Capture Card, or Desktop Audio Echo
Not all OBS echo is from the microphone. Sometimes desktop audio is being captured twice.
Common examples:
- Desktop Audio is active globally, while the same app audio is also captured another way.
- A capture card provides audio, but you are also capturing the same sound through another input.
- A webcam microphone or webcam audio feed is active in addition to your main mic or desktop path.
- You capture Discord through Desktop Audio and also through another app-specific route.
How to fix desktop-audio loops
- In OBS, look at every active audio meter in the mixer while you speak and while desktop audio plays.
- Mute one source at a time and record a short test.
- Check Settings > Audio for global Desktop Audio devices.
- Check your scene for:
- Audio Output Capture
- Application Audio Capture
- Capture card audio
- Webcam audio
If two of those are carrying the same signal, keep only one.
As a rule, if you can hear the same sound source twice in the recording, OBS is usually being asked to capture it twice.

Problem 4: The Voice Sounds Roomy, Hollow, or Reflective
If the recording has one voice, not two, but it sounds distant or reflective, that is the version most people mean by true echo or room reverb.
This is not mainly an OBS routing problem. It is an acoustics and mic-technique problem first.
Fast fixes for real room echo
- Move the mic closer to your mouth.
- Lower the gain so the mic captures less room sound.
- Use headphones so speakers do not bleed back into the mic.
- Reduce speaker playback volume if speakers must stay on.
- Record in a softer space with less bare wall reflection if possible.
What OBS can do here is limited. Its built-in audio filters include Noise Gate, Expander, and Noise Suppression, but those are not the same as true de-reverb.
If routing is fixed and the voice still sounds roomy under the words, exporting the recording for cleanup is often the safer next step. If you want a simple option, SimpleClean is another tool from our team that you can use after recording.
What OBS Filters Can Help, and What They Cannot Do
OBS includes several useful audio filters, but each solves a different problem.
What each built-in OBS filter is actually for
| OBS filter | Helps with | Does not really fix |
|---|---|---|
| Noise Gate | Cutting background sound when you are not talking | Echo during speech, duplicate routing, room reverb under your words |
| Expander | Reducing low-level background sound more smoothly than a hard gate | Duplicate routing, true de-reverb |
| Noise Suppression | Mild steady background noise such as fan-like or white-noise-type sound | Doubled mic audio, strong room echo, loud-room reflections |
That distinction matters.
- Noise Gate only closes down when you are not speaking.
- Expander behaves more gently and often sounds more natural for spoken voice.
- Noise Suppression is for mild steady noise, not a magic echo remover.
So if your voice echoes while you are talking, a gate will not solve it. And if the voice is being captured twice, suppression is the wrong tool entirely.
Can Noise Suppression remove echo in OBS?
Usually, no. OBS’s own Noise Suppression guidance is about mild background or white noise. That supports the practical conclusion that it is not a true room-echo remover.
If you want a deeper explanation of where OBS suppression helps and where it runs out of road, see OBS Noise Suppression vs Krisp.
Does OBS Have a De-Reverb or De-Echo Filter?
OBS’s official built-in filter list covers tools like Noise Gate, Expander, Noise Suppression, and VST hosting. Based on that filter list, the safe takeaway is that OBS does not provide a native one-click de-reverb control in its standard built-in filters.
That is an inference from the official filter lineup, not a hidden-feature claim.
When a VST plugin may help
OBS supports VST 2.x plugins. It does not support VST3.x through its VST filter path.
So if you want to try a third-party plugin route inside OBS, make sure the plugin is available as VST2.
One commonly referenced free bundle is Cockos ReaPlugs, which includes tools such as ReaFIR. Keep expectations realistic: third-party plugins may help in some cases, but they still do not replace solving bad routing or poor mic placement first.
Best Fix by Symptom
| If your symptom is... | Best first move | Best for |
|---|---|---|
| You hear yourself, but the recording is clean | Turn monitoring off | Streamers and live presenters hearing delayed self-monitoring |
| The audience hears two copies of your voice | Remove duplicate mic paths | Anyone using both global audio devices and scene capture sources |
| Game, Discord, or capture-card sound is doubled | Remove duplicate desktop or app-audio paths | Gaming, call, and capture-card setups |
| The voice sounds hollow or far away | Fix mic distance, gain, and speaker bleed; then clean the export if needed | Podcasters, course creators, and screen-recording users in reflective rooms |
Step-by-Step: The Shortest Safe OBS Echo Fix Workflow
- Make a 20-second local recording. Do not troubleshoot from live monitoring alone.
- Ask one question first: Is the echo only in your headphones, in the recording, or in the room sound itself?
- If only you hear it: open Advanced Audio Properties and set the mic to Monitor Off.
- If the recording has doubled voice: remove duplicate mic capture and keep only one input path.
- If desktop audio is doubled: disable overlapping Desktop Audio, Application Audio Capture, capture-card audio, or webcam audio paths.
- If the voice is just roomy: move closer to the mic, lower gain, and switch to headphones.
- Use filters for the right job only: Gate or Expander for pauses, Noise Suppression for mild steady noise.
- If echo remains under the speech: export and process the spoken track with a dedicated cleanup workflow.
When OBS Is the Wrong Tool
OBS is very good at capture, monitoring control, and basic real-time filtering. It is much weaker when the problem is speech already smeared by room reflections.
That is why so many people keep pushing filters and still dislike the result. They are asking OBS to do restoration work after the room sound is already baked into the voice.
If you want the broader post-recording cleanup angle, see Remove Echo in Descript.
Common Mistakes That Waste Time
- Turning on Noise Suppression before checking for duplicated sources
- Stacking every filter at once and making speech sound worse
- Testing only through live monitoring instead of listening to a recorded file
- Using speakers while trying to diagnose mic echo
- Capturing the same mic globally and as an Audio Input Capture source
- Capturing the same desktop signal through multiple audio routes
Conclusion
To remove echo in OBS, diagnose the type first.
- If only you hear it, it is usually monitoring.
- If viewers hear doubling, it is usually duplicate routing.
- If the voice itself sounds roomy, it is usually room echo, not an OBS mixer mistake.
That one decision saves most of the troubleshooting time.
Fix routing and monitoring first. Use OBS filters only for the jobs they actually do well. If the voice still sounds reflective after that, move to post-processing instead of chasing the wrong control inside OBS.