A video feed reaching YouTube does not tell you whether audio is reaching it. To find where sound stops, follow the path from the intended source into OBS, through its stream mix and encoder, and then check what YouTube reports receiving.
Start by playing the sound that should be live and watching the relevant OBS mixer meter. If it moves, check that the source is unmuted and routed to the intended stream output; then inspect an encoder output or local recording before changing settings at random.
Why video can arrive without audio
Video and audio are separate signals. OBS can capture and send one while the other is absent, muted, routed to a different output, or encoded incorrectly. YouTube can therefore receive moving images without receiving a usable audio stream. Do not treat video in the preview as evidence that the sound path is working.
Think of the path in stages: the sound is produced by a microphone, desktop device, application, or media source; OBS receives it and shows its level in the mixer; OBS includes it in the intended stream output; the encoder packages that output; and YouTube ingests and processes it. A fault at any stage can leave video unaffected.
The order matters. If the OBS meter is silent while the source should be playing, first look upstream of or at the OBS input. If the meter moves, the source has reached OBS, but you still need to verify mute state, routing, stream track, and encoded output. If that output contains sound but YouTube reports none, use the specific Live Control Room message to investigate ingestion or format.
This is a diagnostic sequence, not a reason to replace a microphone or interface. The same symptom can come from a disconnected input, the wrong desktop-audio device, a muted mixer channel, a missing stream track, or encoder settings. Record what each check shows so you can narrow the cause rather than changing several things at once.
Check the intended source in OBS
First identify exactly which sound you expect viewers to hear. It might be a microphone, music playing on the computer, audio from a browser or other application, a media source inside OBS, or a combination. The right checks depend on the source; a desktop-audio check will not prove that a microphone is connected, for example.
Play or speak into the source while looking at OBS. The OBS Audio Mixer Guide explains how the mixer displays incoming audio levels. Locate the channel that should correspond to your source and watch it during actual playback. A quiet source may show no activity while idle, so test it deliberately rather than relying on a still screen.
If there is no movement, check whether the intended source is present in the scene or audio settings and whether it names the device you are actually using. A device may have changed after a headset was plugged in, an operating-system update, or a restart. If several devices have similar names, test them one at a time and watch for the meter response.
For a microphone, confirm the correct input is selected and the connection is seated. For desktop audio, check that OBS is listening to the output device on which the sound is playing. For application capture, confirm the intended application is producing sound and that the capture source points to it. For a media source, check its playback state and source properties. These checks establish whether the signal reaches OBS at all.
If the source is present but silent, look for a physical mute switch, an application mute, or a system volume setting before changing OBS. Check filters on the OBS source as well: a filter can alter or suppress the signal. Change one item at a time, then repeat the playback test. The OBS Audio Mixer Technical Details provides further context on mixer behaviour and audio processing.
Read the relevant mixer meter
The mixer meter is a useful boundary in the diagnosis. When the intended sound is playing, movement means audio is reaching that OBS mixer channel. No movement means you should keep investigating the input path or source selection; it does not tell you that YouTube is at fault. A meter that is still because nothing is currently playing is not a fault signal.
Be sure you are reading the right channel. A scene may contain several audio sources, and a microphone meter can move while the music source remains silent, or vice versa. Test each source whose sound needs to reach viewers. If the stream should contain both a voice and a backing track, verify both channels independently.
A moving meter is evidence of input to OBS, not evidence that the audio is part of the stream. A channel may be muted, excluded from the stream mix, or assigned to an audio track that is not being sent. Continue downstream rather than stopping at the first sign of activity.
If you use OBS audio monitoring, listen to the source after it reaches OBS. This can help establish that the signal is audible at that point, but monitoring alone does not prove it is included in the encoded stream. Monitoring and stream routing are distinct checks. The OBS mixer documentation describes the mixer controls; use your own test output to confirm what leaves OBS.
Verify device, mute and volume
With the intended meter in view, check the source and device controls systematically. Confirm the channel is not muted in OBS and that its fader is not set so low that the signal is effectively inaudible. Check physical controls on a microphone, headset, interface, or mixer, then check the application's own mute and volume. A control in one place may not be reflected in another.
Avoid turning everything up as a first response. If the meter is moving, raising a fader may make the result louder but will not correct a missing track or a muted stream output. If the source meter is not moving, increasing the OBS fader cannot restore a signal that never entered OBS. Correct the earliest failed stage, then listen and meter-check again.
Look at source filters and channel-specific settings if the device and mute controls are correct. A filter may be suppressing audio, and multiple sources can have separate controls. Temporarily bypassing a filter for a controlled test can help, but note the original setting and restore it if it is not responsible. Do not make unrelated permanent changes during a live broadcast.
If you can hear the source locally but the meter does not move, compare the device producing that sound with the device selected in OBS. This is particularly useful after changing headphones or audio outputs: the computer may send sound to a new device while OBS continues listening to the previous one. Test with a short, repeatable sound and watch for a response.
Check the encoder's audio output
Once the relevant OBS meter moves, trace the signal through OBS's output. Verify that the source is unmuted and included in the mix or audio track used for streaming. If the configuration offers multiple tracks, check which one the stream encoder sends; sound on a track used only for local recording will not necessarily be in the live output.
Make a short local recording or inspect an encoder output where practical. Play it back and confirm that the expected sound is present. This is a stronger check of the output path than hearing OBS monitoring alone. If the recording is silent while the mixer moves, focus on routing, track selection, and output settings rather than replacing the source device.
YouTube's recommended encoder settings list AAC or MP3 for audio and recommend 128 Kbps and 44.1 kHz for stereo audio. These are YouTube's published recommendations, not a guarantee that every configuration will work. Compare your encoder's actual settings with current guidance and with any stream-specific error YouTube displays. Avoid changing multiple encoding parameters at once, since that makes it harder to identify which change mattered.
Check that the encoder is sending the intended audio stream, not multiple or unintended streams. YouTube's live streaming error messages include separate guidance for no audio, multiple audio streams, unsupported audio codec, and incorrect audio settings. Match the message to the stage: a no-audio report suggests audio is absent from the sent stream, while a codec or settings warning calls for checking the format.
Check YouTube's received stream
Open the Live Control Room for the active stream and read the actual status or error rather than inferring the cause from the picture. YouTube's live streaming troubleshooting guidance points to checking the encoder output and local archive as part of diagnosis. The dashboard's report concerns what YouTube is receiving; pair it with what you observed in OBS and in a recording.
If YouTube reports “Your encoder is sending no audio”, check whether the stream output contains audio at all. A moving OBS meter with a silent recording points back to OBS routing or track selection. A recording with sound but a no-audio ingestion report points later in the path, so inspect the encoder's selected audio output and any stream-specific format error.
If the message concerns an unsupported codec or incorrect settings, compare the active encoder configuration with YouTube's current recommendations. If it reports multiple audio streams, check whether the encoder is sending more than the intended stream. Do not interpret all audio warnings as the same fault; the error text is evidence that helps distinguish absent audio from incompatible or ambiguous audio output.
Use the preview and stream-health information as an end-to-end check, not as a substitute for source testing. YouTube advises testing with audio and video activity representative of the planned stream. For a music loop, test the actual playback source; for a talk programme, speak through the intended microphone. A silent test segment cannot establish that a source which is normally active is working.
Isolate the stage where audio stops
Use the observations below to choose the next check. The stages are alternatives in a signal path: do not skip directly to YouTube when the OBS source meter has not moved.
| Evidence | Likely stage to inspect | Next check |
|---|---|---|
| Intended OBS meter does not move during playback | Source or input to OBS | Confirm device selection, connection, source activity, and mute or volume controls |
| Meter moves, but a local recording is silent | OBS output path | Check channel mute, stream mix, track assignment, and recording or output selection |
| Recording contains the expected sound, but YouTube reports no audio | Encoder or sent stream | Check selected audio output and the specific Live Control Room error |
| YouTube reports a codec, settings, or multiple-stream error | Encoder format or stream configuration | Compare the active configuration with current YouTube guidance and correct the stated issue |
| OBS and YouTube checks pass, but viewers report silence | Playback or monitoring context | Test another playback device and review the live preview and stream health |
These clues narrow the search; none identifies a specific faulty setting without seeing your configuration. For example, a silent local recording does not prove a particular track is missing, but it makes checking the OBS output path more useful than changing YouTube settings. Preserve a note of the result after each controlled test.
When a stream is already live, avoid repeatedly changing devices, tracks, and encoder settings at once. If you can, use a short test stream or an unlisted/private test appropriate to your channel workflow, then inspect its output before relying on the setup for a long broadcast. YouTube's tips for live streaming recommend checking the preview and monitoring audio, video, and stream health. Review the current official instructions because labels and recommendations can change.
For a 24/7 channel, a repeatable preflight check is more useful than waiting for a viewer to report silence overnight: play representative audio, verify the OBS meter, listen to the output or a local recording, and check YouTube's preview and error status. If your wider workflow also depends on a long-running broadcast, the guide to restarting an SRS YouTube stream after a crash addresses a separate failure mode; a restart cannot repair a silent audio path.
Sound quality is also distinct from whether audio reaches YouTube. If the stream is audible but some music is muted or interrupted, investigate the content and rights issue separately; the guide on preventing Content ID from muting parts of a YouTube livestream covers that different symptom. For a prerecorded channel, the Adobe Media Encoder playlist workflow may help you check the media preparation stage, while this page focuses on OBS and the live audio path.
If the remaining problem is keeping a prepared programme running after you have confirmed its sound, StreamNeo can remove the need to leave your own computer switched on for that uploaded-video broadcast; it does not diagnose a silent OBS source or replace checking the YouTube audio output.
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 does YouTube show my video but no audio?
Video and audio travel as separate parts of the stream, so YouTube can receive one without a usable version of the other. Check the intended OBS source meter first, then verify the stream mix and encoded output before using the Live Control Room message to investigate what YouTube received.
The OBS meter moves. Does that mean YouTube can hear the sound?
No. A moving meter shows that audio has reached that OBS channel, but it may still be muted, excluded from the stream mix, assigned to a different track, or absent from the encoded output. Check a local recording or encoder output and compare it with YouTube's status.
What should I check if the OBS meter does not move?
Play or speak into the intended source and confirm OBS is listening to the correct device or application. Then check connection, source activity, physical and software mute controls, volume, and any filters. An OBS fader cannot restore audio that is not reaching the mixer.
Should I replace my microphone or change YouTube settings first?
Neither is a useful first step without evidence. If the source meter is silent, trace the input; if it moves but output is silent, trace OBS routing and track selection; if the output contains sound, use the specific YouTube error to check the encoder or ingestion format. Make one change at a time and retest.