If a media source has no sound on your YouTube stream, trace it from the file to OBS’s source meter, then through the stream track and YouTube’s live preview. The first useful question is whether the meter for that specific source moves while the media should be playing; that tells you which part of the path to check next.
A moving meter is evidence that audio has reached that point in OBS, not proof that viewers receive it. Work through the checks in order, changing one thing at a time so you can tell whether the fault is playback, routing, encoding or YouTube ingestion.
Check that the media source is playing
Start with the source itself, before changing audio settings. In the active scene, confirm that the media source is present and enabled, that the correct file or playlist item is selected, and that playback has started. A file that is paused, waiting to restart, or inactive because its scene is not active may produce no audio at the time you check it.
For OBS’s built-in Media Source, open its properties and verify the file path. OBS documents common video formats including MP4, MOV, MKV and WebM, and audio formats including MP3, AAC, OGG and WAV; check the current OBS media sources guide if the file is in another format or playback behaves unexpectedly. The same properties include controls such as Loop, Restart playback when source becomes active, and Close file when inactive. Their effect depends on how the source is used in your scenes, so check them against the intended playback behaviour rather than toggling them at random.
A VLC Video source is different from the built-in Media Source. VLC must be installed for that source type, and VLC Video has an Audio Track selector that defaults to track 1. If a playlist file contains more than one audio track, confirm that the selected item and track are the ones you expect. Do not look for this VLC-specific selector in the built-in Media Source properties.
If your aim is to play a long devotional or music playlist continuously, also check that the file order and loop behaviour are right; audio routing cannot fix a playlist that has stopped. The practical checks for confirming a continuous playlist are covered in how to check whether a church’s continuous YouTube stream plays the full playlist.
Use the source meter as your first branch
With the media playing, find the mixer entry for that specific media source and watch its meter. Do not rely only on Desktop Audio or a microphone meter: those represent other audio paths and may move even while the media source is silent.
If the source meter does not move, audio is not reaching that meter at the moment. That can mean the file has not started, the wrong source or playlist item is active, or the media’s audio track is missing or unavailable. Return to the playback and source-property checks before changing stream output settings. For a VLC Video source, confirm VLC is installed and the intended Audio Track is selected.
If the source meter moves, OBS is receiving audio at that measurement point. That narrows the search, but it does not show that the source is unmuted, assigned to the streaming track, or included in the encoder output. Continue to the mixer and routing checks rather than treating meter movement as the end of the diagnosis.
Meter position is useful when isolating a problem. OBS’s audio mixer technical details explain that the input level is measured after filters but before the fader. A missing input indication means no audio has reached that measurement point; it can also simply mean there is no audio available yet, for example before playback begins. This is why you should watch while the file is actually meant to be producing sound.
If you do not see a separate meter entry for the source, check that you are viewing the expected scene and mixer sources. Some setups capture an application or a device rather than treating the media as a direct source. In that case, follow the audio path you actually configured instead of assuming the desktop meter represents the file.
Check mute, fader, filters and monitoring
Once the source meter moves, inspect the source’s mixer controls. Confirm it is not muted and that its fader is not at the bottom. A low fader can make the signal very quiet; a mute or a fader at zero can prevent it reaching the mix at a useful level. Make a small, reversible adjustment and observe the meter rather than changing several controls together.
Next, open Advanced Audio Properties from the mixer gear or the Edit menu and review the source’s settings. Check filters if the readings or sound seem inconsistent. Because the input meter is after filters, temporarily disabling a source filter can help establish whether it is suppressing the signal. Re-enable or adjust filters deliberately once you know their effect; do not leave a filter removed if it provides an intended function such as noise control or level management.
Audio monitoring can help you listen to the source through the monitoring device configured in OBS. The OBS audio mixer guide describes the mixer’s mute and monitoring controls and the Advanced Audio Properties route. Set the monitoring device in OBS settings, choose an appropriate monitoring mode for the source, and listen while the file plays. If monitoring is silent, check the monitor mode, selected device and source path.
Monitoring headphones are a diagnostic aid, not a stream-routing fix. Hearing a source through OBS monitoring shows that this listening route works; it does not prove that the source is assigned to the stream output track or audible to viewers. Conversely, monitoring silence can reflect a monitoring-device problem rather than a missing stream signal. Keep those paths separate in your diagnosis.
If an Audio Input/Output Capture source is involved, check that you have not captured the same device twice, once as a scene source and again in global audio settings. OBS notes that duplicated capture can create echo. Device selection also varies across Windows, macOS and Linux, so use the guidance for your operating system instead of applying a single device instruction to every computer.
Verify the track selected for streaming
A source can show a healthy meter and still be excluded from the live mix if its track assignment does not match the track OBS is sending to the stream. In Advanced Audio Properties, inspect the track boxes for the media source. Then check the active streaming audio track in OBS’s applicable Output settings. Menu labels can change between OBS versions, so verify the streaming selection in the version you have installed.
Be careful not to confuse recording tracks with the live stream track. OBS’s multiple audio track recording guide explains separate tracks for recordings and editing; that information does not by itself confirm which track your current stream uses. A recording may contain audio on one track while the live output uses another, or vice versa.
For a straightforward stream where you do not need separate audio mixes, keep the setup simple: assign the media source to the track selected for streaming, and confirm any other sound you want viewers to hear is assigned there too. If you deliberately use separate mixes, document which sources belong on which track. Avoid ticking every track as a guess, because that can obscure the actual routing and may send audio you did not intend.
A short local recording can be useful here, but interpret it carefully. Recording settings may select different tracks from streaming settings. If the local file has sound, that is evidence about the recording path, not conclusive proof that the same audio is reaching YouTube. The next check should still be the actual streaming track and output.
Check encoder and stream output configuration
If the source plays, its meter moves, and track assignment appears correct, test the encoder path before blaming YouTube. Make a short test recording or local archive using the same scene and media playback, then listen to it. OBS recommends a brief test before going live in its Quick Start Guide. If the local test has no media audio, return to the OBS source, filter and routing checks.
If the local recording sounds right but the live stream does not, confirm that you have checked the streaming track rather than assuming the recording’s settings carry over. Review the applicable stream output and encoder configuration. The goal is to establish whether OBS is actually sending an audio stream with the video, not to apply an arbitrary preset.
YouTube’s live-stream error guidance identifies issues including no audio stream, multiple audio streams, an unsupported audio codec, and sample-rate or bitrate problems. Its guidance lists AAC or MP3 for audio codecs and refers to 44.1 kHz and 128 Kbps in relevant error messages. These are platform guidance points, not a guarantee that changing one value will solve every silent stream. Check the current message shown for your event and the protocol you selected, since platform recommendations and error details can change.
If OBS offers more than one audio stream or track for the chosen output, inspect that configuration rather than assuming YouTube will select the intended one. Use the error reported by the encoder or Live Control Room to guide the next test. Record what you changed so that, if the result worsens, you can restore the known configuration.
For a long-running channel, a local test also helps separate a media problem from an unattended-computer problem. If you rely on a personal computer staying on overnight, consider the practical risks of sleep, updates and a dropped process; the trade-offs are set out in how to run a 24/7 YouTube stream without leaving your PC on. If the particular failure is audio fading or stopping later rather than being absent from the start, compare it with how to fix OBS audio going silent during a YouTube radio stream.
Check YouTube Live Control Room
When the OBS mixer and local test suggest audio is present, inspect the event in YouTube Live Control Room. Check the preview and the stream health or error messages for the active broadcast. These messages help distinguish an encoder sending no audio from a viewer playback or preview issue; they are more useful than repeatedly changing OBS settings without evidence.
YouTube’s error guidance describes a “no audio stream” condition as the encoder sending no audio, and notes that some encoders have an option to enable audio. It also flags multiple audio streams and unsupported codecs. If the dashboard reports one of these, compare it with OBS’s stream-output configuration and the selected protocol. Make one relevant change, then check the event again.
If the dashboard identifies sample rate or bitrate, follow the current event’s error instructions and confirm the corresponding encoder setting. The cited YouTube help page refers to 44.1 kHz and 128 Kbps in its examples, but do not treat those figures as a universal fix detached from the current error. The actual dashboard and official help for the chosen ingest method should guide your next step.
YouTube also recommends checking the sound in the encoder, comparing it with a local archive and previewing or monitoring the live event in its streaming troubleshooting guidance. Keep the checks distinct: OBS monitoring tests your local monitor route; a local archive tests the recording path; the Live Control Room preview tests what YouTube has received and is presenting. A difference between those results is a clue to the stage where audio is being lost.
If the audio is missing only in a particular browser or device, ask another listener to check the preview and verify the player is not muted. That does not replace the stream health check, but it can reveal a playback-side issue. Do not assume that because you hear the monitored source locally, all viewers hear it on YouTube.
Run a short private or unlisted test
Before relying on a configuration for a long broadcast, test it with a short private or unlisted event where that suits your channel and audience. Start the media, confirm the source meter moves, verify the intended track is selected for streaming, and inspect YouTube’s preview and health information. You can then stop the test and correct the specific stage that failed without leaving a silent programme running for hours.
Use a repeatable sequence. First check the media locally and in OBS. Then record a short local archive and listen to it. Finally, send a test event to YouTube and check its preview from another device if practical. If the first two tests work but the YouTube preview is silent, focus on stream routing, encoder output and the dashboard’s ingestion message rather than rechecking the file format.
A test is especially useful after changing a scene, replacing a playlist item, updating OBS, or altering audio tracks. Keep a short note of the working scene, track assignment and relevant output settings. That gives you a point of comparison if the next broadcast is silent, without turning every troubleshooting session into a complete rebuild.
For an always-on channel, decide who will notice a failure and what they can check. A local test helps validate the media path, but it cannot guarantee that a future broadcast will remain audible. If you want the computer off while a file-based stream continues, StreamNeo removes the specific burden of keeping your own computer running for that broadcast; it does not change the need to check that your YouTube channel, file and event are ready.
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
Why can I hear the media in OBS but viewers cannot?
You may be hearing OBS’s monitoring route, while the source is muted, assigned to a different track, or omitted from the stream output. Check the stream track and then compare a local archive with the YouTube Live Control Room preview. Monitoring alone does not confirm what viewers receive.
Which OBS audio track should I use for a YouTube stream?
Use the track selected as the active streaming audio track in your OBS output configuration, and make sure the media source is assigned to it. Do not infer the live track from recording-track settings, which can be configured separately. If you use multiple mixes, verify each source’s assignment deliberately.
The source meter does not move. What should I check first?
Confirm that the correct media source is active and the file or playlist item is actually playing. Then check the file path, the selected audio track if this is a VLC Video source, and whether audio is available at the time you are watching the meter. A separate desktop-audio meter is not a substitute for the media source’s own meter.
The meter moves and my local recording has sound, but YouTube is silent. What next?
Check that the streaming track matches the source’s track assignment, then inspect encoder output and the event’s Live Control Room errors. Follow the message for that event and protocol rather than changing codec, rate or bitrate at random. Test again with a short private or unlisted event where appropriate.