A YouTube livestream can show a holding screen between videos when you send it through encoder software such as OBS Studio and switch from a playlist scene to a separate holding-screen scene. OBS’s VLC Video source can play a local playlist, but the official documentation reviewed supports manual scene switching, not an automatic holding screen at every playlist boundary.
That distinction matters if you expect an unattended channel to pause neatly between every clip. You can build and test the two-scene workflow described here, but do not treat the scene change as automatic unless you have independently verified an automation method that works with your current software versions.
A YouTube watch playlist is not an encoder feed
A YouTube watch playlist is a way to organise videos for viewers. It does not send those videos to YouTube as one live encoder feed. For a live broadcast, an encoder produces and sends the audio and video signal; OBS is one way to do that with local media files.
That means there are two separate jobs. The VLC Video source in OBS plays your chosen media as part of the output, while YouTube receives the output from OBS as a livestream. YouTube’s live encoder setup guidance covers connecting an encoder with the stream URL and key. Its playlist help page explains playlists as collections of videos, not as an encoder feed.
If your aim is to run a continuous prerecorded programme rather than manage short transitions by hand, first decide whether OBS is the right workflow. A continuous prerecorded stream plan addresses the broader scheduling question. For a channel that needs a local operator to decide when an interstitial appears, the OBS scene approach offers a visible, understandable control: you choose the scene that is sent to the stream.
Install OBS Studio and VLC
Install OBS Studio and VLC on the computer that will run the broadcast. The OBS documentation for its VLC Video source says VLC must be installed for the source to be available. If you use 64-bit OBS, the documentation specifies 64-bit VLC. Check the current download and compatibility information from the official project pages before installing; menu names and software behaviour can change.
After installation, open OBS and make a small test project before adding your complete programme. If VLC Video does not appear as a source option, close OBS, confirm VLC is installed with the matching architecture, then reopen OBS. Do not assume a missing source means your media files are at fault.
Keep the media files in a stable folder on the same machine. Give them clear names and avoid moving or renaming them after you have added them to the playlist. The source refers to local files, so an OBS project that points to a file on a removable drive may not behave as expected when that drive is disconnected.
A single computer running OBS is a sensible fit when you want direct control and can keep the software open during the broadcast. It is less suitable if your requirement is that the entire show continue while your computer is off. That is a different operating model; the FFmpeg workflow for a continuous stream on Windows explains another encoder-based approach, though it does not remove the need to verify any specific interstitial automation you plan to use.
Add media files to a VLC Video source
In OBS, create a scene for the programme and add a VLC Video source to it. Use the source’s playlist controls to add the local media files in the order you want them to play. The OBS documentation describes playlist controls including Loop Playlist, Shuffle Playlist and Visibility Behaviour. Their exact presentation may vary with the current release.
For a fixed sequence, leave shuffle off. Turn looping on only if you want the playlist to begin again after the last file; leave it off if the sequence should stop at its end. These are separate decisions from the holding screen: looping determines what the playlist source does with its sequence, while scene switching determines which scene OBS sends to the stream.
Check every entry in the list. A file can be in the right place but still be the wrong edit, have a missing audio track, or use an unexpected aspect ratio. Play the source inside OBS before connecting to YouTube. Listen for the beginning and end of each file, and check whether the next clip starts as soon as the previous one finishes. The VLC playlist should not be treated as proof that a holding screen will appear between items.
If your source is set to stop or hide when its scene is not visible, note that behaviour while testing. The OBS source documentation includes Visibility Behaviour controls; a scene change can affect whether playback continues or restarts depending on the selected behaviour and current settings. Decide whether returning from the holding screen should resume the current clip or start the playlist again, then test that specific case rather than inferring it from a brief preview.
Build two scenes for the programme and the hold
Keep the playlist and holding screen in separate OBS scenes. In the programme scene, place the VLC Video source and any other elements that should accompany the clips. In the holding-screen scene, add a still image and, if useful, text such as the channel name or a short message. OBS’s overview guide describes scenes as the place to arrange media and other sources for the stream output.
Make the holding screen readable at the size people will actually view. A simple image with one short line of text is easier to check than a busy layout. Keep important words away from the very edges, where they can be obscured by player controls or crop differently on another display. If you use a logo, confirm that it is legible at smaller sizes and does not cover the programme information you want viewers to see.
Name the scenes so the operator can distinguish them without hesitation, for example “Playlist” and “Holding screen”. If you have more scenes in the project, use names that describe what viewers will see rather than labels such as “Scene 2”. Before streaming, select each scene and verify that its preview contains the expected image and sources.
Audio needs a deliberate choice. If the holding screen should be silent, make sure the playlist audio does not remain audible when you switch away. If you want a continuous bed of music, place and test it in a way that does not duplicate or overlap the clips’ own sound. Listen with headphones and watch OBS’s audio meters while switching. A still image can look correct while a source continues to produce unwanted sound.
Switch scenes manually with a transition
Choose a scene transition in OBS, such as a cut or fade, then switch to the holding-screen scene when you want the interstitial to appear. Switch back to the playlist scene when you are ready for the programme to continue. OBS documents scene transitions, but the reviewed material does not establish a built-in trigger that changes to the holding screen at the end of each VLC playlist item.
A manual transition is straightforward when someone is watching the programme and can act at the right moment. It is not a hands-off schedule for an overnight stream. If you need the hold to appear after every clip without an operator, pause here: the VLC playlist controls and OBS scene documentation cited above do not verify that behaviour. Do not infer it from the fact that the playlist advances from one file to another.
The relevant choice is less about which transition looks nicer and more about what the operator can execute reliably. A cut is easy to recognise in a test; a fade can soften a change between a clip and a still image. Try the effect with the actual media and display before settling on it. The transition does not create a gap between playlist items or determine when a scene switch happens.
| Approach | What it gives you | What to plan for |
|---|---|---|
| Manual scene switch | You choose when the holding scene appears and when the programme resumes | Someone must monitor the stream and operate OBS at the intended points |
| Unverified automatic switch | It could reduce operator work if a suitable method is confirmed | The reviewed OBS material does not establish a per-item holding-screen trigger; test compatibility and behaviour before relying on it |
| Playlist loop or shuffle | You control sequence order and whether the list repeats | These settings affect playlist playback, not automatic scene changes |
Test the whole sequence before going live
Test the project in OBS before you send it to viewers. Start with the first file, observe the transition to the next file, and check the final item against your loop setting. Then switch manually to the holding-screen scene and back. Confirm the visible picture, audio, and the playlist’s behaviour after the return. A test that only checks the still image will miss the most important hand-off details.
If you are connecting to YouTube, create or select the intended live stream in YouTube Studio and enter the server URL and stream key in OBS’s stream settings. YouTube’s encoder instructions describe this connection. Treat the stream key as private: it is the information the encoder uses to send the feed to YouTube, so do not include it in screenshots, public notes or a message to someone who does not need access.
Use YouTube Studio’s Live Control Room preview to check the incoming picture and sound before you make the broadcast public. YouTube’s live streaming tips recommend testing and monitoring the stream. Confirm that the correct stream is selected, that the preview shows the intended scene, and that audio is present without clipping or an unexpected silent section. Follow the current Live Control Room prompts rather than relying on a remembered sequence of buttons.
Keep the first test uncomplicated. Use a short playlist with representative files and check the actual holding image, not a temporary placeholder. Note any file that takes noticeably longer to begin, any audio that continues after a scene switch, and whether the playlist starts over when you return. Then adjust the source settings and repeat the test. This is more useful than assuming the result from the names of the controls.
For a 24/7 channel, also consider what happens when nobody is at the computer. The manual workflow requires a person to switch scenes; it does not by itself solve unattended operation. If you need to compare ways of keeping a prerecorded broadcast running, the article on YouTube live automation tools for music channels can help frame the operational question. Check the current capabilities of any tool you consider, and test the precise playlist-boundary behaviour rather than relying on broad claims about automation.
Verify any automation before relying on it
The critical question is whether a specific, current method can detect the end of each playlist item and switch to a holding scene, then return at the time you intend. The reviewed official OBS material documents adding a VLC Video playlist and switching scenes; it does not document automatic scene switching at each playlist boundary. That is the limit of the evidence here, not proof that no third-party method exists.
Before adopting any automation, verify its compatibility with your OBS version and the VLC source behaviour you use. Check whether it responds to the end of an individual file, the end of the complete playlist, or some other event. Those are different triggers. Establish what happens with a missing or delayed file, when the playlist loops, and when OBS is restarted. If the automation cannot explain those cases clearly, keep a manual operator in the plan or choose a workflow you have tested more thoroughly.
Also verify how the holding period is defined. A fixed timer is not necessarily the same as “between videos”: clip lengths can vary, and the next item may not begin at the time expected. If your intended hold is a short visual break between clips, the method needs to recognise actual item boundaries, not merely switch scenes on a clock. Test the complete sequence with the same files and settings you intend to broadcast.
If the real requirement is to leave your computer switched off, do not confuse that requirement with the OBS scene workflow. StreamNeo addresses the specific burden of keeping a computer running for a file-based YouTube broadcast: you upload the file once, provide the YouTube stream key, and the broadcast runs without your computer, with monitoring and automatic restart if it drops. It is YouTube-only, and it does not change the need to verify whether a chosen playlist workflow supports the interstitial behaviour you want.
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
Can I use a YouTube playlist as the livestream?
No. A YouTube watch playlist organises videos for viewers; it is not the encoder feed for a live broadcast. Use encoder software to send the livestream to YouTube, and treat its playlist of local media as a separate part of that setup.
Will OBS show the holding screen after every VLC playlist video automatically?
The OBS documentation reviewed for this workflow describes VLC playlist controls and manual scene switching, but does not document an automatic holding-screen change at every playlist item boundary. If you have a separately verified automation method, test its trigger and return behaviour with your actual files before relying on it.
Should I enable Loop Playlist or Shuffle Playlist?
Leave shuffle off when you need a fixed programme order. Enable looping only if you want the playlist to start again after its final item; neither setting causes OBS to switch to a separate holding scene.
Can I run this with my computer switched off?
The manual OBS workflow described here depends on OBS running and someone switching scenes. If your requirement is an unattended stream with your computer off, compare a different operating approach and confirm that it supports the exact playlist and interstitial behaviour you need.