STREAMING GUIDE / OBS STUDIO

OBS audio monitoring: hear the source without a loop

Check the local listening path separately from the stream and recording. A working meter does not prove that either destination is correct.

START HERE

Choose the intended Monitoring Device in OBS audio settings, then enable monitoring for one known-working source. On current OBS, the monitor and output-mute controls are independent. Verify headphones and a saved recording separately; avoid capturing the monitoring destination again.

First, identify which controls your OBS version uses

The Audio Mixer changed in OBS 32.1, adding a dedicated monitoring button. OBS 32.2 then removed the redundant Monitor Only option from Advanced Audio Properties because mute and monitoring are controlled independently. Older tutorials showing three monitoring dropdown choices may not match your installation.

Use the 32.2 release notes and the current mixer guide to identify the controls. The speaker button controls whether the source is muted to output; the monitor button enables local listening through the configured monitoring device. Test both destinations rather than inferring one from the other.

Build a small listening test

  1. Use wired headphones or a known-working output for the first check. Play ordinary computer sound to confirm the headphones themselves work.
  2. In OBS Settings > Audio, find Monitoring Device in the advanced options and select that named output.
  3. Use one source whose mixer meter is moving, such as a short Media Source clip. Leave other sources unmonitored for now.
  4. Enable that source’s monitor control. Listen at a low level.
  5. Make a separate local recording and play it afterward to check whether the source is also in the intended recorded mix.

If the source meter never responds, solve capture or playback first. Monitoring cannot manufacture audio missing at the source.

Use the two controls for the result you want

GoalMonitorOutput mute
Audience hears it; you do not monitor itOffUnmuted
You and the audience hear itOnUnmuted
Private cue in your headphonesOnMuted
Silence both routesOffMuted

Output still depends on active-source and track routing. On OBS 31 and earlier, the corresponding dropdown labels are Monitor Off, Monitor and Output, and Monitor Only (Mute Output); muting the mixer speaker button on OBS 31 or older silences both output and headphone monitoring, so leave the speaker unmuted and choose Monitor Only (Mute Output) for a private cue. This table is a routing target, not a promise that every saved profile or third-party control surface uses identical buttons.

A private cue is only private if no other source captures the monitoring device. Always test that assumption in a saved file.

If monitoring remains silent

Compare a Media Source with the problem source. If neither is audible, focus on the monitoring output: reconnect the device, reselect its explicit name, apply the setting, and check the operating system’s app mixer for OBS. If the device was unavailable when OBS started, stop the session and restart OBS after reconnecting it. You can confirm the headphones play both channels outside OBS with the headphone stereo test.

If one source works and the other does not, compare their individual monitor state and source activity. In Studio Mode, check the Program scene you are actually sending, rather than assuming an item visible in Preview is live. Re-enable sources one at a time so a working route remains available for comparison.

If monitoring creates echo or delay

Turn monitoring off and compare a saved recording. If the duplicate disappears, check whether Desktop Audio or another output-capture source is recording the monitor destination. Keep that loop out of the mix by changing the destination or capture design; see the duplicate-route checklist.

Hearing your own microphone later than you speak can be normal for a software listening path. Compare headphones connected directly to an audio interface, if it provides direct monitoring, with OBS monitoring. These are different paths and may include different processing. Bluetooth and phone listening routes can add further delay; do not tune camera synchronization from headphone delay alone.

Check mutes and scene changes before the real session

Record a sequence where you enable monitoring, mute output, disable monitoring, and unmute output while saying which control you pressed. Listen to the file after stopping; separately note what you heard live. Repeat for a scene transition and any Stream Deck OBS audio control or hotkey mute you rely on.

Can this feed a phone? It can become part of a deliberate output route, but any extra playback link needs its own checks. MicDrop can send a supported desktop output to a phone; that does not make the phone a zero-delay studio monitor or change OBS track assignments.

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.