To show a branded holding screen between videos without ending your YouTube Live broadcast, keep OBS connected and switch from a programme scene to a separate holding-screen scene. For a short operator break, YouTube also documents an away slate, but it is not an automatic playlist interstitial.
The distinction matters: OBS can loop a file or a playlist, but that playback setting does not itself switch to another scene at each video boundary. If you need interstitials without an operator, plan and test a separate automation or hosted playout workflow rather than assuming a playlist will do it.
Choose between a continuous feed and a temporary break
A continuous feed is the right approach when the channel should remain live while its content changes. OBS sends one encoder feed to YouTube; switching the scene changes what that feed contains, not the live event itself. You can therefore move between a video or playlist and your own branded artwork while maintaining the same stream.
A temporary break has a different purpose. YouTube’s away slate is a documented option for a short absence during an existing live stream. It is controlled through Live Control Room and is not described as a scheduler that watches playlist items and inserts a branded card between them.
Decide what the viewer should experience. A devotional channel might keep a quiet “Next bhajan shortly” card on screen while an operator prepares the next programme. A study channel could show a simple schedule during a planned pause. If you want the video sequence to run unattended and insert a card every time an item ends, you need a tested automation that can detect that boundary and change scenes, or a playout option that explicitly supports that behaviour.
| Approach | Best fit | What you need to check |
|---|---|---|
| OBS programme and holding scenes | Someone can monitor and switch scenes | Operator availability, source and audio behaviour, stable computer and connection |
| Playlist with separate scene automation | Repeated items with unattended interstitials | Whether the automation detects item end, switches reliably, and recovers after restart |
| YouTube away slate | A temporary break in an existing stream | How to control it, how it appears, and whether audio behaves as intended |
| Hosted continuous playout | You want to operate without a local encoder computer | Current scheduling and interstitial controls, service terms, and recovery behaviour |
Choose the simplest workflow that matches the hours you can actually supervise. A manual scene change is straightforward if someone is present; it is not a hands-off system after the operator leaves.
Build the programme scene in OBS
In OBS, a scene is a layout assembled from sources. Create one called “Programme” and add the source that will show your content. For a single local video, OBS’s Media Source can play a file and offers a loop setting. For a sequence, the VLC Video source can play a playlist and loop it; OBS notes that VLC must be installed for that source type. See the OBS guide to media sources for the documented source options.
A playlist setting controls playback of its items. It does not establish a separate scene transition when one item ends. In practical terms, if the VLC source reaches the end of a clip and moves to the next item, it remains within the scene that contains that source. Do not rely on the playlist alone to display a different holding scene between clips.
Check the programme source in the OBS preview before connecting. Confirm that the picture fills the intended frame, that the audio source is present at the intended level, and that the next item behaves as expected. For a folder-based study sequence, the considerations around organising and preparing files are covered in this guide to building a study stream from a Google Drive folder. The source arrangement may differ, but the principle is the same: establish what the programme scene will show before you rely on it live.
If you use a playlist, test what happens at the end of each item and when the playlist repeats. Watch the preview rather than inferring behaviour from a loop checkbox. If the viewer must see a card at every boundary, document how that boundary will be detected and which control will switch scenes. Without a separate, tested mechanism, schedule someone to make the transition manually.
Create a branded holding-screen scene
Add a new OBS scene, perhaps called “Holding screen”. For a still design, add an Image Source; for a moving card, use a Media Source. OBS’s sources guide explains how sources are added to scenes. Keep this scene separate from the programme scene so you can switch between them without rebuilding a layout during the broadcast.
Design the artwork for the actual viewer’s screen. Use a clear channel name or mark, a short message such as “Next programme shortly”, and a schedule only if you can keep it accurate. Keep important text away from the edges, where it may be difficult to read on a television or mobile screen. Check that your image has the intended aspect ratio and that text remains legible in the OBS preview at the stream’s output size.
Think about sound as well as the picture. If the holding scene should be quiet, check whether programme audio continues from another source when you switch scenes. If you want background audio, decide which source supplies it and test the levels. Scene changes are not a substitute for checking the mixer: an audio source can remain active even when its associated visual is no longer on screen.
A static image is often enough for a short gap. If your channel uses a still devotional image or meditation artwork, the practical choices overlap with this guide to showing a static image during a meditation stream. In either case, make the card useful rather than crowded: tell viewers what is happening, and avoid promising a precise return time unless the next programme is ready to start then.
Before going live, switch between both scenes in the preview. Look for blank edges, obscured text, unexpected audio, or sources that are visible in one scene when they should not be. If you make a change to the artwork or source layout later, repeat the preview check.
Connect OBS to YouTube Live
In YouTube Studio, open Live Control Room and create or schedule the encoder stream. YouTube’s encoder streaming guide describes the connection workflow: the encoder uses the stream URL and stream key associated with the broadcast. Enter those connection details in OBS’s streaming settings, following the current on-screen guidance in both applications.
Keep the stream key private. YouTube describes it as “like your YouTube stream’s password and address”, so treat it as sensitive account access information. Do not put it in a public document, chat, screenshot, or article, and do not send it to someone who only needs to operate a scene locally. If you believe it has been exposed, use YouTube’s current controls to replace or reset it, then update the encoder configuration.
Start the OBS feed and confirm that YouTube receives it in Live Control Room before making the event public. Check the preview, picture and audio, and confirm that the intended event is selected. This is a useful point to catch a wrong source, an empty scene, or an encoder connection problem without asking viewers to wait through troubleshooting.
The purpose of this workflow is to keep the encoder feed going while you change its visual content. YouTube’s guide says to stop sending content from the encoder when you want to end the stream. Avoid pressing a stop control simply to move from one video to the holding card; switch scenes in OBS instead. YouTube also says streams under 12 hours are automatically archived, a point to bear in mind if you are planning the eventual broadcast and archive handling.
Switch scenes without ending the live stream
Once OBS is streaming, selecting the Holding screen scene changes what OBS sends in the continuous encoder feed. When the next programme is ready, select Programme again. The stream remains the same live broadcast as long as you keep the encoder connected and do not stop the feed.
For a manual hand-off, agree on a simple sequence before the broadcast: move to the holding card, prepare or confirm the next item, check its picture and audio, then return to the programme scene. The order prevents an accidental end-of-stream action from becoming part of a scene change. It also gives the operator a chance to confirm that the next video has loaded before viewers see it.
If a playlist is running, remember that it may advance to its next item inside the Programme scene. The documented loop or playlist playback setting is not a signal to OBS to choose a different scene. To place a branded card between items, someone must make that scene change, or a separately configured automation must do it. Do not tell viewers or staff that enabling playlist loop will create the interstitial; it does not establish that behaviour.
A hosted playout workflow may suit a channel that has no one available to manage a local computer. YouTube’s list of encoders and live streaming services includes a cloud service described as supporting continuous 24/7 streaming. Treat that as a listing, not a quality guarantee or endorsement. Check the provider’s current features, terms, scheduling controls, interstitial support, and recovery process directly before choosing it.
For the specific burden of keeping a local computer running and connected through an unattended schedule, StreamNeo can take an uploaded video and run it as a YouTube live stream while your computer is off. It does not make playlist boundaries into scene changes by assumption, so confirm that the workflow you need supports the desired interstitial behaviour before depending on it.
Use YouTube’s away slate for a short break
YouTube documents a temporary away slate that can be used during a break. It is distinct from an OBS holding scene: the away slate is a YouTube Live Control Room feature, while an OBS scene is part of the encoder output. Use the documented approach that fits the kind of break you are taking, and check the current Live Control Room steps because interface labels can change.
YouTube’s instructions involve adding the slate overlay as a Browser Source in OBS. Follow the current YouTube away-slate guidance and test it before relying on it live. In particular, check how the overlay looks alongside your existing scene and whether the audio matches your intention. YouTube notes that the overlay does not affect other audio sources; if the slate video itself has audio, that may need to be included in your stream’s audio settings.
This feature is useful when an operator needs to step away briefly, but it is not a documented playlist scheduler. It should not be treated as a system that notices every clip boundary, waits for an arbitrary interval, or returns to the next item automatically. If you need a repeatable interstitial between each programme video, use the separate scene workflow and automation appropriate to that requirement, and test it independently.
For an ordinary scene switch in OBS, the encoder stays active and the source scene changes. For the away slate, follow YouTube’s own instructions and verify both overlay and audio behaviour. Keep the distinction clear in your runbook so an operator knows which control to use and what it is expected to do.
Plan scene changes and test them before relying on them
Manual scene changes work only when someone is available to make them. If a channel runs through the night, write down who is responsible for the change and what they should do if the next file does not start. A concise checklist can cover the scene to select, how to confirm the preview, what the viewer should see during a delay, and how to return to the programme. Avoid relying on a person remembering an undocumented sequence at an inconvenient hour.
If you want automation, test the exact configuration you intend to leave unattended. It must detect the end of the current item, select the holding scene, and later return to the programme scene as intended. Also check whether the process still behaves properly after OBS is restarted, a file is missing, or the playlist reaches its end. These are test cases, not claims that any particular playlist or scene setup automatically handles them.
Keep a fallback card ready and decide what happens if the next programme is late. For example, an operator can switch to the holding scene, check the next file in preview, and then return to Programme when ready. That is more predictable than leaving a black frame or assuming a failed source will be replaced by the branded image.
A long-running local encoder also depends on the computer and connection remaining available. If you are weighing up the local setup against hosted playout, compare what each option lets you schedule and how you can recover from a dropped feed. The discussion of automatic restart and recovery for a 24/7 stream can help frame those questions; recovery from a disconnection is separate from inserting an interstitial at a video boundary.
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 looping an OBS playlist show the holding screen between videos?
No. A loop or playlist setting controls playback of the source; it does not, by itself, establish an automatic switch to a separate OBS scene at each item boundary. If you require a card between items, arrange a manual scene change or configure and test a separate automation that handles it.
Can I change scenes without ending the YouTube stream?
Yes. Keep OBS connected and streaming, then select the other scene in OBS. The encoder feed continues while its visual content changes; do not stop the encoder just to display the holding scene.
Is YouTube’s away slate the same as an OBS holding scene?
No. An OBS holding scene is a scene in the encoder output, while YouTube’s away slate is a separate temporary-break feature controlled through Live Control Room. Follow YouTube’s current instructions and test the overlay and audio behaviour before using it.
What should I test before leaving the stream unattended?
Test both scenes, the programme audio, transitions, and the behaviour at playlist boundaries. If a separate automation is meant to switch scenes, verify that it does so as intended, including after a restart or a missing file, rather than assuming playlist looping will handle the transition.