If an OBS playlist is not switching videos on YouTube Live, first identify what is actually playing the files. OBS’s VLC Video source, a single Media Source, a browser source and scene automation follow different rules, so the same fix will not apply to all of them.
For a local playlist, start with the VLC Video source and its properties. Check the playlist entries, loop and shuffle settings, and what happens when the source becomes hidden. Then test the behaviour locally before changing a live broadcast.
Identify which playlist or source is involved
The word “playlist” can describe several different OBS workflows. A channel might be using a list of local devotional videos in VLC Video, separate Media Sources arranged across scenes, a YouTube playlist displayed through a browser source, or an automation tool that changes scenes on a timer.
These workflows can look similar on the stream while behaving differently inside OBS. The first useful check is therefore not a setting. It is the Sources list in the scene that is currently producing the broadcast.
Open the relevant scene and look at the source name and type. If it is labelled VLC Video, the checks in the next sections are directly relevant. If it is Media Source, you are probably dealing with one media file rather than a built-in playlist. If it is Browser, the page or player inside that browser source controls playback. If scenes are being changed automatically, the scene switcher may be resetting the source rather than the playlist failing to advance.
This distinction matters when a stream returns to the first file. A reset after editing a playlist is not the same symptom as a file that reaches its end and never moves to the next item. A scene that becomes hidden can also stop or restart playback, even though the YouTube broadcast itself has not ended.
For a broader view of the choices involved in running a pre-recorded channel, see this guide to software for streaming pre-recorded videos to YouTube Live. Use it to compare workflows, not as a substitute for identifying the source in your own scene.
Check whether the source is VLC Video or Media Source
OBS documents Media Source as a way to add supported media files to a scene. VLC Video is the source designed for a playlist of items. OBS describes it as allowing a playlist in a way that is similar to an image slideshow. The official explanation is in the OBS Media Sources documentation.
A Media Source is therefore a reasonable choice when one scene needs to play one file. It is not the same as placing several files in a VLC playlist. Adding more Media Sources to a scene does not automatically create a sequential playlist unless another part of your setup controls which source is visible and when.
VLC Video also has a dependency that Media Source does not have in the same form. VLC must be installed for the VLC Video source to appear in OBS. OBS’s documentation says that 64-bit OBS requires 64-bit VLC. If VLC Video is missing, check that VLC is installed and that its bitness matches the OBS installation where this applies.
Do not treat installing VLC as a fix for every playback problem. It only addresses the source’s availability and compatibility. Once VLC Video is present, you still need to inspect the playlist, playback order and visibility behaviour.
If you are using a Media Source, select it and open its properties. Confirm which single file it references and whether that source is being recreated or reset when a scene changes. If your intention is to play several local files in sequence, consider testing the same files in a VLC Video source rather than adding them as unrelated Media Sources.
A browser source needs a different investigation. Check the page URL, the player’s own controls and whether the page reloads when the source is refreshed. VLC-specific settings such as Loop Playlist and Shuffle Playlist will not control a video player inside a browser source.
Inspect the VLC playlist and playback behaviour
With VLC Video selected, open its properties and inspect the playlist itself. Confirm that every intended file is listed, that the files can be opened locally, and that the order is correct. If one item is missing or points to a moved file, the visible symptom may appear at the transition even though the problem is the playlist entry.
Check Shuffle Playlist separately from Loop Playlist. With shuffle disabled, OBS says that items remain in list order. With shuffle enabled, the next item is selected randomly. Turn shuffle off while diagnosing the problem so that you can tell exactly which file should play next.
Loop Playlist has a different job. OBS describes it as restarting the source when it has run out of media files. It controls what happens after the final item; it does not, by itself, explain why the first item fails to advance to the second. If the source should repeat continuously, enable looping, but do not expect that setting to repair a transition that fails in the middle of the list.
Use a simple test order while checking the source. Put two short local files in the playlist, with recognisable opening frames or audio. Keep shuffle off. Watch whether the first file reaches its end and whether the second one starts. This tells you more than testing a long list of similar-looking videos overnight.
Also check the files themselves. A file that has an unusual container, damaged ending or unsupported track can make a transition difficult to interpret. If a particular item always causes the problem, remove it temporarily and test the remaining pair. You can use this HandBrake guide for preparing videos for 24/7 YouTube streaming if the files need to be standardised, but conversion is not the first step when the source type or visibility is still unclear.
Keep the original playlist unchanged until you know what is happening. Make a small copy for testing, record the order, and change one property at a time. That makes it possible to identify whether the cause is a missing entry, shuffle, looping, a source reset or the file at the transition.
Check whether a scene or source reset is occurring
A playlist can appear to fail when OBS is actually restarting the source. Look for anything that causes the scene or source to be recreated, hidden and shown again, or refreshed while the stream is running.
Start with scene visibility. OBS documents the VLC source’s default visibility behaviour as “Stop when not visible, restart when visible”. It also documents options for pausing or continuing when the source is hidden. The exact choice should match your intended scene design.
This setting refers to whether the source is visible in the active OBS scene. It does not refer to whether the OBS application window is on screen, minimised or covered by another window. A source can be fully visible to the broadcast while the OBS interface is not in front of you.
If a playlist resets whenever you change scenes, determine whether the VLC source is hidden in the intervening scene. If it stops while hidden and restarts when visible, returning to that scene can make playback begin again. That may be expected behaviour under the selected visibility setting rather than a YouTube problem.
Check for manual edits as well. A user report on the OBS forum about adding media to a running YouTube Live stream describes playback returning to the first video after adding a Media Source or editing a VLC playlist during setup. That is a report from one workflow, not proof of a universal OBS bug or a general fix.
The practical response is to avoid making playlist edits during a live test when you can. Build and save the playlist first, then run it through a local test. If you must edit it while preparing the channel, note the exact action and observe whether playback resumes from the beginning. This gives you a reproducible symptom to report rather than a general impression that “OBS is not switching”.
Scene automation deserves its own check. A timed scene change may be doing exactly what it was configured to do, while the source’s visibility setting then restarts the video. Optional scene-switching tools can be useful for a planned sequence of scenes, but they are not required to fix a standard VLC playlist that should advance between local files.
Test changes with a short local playlist
Before testing on YouTube Live, reduce the setup to the smallest useful case. Create a test scene containing only the VLC Video source and a short playlist of two or three local files. Remove browser sources, overlays, alerts and scene automation for this test.
Use files that are easy to distinguish. For example, use one file with a spoken label or a different opening image and another with a different label. The point is to observe the transition, not to judge the finished channel presentation.
Run the test and record four things:
| What to observe | What it helps distinguish |
|---|---|
| The first file never starts | Source availability, file path or source configuration |
| The first file plays but the second never starts | Playlist entry, file transition or media compatibility |
| The second starts, but the list returns to the first at the end | Looping behaviour after the final item |
| Playback returns to the first after hiding or editing the source | Visibility behaviour or a source reset |
Keep Shuffle Playlist off during this test. If the second file starts reliably, add the other files one at a time and retest. If one particular file breaks the sequence, remove it and test it separately. If the short playlist works until you add scene changes, restore those changes one at a time.
Save a copy of the working test scene. It becomes a useful control when you rebuild the full channel. If the full scene later fails but the small scene still works, the difference is probably in the additional sources, scenes, visibility rules or automation rather than in the basic VLC playlist.
Do not use the YouTube dashboard as your first diagnostic tool. YouTube receives the encoded output from OBS; it does not know whether OBS selected the next local file, hid a scene or restarted a source. Confirm the local playback path first, then check the live output.
If your channel depends on long overnight runs, also prepare the media files consistently. Resolution, frame rate and encoding choices can affect how easy transitions are to diagnose. This guide to preparing a 24/7 YouTube loop stream covers file preparation, while this test is specifically about whether OBS moves from one listed item to the next.
Confirm whether the stream itself is resetting
Once the local playlist behaves correctly, reconnect the rest of the broadcast in stages. First restore the complete scene without automation. Then run a private or otherwise controlled live test if that suits your channel. Compare what happens in OBS with what appears in the YouTube player.
If OBS shows the second file playing but the YouTube stream goes back to the first, investigate the broadcast connection and encoder state rather than the VLC playlist. Look for a dropped connection, an encoder restart or a new live session. A reconnect can produce an apparent restart even when the local source was advancing normally before the interruption.
If both OBS and YouTube return to the first file at the same moment, focus on the source or scene state. Check whether a playlist edit, scene switch, source refresh or visibility change happened immediately beforehand. Write down the time and action instead of changing several settings at once.
Network trouble can affect the live broadcast without explaining a local playlist that never advances. Conversely, a perfectly stable network cannot make a Media Source become a multi-file playlist. Keep these two layers separate when troubleshooting.
For a stream that appears to be losing output rather than changing files, review the bitrate and dropped-frames troubleshooting guide. It addresses a different class of failure, but distinguishing dropped frames from source resets can prevent you from changing the wrong OBS property.
YouTube’s own guidance is the right place to check current live-streaming requirements and behaviour. Use the official YouTube Help live streaming pages when the evidence points to the broadcast connection, account, encoder output or live control room rather than to the local playlist.
When to seek OBS-specific help
Seek OBS-specific help when the source type is clear, VLC is available where required, the playlist entries are valid, and a small test still reproduces the failure. Include enough detail for another person to repeat the test.
Record the OBS version, operating system, source type, VLC version where relevant, file formats, playlist order and whether Shuffle Playlist is enabled. Say whether the problem occurs at every transition or only with one file. Also state whether it starts after a scene change, a source edit, hiding the source or reconnecting the live broadcast.
An OBS log is more useful when it is tied to a reproduction. Start with the small test playlist, reproduce the failure, then provide the log and the steps in order. Avoid posting a description such as “playlist does not work” without saying whether you used VLC Video, Media Source or Browser.
The OBS Help Portal points to the project’s documentation, forums and community support channels. Read the current guidance before applying advice from an old forum thread, because source behaviour and interface details can change between versions.
For an always-on channel, also decide whether running OBS continuously is the right operational choice. A spare computer gives you direct control and makes local testing straightforward, but it leaves you responsible for power, updates, connectivity, OBS state and recovery after a restart. A cloud-based YouTube-only workflow such as StreamNeo removes the need to leave your own computer running once the file and stream key are configured, while you still need to check the current YouTube rules and your content rights.
Do not move to another workflow merely because one setting was misunderstood. First establish whether you need a local VLC playlist, a set of scene changes or a browser player. Then choose the arrangement that matches the channel and the amount of hands-on recovery you can provide.
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
Why does OBS start the first video again after I edit the playlist?
Editing a source or playlist can coincide with playback being reset, and a 2020 OBS forum report describes that behaviour in one setup. It does not establish that every OBS playlist resets after editing. Test edits with a short local playlist before using the workflow in a live overnight channel.
Should I use Media Source or VLC Video for several local videos?
VLC Video is the OBS source documented for a playlist of media items. Media Source is described as adding a supported media file to a scene, so several Media Sources need separate visibility or scene logic if you want them to play in sequence.
What does Loop Playlist actually change?
Loop Playlist controls what happens after the source has run out of media files. It does not by itself repair a transition between the first and second items. Turn it on when the finished playlist should begin again after the final item, and test the individual transitions separately.
Why does changing scenes restart my VLC video?
The VLC source’s visibility behaviour can stop playback when the source is hidden and restart it when it becomes visible. Check whether the source is present in the active scene and whether a scene switch or automation rule is hiding and showing it. The setting concerns source visibility in OBS, not whether the OBS window is visible on your monitor.