STREAMING GUIDE / OBS STUDIO

Separate Discord audio in OBS without muting your call

Keep listening to teammates while deciding whether their voices belong in your stream. Build separate sources and check the actual recording before relying on a mute button.

START HERE

Keep Discord playing through your headphones. Capture the game and Discord separately in OBS, remove broad desktop-output capture, and mute only the Discord source in OBS when the audience should not hear it. Your normal Discord headphone playback does not need OBS monitoring.

Choose whether Discord should ever reach the audience

This walkthrough uses Application Audio Capture in OBS 28 or later on Windows 10 version 2004 or later, or Windows 11. It keeps the call you hear separate from the mix you send to viewers. On macOS and Linux, use the platform-specific capture workflow rather than expecting the same source picker.

For a call that should always stay off stream, omit Discord from the OBS mix entirely. If you want to include teammates occasionally, add a clearly named Discord source and begin with its output muted. Either arrangement is easier to inspect than capturing every sound your headphones receive and trying to remove voices afterward.

Agree with participants before broadcasting a call. An application source is not a voice-only filter: notifications or other media played by that application may also be included. Game-integrated voice chat belongs to the game's audio path and needs a separate check.

Build one source for each sound you want to control

Before changing audio settings, choose Scene Collection > Duplicate and name the copy for this test. Confirm that copy is active. Global audio sources belong to the scene collection: disabling Desktop Audio affects every scene in the active collection. Creating just a new scene does not isolate that change. Keep the original collection as your rollback.

  1. Join a test call and confirm that Discord sounds normal in your headphones before opening an OBS recording.
  2. In OBS, add Application Audio Capture for Discord and choose its active window. Name it Discord — audience. Capture the game separately.
  3. In Settings > Audio, disable global Desktop Audio in the duplicated collection for this separated setup. Inspect the scene for any Audio Output Capture source recording the same headphone device.
  4. Keep your own microphone as a separate input. Do not mistake the microphone input you send into Discord for the voices you receive from other people.

Use the OBS application-capture guide if the window selector is unfamiliar. Do the first recording before changing matching rules, then repeat it after restarting Discord. Write down the working selection instead of relying on memory when setting up a later call, or keep a shareable endpoint checklist from the Discord & OBS routing helper.

Mute the audience feed, not the call itself

Use the Discord source's output mute control in the OBS mixer. Do not lower Discord's own volume when the goal is to keep hearing the call. Avoid enabling OBS monitoring for a call you already hear directly: a second delayed copy makes it harder to judge which path is reaching you.

Current OBS separates the mixer’s speaker mute and headphone monitoring controls. The 32.2 release notes explain why older tutorials showing “Monitor Only” no longer match the interface. Your own hearing is not evidence of what OBS is transmitting.

Prove the separation with a short recording

  1. Record three labeled segments: game only, teammate only, and your own microphone only. Use a harmless test phrase instead of a private conversation.
  2. Mute Discord in OBS and repeat the teammate segment while confirming you still hear it through the headset.
  3. Stop recording and play the mixed track you intend to stream. The second teammate segment should be absent; game and your microphone should remain present.
  4. Repeat after changing scenes, rejoining the call, and restarting Discord. Test any hotkey or controller button you plan to use on air.

Excluding Discord from the stream’s selected track does not remove it from other recording tracks. Conversely, muting the source’s output affects its recorded output too; it is not a per-track mute. Inspect each enabled recording track before sharing the file. The separate-track guide covers that distinction.

If Discord still appears in the recording

Mute every OBS audio source, then enable them one at a time while the test caller speaks. The first unexpected source that brings the voice back identifies another capture path. Inspect nested scenes, device captures, and any monitored signal returning into a captured output. Remove the duplicate route and repeat the recording; changing the intended Discord source cannot control a second copy.

If the dedicated source stays silent, reselect the active Discord window and check whether the app is producing sound. Keep a known working scene or saved settings available while you troubleshoot. Do not restore broad Desktop Audio just before going live without rechecking the call: that can undo the separation you were trying to establish.

To map Discord onto its own recording stem—or keep private voice chat off your live mix without muting your headphones—load the Private Discord preset in the OBS multitrack audio planner. Once your call has its own fader, follow how to balance your mic, game, Discord, and alerts in OBS so teammates stay clear over gameplay.

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.