A black picture on YouTube Live does not, by itself, tell you whether the media file, OBS output or viewer playback is at fault. Find the first place the picture disappears: check OBS preview and program output, then compare them with YouTube’s preview and a viewer’s playback.
If the file is already black in OBS, start with the source and file. If OBS looks right but the broadcast does not, check the encoder output, stream health and viewer reports before changing media settings. There is no single setting that fixes every operating system, source type and file.
Locate where the image goes black
Treat each point from the file to the viewer as a checkpoint. A local file is loaded by an OBS source, appears in the scene, is rendered into the output sent by the encoder, reaches YouTube, and is played by each viewer’s device and connection. Compare what you can see at each point instead of changing several settings at once.
Start with the OBS preview while the media is meant to be playing. If it is black there, the problem is visible before the stream reaches YouTube. If OBS preview is normal, check program output as well: preview and program can differ when you use Studio Mode or have not transitioned to the scene you expect. Then check the Live Control Room preview and, if possible, the actual watch page from a separate device.
| What you see | First place to investigate | What the observation does not prove |
|---|---|---|
| Black in OBS preview and program | Scene visibility, source settings and the file itself | It does not establish a particular codec or graphics cause |
| Preview is good, but OBS program is black | Active scene, transition and program output | It does not mean the media file is unreadable |
| OBS output looks good, YouTube preview is black | Encoder output, stream health and ingest | It does not establish that all viewers have the same issue |
| YouTube preview looks good, one viewer sees black | That viewer’s player, device, browser or connection | It does not prove the encoder is failing |
| Several viewers on separate networks see black | Encoder output and the broadcast path deserve attention | It still needs confirmation from output and archive checks |
Make one observation at a time and note when it changes. If a source is black in OBS, adjusting a viewer’s browser is unlikely to help. If OBS is healthy and only one viewer reports a problem, replacing the source file may create a new problem without addressing the one they have.
Check the OBS preview and program output
Select the scene that contains the media and confirm that the source is visible in the Sources list. OBS sources can be hidden, covered by another source, placed outside the canvas, or absent from the scene currently on program output. Check source order as well: an opaque image or colour source above the video can make a working file look black.
If you use Studio Mode, inspect both panes. The preview pane is a prepared scene; the program pane is what OBS is sending out. A correct-looking preview does not guarantee that the program has transitioned to it. For a simpler setup, verify that the scene displayed in the main canvas is the one you intend to stream.
Look at the source’s own controls. Confirm the intended file is selected, the source is not hidden, and playback is not simply paused or at the end of a non-looping clip. If restarting playback makes the image appear, note that as evidence; do not assume it explains a later black screen. A file can also be audible while its image is missing, which is useful to record but does not identify the failing layer by itself.
YouTube Help advises checking the encoder directly and says that poor stream quality may come from the quality of the audio and video sources routed to it. Its guidance is to inspect the output rather than infer quality from a source window alone. See YouTube’s live-stream troubleshooting guidance for the checks to make when a stream looks or sounds bad.
Inspect the media file and source type
OBS documents Media Source and VLC Video Source as ways to add video or audio files. Check which source type you actually used. A local Media Source, a VLC Source, a Browser Source and a captured window are different paths; evidence about one should not automatically be applied to another. OBS’s source documentation and performance guidance can help you identify source and scene considerations.
Confirm the file path and name shown in the source properties, especially if you moved the media, changed a drive letter, or copied a scene collection to another computer. A source may still appear in the scene even when it cannot read the intended file. For a Media Source, inspect whether it is set to use a local file and whether the selected file is the one you expect. For VLC Source, check its playlist or selected item rather than assuming it points to the same location.
Play the file in an ordinary media player as a basic check. If it is black there too, the fault is not limited to OBS. If it plays normally elsewhere but not in OBS, that narrows the issue to how OBS or the selected source handles it; it does not prove which format, decoding or version detail is responsible. Record the file’s format and the OBS version before seeking a more specific answer. Avoid converting the entire library as a first move: test one copy of the affected file and compare the result.
Window capture is a separate case. If you are playing the clip in an external player and capturing that player’s window, the capture path—not an OBS media-file source—is involved. Community reports describe black video with this sort of setup, but reports are context-specific, not a universal diagnosis. If you need a repeatable playlist, compare this approach with using an OBS scene and file source; the guide to looping videos with an OBS scene collection covers that workflow.
Verify encoder output and stream health
When OBS preview and program look correct, inspect the output that OBS is actually sending. YouTube recommends checking the encoder directly. Watch a test stream in the Live Control Room preview before starting a public broadcast, and compare it with OBS at the same moment. YouTube’s live-streaming tips specifically advise checking that preview before you start streaming and monitoring quality during the event.
Look for whether the black image is constant, appears after a scene change, or follows a moment when the media source stops or restarts. Note any OBS warnings, encoder errors or unusual CPU load at that time. These clues may justify simplifying a complex scene or reducing unnecessarily large media dimensions, but performance should be considered when the symptom lines up with a rendering or encoding strain. A black source in an otherwise healthy, low-load preview is not proof that the computer needs a new GPU.
Also check that the stream is still connected and that YouTube is receiving video, not only audio. The Live Control Room’s status and preview are useful evidence, but allow for a difference between what the encoder sends and what a particular player displays. If you are testing privately, an unlisted stream can let you inspect the watch page without directing viewers to an unfinished broadcast.
Do not change resolution, frame rate, bitrate and encoder settings together. If a setting change is warranted by an observed warning, change one item, repeat the same short test and note whether the symptom moves. This keeps a useful comparison: the bitrate and frame-rate checklist for a 1080p YouTube Live stream is relevant to output configuration, but it cannot establish why one source is black.
Compare viewer reports and playback behaviour
Ask affected viewers where and how they are watching. One person seeing a black screen while others can see the image points first towards that viewer’s device, player, browser or connection. If reports come from several people sharing a network, a common local network condition is worth checking. If viewers on separate networks report the same fault at the same time, return to OBS output and YouTube’s stream status rather than assuming an individual playback issue.
A useful report includes the approximate time, whether sound continues, the device and app or browser, and whether reloading changes anything. Keep the questions neutral. “Can you see the moving image on another device?” is more diagnostic than “Is YouTube down?” A viewer who can see the image on a phone but not a television has given you a different clue from several viewers who all lose the picture at the same timestamp.
If the YouTube preview is good but one browser shows a green or black player, test another browser or device before changing OBS. YouTube’s article about a green screen in the video player discusses browser playback, hardware acceleration and graphics drivers. That is adjacent advice for a player-rendering symptom, not a confirmed fix for a local OBS media source. Use it only when the evidence points to playback on the affected device.
Review a local recording or archive
A local recording or YouTube archive helps distinguish what OBS produced from what a viewer’s player displayed. If the local recording has the same black section, the defect was present in the output captured on the streaming computer. Revisit the scene, source and encoder path at that time. If the local recording is healthy while YouTube playback is black, investigate the stream path or playback layer instead.
Make sure the recording overlaps the reported moment and includes the relevant output. A recording of a different scene or a short clip made after the issue passed cannot rule out an intermittent fault. Compare timestamps, scene changes and whether sound continues. If YouTube’s archive is available, compare it with the local recording rather than relying only on a viewer’s memory of what appeared.
An archive is evidence, not a verdict. It can show where the symptom appears in recorded output, but it may not capture every viewer’s playback conditions or explain why a source stopped rendering. YouTube’s troubleshooting guidance also recommends checking the local archive when stream quality is poor. If both OBS output and recording are clean, avoid rebuilding the media source until you have evidence that the defect begins there.
Narrow down the source of failure
Write down the observations in order: source type, OBS preview, program output, local recording, Live Control Room preview and viewer playback. Add whether sound is present and when the picture first turns black. This short timeline is more useful than a list of settings you have already changed, because it shows the first confirmed failing point.
| Evidence pattern | Next check |
|---|---|
| The file is black in a normal player and OBS | Verify the file itself and test a known-good copy |
| Normal player works; OBS media source is black | Confirm source type, selected path, visibility and OBS version |
| OBS preview is fine; program output is black | Check the active scene and transition state |
| OBS program and local recording are fine; YouTube preview is black | Review encoder errors, stream status and ingest evidence |
| Local and YouTube output are fine; one viewer is affected | Compare that viewer’s device, browser or network |
| The picture fails when a heavy scene becomes active | Simplify that scene for a controlled test and watch performance indicators |
For an always-on station, test a short representative section before leaving the stream unattended: include a scene change, the media source you intend to repeat, and an actual watch-page check. If a PC is already running the broadcast, a spare-PC setup for continuous YouTube streaming can be relevant to operating continuity, but it will not itself fix a source that renders black.
When the defect is clear in OBS, keep testing the media source and output locally. When the defect appears only downstream, preserve the source as-is while checking the encoder, YouTube preview and affected viewers. StreamNeo can remove the need to keep a personal computer running for an uploaded-file broadcast, but it does not change the need to verify that the file and YouTube channel are ready before a long-running 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 OBS media file black on YouTube Live?
First check whether it is black in OBS preview or program output. If OBS is already black, investigate the source and file; if OBS is clean, compare the encoder output, YouTube preview, archive and viewer playback before deciding where to troubleshoot.
The video plays in my media player but not in OBS. What should I check?
Confirm that OBS is using the intended file and source type, and that the source is visible in the active scene. Playback elsewhere is a useful check, but it does not prove that OBS can render the file in that setup; record your OBS version and file format before trying a targeted change.
Should I turn off hardware acceleration or update my graphics driver?
Only consider browser hardware acceleration or driver checks when the evidence points to playback in a particular browser or device. YouTube’s guidance is about a green-screen player issue, not a universal fix for black video from an OBS media-file source.
What details should I include when asking for help?
Include your OBS version, operating system, source type, media format, and whether sound continues. Say whether the image is black in OBS preview, program output, local recording, YouTube preview or only viewer playback, and include the relevant OBS log if available.