A black screen in a prerecorded YouTube live stream can begin in OBS, during the encoder connection to YouTube, or later in viewer playback. Compare the OBS preview, a local recording, YouTube’s incoming preview and the public or unlisted stream in that order; where the picture first disappears determines what to check next.
Do not assume that one setting fixes every black screen. An OBS preview that looks correct is useful evidence, but it does not guarantee that YouTube receives or plays the same picture.
Identify where the screen turns black
Start by observing the stream while the file is actually playing. Note whether the picture is visible in the active OBS scene, in an OBS local recording, in the Live Control Room preview, and in playback from the event page. Check audio separately: sound can continue even when the image has disappeared, and a silent picture does not tell you where the video failed.
Use the first point of failure to choose a branch:
| What you see | First area to investigate |
|---|---|
| OBS preview is black | Media Source, scene selection and visibility, playback state, layering and canvas position |
| Preview is visible but local recording is black | OBS output and rendering or encoding performance |
| Preview and recording are visible but YouTube’s incoming preview is black | Event selection, stream destination, stream key and outgoing stream health |
| Incoming preview is visible but viewer playback is black | Event playback, quality selection, delivery delay and the viewer’s page |
This comparison is more useful than changing several settings at once. If you change the file, scene, encoder and network configuration together, a successful retry will not tell you which change mattered. Record what each stage shows before making a change, then repeat the same checks.
A useful test needs movement as well as audio. A still image might show that a source is present, but it will not reveal a playback restart, a video that has reached its end, or problems that only appear as the scene runs. Keep the test private or unlisted if you do not want viewers to see troubleshooting.
Check what OBS is showing
If the active OBS preview is already black, begin with the scene and its prerecorded source, rather than YouTube. For a local video file, check that the scene uses a Media Source, that its Local File field points to the intended file and that the source is visible in the scene you are broadcasting. It is easy to check one scene while OBS is sending another.
Play the source in OBS and inspect its playback state. If the video has ended, its end behaviour may leave nothing visible. OBS’s Media Source properties include Loop and Show nothing when playback ends. Loop is relevant when you expect the video to continue; the other setting matters when playback may finish during a longer broadcast. OBS documents these properties in its Media Sources guide.
Also check Restart playback when source becomes active if the video needs to begin again when the source becomes visible. Close file when inactive can affect a source that is removed from the active scene and later brought back. These properties describe playback behaviour; they are not general remedies for a black screen. Check the behaviour that matches the moment the picture disappeared.
An OBS scene can contain several sources stacked in an order. A visible source above the video can cover it, while a hidden eye icon can make the video source absent even though it remains in the source list. For diagnosis, verify visibility and temporarily move the video higher in the stack if appropriate. Then check its transform, size and position: a source can be active but outside the canvas or reduced in size.
If the scene uses a playlist through VLC Video Source, the VLC dependency is relevant: OBS documentation says VLC must be installed and the installation must match OBS’s bitness. That is not a requirement for the ordinary Media Source. Do not install VLC as a first step unless the scene actually uses the VLC source.
Once the preview shows the intended file, leave the scene alone while you test the next stage. A good preview narrows the possibilities, but it cannot show whether the recording output or YouTube connection is carrying the same frames.
Compare with an OBS local recording
Make a short local recording using the same scene and file, then play it outside OBS. This gives you a second observation of the video output before it travels to YouTube. If both preview and recording are black, return to the source, active scene and rendering path. If the preview is visible but the recording is black, investigate OBS output or performance rather than assuming the file itself is blank.
Keep the recording test representative. Include the part of the file where you first noticed the failure, and allow enough time to see whether it ends or restarts. Check whether the recording contains picture and audio, whether the frame remains black throughout, and whether it turns black at a particular transition. A short test that stops before the failure point can give false reassurance.
OBS composites and renders scenes using GPU resources. If you see stuttering, render or encoding lag, or a preview that fails under a complicated scene, simplify the scene and test again. OBS’s performance guide recommends steps such as reducing output resolution or frame rate and removing unnecessary load when performance is the issue. On Windows, it also suggests running OBS as administrator as an initial check for GPU overload. Treat these as targeted tests: they are not universal fixes for a black image with no evidence of performance trouble.
Close only applications you know are using substantial graphics resources, and check whether filters or oversized sources are doing work the scene does not need. Make one change at a time and repeat the local recording. If the recording becomes correct after a specific change, note it before proceeding to YouTube.
A correct local recording means OBS produced visible output in that test. It does not establish that the intended YouTube event received it. Keep the event and outgoing connection as the next branch if the incoming preview is still black.
Inspect YouTube’s incoming preview
When the OBS preview and local recording both show the video, inspect the scheduled or live event in YouTube’s Live Control Room. Confirm that OBS is sending to the intended event, and that its server URL and stream key correspond to that event. A stream can be active in OBS while the selected destination is wrong or YouTube has not yet produced an incoming preview.
For a scheduled event, follow YouTube’s setup flow and wait for the incoming preview. Read the stream-health notices instead of treating OBS’s streaming status as proof that YouTube received usable video. YouTube explains how to set up a live stream with an encoder and inspect its status in Live Control Room. If the incoming preview is black, keep your local recording as evidence that the picture existed before the connection, then check the event, destination and stream health.
Only review encoder settings if the connection evidence points in that direction. YouTube accepts RTMP or RTMPS and publishes supported codecs, keyframe guidance, frame-rate limits and bitrate recommendations in its live encoder settings guidance. Compare your output with the current table for its resolution, frame rate and codec rather than applying one bitrate to every stream. The guidance recommends constant bitrate encoding and keyframes every two seconds, with a maximum interval of four seconds.
A mismatch in output configuration can affect whether the signal is usable, but a black preview alone does not identify a codec or bitrate problem. Use stream-health messages and the encoder’s actual configuration to decide whether to adjust output. If you do change a setting, repeat the incoming-preview test before starting the event for viewers.
Check public or unlisted playback
If YouTube’s incoming preview shows the moving video, open the event page as a viewer and check playback there. Confirm that you are on the right event and that the player is not paused or set to a quality that is still loading. Allow time for delivery or processing, then check playback again. A good incoming preview and a black player are different observations from a black incoming preview.
If practical, check the page in a separate session or on another device without treating that as proof of a browser-wide problem. The official material does not establish a single universal fix for a black viewer player, so do not jump to changing codecs, browser settings or account configuration without supporting evidence. Check what the player is actually doing and whether the incoming preview remains intact.
YouTube transcodes a live stream into output formats for viewers on different devices and networks. That work means what you see at the encoder, in the incoming preview and in viewer playback are distinct stages. A visible picture in one stage is evidence about that stage, not a guarantee about the next one.
If the viewer page stays black while the incoming preview continues to show video, preserve the event details and stream-health information. Recheck the player and event page after a short wait, and use YouTube’s current help material if the issue persists. Avoid reworking the OBS scene when your observations place the disappearance after YouTube has already received the picture.
Narrow down the affected stage
Keep a small record of the test: active scene and file, whether OBS preview showed movement, whether the local recording did, what Live Control Room displayed, and what the viewer page showed. Add the time at which a change occurred, such as the video reaching its end or a scheduled event becoming live. This makes a repeat test comparable without relying on memory.
A black source in both preview and recording points back towards the OBS scene, source properties or rendering path. A visible preview and black recording points towards OBS output or performance. If both are visible but the incoming preview is black, check the event and outgoing connection. If YouTube’s preview is good but viewer playback is not, keep the investigation on the viewer-facing stage rather than changing a source that already rendered correctly.
Do not treat network trouble as the default explanation for a black image. Look for evidence such as OBS dropped-frame counts rising or a connection indicator turning yellow or red. OBS’s dropped frames guidance associates those signs with an unstable connection or a bitrate the connection cannot sustain. Where the indicators support that diagnosis, check server choice, stable upload capacity, Wi-Fi versus wired networking, VPN or firewall interference, and network hardware.
For a 24/7 stream, the file and the connection are separate concerns. A long-running broadcast can expose an end-of-file setting or a source that did not restart, even if a short preview looked fine. If the stream is intended to run continuously, review how long YouTube can retain a live event and what happens when a broadcast must be restarted in the guide to YouTube live-stream duration and resets. If your plan depends on a prerecorded loop, also check the scene and file workflow in this guide to changing videos in a running YouTube loop stream.
Retry only after verifying the source
Before retrying the real event, run a private or unlisted test with the same scene, file and output settings. Include movement and audio, and let it run through the part of the video where the earlier failure appeared. YouTube specifically recommends testing with audio and movement similar to the intended stream, then monitoring stream health. Check the preview and recording in OBS, the incoming preview in Live Control Room and viewer playback.
Verify the destination before you begin: confirm the event, server URL and stream key, and wait for the incoming preview when the event is scheduled. Check that the media source points to the right file, is visible in the intended scene and has the required loop or restart behaviour. These checks reduce ambiguity; they do not guarantee that a future stream will be free of problems.
If the source file ends, decide whether the event should show nothing, switch to another source or repeat the file. YouTube says automatic archiving applies to streams under 12 hours after the encoder stops sending. If the broadcast is longer, do not rely on that archive behaviour without checking YouTube’s current guidance. For an always-on channel, plan for the file’s end behaviour as well as the stream’s end behaviour.
If local OBS operation is the part that repeatedly fails overnight, consider whether keeping a personal computer awake is the right operating arrangement. StreamNeo can remove the need to leave that computer running by taking an uploaded video and stream key for a YouTube broadcast; it does not resolve an incorrect source, event or viewer-side problem, so diagnose those first. If you would rather keep OBS on your own machine, check practical measures to prevent OBS from sleeping during a 24/7 stream.
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 live stream black when OBS looks fine?
A correct OBS preview shows that OBS can display the scene, but the recording and YouTube connection are later stages. Check a local recording next, then Live Control Room’s incoming preview and viewer playback. The first stage where the picture disappears is the best place to focus.
Why does OBS show a black screen when I play a prerecorded video?
Check that the active scene contains the intended Media Source, that its file path is correct and that the source is visible and inside the canvas. Then inspect playback state, end behaviour and whether another source covers it. If a local recording is also black, investigate OBS’s output or rendering path after checking the source.
Should I change the bitrate to fix a black screen?
Not without evidence that output settings or the connection are involved. Compare YouTube’s published encoder requirements with OBS’s actual settings, and check stream-health notices or dropped-frame indicators. A black OBS preview, for example, points first to the scene or source rather than upload bitrate.
How should I test a prerecorded stream before going live?
Use the same scene, file and output settings in a private or unlisted test. Include movement and audio, then check OBS preview, a local recording, YouTube’s incoming preview, stream health and viewer playback. This lets you identify where the picture fails without assuming a single fix.