If a black screen appears between videos in an OBS YouTube Live playlist, first check which source is playing the files and what it does when hidden or when an item ends. OBS documents playlist and loop controls, but does not promise that separate playlist items will transition without black frames.
For local files, the built-in VLC Video source is the documented playlist option, provided VLC is installed. If the gap remains after checking playback and visibility, try joining the clips into one continuous file and playing it as a Media Source; treat that as a troubleshooting experiment, not a guaranteed fix.
Confirm the source and playback state
Start by identifying exactly how the videos enter your scene. A VLC Video source containing several local files is different from a scene with separate Media Sources, a browser source, or another plugin. The steps below principally apply to a local-file playlist in VLC Video. If you are using online URLs or a third-party source, do not assume that its controls behave the same way.
In OBS, select the scene that should show the video and inspect its Sources list. Select the relevant source and open its properties. Confirm that the playlist contains the intended files and that the source is enabled in the scene. If the source is VLC Video but the source type is unavailable, OBS says VLC must be installed for it to appear. See the OBS Media Sources guide for the documented distinction between VLC Video playlists and individual Media Sources.
Then watch the source preview before changing settings. Does the first file play? Does the preview go black only at the boundary between two files, or also while an individual file is playing? Does it recover by itself, stay blank, or move to the next item? These observations separate a transition gap from a file that did not load, a playlist that ended, or a source that became hidden.
If the source is not playing at all, check the file paths and whether the files open locally in a media player. A playlist entry pointing to a moved or renamed file cannot display that file. For a channel that depends on a long sequence of local recordings, keep the files together in a stable folder and avoid changing their names or locations after you have added them. That will not remove a transition gap, but it avoids troubleshooting a missing file as if it were a transition problem.
If you are using separate Media Sources, remember that each is a source for an individual local file, rather than the documented multi-item playlist source. Scene changes or source activation may be what you see at a boundary. Decide whether the videos genuinely need separate controls, or whether a single playlist or joined file better fits the programme.
Check what happens when the source is hidden
A source can become hidden when you change scenes, toggle its visibility, or use a scene arrangement that temporarily removes it from view. OBS's VLC Video settings include Visibility Behaviour choices for what happens when the source is not visible. The documented choices include stopping and restarting playback, pausing and unpausing, or always playing. The right choice depends on whether you expect the playlist to continue while another scene is shown.
If you use a single scene throughout, visibility behaviour may not explain a black interval between two files. It is still worth checking because a scene switch near the same time can make the symptoms look like a playlist boundary. For example, if you briefly switch from a “programme” scene to a holding scene and back, a stop-and-restart behaviour can make the source begin again rather than continue where you expect.
Choose the behaviour deliberately. “Always play” may be appropriate when the playlist should keep advancing off-screen, but it can also mean media continues while viewers see another scene. Pause-and-unpause can preserve a paused position when the source is hidden. Stop-and-restart may be useful when you want playback to begin afresh on showing the source, but it is a poor fit if you expect a background playlist to run continuously.
After changing this setting, test by hiding and restoring the source yourself. Note whether playback pauses, stops, or continues, and whether the visible return to the scene is clean. Do not change several settings at once: one controlled change makes it easier to tell whether visibility was part of the problem.
For local news loops, a devotional channel, or a study station, consider whether the source should keep playing during every scene change. A holding slate can be useful when the programme is intentionally paused, but it is not a repair for a gap between files. If you need help planning how a programme changes without interrupting the broadcast, this guide to switching videos in a running YouTube stream without turning on your PC covers the broader operating decision.
Check whether playback reaches the end
A black screen after the last video in a playlist is different from a short blank interval between two items. Watch the source preview and establish whether the playlist has another item queued. If the playlist has finished, the expected next state depends on its settings; a loop control is relevant at the end of the complete list, not a documented setting for making each file boundary seamless.
Check the order and contents of the playlist in source properties. Look for an empty list, an unintended last item, or a file that fails to load. If you recently changed the playlist, confirm that the current version is saved and loaded in the scene you actually use for the broadcast. Do not infer from a playlist editor window alone that the live scene is using that same source.
For diagnosis, use a short playlist with files you can recognise and observe. Let the first file finish, then check whether the next one starts and what the preview shows between them. If the preview goes blank and stays blank, note whether the source advances, whether the file counter or selection changes, and whether the same behaviour repeats when you test the sequence again. The pattern is more useful than a single glance at the programme output.
If playback stops at the end of the list, test the loop setting in the next section. If it stops on a particular file, check that file separately: can it play by itself from the same source? A failure tied to one item is a reason to inspect that file or its path, not evidence that the playlist needs a general transition setting. The available evidence does not establish that every black frame has one common cause, so keep the diagnosis tied to what you observe.
Avoid editing a live playlist while viewers rely on it unless you have a recovery plan. An OBS forum thread contains an individual report of a stream returning to the first video after the user added media while live. That report is not evidence that every playlist change resets a stream, but it is a sensible reason to make and test changes before a broadcast rather than relying on a live edit. Keep a copy of the current working order so you can restore it if a change behaves differently than expected.
Review OBS loop settings
OBS's VLC Video properties include Loop Playlist and Shuffle Playlist. Loop Playlist concerns what happens once the source has run out of media files: it lets playback return to the beginning of the list. It is not documented as a control for the hand-off from one item to the next, so enabling it should not be treated as a promise that black frames between items will disappear.
Use Loop Playlist if your programme is meant to repeat after its final item. Leave Shuffle Playlist off if you need a fixed order, such as a sequence of announcements or a service schedule. If order does not matter, shuffle may suit a background station, but it changes what comes next and can make it harder to reproduce a particular boundary while troubleshooting. Keep the intended programme in mind rather than enabling every option in the hope that one will remove a gap.
Media Source has its own Loop control for an individual local file, along with options related to playback ending and unloading while inactive. Those controls apply to that source's file and behaviour; they do not turn a single-file source into a multi-file playlist. The OBS Sources Guide provides an overview of the source categories. Check the current documentation if your OBS version presents a control differently.
Use this comparison to decide which control is relevant:
| Setup | What OBS documents | What it does not establish |
|---|---|---|
| VLC Video | Playlist playback, loop and shuffle controls, and visibility behaviour; VLC is required for the source to be available. | That separate items transition without black frames. |
| Media Source | Playback and looping of an individual local media file, with playback-ending and inactive-source options. | That it acts as a multi-file playlist or fixes every file-boundary gap. |
| One joined file | A practical way to test playback as one continuous media item instead of switching playlist entries. | That joining clips will remove every gap on every system or with every file. |
Change one relevant loop or visibility option at a time, then play through the same boundary again. If the black screen appears between ordinary items while the playlist continues, loop is unlikely to be the answer on its own. If the issue occurs only after the final item, loop is directly relevant, though you should still verify that playback actually returns to the beginning.
Try a continuous joined file in Media Source
When the black interval appears specifically as one playlist item gives way to another, a useful experiment is to join the clips into a single continuous file and play it as a Media Source. This avoids switching between separate playlist items. It is a practical inference from the difference between OBS's playlist source and its individual-file source, not a fix verified by the documentation or guaranteed to work for every setup.
Prepare a test copy rather than replacing your originals. Use a video-editing or media-joining tool you already trust, and make sure the resulting file contains the intended order, picture and sound. If the source videos have different frame sizes, frame rates, audio arrangements, or encoding settings, the joined output may need to be rendered into a consistent format. The research behind this guide does not establish a preferred format or guarantee that a particular joiner will produce a problem-free file, so inspect the result before putting it into OBS.
Add the joined file as a Media Source in a test scene and play it from beginning to end. Check the points that used to be playlist boundaries, including the audio. If those boundaries now look and sound acceptable in the preview, test the same file through the output path you intend to use. If the black interval remains, the cause may not be the playlist hand-off alone; go back to the individual files, source state, and scene behaviour rather than assuming that another render will fix it.
A single file has trade-offs. It can be simpler to play as one item, but a correction to one segment may require another export. A long joined file can also take time to prepare and should be checked for completion before broadcast. Separate playlist entries are easier to reorder and replace, but their boundaries remain distinct transitions that OBS's documented controls do not promise to render without black frames.
Keep an unjoined copy of the programme and the original clips. This lets you compare behaviour and return to the editable sequence if the continuous version has a problem. For a station that changes content often, the convenience of individual files may outweigh the benefit of testing a single render. For a stable overnight programme, a single file may be easier to validate once and replay, but that still depends on how it behaves on your machine.
Test transitions before going live
Treat the transition itself as a test case. Build a short, representative playlist or a test joined file with the same type of content and source settings you plan to use. In OBS, watch the preview across a complete file boundary, then watch through the end of the playlist if looping is part of the programme. Look at the audio as well as the picture: a silent or abruptly cut interval can matter even when the image appears acceptable.
Test the scene visibility behaviour too. Hide the source, change to the scene you use as a holding screen, and return to the programme scene. This checks a different event from a normal file boundary. If you plan to use a loop, test the end of the final item and confirm what happens at the restart. Record which change you made and what changed in the result; that makes it easier to reverse a setting that has no benefit.
Before relying on the setup, run it privately or use a short unlisted YouTube stream. Check the received picture and sound on YouTube, not only the OBS preview. A preview can help you inspect a source, while a private or unlisted test checks the broadcast path as well. YouTube's live streaming help is the place to check current official guidance for managing a live stream. Keep the test limited to the intended audience and confirm its visibility before starting.
Do not make a late change to an all-night broadcast based on one successful transition. Replay the sequence more than once in the conditions you can realistically test, and include the point where the playlist reaches its end. This is prudent operational testing, not a promise that an unobserved overnight run will behave identically. If your channel has an important schedule, keep a holding scene and a known-good file ready so you can respond without rebuilding the whole show while live.
For a practical preflight beyond this one symptom, use a bitrate check before going 24/7. A stable connection will not remove a source-level gap, but testing the whole path can help distinguish a local playback issue from a problem that appears only after the stream reaches YouTube. If a file or scene change is part of your test, make a note of the exact version used so the live configuration matches what you validated.
Confirm what YouTube receives
OBS preview and YouTube playback answer different questions. The preview shows how OBS is composing its current scene; YouTube playback shows what viewers receive after the stream has been sent and processed. If the preview is clean but the YouTube test shows a black interval, note the time and compare it with the OBS preview or a local recording. That comparison helps locate the stage where the problem appears, without assuming the cause in advance.
Check that you are viewing the correct test stream and that playback has caught up to the point you are inspecting. A delay between the OBS output and YouTube playback can make a transition appear at a different time. YouTube's live control room and current Help pages describe the controls available for monitoring a broadcast; consult YouTube's official live-stream help for current instructions. Do not rely on an old menu path if YouTube has changed the interface.
If a black interval is visible in both OBS preview and the YouTube test, return to the source and playlist checks. If OBS looks normal but YouTube alone shows the problem, preserve the test details and inspect the output and stream status before changing the playlist. Avoid diagnosing an encoding or network fault solely from a black frame: the evidence in this case does not identify one universal cause.
A YouTube test also tells you whether the sound stays continuous and whether the correct scene is reaching viewers. Check the stream from a separate browser or device if practical, since the creator view may not match an ordinary viewer's playback. Keep the test private or unlisted as appropriate, and check its visibility and audience before starting; a test should not accidentally become the public programme.
If the channel needs to run while your own computer is off, OBS on a local machine is not the only way to organise playback. StreamNeo takes an uploaded video and runs it as a YouTube live stream, so you do not have to keep a computer running just to repeat that file; that addresses the specific burden of leaving a machine on, not OBS playlist transition behaviour. If you continue with OBS, make sure your test and monitoring plan fit the computer that will actually run the channel.
For a playlist channel, the source configuration is only one part of dependable operation. Plan how you will recover if the file stops, the wrong scene appears, or a broadcast needs attention. The guide to building a YouTube playlist for a 24/7 live stream can help you think through order and repetition, while this page focuses on the black screen at item boundaries.
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 OBS have a setting that guarantees black-free playlist transitions?
No. OBS documents playlist playback and controls such as looping and visibility behaviour, but the documentation does not guarantee gapless transitions between separate items. Test the specific files and setup you plan to use before a live broadcast.
Should I turn on Loop Playlist to remove the black screen?
Use Loop Playlist when you want the list to begin again after its final item. It is not documented as a control for the transition between ordinary playlist entries, so it may not address a gap between videos.
Will joining the videos into one file always remove the gap?
No. Playing one joined file as a Media Source is a reasonable workaround to test because it avoids changing playlist items, but it is not a verified or guaranteed fix. Inspect the joined file and test the relevant points in OBS and on YouTube.
Can I use Media Source for a playlist?
OBS documents Media Source for an individual local media file, while VLC Video is the built-in source for a playlist of local items. If you use Media Source, you can test a joined file, but do not expect it to provide the same multi-item playlist controls.