A black screen between clips can begin in OBS, in the hand-off to YouTube, or during playback on YouTube. OBS documents two media-source behaviours worth checking: a source can hide itself when a file ends, and an inactive source can take a short time to appear again while it reloads.
Neither behaviour proves what is happening in your setup. Compare OBS’s live output, a local recording of the change, and the YouTube playback before changing settings; that comparison narrows down where the blank interval first appears.
Find where the blank enters
Start with one transition that you can reproduce, rather than changing several settings at once. Note the time, the outgoing clip, the next clip, and which scene should be visible. If possible, keep OBS’s live or program output and the YouTube stream open so you can observe the same hand-off in both places.
Make a short local recording that includes the change between clips. A recording is useful because it shows what OBS composed and sent to its recording output, but it does not by itself prove what viewers received. Compare it with the live/program view and the YouTube playback. If the recording is already black, begin with the source, playlist, or scene. If it is clean while YouTube is black, focus next on the outgoing stream and YouTube’s live monitoring rather than assuming a particular cause.
In Studio Mode, distinguish the edit preview from the program output. The preview is a place to prepare a scene; it is not necessarily what viewers are seeing. OBS’s Studio Mode overview explains the preview and program workflow. For diagnosis, use the program side as your reference.
A showroom loop may combine product clips, a logo, a price card, and a holding background. If only one element disappears, that points to a different problem from the whole canvas going black. Write down whether audio continues, whether the logo remains, and whether the blank lasts until the next clip or only briefly. Those observations help separate a hidden video source from an empty scene or a wider interruption.
If you are still choosing a playlist method, the comparison of OBS Playlist Source and VLC Source for a 24/7 music stream can help you identify which controls apply to your setup. The relevant settings differ by source type, so first identify the source that actually plays the clips.
Check “Show nothing when playback ends”
For an OBS Media Source, open its properties and look for “Show nothing when playback ends”. OBS documents that this setting hides the source when its file has completed playback. If that source is the only visible content, or if nothing beneath it fills the canvas, the output can become black after a clip finishes.
The key question is what should occupy the screen during the gap. If the next clip is expected to start immediately, check whether it is actually part of the same playlist or whether a different source or scene is meant to take over. If you want a product card or branded holding image to stay visible, make sure it remains visible underneath the video source in the scene composition. Do not rely on the last frame of a clip as a deliberate holding screen if the source is set to hide at its end.
Test the setting during a short, controlled run. Change only this property, then repeat the same clip transition and compare the recording and live output. If the blank changes, you have evidence that the setting is involved; if not, restore your intended configuration and continue down the checks. A single setting change is more informative than simultaneously editing the playlist, transition, and scene.
OBS’s Media Sources documentation describes the option and its effect. Documentation identifies a possible mechanism, not the state of your source: you still need to check whether the option is selected and whether that source is visible in the scene at the end of the clip.
Check whether an inactive source closes
The same OBS Media Source properties include “Close file when inactive”. OBS says this unloads a hidden or off-scene media file to free memory, and warns that when a scene showing it returns, there may be a small period when the source is not showing while it reloads. That can matter when your sequence hides a source between clips or switches scenes before returning to it.
Look at how the source is used, not just at the checkbox. Does the next clip use a source that was on another scene? Is the source hidden between items? Does the black interval line up with the moment that source becomes active again? If so, the reload behaviour is a plausible explanation to test. It is not proof, because a blank scene, invalid next item, or playback hand-off can look similar.
If appropriate for your setup, temporarily change this option and repeat the test. Note whether the source reappears more promptly and whether anything else changes, such as memory use or playback behaviour. The practical trade-off is that unloading can conserve resources, while keeping a file ready may avoid a reload delay. Choose based on observed behaviour on the machine and scenes you actually use, not on a blanket rule.
This setting is relevant to Media Sources; do not assume it exists or behaves identically in a VLC playlist, browser source, or another encoder. For a 24/7 setup, a test should include more than a single clip pair if your scenes alternate in different ways. A source can be continuously visible in one part of the loop and hidden in another.
Verify the next playlist item or scene
A transition can appear black simply because there is no valid next picture to show. In a VLC Video source, inspect the playlist order and confirm that the next file is present and playable. Check whether loop and shuffle behaviour match your intention: shuffle can make the next item less predictable, and a playlist that reaches its end may not restart unless its loop behaviour is set as intended.
For a Media Source sequence, verify the file path and the source that is supposed to play next. A clip that was moved, renamed, or exported differently may not load as expected. Avoid inferring a missing file solely from a black frame; use OBS’s visible source state and a controlled local test to confirm whether the next item starts.
If your clips live in separate scenes, inspect the scene change as well as the media item. OBS scenes are arrangements of sources, and the live output can be an empty scene even when the desired clip is visible in the preview. Make sure the intended next scene is in program output and that its video source is enabled and positioned so it is not covered by another source.
For recurring loops, write down a simple sequence such as “clip A, clip B, holding card, clip C” and test each hand-off. Confirm the playlist’s actual order against that plan. The guide to keeping an OBS radio stream running after a playlist ends deals with a related end-of-playlist question; for a showroom, the important distinction is whether your sequence is meant to continue within one source or switch to another scene.
Inspect the transition between clips
OBS can transition between scenes using configured effects such as Fade and Cut. A transition can reveal an empty scene, or a fade can expose an interval where neither the outgoing nor incoming content fills the canvas as you expect. Check the transition assigned to the scene change and inspect both scenes independently before changing its duration or style.
In each scene, identify the layers that should always remain visible: perhaps a background colour, a showroom frame, or a holding card. Confirm their visibility and position beneath the clip source. If the outgoing clip source hides when playback ends, an underlying background can prevent a fully black canvas, provided that background is itself visible in the scene being output.
If you use Studio Mode, prepare the next scene in preview, then confirm the transition actually takes it to program. Do not diagnose from preview alone. A preview that looks correct while the program side is empty is a scene-operation issue, not evidence about YouTube playback.
For a useful test, duplicate the relevant scene or make a short test sequence, then use a simple Cut between known-good clips. If the black gap persists, the transition effect is less likely to be the cause; if it changes, inspect the original transition and scene composition more closely. This test does not guarantee that all transition-related gaps will disappear, and it should not replace checking the source and playlist.
Separate OBS output from YouTube playback
Compare three points: OBS program output, the local recording, and the YouTube playback. The pattern is more useful than guessing from the platform named in the title.
| What you observe | Where to investigate first | What it does not prove |
|---|---|---|
| The local recording and YouTube both show the same gap | Source visibility, file completion, playlist order, scene composition, or transition | That OBS alone is responsible; verify which element disappears and when |
| OBS program output and recording look clean, but YouTube playback shows a gap | The outgoing stream path and YouTube Live monitoring | That YouTube caused the blank; a recording and live output may not capture every delivery issue |
| OBS program output is black, and the local recording is black too | The active scene, source visibility, and playback state | That a single Media Source setting is at fault |
| The screen freezes or drops out while OBS reports connection trouble | Stream connection and output diagnostics | That every black interval is a network issue |
OBS’s Help Portal describes its dropped-frame and connection indicators. A rising dropped-frame counter alongside a yellow or red connection indicator is a reason to investigate whether the connection to the streaming service is unstable or cannot keep up with the configured bitrate. A black interval without that signal is not enough to diagnose a connection problem.
YouTube’s live streaming help points to Live Control Room metrics for monitoring a broadcast. Use those metrics alongside OBS observations if the recording is clean but the viewer-side playback is not. The available monitoring can help you locate a delivery concern; it does not identify this particular symptom automatically.
If you make a change, keep a note of the result: which setting changed, which transition was tested, and what each of the three views showed. That record stops you from repeatedly changing settings that did not affect the gap. For a broader connection issue, the checklist on YouTube stream health reporting poor despite good internet covers what to inspect before blaming the local internet connection.
Test the corrected scene and playlist
Once a plausible cause is found, test the corrected setup with a short recording and a live unlisted or otherwise appropriate test, following your usual channel workflow. Include the transition that previously showed black, plus a later hand-off if the playlist uses more than one source or scene. Watch the program output and check the playback afterwards rather than treating a successful preview as proof.
Change one thing at a time. For example, if the gap coincides with a Media Source ending, first test “Show nothing when playback ends”; then separately test whether “Close file when inactive” affects a scene reload. If you also alter the transition and playlist order, you will not know which change mattered. Restore settings that were not implicated so the final setup remains understandable.
Before leaving the channel unattended, confirm that every playlist item opens, the loop or end-of-list behaviour is intended, and the background or holding content remains visible where required. Observe at least one complete pass through the relevant sequence, including scene changes. A test cannot prove that no future gap will occur, but it can show whether the identified hand-off behaves as expected now.
If the problem persists, capture the OBS version, source type, relevant properties, scene arrangement, exact clip pair, and whether the local recording contains the gap. These details make a follow-up diagnosis more useful than saying only that YouTube went black. Check the current OBS and YouTube documentation because controls and interface wording can change across versions.
For channels whose main operational concern is keeping a pre-recorded loop running without leaving a computer on overnight, StreamNeo removes the specific task of keeping a desktop encoder running by turning an uploaded file into a YouTube live stream that can continue with your computer switched off. It is YouTube-only, so it is not a remedy for an OBS scene that must combine interactive sources or several live inputs.
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
Does “Show nothing when playback ends” cause a black screen?
It can hide a Media Source when its file completes. If no other visible source covers the scene, that may leave a blank canvas, but check your actual properties and output before treating it as the cause.
Why does a source take a moment to appear after a scene change?
OBS documents that “Close file when inactive” unloads a media file when its source is hidden or off the current scene. When the source returns, it may take a short time to reload; test whether the gap lines up with that change in your scene.
If my local recording is clean, is YouTube responsible?
Not necessarily. A clean recording narrows the investigation towards the outgoing stream and YouTube playback, but does not by itself prove which part introduced the blank. Compare OBS’s program output and the YouTube Live Control Room metrics as well.
Should I change my transition to Cut?
A Cut can be a useful controlled test because it helps you see whether a fade or scene transition is involved. It is not a universal fix: an empty next scene, hidden source, or missing playlist item can still produce a black screen.