A black screen on a pre-recorded YouTube live stream is fixed by finding where the picture disappears, rather than changing settings at random. Check the video source, encoder preview and local recording first, then compare them with YouTube’s ingest view and the viewer’s playback.
Audio can continue while video is missing, so hearing sound does not prove that the complete stream is being sent. The steps below separate a source problem from an encoder, YouTube ingest, network or viewer problem.
Start by locating where the picture disappears
Follow the signal path in order:
video file → media source → encoder scene → encoder output or local recording → YouTube ingest → viewer playback
The first place where the picture turns black is the most useful evidence. If the video file itself is black, changing YouTube’s stream settings will not help. If the encoder preview contains a picture but YouTube’s preview is black, inspect ingest messages and the outgoing configuration. If YouTube looks healthy but one viewer sees black, investigate that viewer’s playback instead of rebuilding the broadcast.
Start with the encoder preview. Confirm that the intended scene is active, the pre-recorded media source is visible and playing, and that the source is included in the scene being sent. A media file can be loaded in the encoder without actually being visible in the live scene. It may be hidden behind another source, placed outside the canvas, paused at its first frame or routed to a different scene.
Next, make a short local recording using the same scene and source. Watch the recording from beginning to end. If both the preview and recording are black, the problem is on your computer or in the source path. If both contain a picture, compare them with YouTube’s Live Control Room preview and health messages.
YouTube’s live-stream troubleshooting guidance recommends checking the encoder directly, reviewing encoder errors and examining a local archive for audio or video problems. That makes the preview and recording more useful than guessing from a viewer’s report alone.
| What you can see | Where to investigate first |
|---|---|
| The file is black in an ordinary player | File, codec, colour format or playback compatibility |
| The file looks fine, but the encoder preview is black | Source, scene, visibility, routing or encoder load |
| Preview and local recording look fine, but YouTube is black | Ingest configuration, stream health or connection |
| YouTube is healthy, but one viewer sees black | Viewer device, browser, app or local connection |
| Audio works but picture is absent at several stages | Video stream, source decoding or video configuration |
This is a diagnostic sequence, not a guarantee that every setup behaves identically. Menus differ between OBS and other encoders, and the exact cause depends on the file, scene and health message.
Check the video file and playback source
Before changing the live broadcast, open the original file in a normal video player. Scrub through several points, including near the beginning and later in the file. Check that the picture appears while the audio is playing. A file that contains audio but has no usable video track will produce the same symptom as a failed live encoder: sound with a black frame.
If the file plays correctly, add it to the encoder again or reopen the media source. Confirm that the source is not paused, hidden or configured to stop after reaching the end. For a loop, check what the encoder is meant to do when playback finishes. A source may show a picture during the first pass and turn black when it reaches the end if the loop or restart behaviour is not configured as intended.
Look at the scene itself, not only the source list. The media source must be visible in the active scene and positioned inside the output canvas. A full-screen colour, browser capture or blank overlay above it can cover the video while the source continues to report that it is playing. Temporarily hide other visual sources so that only the pre-recorded video remains, then test again.
Audio-present/video-black symptoms deserve a separate check. The audio track may decode normally even when the video codec, profile, pixel format or hardware decoding path does not. If the file plays in one application but not in the encoder, create a short test copy in a broadly supported format using a trusted local tool, or test another known-good video in the same source. Do not replace the working file until you know which comparison changed the result.
A useful comparison has three parts:
- Play the original file outside the encoder.
- Put that file in a simple scene containing no other visual sources.
- Test a different known-good video in the same scene and source type.
If the known-good video also appears black, the file is less likely to be the cause. If the known-good video works but the original does not, inspect the original’s video track and encoding. If the original works in the simple scene but not in the full broadcast scene, restore the other sources one at a time until the covering or routing problem returns.
For channels built around long loops, keep the source test separate from the overnight test. Advice in Can YouTube Live loop a video automatically? is relevant to the loop design, but it does not establish that a black frame is caused by looping. First prove that one complete pass produces picture and sound.
Updating the encoder is also reasonable when the source behaves correctly but the preview does not. YouTube’s troubleshooting page advises using the latest version of the encoder and says that trying a different encoder can help when the sources and archive appear sound but the output does not. Treat that as a controlled comparison, not as proof that your original encoder is at fault.
Compare encoder preview with YouTube ingest
When the encoder preview and local recording contain a picture, move one step downstream. Open YouTube Live Control Room and inspect the preview, stream health and any timestamped messages. A successful connection only shows that a connection exists. It does not prove that a usable video stream is reaching YouTube.
YouTube displays stream errors beside the health indicator. Red messages are critical and yellow messages indicate a problem that may affect quality. Read the wording and timestamp before changing settings. A message about missing video calls for a different response from one about resolution, frame rate or keyframes. YouTube’s stream health and error reference explains the categories used in Live Control Room.
Look specifically for messages involving:
- missing or multiple video streams
- an unsupported video format or setting
- a resolution mismatch
- an incompatible frame rate
- a keyframe interval that does not meet the ingest requirement
- a connection or bitrate problem that prevents a stable upload
Check that the selected output resolution and frame rate agree throughout the chain. The source may be one size while the encoder is configured for another, and the stream settings selected for YouTube must match the output being sent. A mismatch is evidence to investigate, not a reason to change every setting at once.
YouTube’s current encoder guidance lists RTMP and RTMPS as connection options, H.264, H.265 and AV1 as video codec options, and AAC or MP3 for audio. It recommends a two-second keyframe frequency and says not to exceed four seconds. These are published technical settings, not a universal cure for a black screen. Change the relevant value when the encoder configuration or YouTube’s message indicates that it is relevant.
The YouTube encoder settings guidance is the right reference for the current published requirements. Follow the settings for the encoder you are actually using, because a menu label or available codec can differ between applications.
If the local recording is healthy but the YouTube preview remains black, check the outgoing stream configuration before replacing the source. Confirm that video is enabled, the selected scene is the one being transmitted, and no profile or codec option is producing an unsupported stream. Then restart the test broadcast and see whether the new health message changes. A changed message is useful evidence; no message change suggests that the adjustment may not have addressed the failing point.
If viewers see black but audio works
Separate reports by viewer and network. One viewer seeing a black picture while others see the stream normally usually points towards that viewer’s device, browser, app, connection or playback settings. Several viewers using one shared connection may point towards that network. Reports from viewers on different networks are more relevant to the encoder or YouTube delivery path.
Ask an affected viewer to try the stream in another current browser or on another device. They should also check whether the same black playback appears for other live streams. This comparison avoids treating a local browser problem as a broadcast failure. If the picture works on a phone but not on a particular computer, keep the encoder unchanged while that viewer checks the device and connection.
If audio plays and the video is black for viewers across unrelated networks, compare their reports with the Live Control Room preview. A healthy creator-side preview does not rule out every delivery issue, but it shifts the investigation away from the original file and scene. Check the stream health messages and test the outbound connection as YouTube recommends in its official live-stream troubleshooting steps.
Do not ask viewers to diagnose the encoder from a single report. Record the time, which device they used, whether audio continued and whether other streams played normally. The time matters because it can be compared with YouTube’s timestamped health messages and with changes in the encoder log.
If your stream is designed for continuous playback, also distinguish a brief playback failure from a persistent black output. A viewer may join during a transition between files, while the encoder may recover by itself. If the black frame repeats at every file boundary, inspect the source restart and transition behaviour. If it begins at an unpredictable time and affects every viewer, inspect the encoder and connection records instead. Guidance on why a YouTube live stream keeps disconnecting when looping a video can help with a related looping failure, but disconnection and black video are not the same symptom.
Test a short recording or stream preview
Run a representative test before the next public broadcast. Use the actual pre-recorded file, the intended scene, the normal resolution and frame rate, and the same audio path. A still image or a different short clip can prove that the encoder opens, but it will not prove that the real file survives its opening, movement, transitions and loop boundary.
YouTube recommends testing with audio and movement similar to the planned stream, then monitoring stream health and messages during the broadcast. For a pre-recorded channel, include enough of the file to exercise the part where the black screen was observed. If the issue appeared after a loop, include the end and restart rather than stopping the test before that point.
Use this short test record:
- time the test and note the file and scene used
- watch the encoder preview while the video is playing
- make a local recording and review it after the test
- inspect YouTube’s preview and health indicator
- note every error and its timestamp
- ask one viewer on a different connection to check playback
Keep the test private or otherwise limited according to your normal YouTube workflow. The purpose is to establish whether the picture survives each stage, not to collect viewer feedback about the content.
If the preview, recording and YouTube ingest all show picture, but the original public stream later turns black, compare what changed. Possible differences include a different scene, file, scheduled event, encoder profile, computer load or network. If nothing changed, save the timestamps and logs before restarting again, because repeated restarts can remove useful evidence.
Apply the fix for the failing point in the signal path
Once the failing point is known, make the smallest relevant change.
When the source or scene is failing
Reopen or replace the media source, confirm that it is visible in the active scene and remove visual layers that may cover it. Test a known-good file in the same source. If the known-good file works, inspect the original file’s video track and encoding rather than changing the YouTube event.
If the source fails only at the end of a loop, check the source’s restart behaviour and the transition between files. For devotional channels, ambience stations and other continuous channels, test the exact order of files that will run overnight. An ordinary OBS restart setup for a PC reboot may help with recovery after a restart, but it will not correct a media source that is black every time it loads.
When the encoder output is failing
Confirm the correct scene is being sent, then check encoder errors, CPU load and the local archive. Update the encoder. If the same source works in a simple scene but not in the full one, rebuild the scene gradually. If the source and archive look correct but the outgoing output remains wrong, compare with another encoder as a controlled test.
Avoid changing codec, bitrate, resolution and frame rate together. You will lose the ability to tell which change mattered. Start with the exact setting named by the encoder or YouTube health message, then run the same short representative test again.
When YouTube ingest is failing
Use the wording in Live Control Room to correct the matching setting. Check that the stream contains one usable video stream, that its resolution and frame rate agree with the selected configuration, and that the keyframe frequency follows YouTube’s published guidance. Recheck the connection settings and stream key carefully without publishing the key.
If YouTube reports an unsupported format, test a compatible output rather than assuming the file itself is bad. If it reports a resolution or frame-rate mismatch, make the encoder and ingest choices agree. If the message concerns the connection, test the outbound internet path and contact the internet service provider if that test shows a problem.
When only viewer playback is failing
Keep the broadcast running if the creator-side preview and other viewers are receiving picture. Ask the affected viewer to test another browser, device or connection and to check whether other live videos have the same problem. If many viewers on separate networks report the same symptom, return to the YouTube preview and health evidence before treating it as a local playback issue.
Choose a workflow that reduces repeat failures
After the immediate repair, decide whether the workflow suits the channel. Existing encoder software is useful when you need scene control, overlays or frequent changes and can keep a computer available for the broadcast. Dedicated hardware may suit a fixed installation where you want a physical appliance, but it is not a remedy for a black source, an incorrect scene or an unsupported stream configuration.
YouTube lists AJA HELO Plus with a PlayToStream feature for scheduling pre-recorded media directly to YouTube Live without a computer. That is an optional specialised workflow for a particular need, not the first purchase for an unexplained black screen. YouTube also lists software and cloud-based tools in its encoder directory, but a listing does not establish that a product fixes your particular fault.
A cloud-hosted workflow can remove the need to leave your personal computer running. For a channel that needs a file sent continuously while the computer is switched off, StreamNeo removes the recurring task of keeping an encoder open, watching for a drop and restarting the broadcast manually. You still need to check the source file, YouTube channel and stream configuration, and you should test the complete path before relying on it overnight.
Choose based on the operating problem you actually have: scene control, scheduled playback, recovery after a local restart, or continuous operation without a local computer. For a channel that changes files often, a workflow with clear source management may matter more than a fixed appliance. For a simple, stable file, fewer moving parts may be more useful than additional controls.
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 is my YouTube stream black but I can hear audio?
Audio and video can fail separately. Check whether the file, encoder preview and local recording contain picture, then inspect YouTube’s health message for missing video, an unsupported setting or a mismatch. Do not assume that working audio proves the video source is valid.
Why does OBS show the video but YouTube is black?
Compare the OBS preview and local recording with YouTube’s ingest preview. If local outputs are healthy, inspect the outgoing video stream, resolution, frame rate, codec and keyframe message, then run a short test after the relevant change.
How do I test a pre-recorded YouTube live stream without a black screen?
Use the actual file and intended scene in a short representative test. Watch the encoder preview, review a local recording, check YouTube’s stream health and ask a viewer on another connection to confirm playback.
Should I change the codec immediately?
No. Change the codec when the encoder or YouTube reports an unsupported format or related incompatibility. Otherwise, first identify whether the picture is already missing in the file, scene or local output.