To switch between prerecorded videos in an OBS YouTube stream, choose the behaviour you need: play files in sequence, move between scenes yourself, or switch scenes when a clip ends. These are different workflows, and only the last two involve changing scenes; a VLC Video playlist advances through files within its source.
For a simple ordered run of clips, start with a VLC Video source. Use separate scenes and Studio Mode when you need to choose the moment of each change. For an end-triggered scene change, configure a third-party plugin and verify its compatibility with your OBS version before you depend on it.
Choose how the videos should advance
First decide what “switch” means for your channel. If a set of clips should play one after another without an operator choosing each one, put them in a playlist. If you need to decide when a hymn, announcement or news segment goes live, prepare separate scenes and transition manually. If the next scene should appear when the current clip ends, use an automation plugin and test its trigger behaviour.
| What you need | Starting workflow | Main trade-off |
|---|---|---|
| Play files in a defined order | VLC Video playlist | Requires VLC; playlist and source visibility settings affect playback. |
| Choose when the next clip appears | Separate scenes with Studio Mode | An operator must select and transition to the next scene. |
| Change scenes when media ends | Advanced Scene Switcher macro | Adds third-party configuration and compatibility checks. |
A playlist is not the same as automatic scene switching: it plays a sequence inside a source, while the other workflows put another OBS scene on the programme output. For example, a kirtan channel might loop a prepared set in one scene overnight, then use separate scenes for a live announcement that needs careful timing. If you are planning the wider channel setup, see how to run a 24/7 Bengali kirtan stream on YouTube.
Keep YouTube delivery separate from these choices. OBS encodes whichever scene or source is on its programme output; the YouTube stream connection carries that output to viewers. Changing the video workflow does not itself create or configure the YouTube broadcast.
Set up a VLC Video playlist for sequential playback
OBS’s ordinary Media Source is intended for an individual local file. For a playlist, add a VLC Video source to a scene and build the list in the order you want. The OBS Project’s Media Sources guide describes the available media source types and the VLC dependency. VLC must be installed for the VLC Video source to work.
If the source is missing or fails to load, check that VLC and OBS have matching architectures. The OBS documentation states that 64-bit OBS requires 64-bit VLC. Install the matching VLC version, then restart OBS if needed and check whether the source is available. Do not assume a file problem is the cause until you have checked this dependency.
In the VLC Video source properties, add each file and arrange the list. Review Loop Playlist and Shuffle Playlist rather than relying on memory or assuming a particular order. The documented defaults are loop on and shuffle off, but a saved scene or copied configuration may not reflect the settings you expect. For a fixed programme, confirm the first file, the sequence, and whether the playlist should return to its beginning after the last clip.
Decide what should happen when the source is not visible. OBS provides VLC source behaviour options such as stopping or restarting, pausing and resuming, or continuing playback while off-scene. Those choices matter if another scene temporarily replaces the playlist: when you return, the video may have continued, paused, or restarted depending on the setting. Use a short test before relying on it for a long broadcast.
Fit the source to the canvas and inspect both picture and sound. In the Sources dock, visibility controls whether a source appears, and the order of sources determines which ones layer above others. Check that a logo or text overlay is meant to sit above the video, and that the VLC audio is audible at a sensible level in the mixer. A clip can be playing correctly while being obscured by another source or routed at an unusable level.
For a channel that needs different blocks at different times, playlist order alone may not be enough. You could make a longer programme file, use separate scenes, or use an automation setup; the right choice depends on how much operator input the schedule allows. Readers weighing a different playlist tool can compare the trade-offs in the vMix playlist workflow, but its instructions are not a substitute for checking the OBS configuration described here.
Prepare separate scenes for manual switching
Manual switching is the most predictable choice when a person should decide exactly when a clip becomes live. Create a scene for each segment, such as “Opening chant”, “Instrumental”, and “Notice”. Add that clip as a Media Source in its scene. A scene can also contain titles, a logo, or other sources that belong with that particular segment.
A Media Source handles one local file. In its properties, choose whether playback should restart when the source becomes active and whether the file should close when inactive. Restarting is useful when returning to a scene should start its clip from the beginning. Closing the file when inactive may save resources, but reopening can cause a short delay; if a seamless return matters, test the setting with the actual files and machine.
Name scenes and sources so you can identify them without guessing. If there are several similar clips, include a useful title or sequence label in the scene name. Check that each scene has the intended file, crop, audio level and overlays. A scene that looks right in the editor can still contain a muted source or an old file path, so inspect the mixer and play each clip rather than treating the scene list as proof.
Manual scenes are not automatic. OBS will not move to the next scene merely because a Media Source reaches the end unless you have configured an automation method. That distinction is especially useful for devotional or local-news channels: you may want an operator to hold on a closing prayer, wait for a presenter, or decide whether an announcement is ready before moving on.
Use Studio Mode to preview and transition
Studio Mode separates the scene you are preparing from the scene viewers currently see. The Preview pane is for editing and selecting the next scene; the Program pane is the live output. Selecting a scene in Preview does not by itself put it on air. When you are ready, press Transition or use a configured transition hotkey or Quick Transition.
Choose a transition deliberately. A Cut changes immediately; a Fade takes the duration configured for that transition. A brief fade can soften a change between music videos, while a cut may suit a news slate or a timed announcement. The duration is a presentation choice, not a way to make the next file load more reliably. If a source needs time to open, test it and choose settings that avoid showing a blank frame.
Before the broadcast, practise the sequence in Studio Mode: keep the current scene on Program, select the next scene in Preview, verify it, then transition. Confirm that the live side changes only when intended. If another operator is helping, agree on the scene names and transition cue; Studio Mode provides control, but it cannot decide whether a segment is editorially ready.
You can switch scenes without Studio Mode, but the preview/program separation is valuable when the change needs a check first. It is also useful when a 24/7 stream includes both a loop and occasional announcements: keep the loop live while preparing the announcement, then transition when the wording and sound are ready. For broader guidance on keeping OBS running through interruptions, see how to fix OBS stopping a 24/7 YouTube live stream.
Configure Advanced Scene Switcher for media-ended changes
A scene change triggered by the end of a clip needs automation beyond a basic playlist or manual Studio Mode workflow. Advanced Scene Switcher is a third-party OBS plugin with macros, media conditions and scene-switch actions. Its update notes describe handling media playback completion; the exact controls and names can vary by plugin version, so follow the documentation for the version you install.
Start by checking the plugin’s OBS Project resource listing. At the research check, that listing identified Advanced Scene Switcher 1.36.1 and OBS 31.1.1 as the minimum supported OBS version. These are version-specific details, not a promise that all later or earlier combinations work. Recheck the listing and the plugin’s own documentation before installing, especially after an OBS update.
Once compatibility is established, create a macro for the source and scene you actually want to monitor. Use a media condition that detects the end of the relevant clip, then an action that changes to the intended next scene. Match the macro to the exact scene and source names. A broad condition can fire when a different media source ends, or fire again when you did not expect it.
Plan what should happen after the final clip or an unexpected end. A fallback scene might show a holding image, a slate, or a known playlist. Set the conditions and actions so the macro does not repeatedly trigger into a loop of scene changes. If the next scene contains a source that immediately ends as well, consider whether that is intended to cascade or whether another condition is needed to prevent a chain of unwanted transitions.
Do not confuse this with OBS’s built-in Automatic Scene Switcher. The built-in feature and a plugin macro are not interchangeable descriptions of the same media-ended setup. Use the plugin’s documented condition and action for the behaviour you want, then verify what happens when playback ends, when you leave the monitored scene, and when the source is restarted.
Check OBS and plugin compatibility before relying on automation
OBS, VLC and plugins have separate version and architecture requirements. The VLC dependency applies to VLC Video playlists; the Advanced Scene Switcher compatibility check applies to its own plugin. Installing one does not satisfy the other, and a plugin that worked on an older OBS installation should not be assumed to work after an update.
Before changing a working broadcast setup, note the OBS version and operating system, then check the plugin’s current supported versions and installation notes. If you run a portable or otherwise unusual OBS installation, verify that the plugin is being installed in the location used by that installation. The OBS resource page and plugin documentation are the relevant places to confirm current requirements; avoid relying on an old forum post or a tutorial made for a different release.
A compatibility check is not a guarantee of correct behaviour. Even when a plugin loads, its macro may not match your source names, may respond differently to a particular media format, or may conflict with another configured action. Test in a duplicate profile or a non-public session before changing a channel that viewers depend on overnight.
For uninterrupted operation, decide what the channel should show if the automation does not act as expected. A stable fallback scene is easier to recover from than a blank canvas or an unintended desktop capture. If you are comparing ways of hosting a continuous OBS setup, the OBS on Linode setup guide is relevant background, but it does not remove the need to verify local scene and plugin behaviour.
Test transitions before going live
Test the whole path, not only the scene switch. OBS recommends testing scene configuration and stream performance before a first live stream. Start with a local recording or a private test broadcast, using the same files, audio devices and transitions you intend to use. Watch the resulting recording from a viewer’s perspective to catch black frames, clipped titles, missing audio and abrupt changes.
For a playlist, check the first item, a middle item, the end of the list, and the loop or stop behaviour. Confirm shuffle is off if order matters. Switch away from the playlist scene and return to see whether playback pauses, continues or restarts as configured. Do this with representative files rather than assuming every encode will behave identically.
For manual switching, practise selecting scenes in Preview and transitioning at the intended cue. Check that no unprepared scene is sent to Program by a stray click or hotkey. For media-ended automation, test clips of different lengths, the transition after each expected end, and the fallback path. Include a test where you leave the monitored scene before a clip finishes, and confirm the macro does not unexpectedly change the live output later.
Then check the YouTube connection. In YouTube Studio’s Live Control Room, create or select the stream and configure OBS with the supplied server URL and stream key. YouTube Help explains that a stream key is the encoder credential used to send the feed to YouTube; keep it private, as someone with the key may be able to send a feed to your stream. The YouTube live streaming setup guidance covers encoder setup. Verify the correct account and stream are selected before starting a public broadcast.
YouTube settings such as latency and DVR affect how the delivery behaves for viewers, not which OBS scene is active. Lower latency settings can involve a trade-off with playback buffering, while DVR allows viewers to pause and resume from their position. Check YouTube’s current live stream latency and DVR guidance for the available settings and implications. A viewer may see a scene change later than the operator because of delivery delay; that does not mean OBS failed to transition.
If the channel is meant to run while your computer is off, local OBS with a VLC playlist or plugin macro is not that arrangement: it depends on the computer running the broadcast. StreamNeo turns an uploaded video into a YouTube live stream, so the specific burden of keeping your own computer on to play a prepared file is removed; it is YouTube-only and is a different workflow from controlling OBS scenes.
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
Will OBS automatically switch to the next scene when a video ends?
Not by default in the manual-scene workflow. A VLC Video source can advance through its own playlist, while a scene change at media end requires an automation configuration such as an Advanced Scene Switcher macro. Test the exact source and scene behaviour before relying on it.
Do I need VLC for every OBS video?
No. OBS Media Source is for an individual local file and does not require VLC Video’s playlist workflow. VLC must be installed when you use the VLC Video source, and 64-bit OBS requires 64-bit VLC according to the OBS documentation.
Can I choose the transition timing myself?
Yes. Put clips in separate scenes, turn on Studio Mode, prepare the next scene in Preview, and use Transition when you are ready. This is a manual workflow; it will not advance simply because the current clip ends.
Is Advanced Scene Switcher compatible with every OBS version?
No universal compatibility should be assumed. Check the plugin’s current OBS Project listing and documentation for its supported OBS versions and operating systems, then test the macro with your own sources before using it on a live channel.