If OBS stops after one video, first identify whether it is playing local files through a VLC Video source or showing a YouTube playlist in a Browser Source. Those are different playback systems, so OBS’s local playlist controls will not fix a YouTube embed, and adding autoplay is not a universal fix for a playlist that fails to advance.
Check the source type, then follow the matching route below. A local playlist needs VLC and the right loop setting; an embedded YouTube playlist needs its playlist URL and player setup checked. If you see an error, record it before changing several settings at once.
Identify the playlist OBS is playing
In OBS, select the source that displays the video and open its properties. The source name and settings give you the first useful clue. A VLC Video source lists media files; a Media Source usually points to one local file; a Browser Source displays a web page or embedded player. The word “playlist” may describe what you intend to play, but it does not tell you which source is doing the work.
This distinction matters because each source has its own controls. OBS documents Media Source for an individual media file, with a Loop option to replay that file after it ends. VLC Video can play several media files as a playlist and has a separate Loop Playlist option. A Browser Source is not an OBS VLC playlist: it shows web content, so the embedded player and the URL determine what video or playlist is available.
If you are unsure, open the source properties rather than relying on what appears in the preview. A Browser Source will show a URL field. A VLC Video source will show a playlist or file list. Note the source type, your OBS version and operating system, and whether the first video reaches its end before playback stops. Those details help distinguish a playlist-advance problem from a source that never had a second item to play.
| What you want to play | OBS source to check | Relevant control or next check |
|---|---|---|
| Repeat one local video | Media Source | Enable Loop |
| Play local files in sequence and repeat them | VLC Video | Add the files and enable Loop Playlist |
| Play a YouTube playlist | Browser Source | Check the playlist embed URL and player behaviour |
| Diagnose an embed error | Browser Source | Record the exact error and inspect the page setup |
For an example of a different way to repeat a single video, see this guide to making a YouTube live stream repeat a video automatically. It covers a repeat-one use case; it does not make a Browser Source behave like a local VLC playlist.
Check the local VLC source and installation
If the source is VLC Video, confirm VLC is installed on the computer running OBS. OBS’s media sources documentation says the VLC Video source depends on VLC being installed, and that 64-bit OBS requires 64-bit VLC. If VLC Video does not appear among your source choices, check the installation and matching architecture first. Restart OBS after installing VLC, then see whether the source is available.
Next, inspect the playlist itself. Confirm that the expected files are present in the source’s list and that their paths still point to the files on disk. A moved folder, an external drive that is disconnected, or a filename change can leave OBS unable to open a later item even when the first one still plays. If a file is missing or unsupported, the visible symptom may look like the playlist has stopped; check whether OBS displays an error or skips to a blank image.
Test each file on its own before testing the queue. Temporarily create a VLC Video source containing only the file that should play second. If it will not play by itself, the issue is with that file, its path, or its decoding environment, not the order of the playlist. If it plays on its own, return to the original source and check the playlist ordering and playback options.
A Media Source is not interchangeable with VLC Video. If you have added one file to a Media Source and expected OBS to move on to the next file in a folder, it has no multi-file playlist to advance through. Enable Loop if your intention is to replay that one file, or use a VLC Video source when you need a sequence of local files. For longer unattended use, consider whether a single prepared video is simpler than managing a changing local queue; the ocean sounds stream guide is one example of a single-file-style channel format.
Enable and test Loop Playlist
In the VLC Video source properties, add the local files you want to play and check the playlist order. Then enable Loop Playlist if the sequence should start again after its final item. This is distinct from looping one file: the setting applies to the playlist as a whole, so the source can return to its first item after reaching the end of the list.
Test with two short files before leaving the channel unattended. Watch the transition from the first file to the second, then from the last file back to the first if you have enabled Loop Playlist. A successful preview test establishes that the source can advance and repeat under current conditions. It does not establish that every later session will be free of file, computer, or network interruptions, so check the actual stream as well.
If the first file plays but the second does not, do not assume the loop option is at fault. Test that second file independently, confirm its path and format, and inspect the OBS status or logs for a file-open or playback error. If the queue reaches the end and stays stopped rather than returning to the first entry, check that Loop Playlist is selected, not only a control intended to repeat a single item.
If your goal is one file repeating continuously, use Media Source’s Loop option instead. If your goal is a sequence that repeats, keep the files in VLC Video and use Loop Playlist. The distinction is useful for a study or devotional channel where a sequence and a single long recording create different listening patterns; this Hindi government-exam study stream guide explores a channel use case, rather than prescribing a playback setting.
For Browser Source, check the embedded player setup
If OBS uses a Browser Source, inspect the URL and determine what it actually loads. A YouTube playlist page, a single video watch URL, and a YouTube playlist embed are not the same thing. A page that embeds only the first video cannot advance through a playlist merely because the playlist exists elsewhere on YouTube. If playback ends after the first item, verify that the URL or embed code includes the intended playlist rather than only the first video’s ID.
YouTube’s official instructions for embedding videos and playlists describe how to use its embed player. Check the current instructions and compare them with the URL in the Browser Source. If you edit the URL, remove private or account-specific information before sharing it for troubleshooting. Do not post stream keys, login details or other credentials.
When testing, load the Browser Source and observe what appears after the first video ends. Does the player show the next item, display an error, show a blank area, or stay on the finished video? These outcomes point to different problems. A visible error calls for investigating the error and the embedded page. A finished first video with no error makes it especially important to verify that the player received the playlist, not just the first video.
Do not apply VLC playlist controls to this source. OBS’s Loop Playlist setting belongs to a VLC Video source and does not manage a YouTube playlist in a Browser Source. Likewise, a Browser Source can load a web document, but its presence alone does not prove that the document has been constructed to continue through a playlist. Keep the troubleshooting steps tied to the source type you actually have.
If the Browser Source shows Error 153, treat it as a specific error branch rather than a generic explanation for every stopped playlist. The OBS forum discussion about Error 153 includes community guidance that the way an embedded page is loaded can matter. It is a forum discussion, not a complete official compatibility specification. Confirm that Error 153 is actually visible, consult current guidance, and avoid assuming that an iframe workaround applies to a stop with no error.
Distinguish autoplay from playlist continuation
Autoplay answers whether the player starts playback without someone pressing Play. Playlist continuation answers whether the player has a next item and moves to it when the current video ends. They are related, but they are not the same setting or test. A player may start the first item automatically and still fail to advance because it was given only a single-video embed or because something else affects the embedded player.
YouTube’s embed instructions document adding autoplay=1 to embedded video code to request automatic playback. Check the current YouTube instructions for the URL format you use. That parameter addresses start behaviour; it does not establish that autoplay alone fixes every embedded playlist, nor does it diagnose why a playlist stops after its first item.
Test the two behaviours separately. First, load the source and see whether the first video begins without interaction. Then, let the first video finish and observe whether the player moves to the next item. If the first test fails, investigate autoplay and the player’s ability to start. If the first test passes but the second fails, verify the playlist URL and whether the embed contains a playlist. Avoid repeatedly toggling autoplay when the actual fault is that the player was given only one video.
This separation also helps when you report the problem. “The Browser Source starts but does not advance” is more useful than “autoplay is broken” if video one plays and then stops. Include whether the player shows an error and whether the same embed advances outside OBS. The comparison can narrow down whether you are looking at the playlist itself, the embed setup, or its behaviour in OBS’s browser environment without claiming a cause before you have evidence.
Capture the failure and inspect logs
Reproduce the problem deliberately, then write down what happened in order: whether the source started, whether the first video reached its end, what the screen showed next, and whether the source began again after a brief wait. Note your OBS version and operating system, the source type, and whether the playlist consists of local files or a YouTube embed. Record the exact error text, if any.
For a YouTube source, note the general URL format and whether it is a playlist embed or a single-video URL. Remove tokens or details you do not want to share. For a local source, record whether the missing item plays on its own and whether its file path is still valid. These observations make it possible to distinguish “second file cannot open” from “there is no second item in the embedded player”.
Check OBS logs around the moment the video ends or the source changes. They may help show whether a local file failed to open or whether a source reported an error. Logs are evidence to investigate, not a guarantee that every player-level failure will be explained in one line. If the issue persists, share the relevant section through an appropriate support channel along with the OBS version, OS, source type and a concise reproduction sequence. Do not share credentials or a live stream key.
Change one thing at a time and repeat the same test. If you change the URL, source type and loop setting together, a successful result will not tell you which change mattered. Restore a known configuration when a test makes the behaviour worse, and keep a note of the original values. This is especially useful in a channel that already has a working scene: you can test a duplicate scene or source without disturbing the live output.
Choose a playback workaround that fits the job
The most reliable workaround is often the one that removes the uncertain hand-off you have actually observed. For a local sequence, keep the playlist in VLC Video, ensure every file opens, and test Loop Playlist. For one file, use a Media Source and its Loop option. For YouTube content, verify the playlist embed before replacing the player or moving to a different playback method.
If the first video plays in a Browser Source but the next does not, one community resource describes a Lua script that creates a Browser Source URL from a first video and following YouTube video IDs, with autoplay and loop options. It is a third-party community approach, not an official OBS fix. Review the resource and current requirements before relying on it, and test it off-air first. It may suit someone comfortable maintaining a script; for a non-technical operator, extra configuration can be a new failure point rather than a simplification.
Another route is to prepare a single local video that already contains the sequence, then play it as one file. That avoids a transition between separate playlist items, but it also means revising and re-uploading or replacing the prepared file when the sequence changes. It does not make YouTube’s embedded playlist continue; it changes the playback plan. For a channel that needs the same material to run while the operator’s computer is off, StreamNeo removes the specific burden of keeping that computer on to play and send the file; it does not change what an embedded YouTube playlist can do.
A locally controlled setup can be preferable when you need to change items frequently or want direct control over the OBS scene. It depends on the computer, files, installed playback software and a stable connection remaining available. A prepared single video reduces queue-management work, but is less convenient to update. A cloud file-based approach can remove the need to leave your computer running, while giving up the flexibility of changing a live local playlist through OBS. Choose based on which constraint matters for your channel, and test the whole path before making it the overnight setup.
For a more technical alternative, the guide to running an always-on YouTube stream with Docker and FFmpeg covers a different operating route. It is more appropriate if you are comfortable managing that workflow than if you simply need to correct one OBS source setting. Whichever route you choose, run a controlled test that crosses the transition where the old setup failed, and check both the player and the live output before leaving it unattended.
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 turning on autoplay make a YouTube playlist continue?
Not necessarily. YouTube documents autoplay as a way to start an embedded video automatically, but that is separate from whether the embed has a playlist and advances to its next item. Check the playlist URL and test what happens when the first video ends.
Where is Loop Playlist in OBS?
It is a setting for the VLC Video source, which can play a list of local media files. It does not control a YouTube playlist shown in a Browser Source. For one local file, check the Media Source’s Loop option instead.
Why does VLC Video not appear in my source list?
OBS’s VLC Video source requires VLC to be installed, and the OBS documentation says 64-bit OBS needs 64-bit VLC. Check that VLC is installed with the matching architecture, then restart OBS and check the source list again.
Should I use an iframe workaround for Error 153?
Only investigate that branch if the Browser Source actually shows Error 153. The cited OBS forum discussion is community guidance, not an official guarantee that a workaround will resolve every embed or playlist problem. Check current documentation and test any change before relying on it in a live channel.