Audio can reach YouTube while video fails somewhere else in the signal path, so audio alone does not identify the cause. Check the encoder preview and a local recording first; that tells you whether to investigate the source and encoder or move on to YouTube’s incoming stream and your connection.
For a YouTube live stream with audio but no video, work through those checks in order. Do not assume a black-screen setting, an ingest fault or a particular piece of equipment is responsible until you have seen where the picture disappears.
What audio without video can indicate
A live broadcast carries audio and video as separate streams of media, even when your encoder packages them together for delivery. One can be present while the other is missing, invalid or not reaching the viewer. Hearing the programme therefore shows that some audio is getting through; it does not confirm that the encoder is producing a valid video stream.
For a radio-style channel, the picture may be a static cover image, a visualiser, a schedule, or a loop of artwork. Each depends on a visible video source being included in the output. Music can continue if that source is hidden, absent from the active scene, not playing, or not being encoded as expected. Those are possibilities to check, not conclusions that follow from the symptom.
The video might instead exist in the encoder output but fail later, between the encoder and YouTube, or appear differently to you and your viewers. YouTube’s stream-health information can flag problems in the incoming stream, including video-stream and configuration issues. The viewer’s player is another observation point, so check whether the problem is visible to you in the Live Control Room and whether viewers report the same thing.
The key question is not simply “Why does my YouTube radio livestream have audio but no video?” It is “At which point can I last see the expected video?” The comparison below makes that decision practical.
| Encoder preview | Local recording | YouTube live output | First place to investigate |
|---|---|---|---|
| No picture or wrong picture | No picture or wrong picture | Audio only or still unclear | Source, active scene, routing and encoder output |
| Picture looks right | No picture or wrong picture | Any result | Recording settings or differences between preview and output; capture another test |
| Picture looks right | Picture looks right | Viewers see audio only | Live Control Room health, outgoing stream and viewer observations |
| Picture looks right | Picture looks right | Some viewers see video, others do not | Compare devices and playback conditions before changing the encoder |
These observations narrow the next check, but none by itself proves a specific cause. A short test with the same scene, source and encoder settings used for the live broadcast is more useful than an unrelated recording.
Check the encoder preview and a local recording
Start in the application that creates your broadcast. Look at its preview or program output, not only the source’s own window. Confirm that the active scene contains the intended visual source and that it is visible in the composed frame. A source can exist in the project but be hidden, covered by another layer, disabled in the active scene, or positioned outside the visible canvas.
For a static radio image, check that the image itself loads and fills the intended area. For a visualiser or video loop, make sure it is playing and that movement appears in the output. If you use scenes, confirm that the scene actually selected for the stream is the one you inspected. Do not change several things at once: first note what the preview shows, then make one small correction and check again.
Make a short local recording if your encoder supports it. Use the same scene and representative audio and video sources as the planned broadcast. YouTube advises creators to inspect how the stream looks and sounds in the encoder, check sources and encoder errors, and review a local archive as part of troubleshooting. Its encoder settings guidance also recommends testing with audio and video movement similar to what you intend to stream.
Compare the recording with the preview. If both contain the picture, you have evidence that the encoder can produce video in that test. If the preview looks right but the recording does not, inspect whether the recording and streaming outputs use different settings or sources. If both are black, frozen, or showing the wrong image, look upstream before changing YouTube settings.
For a video playlist with mixed source dimensions, scaling and scene composition can complicate the result. The steps in handling different video resolutions in a YouTube playlist are relevant when the picture appears inconsistently as items change, but they are not a substitute for checking the current preview and recording.
If video is missing before YouTube
When the preview and local recording both lack the expected video, keep the investigation at the source and encoder end. Check whether the intended file, image, visualiser, capture input or other source is available and active. If the radio stream is assembled from a playlist, check that the visual component is part of the scene rather than assuming the audio playlist also supplies a picture.
Next, inspect the scene or composition. Verify that the video layer is enabled, not obscured by another source, and inside the visible canvas. Check the output resolution and aspect ratio against the canvas so that the image is not placed beyond its edges or cropped unexpectedly. If there are multiple scenes, make a note of which one the live output is using; a preview of one scene does not verify another.
Then inspect encoder messages and settings. YouTube’s current live encoder guidance lists supported video and audio codecs and recommends constant bitrate encoding, but its appropriate bitrate recommendations depend on codec, resolution and frame rate. Use the official table for your intended output instead of copying a bitrate from a different setup. The same guidance recommends a two-second keyframe interval and says not to exceed four seconds. Check the current YouTube encoder settings page before changing settings, because supported formats and recommendations are documented there.
A setting mismatch can affect whether video is accepted, but changing settings blindly can create new problems. Record the current configuration before adjusting it, and test one change at a time with both audio and representative video movement. Look for encoder errors and check whether the local recording changes after each adjustment. If the local output remains wrong, YouTube cannot be used as the first explanation because you have already found the problem before delivery.
YouTube’s general troubleshooting advice also points to encoder errors and CPU load when the local output itself has problems. Those checks do not mean CPU load is necessarily the cause; they are useful observations. If you use OBS, its official Help Portal points to the Auto-Configuration Wizard and additional streaming guidance. Use that guidance to review your own configuration rather than replacing hardware on the basis of audio without video alone.
If local output has video but viewers do not
If both the encoder preview and local recording show the expected picture, move downstream. That result makes a missing scene source less likely for the test you made, but it does not establish that the live delivery is healthy. Confirm that the live stream uses the same scene, profile and output configuration you tested. A recording can be configured separately from the streaming output.
Check the live page or preview in YouTube’s Live Control Room and compare it with what viewers report. Ask whether the issue affects every viewer, a particular browser or device, or only one playback moment. If possible, view the public stream from a separate device or network. This helps distinguish an incoming-stream problem from a local playback or display issue without treating any one report as proof.
For channels built around repeated music and artwork, the difference between a pre-recorded file and an encoder-generated scene matters. If you are assembling an always-on playlist, compare your setup with streaming a Winamp radio playlist to YouTube around the clock to understand where the playlist and visual output meet. That article may help you review the workflow, but the preview and local recording remain the evidence for your current stream.
If you are considering a change in how the channel runs, understand what a hosted workflow changes before treating it as a fault fix. A hosted always-on YouTube stream setup can remove the need to keep your own computer running, but it does not make source and YouTube checks unnecessary. First establish whether your existing file or scene contains the picture you expect.
Review Live Control Room health messages
Open the stream’s Live Control Room and inspect its health indicator and any accompanying messages. Look at the message text and timestamp, then compare it with the point at which the video disappeared. A warning during a test is more informative than a general recollection that the stream was “healthy” at some earlier time.
YouTube says the dashboard reports errors detected in the stream being sent to it. Messages may point to format or stream-configuration problems. The YouTube Live Streaming API documentation describes health status and configuration issues for live streams. Use the dashboard’s current messages to guide the next check; the existence of a health indicator does not mean that every visual issue will produce a clear explanation.
If the message concerns a video format or stream configuration, compare the active encoder output with YouTube’s current published settings. Check video codec, resolution, frame rate, bitrate mode and keyframe interval as applicable. Avoid copying settings from a tutorial for a different resolution or codec. If YouTube reports no relevant errors but viewers still see audio only, keep testing rather than treating the absence of a warning as proof that delivery is fault-free.
Save or note the exact message, its timestamp, and the encoder settings in use. That gives you something concrete to compare after a test. If you ask for help, provide those details along with whether preview and recording showed video; “audio but no video” by itself leaves too many stages unresolved.
Test the outbound connection
When the encoder output appears healthy but the YouTube output does not, test the connection carrying the stream out of your location or service. YouTube’s troubleshooting guidance recommends testing the outbound connection when the encoder view looks and sounds right but delivery does not. This is a next check based on the signal path, not a claim that the internet connection is at fault.
Use a test that reflects the actual upload path and stream conditions, and compare the result with the encoder’s stream health during a controlled test. A connection may behave differently at another time of day or under other household or office use. If you see interruptions or inconsistent upload capacity, reduce competing upload activity for a test and observe whether the outcome changes. Keep the encoder scene and settings steady while testing so you can attribute any difference more carefully.
For a live test, include both audio and moving or changing video where appropriate. YouTube’s settings guidance explicitly recommends testing with audio and movement similar to the intended programme, then monitoring stream health. A static radio image is representative only if that is what the real channel will send; if your stream includes a visualiser or rotating artwork, include that too.
If connection testing suggests a problem, repeat the test and consider the path between encoder and router as well as the internet service itself. If it does not, return to the exact Live Control Room messages and encoder output rather than buying a new capture device or replacing the computer. A useful investigation separates source, encoder, incoming-stream and viewer stages before deciding what to change.
Keep a repeatable pre-flight check
For a channel that runs all day, a short pre-flight check is easier to repeat than a late-night reconstruction. Before starting or changing a stream, verify the active scene, preview picture, representative audio, and a local recording. Then inspect YouTube’s health indicator during a test and confirm the live picture from a separate playback view when practical.
Write down the working scene and encoder configuration. Note which video source is used, what the preview and recording looked like, and whether Live Control Room reported an issue. If the problem returns, compare the current observations with that known-good test. You will be able to see whether something changed in the source, the encoder profile, the outgoing connection, or only the viewer’s playback.
For an always-on channel, avoiding a dependency on a computer left running may be part of the operational decision, separate from diagnosing this particular symptom. StreamNeo can remove the need to keep your own computer switched on for an uploaded video broadcast, which addresses that specific overnight-running burden; it does not replace checking that the source file and YouTube output show the intended picture.
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 my YouTube live stream have audio but no video?
Audio and video can fail at different points, so sound working does not confirm that valid video is being sent. Check the encoder preview and a local recording first, then follow the result to source and encoder checks or to YouTube health and connection checks.
Does a YouTube livestream black screen with audio mean YouTube has an ingest fault?
No. The same appearance can result from a problem before delivery, during ingestion, or at playback, and the symptom alone does not identify which. Compare the encoder preview, local recording and Live Control Room messages before drawing a conclusion.
What should I check first in OBS?
Inspect the active scene and program preview, confirm that the visual source is enabled and visible, and record a short local test using the same scene. If the recording also lacks the expected picture, review source routing and encoder messages before investigating YouTube delivery.
Should I buy a capture card or change my internet plan?
Not on the basis of this symptom alone. A capture card is relevant only if your setup depends on a capture input that is not producing video, and a connection change is only worth considering after an outbound test points that way. First identify where the video disappears.