How to stop your stream from hearing Discord

First, confirm this is actually your problem

The symptom is specific: people watching your stream, or the VOD afterward, can hear your Discord call. Your teammates' voices are on the broadcast even though you never added Discord as a source. If instead your teammates are complaining that they can hear your game or their own voices coming back, that is a different wiring problem, and the walkthrough on how to fix mic echo covers it.

This one matters more than most audio annoyances. Your friends did not agree to be broadcast, so it is a privacy problem. Anything playing on their end can leak through, so it can become a rights problem. And a second conversation running underneath your commentary just sounds like a mess. The good news: once you see why it happens, the fix is mechanical.

Why your stream hears Discord at all

Streaming apps typically capture desktop audio: one big lane that carries everything your computer plays out of your default output device. Your game is in that lane. Your browser is in that lane. And Discord, which is just another app playing sound, is in that lane too. The capture cannot tell a teammate's voice from a game explosion; it is all one stream of sound coming out of one device.

So the real task is not "mute Discord on stream", it is "get Discord out of the lane the stream captures". That is a routing job, and there are a few ways to do it. If the idea of lanes and destinations is new, the primer on what audio routing is will make the rest of this page click faster.

Fix 1: send Discord to a second physical output

The classic trick: if your stream captures your main output device, point Discord at a different one.

1. Plug in or enable a second output device: a USB headset, a second audio interface, even motherboard audio you normally ignore.
2. In Discord, open Settings, then Voice & Video, and set the Output Device to that second device.
3. In your streaming app, make sure desktop capture still points at your main device only.

This works, and it is worth knowing. It is also fragile in practice. You need spare hardware, and you need a way to actually hear both devices at once: game in one ear path, teammates in another, which usually means wearing one output and physically mixing or giving up on the other. Unplug the second device, or let a Windows update shuffle device names, and Discord quietly falls back to the default output. The moment it does, your teammates are back on the broadcast and nothing warns you.

Fix 2: use per-app output pickers where they exist

Windows can assign an output device per app, no extra hardware required.

1. Open Settings, then System, then Sound, then Volume mixer.
2. Find Discord in the app list and set its Output device to something other than the device your stream captures.
3. Some streaming apps can also capture a specific application instead of the whole desktop. If yours can, capturing only the game skips Discord entirely.

The honest caveats: the app only appears in the volume mixer while it is actively playing sound, so you may have to join a call just to set it. Some apps ignore the assignment or spawn helper processes that slip back to the default device. And Windows has a habit of forgetting per-app assignments after updates or device changes. Streamers who rely on this tend to re-check it before every broadcast, which tells you what kind of fix it is: it works until the day it silently does not.

How Patchd keeps Discord off the stream by construction

Patchd is a virtual audio mixer, a piece of software that sends sound between your apps and devices, and it starts from the insight this whole problem hinges on: chat is not desktop audio. Every Patchd setup includes two fixed strips, Desktop and Communications. Point Windows' default playback device at Patchd Desktop and its default communication device at Patchd Communications (Patchd's setup walks you through both), and chat apps like Discord land on the Communications strip while your game, music, and browser stay on Desktop. Those two Windows settings build the separation you were trying to make with spare headsets and volume-mixer settings, on the Free tier included.

Each strip has a row of colored routing pills, one per destination: your hardware outputs and your buses (a bus is a virtual output that other apps see as a microphone). A lit pill means the strip feeds that destination; an unlit pill means it does not, ever. So the routing for this fix is three clicks:

1. On the Desktop strip, light the pill for your headphones and the pill for Bus 2, a bus of its own that OBS captures as the game's source, beside your mic on Bus 1. Game audio reaches your ears and the stream.
2. On the Communications strip, light the green pill for your headphones, the one showing their device name. Your teammates reach your ears.
3. On that same Communications strip, leave every BUS pill unlit. That is the entire fix.

The unlit pill is worth staring at for a second, because it is a different kind of guarantee than the Windows fixes above. You are not muting Discord in a hurry before you go live, and you are not trusting an app to keep respecting a per-app setting. The Communications strip simply has no route to any bus. Audio that is never routed somewhere is never captured there. Off by construction, not off by vigilance.

Everything else about your stream keeps working exactly as before. Desktop still feeds Bus 2, so viewers hear the game. Your mic strip still feeds Bus 1, so viewers hear you. You can talk over a heated call, take a private ping mid-boss-fight, or leave voice chat running for hours, and none of it can reach the VOD, because there is no lit path for it to travel. If you want the full picture of a stream built this way, mic and game and chat each on their own strip, the streaming audio setup guide walks through it end to end.

The short version

• Your stream captures desktop audio, and Discord lives inside desktop audio. That is the whole problem.
• A second physical output works but needs spare hardware and fails silently when devices change.
• Windows per-app output pickers work until an app ignores them or an update resets them, so re-check before every stream.
• In Patchd, chat has its own fixed Communications strip. Point Windows' default communication device at it, light its headphones pill, leave its bus pills unlit, and Discord is off the broadcast by construction.

Patchd draws the whole signal path on screen, so "is chat on the stream?" stops being a thing you hope about and becomes a pill you can see is not lit. It is in open beta now.