If you have ever wanted to route Discord into your stream but not your ears, or capture only your music channel while muting notifications, you have run into the limits of basic audio setup. Loopback audio is the feature that makes flexible routing possible, and understanding it unlocks a far cleaner stream mix.
What loopback means
Loopback is the ability to feed an application’s audio output back into a recordable input, as if it were a microphone. Normally your operating system sends app sound straight to your speakers and nowhere else. Loopback intercepts that stream so OBS or your interface can grab it, letting you decide exactly which sources reach your viewers.
Two ways to get it
There are hardware and software routes. Some USB audio interfaces include a built-in loopback channel that mixes your mic and computer audio into a single input. On the software side, virtual audio cable tools create fake devices you assign apps to, then capture in OBS. Both achieve the same goal: granular control over what is heard.
Hardware versus software loopback
| Method | Pros | Cons |
|---|---|---|
| Interface loopback | Simple, low latency, no extra apps | Often one mixed channel, less flexible |
| Virtual audio cable | Very flexible, per-app routing | More setup, potential for routing mistakes |
| OBS per-app capture | No extra software on modern OBS | Availability depends on OS version |
Recent OBS versions on Windows can capture individual application audio directly, which covers many needs without any virtual cable. For anything more complex, such as sending different mixes to your headphones and your stream, a virtual audio routing tool remains the powerful option.
A simple loopback setup
On an interface with loopback, set the interface as an OBS audio input and enable its loopback mix so mic plus system audio arrive together. With software routing, create a virtual output device, point your music or game to it, and add it as an audio capture source in OBS while your notifications stay on the default device, unheard by viewers.
Common loopback use cases
Loopback shines the moment you want to separate what you hear from what you broadcast. Streamers use it to keep Discord voices in their own ears but off the public stream to respect friends’ privacy, to route a music player onto its own channel so it can be muted for copyright-safe VODs, or to send a soundboard into the stream without it blasting their own headphones twice. Each of these needs individual routing that a single mixed output cannot provide.
Musicians and karaoke streamers lean on loopback even harder, sending a clean instrument or backing-track feed to viewers while monitoring a different balance themselves. Once you map out which apps should reach viewers, which should reach only you, and which should reach both, loopback and virtual devices give you a small mixing desk in software. Sketching that routing on paper first saves a lot of trial and error.
Frequently asked questions
Will loopback cause an echo on my stream?
It can if you accidentally route your own monitored audio back into a captured channel, creating a feedback loop. Avoid capturing a device that also carries your microphone monitoring, and keep OBS “Monitor and Output” settings tidy. Set up one source at a time and test to catch echoes early.
Do I need loopback if I only stream game audio and voice?
Not necessarily. A basic setup with a mic input and desktop audio capture handles simple streams fine. Loopback becomes valuable when you want to exclude certain apps, mix music separately, or send a different balance to your ears than to your viewers.
Bottom line
Loopback audio lets your streaming software capture app sound as if it were an input, giving you precise control over your mix. Use an interface’s built-in loopback or OBS per-app capture for simple needs, and a virtual audio cable for advanced multi-mix routing. Set sources up individually and test for echoes to keep the stream clean.
