To mute one source’s sound in OBS while keeping your YouTube stream running, click the speaker-shaped mute button on that source’s row in the Audio Mixer. Leave its Sources eye icon enabled if its picture should remain visible; that eye controls visibility, not audio.
The key is to identify the right mixer row before changing anything. If the sound carries on after you mute it, another source may be capturing the same device or application, so check for a duplicate audio path rather than muting the whole stream.
Find the source in the Audio Mixer
The Audio Mixer is where OBS presents audio sources and their individual output controls. Find the source whose sound you want to stop, then use its row’s speaker-shaped mute button. OBS describes this control as muting or unmuting that source to your output in its Audio Mixer Guide.
If the Audio Mixer is not visible in your OBS layout, look through the dock or layout options to bring it back. Its position can vary with a customised workspace, so do not assume it has disappeared from the programme. You need the mixer row, not the Sources list, to mute one source’s sound.
A source’s name in the mixer is the starting point, but it may not describe the content as clearly as you expect. A media source could have a file name, an application capture might be named after a window or programme, and device audio could use a microphone or capture-device label. Take a moment to match the name to the sound you mean to stop.
This is a source-level action. It is different from muting the stream’s master output, changing your computer’s volume, or turning off a device for every scene. Those broader changes can affect other sounds you intend to keep. For example, muting desktop audio to silence a music application might also remove browser notifications or other computer audio that your scene uses.
If you are looking into an OBS sound problem more generally, the audio settings checklist for media sources covers a different symptom: when a source is not audible as expected. Here, the objective is narrower: stop one source from reaching output without stopping the broadcast or removing its picture.
Identify the correct audio row
Before clicking anything, compare the mixer row names with the sources in the scene you are using. OBS can contain multiple sources that produce sound, including media, microphone, desktop audio, and audio capture sources. A row that sounds plausible is not necessarily the one currently carrying the sound you want to mute.
When practical, use the mixer’s activity indication while the sound is playing. See which row responds when the target sound occurs. If several rows respond together, do not assume they are all separate sounds: more than one may be capturing the same device or application. That possibility matters because muting one row will not silence a second capture path.
The problem can also come from a source that is not obvious in the current scene. Review the audio sources available in the active scene and any global audio devices configured for OBS. The OBS Audio Sources guide explains the different ways audio can enter OBS. Use the names and activity you see to narrow down what is actually reaching the mixer.
For example, imagine a devotional video source playing bhajan audio while desktop audio is also capturing the computer’s output. If both the media source and desktop audio carry that same sound, the mixer can show activity on both rows. Muting the media source row stops that source’s contribution, but desktop audio may continue to send the same material. The right diagnosis is a duplicate route, not a failure of the mute button.
Make the smallest change that addresses the intended sound. If the target is a microphone, select its input row rather than a music source. If it is an application, determine whether OBS captures the application directly or receives it as part of desktop audio. A clear source-to-row match makes troubleshooting easier and reduces the chance of removing audio from the rest of the scene.
Mute with the speaker button
Once you have identified the row, click its speaker-shaped button. That mutes the selected source to OBS output. The OBS guide calls it the “Mute Button” and describes its purpose as muting or unmuting the source to your output. Click the same control again if you need to restore that source’s audio.
The control applies to that mixer source, not every other source in the scene. If you want a music bed to stop while spoken announcements continue, mute the music source’s row rather than the master output. If you want a microphone to stop while the background video continues, mute the microphone row. The distinction is useful in a local news loop, study channel, or ambience stream where several audio elements can have different roles.
A mixer mute does not promise to silence every route carrying the same sound. If desktop audio and a media source both include the same music, muting only the media source leaves desktop audio untouched. Do not use a source-level mute as evidence that another capture path is inactive; check the other rows and your configuration if the sound persists.
You do not need to reach for recording-track settings to perform this live mute. OBS’s multiple audio track recording guide discusses tracks for recording and later editing. Those controls serve a different purpose from muting a source in the live Audio Mixer. If you want to keep separate versions of audio in a recording, that is a separate setup question; it is not the first control to use when silencing one live source.
Keep the video visible with the Sources eye
The eye icon in the Sources dock changes whether a source is shown in the scene. Leave the eye enabled when you want the video to remain visible. OBS’s Sources Guide documents the eye control as a way to hide or show a source; it does not replace the mixer’s audio mute.
This separation matters when the source combines video and audio. A looping background clip, for example, might need to stay on screen while its soundtrack is muted. Use the mixer speaker button for the audio and leave the Sources eye alone for the picture. Clicking the eye instead hides the source from view, which changes the visual output rather than addressing the audio you meant to stop.
| OBS control | What it changes | Does the picture stay visible? |
|---|---|---|
| Audio Mixer speaker button | Mutes or unmutes that source’s audio to output | Yes, if the source remains visible |
| Sources eye icon | Hides or shows the source in the scene | No, when the source is hidden |
This table describes the intended effect of each interface control. A custom setup can route audio in other ways, so use the meter activity and an output check to confirm which signal remains. If your aim is to remove both the picture and its sound, hiding the source may be appropriate, but it is not the audio-only action.
In a long-running visual stream, such as rain sounds or a study loop, the image may be the reason the source is present even after its audio is no longer wanted. Keeping the eye enabled avoids needlessly removing the picture from the scene. For ideas on the broader operating arrangement, see how a cloud service can run a 24/7 rain sounds channel; it is separate from the OBS controls described here.
Check for duplicate audio capture paths
If viewers can still hear the target sound after you mute the suspected row, look for another row carrying it. Check both scene-level sources and global audio device selections. OBS warns that adding a device as an Audio Input or Output Capture source while also selecting it globally can cause echo; its Audio Sources documentation covers this risk.
For application audio, check whether the application is captured directly and also included in desktop audio. OBS’s Application Audio Capture guide explains the application-specific option and cautions against leaving duplicate global desktop audio capture enabled when using it. The guide’s stated support includes Windows 10 version 2004 or later and Windows 11. If you use a different operating system or setup, check the current OBS documentation rather than assuming the same capture option is available.
Work through the routes methodically:
- Keep the target sound playing at a manageable level and observe which mixer rows show activity.
- Mute the row you believe corresponds to the source, then check whether the sound is still present in the output.
- If it remains, inspect other active rows for a second capture of the same application or device.
- Review global audio-device selections as well as sources added to the scene. Look for a device selected in both places.
- Change only the duplicate route you have identified, then check the output again.
Treat this as a diagnosis, not a reason to mute every row with activity. Some rows may be carrying separate audio that belongs in the stream. In the devotional example, the media source might be carrying the file’s audio and a microphone might be carrying a presenter. If only the file sound should stop, muting both would remove more than intended.
An echo can be a clue that one signal is arriving twice, but a persistent sound after muting can also mean you chose the wrong row or that routing is more involved than expected. Use what the meters and output check show; do not conclude that one mixer row controls all copies of a signal. The behaviour of a heavily customised routing setup may differ from the straightforward source-level case described here.
Test the stream audio before leaving it running
After muting the row, check the resulting output. A preview or local monitoring check can help, but confirm that you are listening to the stream output you intend to assess, not just the source inside your own setup. OBS’s mixer documentation supports the source mute control; it does not guarantee how every custom route or YouTube-side configuration will behave.
If you hear the unwanted sound, return to the mixer and inspect for another active capture path. If you no longer hear it, also check that the audio you meant to keep is still present. A change can solve the immediate problem and still remove a useful sound by mistake, especially if multiple sources have similar names or the same device is configured in more than one place.
For a 24/7 channel, record what you changed in your operating notes: the source row muted, any duplicate path found, and the check you used to confirm the result. That makes it easier to undo the change when you later need the sound again or when another person takes over the stream. If you are troubleshooting the broadcast as a whole, the guide to monitoring and troubleshooting a YouTube live stream can help put this single audio check into a wider monitoring routine.
Do not use a recording’s multiple audio tracks as a substitute for checking live output. Separate tracks can be useful when editing a recording later, but the live question is whether the intended source is still reaching the broadcast. Keep the test focused: the unwanted audio should be absent, the wanted audio should remain, and the picture should still be visible if that is part of the plan.
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
Will muting one OBS mixer row stop the whole YouTube stream?
No. The speaker button mutes the selected source to output, rather than stopping the broadcast. Check other mixer rows if the same sound is still audible through a separate capture path.
Can I mute a video source and keep its picture on screen?
Yes. Mute its audio with the speaker button in the Audio Mixer, and leave its Sources eye enabled. The eye controls whether the source is shown in the scene, not whether its audio is muted.
Why can I still hear the sound after muting the source?
Another row may be capturing the same device or application, or you may have selected a different row from the one carrying the sound. Check scene-level sources and global audio-device capture for duplicates, then test the output again.
Should I use audio tracks to mute a live source?
Not as the first step for this task. OBS describes multiple audio tracks as a recording and editing feature; use the source’s Audio Mixer mute button for the live source-level change, then verify your output.