START HERE
Record a test with your live preview muted, headphones on, and source monitoring disabled. If the echo remains, remove duplicate capture routes one at a time. If it disappears, rebuild monitoring carefully without capturing its destination again.
Separate recording echo from headphone echo
Speak a short phrase, then leave a few seconds of silence in a local recording. Close or mute Twitch, YouTube, and dashboard preview players on the streaming computer. Listen to the file afterward. If the file sounds clean but your headphones repeat your voice, investigate local mic monitoring or sidetone rather than changing the stream mix.
A close duplicate can sound hollow or unusually loud instead of producing a distinct repeated word. A later copy sounds like an echo. Neither observation identifies the exact source by itself; the useful test is removing one route and hearing what changes. Keep headphone volume low while testing possible feedback paths.
Look for the same signal captured twice
Inspect the active scene, any nested scenes, and global audio devices under Settings > Audio. Typical overlaps include a microphone selected globally and in an Audio Input Capture source, or a game recorded through both Desktop Audio and an application source. The OBS source documentation specifically warns about capturing a device both globally and in a scene.
- Label sources by what they capture, such as Headset microphone or Game application.
- Make the test sound and note every responding meter.
- Temporarily mute one candidate from the output, record again, and compare.
- Once the duplicate is identified, keep the intended route and remove or disable the unnecessary capture.
Do not delete an entire shared scene just to silence one source. It may also be used by other scenes.
Check whether monitoring comes back into capture
Imagine a microphone sent to your headphones by OBS. If Desktop Audio captures those same headphones, the microphone can return to the mix through that device. A virtual cable can create the same loop when its playback end receives monitoring and its recording end is captured again. Use the Windows & OBS routing helper to verify which endpoint feeds each app.
Disable monitoring for the suspect source and make another recording. If that breaks the echo, inspect the Monitoring Device under Settings > Audio and the devices your other sources capture. Choose a monitoring destination outside that captured route, or keep monitoring off. The monitoring guide explains current and older OBS controls.
Do not assume muting the broadcast also silences your headphones: current OBS handles output mute and monitoring independently.
Rule out a real second microphone path
With all software monitoring disabled, listen again using headphones and temporarily mute other microphones, webcams, and capture devices. If the echo disappears when a nearby speaker is turned down, an open microphone was hearing the room playback. Move the microphone closer to the speaker’s mouth and keep computer sound in headphones while testing.
If the echo occurs only when a guest talks, ask the guest to mute their own live preview and use headphones too. Your OBS settings cannot remove a delayed copy already mixed into their outgoing call audio. Compare the incoming call alone with your local microphone alone before deciding which side needs attention.
Prove the route is clean before adding effects
Use a simple record: say “microphone,” play a short game sound, then trigger one alert, with silence between them. Each should appear once in the file. Restore scene transitions, browser alerts, and voice chat separately. The first addition that restores the echo narrows the cause considerably.
For Windows application capture, OBS recommends disabling overlapping global Desktop Audio when building an application-only mix. Its application capture guide describes that arrangement. Keep a whole-device source only when its inclusion is deliberate and you have checked which other sources overlap it.
Common questions
Will noise suppression remove doubled audio?
It is not a routing repair. Two copies of clear speech can survive suppression, and aggressive processing may damage both. Fix the extra path first, then assess any remaining room noise with an unprocessed recording.
Why did it start after switching headphones?
A source or monitoring destination set to Default may now follow a different device. Compare named devices before and after the switch. A new headset may also expose its own sidetone control, which affects what you hear without necessarily changing the recording.
After eliminating duplicate paths, drop a short OBS recording or capture your live preview tab in the stream loudness & stereo balance checker to verify phase correlation, centered mic placement, and safe output headroom.
Sources & version notes
Documentation checked November 18, 2026. Use the platform and version notes in this guide when comparing settings. The troubleshooting checks are intended for your own setup; this review date does not represent hardware testing.