To add a countdown slate between videos in a 24/7 YouTube stream, make a separate OBS scene for the slate and keep your video playlist in its own scene or source. You can switch between them manually, or try a community-described Advanced Scene Switcher workaround that detects a clip nearing its end; that automation is not built into OBS and needs testing in your setup.
A slate can be a fixed card, a countdown video, or a live timer presented through a source. The key decision is not its appearance but how playback behaves when OBS changes scenes: the clip may stop, continue, or restart depending on the source and its settings. Build a complete transition cycle and test it before leaving the stream unattended.
Choose a countdown slate format
First decide what viewers should see during the gap and for how long. A fixed image with text such as “Next session starts shortly” is useful when the break is open-ended. A pre-rendered countdown video suits a known break, for example a short interval between devotional recordings, because its duration is fixed and it can be added as a media source. A browser source can show web content, including a timer, but that introduces another dependency and needs its own testing.
OBS’s Media Source is intended for a single media file, while VLC Video is the source for a playlist of files. OBS documents support for common video types including MP4, MOV, MKV, and WebM, but file extensions alone do not guarantee that every codec combination will play correctly. Use a file you have already previewed in OBS rather than assuming a video that plays in another application will behave identically in your stream. The official OBS Media Sources guide explains the source controls.
A pre-rendered timer is straightforward if the break duration is settled. If the playlist advances at variable times, or a clip sometimes ends early, a fixed countdown may reach zero before the next video appears. You can use a longer slate and return manually, or use a non-timed card that does not imply a precise start time. Avoid a countdown that viewers are likely to treat as a promise if your transition is not reliable.
Keep the design legible at the size people watch. Use a clear phrase, a visible timer if appropriate, and enough contrast against the background. If the stream is a study channel, the slate might name the next subject; for a local news loop it might say that the next bulletin is loading. Do not put essential information only in small text near the edges, where display cropping or mobile viewing can make it hard to read.
Create a dedicated countdown scene
In OBS, add a new scene and give it a clear name, such as “Break slate”. Add the components needed for the card: an image or colour background, text, and either a countdown media file or browser source. Each component is a source. The OBS Sources Guide describes adding, showing, hiding, sizing and positioning sources in a scene.
Layer order matters. Sources higher in the Sources list appear above sources lower in the list, so keep text above the background image and place any timer where it is not obscured. Use the preview to position and size each source for the stream canvas. If you use a countdown video as a Media Source, decide whether it should loop, restart when it becomes active, and show nothing when playback ends. OBS documents these as separate options; check them rather than relying on defaults.
For a countdown that should start from its beginning every time the scene is shown, test the restart behaviour when the source becomes active. A file that resumes halfway through may display the wrong time on a later visit. Conversely, if you want a background animation to continue through a brief switch away, a restart may be undesirable. The right setting depends on the job the source is doing, so watch the source through the same scene changes you intend to use live.
A browser source can make a timer visually flexible, but its content may rely on an external page or network access. That is a practical trade-off for an unattended stream: a local media file has fewer external dependencies, while a browser page may be easier to update. If using one, test loading, resizing, and what appears if the content fails to load. OBS’s source documentation describes the source type, but does not certify any particular timer page.
Keep playlist playback separate
Keep the programme videos separate from the slate. You can put the VLC Video source in a dedicated playback scene and switch to the slate scene at a boundary. Alternatively, the VLC source can be in another arrangement of scenes, but make its visibility and playback behaviour explicit. Separating the playlist from the slate makes it easier to see which source is meant to advance and which source is meant to mark a break.
For one repeating file, a Media Source has a Loop control. For a queue of several clips, VLC Video provides playlist controls, including Loop Playlist and Shuffle Playlist. Leave shuffle off if the sequence matters. OBS notes that VLC must be installed for VLC Video to appear and that 64-bit OBS requires 64-bit VLC. Consult the official Media Sources documentation for the available source settings rather than inferring them from another version or setup.
VLC Video’s visibility behaviour is especially important when scenes change. OBS documents options for playback to continue, pause, or stop when the source is not visible; its default is to stop when hidden and restart when visible. If switching to the slate hides the playlist, that setting may affect whether the current clip resumes, starts over, or progresses as expected. Choose the behaviour deliberately and test it with the actual playlist.
| What you need | OBS source | Useful controls | Main trade-off |
|---|---|---|---|
| Repeat one video | Media Source | Loop; restart when active; show nothing when ended | Simple playback, but it is a single file rather than a multi-item queue |
| Play several clips in order | VLC Video | Playlist order; Loop Playlist; Shuffle Playlist; visibility behaviour | Requires VLC and careful testing of what happens while hidden |
| Show a timed break | Media Source in a separate scene | Restart when active; loop off; end behaviour | Fixed duration may not match variable clip lengths |
| Show a fixed card | Image and text sources | Layering; position; visibility | Does not show an automatic timer or trigger a return by itself |
If you regularly replace or add clips, check how the change interacts with your playlist and scene setup before broadcasting. The steps in adding new videos to an always-on YouTube stream are relevant to maintaining the queue, while this article focuses on what appears at the boundary. Keep copies of the playlist and slate files in a location you can find again, and confirm that OBS still points to the intended files after any move or rename.
Try a boundary-triggered scene switch
OBS scenes and sources do not, by themselves, provide a guaranteed “show a slate between every playlist item” workflow. A community-described approach uses the Advanced Scene Switcher plugin to watch media state and change scenes when a playlist item is nearly finished. Treat it as a workaround, not an official OBS recipe: its success depends on the plugin version, source configuration, playlist behaviour, and the way your scene changes affect playback.
The general idea is to define a condition for the playlist source, such as it still playing with less than a chosen amount of time remaining, and then switch from the playback scene to the slate. Some OBS forum examples use a threshold around one or two seconds; another discussion describes a threshold under 1,000 milliseconds. These are examples reported by community members, not settings guaranteed to work for every file or installation. Start by understanding the condition in the installed plugin and use a threshold that you can observe reliably in tests.
A near-end condition may be more useful than waiting for an “ended” event. In a looping playlist, a source may advance to the next item instead of entering the state that a rule expects. However, moving the trigger earlier creates a different risk: a slow or imprecise transition can cut off the tail of the clip, while a late trigger can leave a moment of black or miss the boundary. The right point is something to establish empirically with your own clips.
Some community examples pair the scene change with advancing the playlist, while others depend on how the VLC source handles the next item. Do not add actions until you know which part is actually responsible for changing the playlist item in your setup. If both OBS’s source and the macro advance it, you could skip a clip; if neither does, the same clip could resume. Read the plugin’s current controls and test a short playlist with distinct filenames or visible opening frames so that an unexpected advance is obvious.
You can also keep the transition manual. Switch scenes with OBS controls or a configured hotkey when you can supervise the stream. That is less convenient for a long unattended schedule, but it avoids depending on an unverified trigger. For a service that needs the same boundary behaviour every day, compare the time required to supervise manual changes against the effort of testing and maintaining the automation.
For the community discussion of media conditions and scene changes, see the Advanced Scene Switcher thread on the OBS forum. A separate OBS forum discussion of VLC playlist scheduling illustrates that playlist behaviour and scene control have to be considered together. Forum posts report individual setups; they are useful leads, not compatibility guarantees.
Configure the return to playback
The slate needs a return path as well as an entry. If it contains a countdown video, you might use a second plugin condition that reacts when the slate media ends and switches back to the playlist scene. Check that the slate source actually reaches the expected ended state, and that its end behaviour does not loop or remain visible as an empty source in a way that confuses the rule. If the slate is a static card, it has no natural end event, so use a manual switch or another deliberate timing mechanism.
Decide when the playlist should move on. If the playlist continues while hidden, the next clip may already be playing by the time the slate ends. If it pauses while hidden, it may resume on the same clip, depending on the chosen visibility behaviour and the source. If it stops and restarts when visible, it may restart that clip rather than continue. A scene change alone does not tell you which of these outcomes applies; verify them with a short test.
Write the intended sequence in plain language before configuring rules: “clip nears end; show slate; playlist advances once; slate finishes; return to the next clip.” Then check whether each action happens once and only once. If a macro both switches scenes and advances the playlist, look for repeated triggers around the boundary. If the playlist advances on its own, avoid a duplicate advance action. The goal is a predictable sequence, not the greatest number of rules.
If you use StreamNeo to run an uploaded file as a continuous YouTube broadcast, a separate OBS slate-and-playlist transition is not the workflow that service is designed to automate; the OBS setup here is for people building the scene and source arrangement in OBS. Keep the distinction clear when choosing your approach, and do not assume a slate inserted in one playback workflow will carry into another.
Test timing and edge cases before going live
Test with the exact OBS, VLC, and plugin versions you plan to use. A useful test is a complete cycle: play a clip, observe the boundary trigger, confirm the slate appears, watch the slate end, and verify that the intended next clip returns. Repeat with more than one playlist item and check the result when the playlist loops. A single successful switch does not establish that the rule will behave the same at every later boundary.
Pay close attention to the source visibility setting. Forum reports describe cases where hidden VLC playback and media-state rules behave unexpectedly. Try the relevant continue, pause, or stop behaviour one at a time and observe both the picture and the playlist’s position after returning. If the rule depends on a source being active or on its remaining time, confirm that the value changes as expected while the source is hidden.
Check clips with different lengths and endings. A rule based on a fixed remaining-time threshold may behave differently on a very short clip, a file that freezes at the end, or a clip whose final frame is black. Listen as well as watch: a transition may show the slate while audio from the playlist continues, or cut audio earlier than intended. Decide whether the slate should carry silence, a short music bed, or the end of the previous clip, and set source audio levels accordingly.
Do not rely on a countdown reaching zero as proof that the return rule fired. Watch the actual scene transition and confirm the next video is visible and audible. If you intend to leave the broadcast unattended overnight, run a longer supervised test that covers repeated cycles, not just a single pair of clips. For stream status checks beyond the OBS preview, the guide to checking whether a 24/7 YouTube study stream is actually live covers a separate but useful monitoring question.
Keep a fallback. Save the scene collection before changing rules, know how to switch to a stable playback scene manually, and have a plain static slate ready if the timer or macro fails. If the transition misfires, it is better to display a clear card or continue the programme than to leave a blank canvas while troubleshooting. After changing plugin settings, restart or reload only as required by the installed software and test again before treating the configuration as dependable.
Decide whether automation is worth maintaining
A timed slate is most useful when a gap itself has value: it gives viewers a moment to orient themselves, announces the next programme, or avoids an abrupt cut. It also adds another source and transition to maintain. If the playlist already plays clips back-to-back without a distracting pause, adding automation may make the stream more complex without improving the viewing experience.
For a small devotional channel, a static “Next bhajan” card may be enough if someone is already supervising the stream. A station that runs a known sequence may benefit from a rendered countdown and a thoroughly tested return macro. A local news loop with changing clip lengths may be better served by a non-specific break card than a clock that implies the next segment will start at an exact moment. Match the slate to the reliability you can demonstrate, not the reliability you hope the automation has.
It can also help to think about rights and viewer expectations separately from scene mechanics. A countdown does not change the rights status of the videos in the playlist, and a slate does not make a stream compliant by itself. If your sequence includes commercial music, review the guidance on playing Bollywood songs around the clock on YouTube Live and check YouTube’s current official policies for your situation.
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 OBS add a countdown slate between playlist videos by itself?
OBS provides scenes, media sources, and VLC playlist controls, but the reviewed official documentation does not describe a built-in automatic between-item slate sequence. A community-described Advanced Scene Switcher workaround can watch media conditions and change scenes, but it is configuration-dependent. Test the full cycle with your installed versions before relying on it.
Should I use Media Source or VLC Video?
Use Media Source for a single file, such as a looping programme video or a pre-rendered countdown. Use VLC Video when you need a playlist of several files, and check the playlist order, loop and shuffle controls, and hidden-source behaviour. VLC must be installed for VLC Video to appear in OBS.
Why might an “ended” trigger miss the boundary?
A looping playlist may move to the next item rather than leave the source in an ended state. A near-end condition is one community-reported alternative, but the timing threshold and scene action need testing against your actual clips and settings. Do not assume the same rule will behave identically in every setup.
What should I test before leaving the stream unattended?
Watch repeated cycles, including a playlist loop, and verify that the slate appears, the playlist advances once, and playback returns with the intended clip. Check both picture and audio, plus what happens while the playlist source is hidden. Keep a manual fallback and confirm the stream itself remains live.