Skip to content
saturalabs

OBS Audio Monitoring: Hear Sources and Fix Common Problems

Set up audio monitoring in OBS Studio, understand Monitor Only versus Monitor and Output, and troubleshoot silence, echo and missing recordings.

In this guide
The short version

Choose a monitoring device in OBS Audio settings, then select a monitoring mode for each source in Advanced Audio Properties. Record and play back a test: hearing a source yourself does not prove viewers will hear it.

Audio monitoring in OBS Studio sends selected sources to a listening device such as your headphones. To hear a source and include it in your output, choose your monitoring device in Settings → Audio and select Monitor and Output for that source in Advanced Audio Properties. Then record and play back a test to confirm the intended audio is actually in the file.

Monitoring and recording are different signal paths. A moving meter shows that OBS is receiving a signal; it does not by itself prove that your headphones, stream and recording are all receiving the right mix. OBS's Audio Mixer Guide recommends checking levels and listening to a recording before going live.

What the three monitoring modes mean

Choose a mode for each source
ModeMonitoring deviceOBS output
Monitor OffOBS does not send that source to the monitoring device through its monitoring path.The source can still be sent to selected output tracks.
Monitor Only (mute output)OBS sends the source to the monitoring device.The source's normal output path is muted; do not use this if that source must be heard in the recording or stream.
Monitor and OutputOBS sends the source to the monitoring device.OBS also sends it to the selected output tracks, subject to routing and source settings.

Monitoring is set per source, not as a guarantee that you hear the complete final mix. Other capture paths can still send sound elsewhere or accidentally capture your monitored output again. The OBS community's explanation of monitoring and output describes these separate destinations.

How to set up audio monitoring in OBS

  1. Connect your headphones. Select the output device you intend to use and set a comfortable listening volume. Headphones reduce the chance that speakers feed sound back into your microphone.
  2. Choose the monitoring device. In OBS, open Settings → Audio and find Monitoring Device in the Advanced section. Choose your headphones or intended output, then apply the setting. A system default can change when devices are connected or switched.
  3. Find the source. Activate the scene and play or speak into the source while watching its meter in the Audio Mixer. A missing or still meter calls for an input or capture check before a monitoring adjustment.
  4. Open Advanced Audio Properties. Use Edit → Advanced Audio Properties or the Audio Mixer source menu. In the Audio Monitoring column, select Monitor and Output for a source you need to hear and send to the recording or stream.
  5. Check the whole path. Verify the source is unmuted as intended and assigned to the output track you are testing. Record a short sample with a recognizable sound from each source, then play the file back and check each intended track. For a stream, use a private test where possible.

Menu labels and device availability can vary by OBS version and operating system. If you can already hear a source directly through hardware or an application, enabling OBS monitoring may create a second, delayed copy. Monitor only what you need and compare the saved output.

Which mode should I choose?

For a media source or capture card that must be heard by you and viewers, start with Monitor and Output and verify the result. For a microphone that you hear directly through an audio interface, Monitor Off can avoid hearing two copies while still allowing the mic into assigned output tracks. Monitor Only is useful for a source intended solely for your own monitoring, but it normally removes that source from OBS's output path.

Some setups route audio between devices or applications in ways that differ from these examples. An OBS meter, your headphones and the actual stream or file each answer a different question. Use short tests rather than assuming a particular checkbox proves the result.

Fix audio monitoring that is not working

Test one source at a time
What you noticeWhat to check
The meter moves, but headphones are silentCheck the selected monitoring device, its system volume and the source's monitoring mode. Make sure the device is connected and not redirected to another output.
You hear it, but the recording does notCheck that the source is not set to Monitor Only, then verify source mute state, track assignments and the track used in the recording. Test the saved file.
Nothing moves on the meterCheck the active scene, capture source, device selection and permissions. Monitoring cannot fix a signal OBS is not receiving.
You hear an echo or delayed voiceCheck for direct hardware monitoring plus OBS monitoring, duplicated captures, speakers feeding the microphone, or a monitored device being captured again.
A source is missing after changing devicesCheck whether the system default changed and confirm both the capture and monitoring devices. Run another short recording test.

A monitoring output routed back into a captured desktop device can create a loop or duplicate audio. Review your routing and avoid recapturing the monitoring path. OBS describes avoiding duplicate desktop and application capture in its application audio capture guide. If a particular version behaves unexpectedly, test with a simple scene and consult current OBS release notes and support resources.

Monitor tracks and check the final file

Audio monitoring is not the same as assigning sources to independent recording tracks. If you want to edit microphone and gameplay separately, configure the sources and recording tracks, then open the saved file in software that can inspect all of its tracks. Some players play only one track by default. Follow the OBS separate tracks guide for the recording workflow.

For commentary over music, OBS audio ducking uses a compressor to lower the music in response to your microphone. Monitoring helps you listen to the setup; it does not perform the ducking itself.

Can monitoring remove background noise?

No. Monitoring lets you hear a signal so you can find issues; it does not remove noise. Fix the source first where possible: move the microphone, reduce room noise and check levels. See how to reduce microphone background noise for diagnosis.

For a saved recording, the Saturalabs voice isolator can test an estimated voice separation after upload. It is not a live OBS filter, and results may retain noise or change wanted speech. AI WAV downloads require an account and sufficient credits; keep the original and compare the result before downloading.

Common questions

Why can I hear my voice twice?

One copy may be coming directly from your interface and another through OBS, or a monitored output may be captured again. Identify each route one at a time and listen to the recording to see which copies are present.

Does Monitor Off mute the stream?

No. It turns off OBS monitoring for that source; the source can still reach assigned output tracks. Confirm the output with a test recording or stream.

Do I need a monitoring plugin?

OBS includes per-source audio monitoring. Check its built-in device and mode settings first; a plugin may offer different routing features but is not required for the basic workflow above.

From the Saturalabs journal

Practical notes on sound isolation, music, and clearer dialogue. About our guides ↗

Your next step

Work with a saved voice recording

Compare voice isolation on an uploaded recording after your session. AI WAV downloads require an account and credits.

Open the tool