Monitoring in OBS is the operator’s local listening path. It lets you hear a sleep-sounds source through a selected device, while the stream or recording output is a separate path that must be checked on its own.
For a source that should be heard by you and your viewers, select a monitoring device in OBS, set the source to the combined monitoring mode, and test the result with a short recording or test stream. The exact labels and routing behaviour can vary between OBS versions, so confirm what your installed version shows before leaving the channel unattended.
Understand the two audio paths
A source can be active in the OBS mixer without proving that you hear it locally or that viewers receive it. The mixer shows activity inside OBS. Monitoring sends that source to the device configured for monitoring, such as headphones or a monitor output. Stream and recording output sends audio onwards to the broadcast or saved file.
These paths are related but not identical. You might hear a source locally while it is excluded from the stream, or see a meter moving while your selected listening device receives nothing. That is why a sleep-sounds channel needs a short check of both sides before a long broadcast.
The OBS Audio Mixer Guide describes the monitor control as playing a source through the monitoring device configured in Settings. Read the OBS Audio Mixer Guide alongside the controls in your installed build, rather than assuming that a setting from an older tutorial has the same name.
For example, imagine that rain audio is playing from a local file. The operator should hear the rain through headphones, and a recording made from the same scene should also contain it. Hearing the rain in the headphones alone is not enough evidence that the audience feed contains it.
Select the monitoring device in OBS
Open OBS and go to Settings > Audio. Find the monitoring device setting and choose where you want OBS to send monitored audio. The available choices depend on the computer, operating system, sound hardware and connected devices.
Headphones are often practical while configuring a sleep stream because they let you listen without sending the signal back into a microphone or room speaker. Another suitable output may be appropriate if the channel is being operated from a control room. The important point is that the selected device is the one you are actually listening to.
After choosing the device, apply the setting and return to the main OBS window. If the device is disconnected, renamed by the operating system or changed after OBS starts, the monitoring route may no longer behave as expected. Check the selection again if the meter moves but you cannot hear anything.
The monitoring device is not the same as a scene-level audio source. It tells OBS where to play monitored audio. It does not, by itself, add a microphone, system sound or file to the stream. If your source is a device capture, OBS has separate source controls for bringing that device into a scene.
OBS documents several ways to add audio sources in its Audio Sources guide. The guide also warns that capturing a device in a scene while selecting the same device as a global audio device can create an echo. Keep that distinction in mind before troubleshooting the monitoring setting.
If the computer has several outputs with similar names, identify the one connected to your headphones or monitor. A test tone or short audio file can help, but do not rely on the name alone. Some systems expose a monitor jack, a built-in speaker output and a display audio output as separate choices.
Add the sleep-sounds source
For a local rain, fan, brown-noise or ambient recording, add a Media Source to the scene that will be broadcast. Give it a clear name such as Rain loop or Night ambience, so you can identify it later in the mixer.
In the Media Source properties, select the local file. OBS lists formats including .mp3, .aac, .ogg and .wav in its Media Sources guide. The file must be available to the computer running OBS, and the scene containing it must be the one used for the broadcast.
If the audio is part of a video file, the Media Source may also carry the file’s visual output. If you are using a still image or another visual layer for the stream, check the source properties and scene arrangement so that the audio source is present even when the visual design is simple.
For a device such as a microphone or another audio input, use the capture source that matches your operating system and equipment. Do not add a device capture simply because it appears in a tutorial. A sleep stream normally benefits from a deliberately small source list: the intended file or input, the required visual sources and nothing that could add room noise or a duplicate signal.
If your channel is built around an always-on music or devotional format, the same separation helps when you expand the setup. The advice in How to set up an always-on Indian music channel on YouTube is relevant here because source organisation matters more as the number of files and scenes grows.
Open Advanced Audio Properties
With the source visible in the Audio Mixer, open its audio settings. Depending on the OBS version and interface layout, you can use the mixer’s settings menu or go through Edit > Advanced Audio Properties. Select the row for the sleep-sounds source.
This window contains per-source audio controls, including the monitoring choice. The setting belongs to the source, not just to the whole scene. If you have a rain file in one scene and a separate fan file in another, inspect each source that may be used during the broadcast.
Before changing anything, confirm the row name. It is easy to alter a similarly named microphone, desktop-audio source or duplicate media source by mistake. A clear naming scheme is more useful than a long collection of unnamed sources.
The mode names and their exact routing behaviour should be checked against the installed OBS version. The practical labels commonly shown in OBS are described in forum guidance, but that is not a current, versioned official reference for every release. Treat the labels below as a way to understand the choice, then verify what your own build does.
Choose the monitoring mode
The monitoring mode answers a simple question: should this source be played to your local monitoring device, the stream or recording output, or both?
| Mode shown in OBS | Local monitoring | Stream or recording output | Suitable use |
|---|---|---|---|
| Monitor Off | No | Depends on the source and output configuration | When you do not need to listen locally |
| Monitor Only (mute output) | Yes | No for that monitored source | Checking a source privately |
| Monitor and Output | Yes | Yes | A viewer-facing sleep source that you also need to hear |
These labels and their routing semantics are not guaranteed to be identical across OBS versions. Confirm the result with a recording or test stream rather than treating the table as a promise about every installation.
Monitor Off means that OBS does not send the source through the monitoring device. It does not automatically mean that the source is absent from the audience output. A source can still be part of the stream or recording according to the rest of the audio configuration.
Monitor Only (mute output) is useful for a private check. It lets you listen locally while excluding that source from the stream or recording. This is appropriate for checking a microphone or a file before broadcast, but it is not the right final mode if viewers need to hear the sleep sounds.
Monitor and Output is the intended choice when both paths are required: you want to hear the source locally and you want it included in the stream or recording. Select it for the sleep-sounds source only after confirming that the installed version uses the same label and behaviour.
Do not confuse local monitoring with audience output. Viewers do not need you to monitor a source locally in order to hear it, and you should not use your own headphones as proof of what YouTube receives. Monitoring is an operator check; the recording or test stream is the audience-path check.
Use Monitor and Output carefully
Set the sleep-sounds source to the combined mode if the local and audience paths are both intended. Start playback and watch the mixer meter. Then listen through the selected monitoring device while checking that the source remains enabled in the scene used for streaming.
Keep the monitoring volume comfortable. Sleep audio is often played for long periods, and a monitoring check should not become a reason to listen at a level that is unpleasant or unsafe. This is a listening decision for your equipment and room, not a universal OBS setting.
Watch the mixer for peaks. OBS explains that digital audio reaches its maximum convention at 0 dBFS and that audio at or above the ceiling can clip. The OBS Audio Mixer Technical Details also discusses meter references such as the alignment level and permitted maximum level. Those engineering references are not a recommended loudness target for every sleep-sounds file.
A quiet recording can still be unsuitable if it contains sudden peaks, clicks or a sharp transition when the file loops. Listen through the beginning, middle and end of the file. If the loop joins two sections with different background levels, the monitoring mode will not fix that edit; you need to correct the source file or choose a better loop point.
If you hear an echo, mute possible duplicate inputs one at a time. Common causes include the same device being enabled globally and added again as a scene source, or the monitoring playback being captured back into OBS as another input. The OBS guide on audio sources specifically notes the duplicate-device echo risk.
Loop a local file with a Media Source
Monitoring controls whether you hear a source. They do not determine whether that source repeats. For a single local sleep-sounds file, open the Media Source properties and enable Loop. OBS then plays the file again when playback completes, subject to the behaviour of the installed version and the file itself.
Keep the loop setting separate from the monitoring setting when troubleshooting. If the file plays once and stops, inspect Loop. If the file meter moves but you cannot hear it, inspect the monitoring device and mode. If you hear it but the recording is silent, inspect the output path and test recording.
A single looping file is simple to inspect, but a long stream may need several tracks or a playlist. OBS documents a VLC Video source with a Loop Playlist option, and VLC must be installed for that source to appear. Use it only if the playlist workflow is useful for your channel and confirm the transitions before going live.
For broader playlist design, see how to make a YouTube livestream playlist loop continuously. The playlist itself does not replace an audio check: each file can have a different level, channel layout or silence at its beginning.
If a gap matters to your format, test the transition rather than assuming that a loop is seamless. A sleep audience may notice a sudden cut, a restart click or a period of silence even when the visual scene does not change. The Media Source’s loop option controls repetition, not editing quality.
Check for duplicate routes and echo
Before testing the final scene, simplify the audio path. Keep the intended Media Source or input, the selected monitoring device and the required output. Temporarily disable sources that are not needed for the sleep stream.
A duplicate global and scene-level capture can send the same sound into OBS twice. The two copies may arrive at slightly different times, producing an echo or a fuller but unclear sound. Monitoring that result can make the problem seem like a headphone fault when it is actually a duplicated input.
Also avoid capturing the output of your headphones or speakers back into OBS. If a microphone is open in the same room, it may pick up the monitoring playback and send it back into the stream. Use headphones while testing if that helps isolate the source, and mute any input that is not part of the intended broadcast.
Check the source’s mute state, scene visibility and mixer fader. A source can be correctly monitored but muted in the scene, or present in another scene that is not currently live. These basic checks are more useful than repeatedly changing the monitoring device.
If the audio path remains unclear, make a new test scene containing one visual source and one Media Source. Set the file to loop, choose the monitoring device, select the intended monitoring mode and record a short sample. Add complexity only after that simple path behaves as expected.
Verify the local and audience behaviour
Do not start with an overnight broadcast. First, make a short recording using the same scene, source and audio settings that you plan to use for the live stream. Listen to the recording from beginning to end, including a point where the file loops if the test is long enough to include one.
During the test, check four things:
- The source meter moves when the file plays.
- You hear the source through the selected monitoring device.
- The saved recording contains the source.
- The source continues after its loop point without an unexpected gap, click or duplicate sound.
A moving meter proves that OBS has signal activity at that point in the chain. It does not prove that your headphones are receiving the signal or that YouTube viewers will receive it. The recording is the quickest way to inspect the output path without asking viewers to diagnose your setup.
If you plan to stream to YouTube, use a private or otherwise appropriate test arrangement and inspect the result from the viewer side. Follow YouTube’s current guidance for live streaming and visibility before choosing how to test. You can also consult OBS’s Quick Start Guide, which recommends testing before going live.
Check the stream’s audio while the source is playing, not only when OBS is open locally. If the local headphones sound correct but the viewer-side test is silent, return to the source’s monitoring mode, mute state, scene selection and output settings. If the viewer hears audio but you do not, return to the monitoring device and local output path.
When the test is complete, write down the working scene, source name, monitoring device and mode. This small record is useful if the operating system changes its default output or if you reconnect headphones before the next session.
For a channel that stops when the operator’s computer is turned off, local OBS monitoring is only part of the operating decision. The discussion in how to fix a YouTube livestream that stops when your computer is turned off can help you separate the local setup from the question of where the stream should run.
If your aim is a genuinely unattended schedule, remember what this OBS procedure does and does not establish. It checks the audio path you configured. It does not guarantee that a computer, connection, source file or YouTube broadcast will continue without interruption.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Do viewers hear audio if I do not monitor it locally?
They can, depending on the source and output settings. Local monitoring is for your listening device; it is not a requirement for audience audio. Confirm the viewer path with a recording or test stream rather than relying on your headphones.
Which OBS mode should I use for sleep sounds?
Use the mode labelled Monitor and Output when you want to hear the source locally and include it in the stream or recording. Labels and routing behaviour can vary by OBS version, so verify the result in your installed build.
Why does my sleep file play once and stop?
Open the Media Source properties and check that Loop is enabled. If you are using a playlist, check the playlist source’s loop setting and confirm that the required media software is installed.
Why do I hear an echo after enabling monitoring?
The same device may be captured globally and again as a scene source, or the monitoring playback may be returning through a microphone. Disable duplicate inputs, avoid capturing your headphone output, and use a short recording to identify which path is adding the second signal.