A black picture from an OBS Media Source is a symptom, not a diagnosis. Check the selected file, source visibility and playback first; then compare OBS output with YouTube to find where the picture disappears.
For a continuous channel, also check whether the clip has simply ended: Media Source’s Loop option is off by default. Test the selected source before changing encoder settings or leaving a stream unattended.
Check the selected source and file
Start in the scene that is meant to be on air. In the Sources dock, select the actual Media Source and open its properties. Confirm that it points to the intended local file, not an old path, a renamed copy or a file on a drive that is no longer mounted. If you have several similarly named scenes or sources, select each deliberately rather than assuming the highlighted item is the one producing the picture.
Check whether the file opens and plays outside OBS. This is a useful separation: if it cannot play in a normal media player, the problem may be the file or its location rather than the scene. If it plays there, that still does not prove OBS can decode it in the same way, but it gives you a dependable starting point. For example, test the bhajan video you expect to loop, rather than a different clip with a similar name.
OBS lists common video types supported by Media Source, including MP4, TS, MOV, FLV, MKV, AVI, GIF and WebM. That list does not mean every file with one of those extensions is valid or will decode correctly. If a file has been edited, copied from a phone or exported by an unfamiliar tool, try a known-good local file in a temporary scene. Avoid replacing codecs or reinstalling OBS before you have made this simple comparison.
Check the path itself. A Windows laptop may have a file under Downloads, while the scene still points to a copy on a USB drive that has been removed. A network location or synchronised folder can also be unavailable at the moment OBS tries to read it. Store the broadcast copy somewhere stable on the machine and confirm the exact path in source properties. If the stream is run from a dedicated PC, document which file and scene are intended to be used after a restart.
The same first checks help with prerecorded services and other long-form material; the Windows laptop guide to streaming prerecorded church services covers the broader preparation around the file and broadcast. Here, keep the focus on whether this selected source can produce a picture in OBS.
Confirm the source is visible and not covered
A correctly selected file can be playing while another layer hides it. In OBS, the Sources list is stacked: a source above another is drawn over it and can cover it entirely. Look for an image, colour source, browser source, text panel or another video above the Media Source. Temporarily hide the suspected covering source with its eye control, then watch the preview. If the picture appears, you have found a compositing issue, not evidence that the file is black.
Check the eye icon beside the Media Source itself. If it is disabled, the source is hidden in that scene. Turn it on and inspect the preview again. Source visibility can differ from scene to scene, so check the actual scene in the programme output, not a scene you use only for testing.
Also check placement. A source can be positioned outside the canvas, reduced to a tiny size or cropped until no useful picture remains. Select it and use the preview transform handles or source transform controls to see its bounds. If you need to fit an image to the canvas, do so deliberately and ensure that the crop has not cut away the whole frame. OBS’s source ordering and visibility guide explains how the list order and eye control affect what is shown.
For a quick isolation, make a temporary scene containing only the selected Media Source. Do not delete or rebuild the live scene as a first step; a duplicate scene lets you test without disturbing the channel layout. If the source is visible alone but disappears in the working scene, compare visibility, ordering, transforms and scene-specific filters. If it remains black by itself, continue to playback and rendering checks.
Check whether playback ended and Loop is enabled
Watch the preview from the beginning of the file through the point where it turns black. If the picture is present at first and disappears at the end, inspect playback settings before looking elsewhere. OBS Media Source’s Loop setting is off by default, so a finite clip can finish rather than start again. Enable Loop if the source is meant to repeat, then test that it reaches the end and begins again as expected.
There are two settings that are easy to confuse. “Restart playback when source becomes active” concerns what happens when a source becomes active; it is not the same as continuous looping. “Show nothing when playback ends” can leave an empty source when a file completes. Check both in the source properties, but change them to match the intended behaviour rather than treating any single setting as a universal fix. OBS documents these controls in its Media Sources reference.
Test more than the opening seconds. A clip may contain a black section by design, a transition, or a long still image. Seek or wait through the relevant point and compare against the original file in a player. For a devotional stream, for instance, a title card may be black before the programme begins; for a local news loop, a transition slate may be expected. The question is whether the image shown in OBS matches the file at that playback time.
If you are using a playlist rather than one file, OBS VLC Video may suit the job better. It supports extended media playback through VLC and has a Loop Playlist option that defaults on, but VLC must be installed for the source type to appear. OBS specifies that 64-bit OBS requires 64-bit VLC. Use it when you genuinely need a list of files or extended support; for one compatible local file, built-in Media Source is simpler. Do not switch source types just because a black frame appeared once: test the selected file and current source first.
A guide to restarting an OBS video playlist automatically is relevant if your actual problem is a sequence reaching its end or not cycling as intended. That is a different question from a source that never displays a picture, so distinguish the two before changing the scene.
Test local media playback
Now test the selected source in the OBS preview while the file is actively playing. If the preview shows the expected picture, record a short local sample and review it. This checks not only the preview but the composed output that OBS is producing. Use a representative section with movement and audio, not just a static opening frame; a still image can conceal a playback problem that appears later.
If the preview is black and the recording is black too, stay on the OBS side of the boundary. Recheck the source path, visibility, stacking and playback state. Then test a known-good file in a clean scene. If that file appears but the intended one does not, the difference is likely in the file or its decoding path. If neither appears, that points towards a broader OBS scene or rendering issue, but it still does not identify a single cause by itself.
If the preview looks correct but the local recording is black, check that you recorded the intended scene and output, and that the recording contains the same moment you saw in preview. Confirm the selected programme scene, rather than assuming the preview and output are identical in a studio-style layout. Make a second short test after verifying the scene selection. Keep these clips local and short; the aim is diagnosis, not a replacement for a long-running archive plan.
For a 24/7 channel, make a reliable local recording plan as well as checking the live picture. YouTube says streams under 12 hours can be automatically archived, while streams longer than 12 hours may not be captured at all; this is an archive limitation, not an explanation for a black Media Source. Review YouTube’s archive guidance and confirm that any local recording you rely on is actually growing. A local file that stops growing is a separate issue to investigate, even if the live output looks healthy.
Separate OBS rendering from YouTube delivery
Compare the same moment at each stage: OBS preview, local recording, YouTube Live Control Room preview, then the public watch page. Write down what you see rather than labelling the entire chain “black”. If OBS preview and local recording are both good, but the Control Room preview is not, focus next on the outgoing stream and YouTube’s reported stream health. If Control Room is correct but the public page is not, check the page, player and viewing device as well as the live output.
YouTube advises testing representative audio and motion, monitoring stream health and messages, and checking the output rather than assuming that a connected encoder means everything is fine. Its live encoder troubleshooting guidance can help you inspect the delivery side. Follow the messages shown for your stream. Do not change resolution, bitrate, codecs or keyframe settings merely because the Media Source looked black in OBS; those settings do not establish why a local source is empty.
A useful evidence sequence is simple. Note whether the selected source moves in OBS preview. Note whether the local recording reproduces that image. Then note whether the Live Control Room preview and public page show it. This creates a boundary: source and scene, OBS composed output, or delivery and playback. It does not guarantee that only one fault exists, but it stops you from applying a YouTube fix to a source-level problem or vice versa.
For a 24/7 devotional or ambience stream, do this test before leaving the channel unattended, and repeat it after a scene, file or output change. A thunderstorm sounds channel walkthrough is another example of why a continuous loop needs both content playback and a live-output check. The diagnostic principle is the same whether the content is rain, music or a local community programme.
Investigate performance only when symptoms support it
GPU resources are used for scene compositing and rendering. If OBS reports rendering or encoding overload, or if the output is choppy, delayed or missing frames, reduce unnecessary sources and filters, and consider whether the media resolution is higher than the channel needs. OBS’s rendering and performance guide describes performance steps for those symptoms.
Do not infer overload from a black frame alone. A hidden source, wrong path or completed clip can look just as black while asking very little of the computer. First establish that the source is visible, correctly selected and playing. Then use OBS’s indicators and the character of the output to decide whether performance is a credible branch. Removing an animated overlay or browser layer can be a sensible controlled test; changing several settings at once makes it harder to learn what helped.
Likewise, do not treat running OBS as administrator, changing codecs, reinstalling graphics drivers or buying a more powerful machine as a universal Media Source remedy. There may be contexts where a performance change is appropriate, but take it in response to evidence such as overload or persistent choppy output. Make one change, test the same source and compare the recording. If the symptom is still a static black picture, return to source, visibility and playback checks.
Preview before leaving the stream unattended
Once the source works locally, run a short end-to-end check before leaving the channel unattended. Confirm the expected scene is active, the Media Source is visible, the clip is playing and looping if required, and representative motion and audio reach YouTube. Check the Live Control Room messages and public watch page. If you have a local recording plan, verify that its file grows during the test and that you know where it is saved.
For unattended operation, record the specific settings that matter: source path, scene name, whether Loop is enabled, and which output you checked. A small note prevents a later restart from relying on memory, especially if someone else maintains the channel. Keep a known-good test file available so that you can distinguish a changed content file from a wider OBS problem without rebuilding the live scene.
A continuously active local OBS session also depends on the computer remaining on and the scene continuing to play. If that has been the recurring source of overnight interruptions, StreamNeo removes the need to keep that computer running for a file-based YouTube broadcast: you upload the video, provide the stream key, and the channel continues from the cloud with monitoring and automatic restarts. It is YouTube-only, so it is not a fit if you need the same broadcast sent to other platforms.
If OBS preview and recording are correct but YouTube delivery is not, keep the source in place while investigating stream health. If YouTube is correct but a particular viewer sees black, check the public page on another device or connection before changing the source. A repeatable comparison is more useful than treating the word “black screen” as a cause.
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 OBS Media Source showing a black screen?
The phrase describes an outcome, not its cause. Check that the intended file is selected and accessible, that the source is visible and not covered, and that playback has not ended; then compare preview, local recording and YouTube output to locate the boundary.
Does OBS Media Source loop automatically?
No. OBS Media Source’s Loop option is off by default, so enable it when a finite clip should repeat. “Restart playback when source becomes active” is a separate control and does not mean continuous looping.
Should I use VLC Video instead of Media Source?
Use VLC Video when you need a playlist or its extended media support, and install VLC first. OBS requires matching 64-bit VLC for 64-bit OBS; for one supported local file, test the built-in Media Source before switching.
Does a black OBS preview mean YouTube is at fault?
No. A black preview can arise before anything is sent to YouTube, while a correct OBS preview and recording with a bad YouTube preview points you to investigate delivery. Compare the stages and use YouTube’s stream health information rather than guessing.