For a predictable sequence of local videos in an OBS YouTube Live broadcast, use a VLC Video Source, add files in the intended order, and leave Shuffle Playlist off. That preserves the list’s playback order; it does not, by itself, promise that OBS will reopen on the same file or timestamp after a restart.
Treat sequence and restart recovery as separate requirements. OBS documents the playlist controls, while a community plugin listing describes restoring the current file but does not promise its exact playback position. Test the behaviour you need before relying on it overnight.
Sequence and playback position are different
A playlist sequence answers a simple question: which file plays first, which follows it, and what comes after that. If your bhajan stream should move from an opening prayer to a set of songs and then an evening chant, a correctly ordered VLC Video Source list with shuffle disabled is the relevant control.
Playback-position recovery is a different question. It asks whether, after OBS closes and opens again, the broadcast resumes the same file and whether it resumes at the precise point where that file stopped. Keeping the list in order says nothing about either outcome. The playlist might begin again at its first item, or a source could behave differently depending on its configuration and version; the official documentation reviewed here does not establish a blanket restart-resume guarantee for the built-in source.
YouTube is the destination in this workflow, not the manager of the local OBS playlist. OBS sends its output to the live stream; the file list and playback controls are in OBS. Do not assume that reconnecting YouTube will restore the item or position being played on the computer.
This distinction matters for both content and operations. A study channel might be comfortable restarting its ambient loop from the beginning, while a local news loop may want the next scheduled item to follow a fixed sequence. Neither need necessarily requires resuming a video at its exact interrupted frame. Decide which behaviour matters before changing settings.
Install VLC for the OBS playlist source
OBS documents the VLC Video Source as the source type for a playlist, while its ordinary Media Source is for an individual file. The VLC source depends on VLC being installed, and OBS notes that 64-bit OBS needs 64-bit VLC. Check the OBS media sources documentation for the current requirements and descriptions before troubleshooting a missing source or an empty list.
Install VLC from its official source, then restart OBS if the VLC Video Source is not available in the Sources menu. Make sure the VLC and OBS builds match the architecture noted in OBS documentation. If you have updated either application recently, check that the source still appears and that a test file plays before building a long playlist.
To add the source, choose the scene that carries your prerecorded programme, add a source, and select VLC Video Source. Give it a descriptive name such as “Night playlist” rather than leaving several sources with indistinguishable names. Open its properties and use the playlist controls to add the files you intend to broadcast.
Avoid treating the ordinary Media Source as a drop-in playlist. It is appropriate when a scene needs one file, but a multi-file sequence needs a source that exposes a playlist. If you only have one continuous recording, the guide to looping a Media Source without a black screen covers a different setup. For many files in sequence, start with VLC Video Source instead.
Add files in the intended order
Add each file to the VLC Video Source list in the sequence you want viewers to hear or see it. Then inspect the displayed list rather than relying on the order in which files happen to appear in a folder. Names such as “01 opening”, “02 morning set”, and “03 closing” can help you and a second operator recognise the intended sequence, but the important check is the order shown in the source properties.
A practical way to build a schedule is to write down the intended progression first. For example, a devotional channel might list a short opening, morning bhajans, a longer instrumental section, and a closing prayer. A lofi channel might place a quiet introduction before its longer study mix. These are editorial choices, but a written sequence makes it easier to notice a file inserted in the wrong place before going live.
After adding files, review the whole list from top to bottom. If you insert a new item later, verify its placement in the list rather than assuming OBS appended it where you expected. Move items using the controls available in the source properties, then save the scene collection and reopen the properties to confirm the order has persisted in your working setup.
Use files that your local installation can read and play. Test each item, particularly if files come from different editing software or use different formats. A list can be correctly ordered but still appear to skip a file if one is unreadable, has been moved, or fails to start. Keep the media in a stable location rather than reorganising folders after configuring the source.
If you are streaming a continuous ambience track, a single looping video may be simpler than a playlist. For footage intended to run as a repeating scene, see the options in free rain and fireplace footage for a YouTube Live loop. If your programme is deliberately a sequence of separate segments, retain the VLC playlist and check each boundary during testing.
Leave Shuffle Playlist off
Shuffle Playlist determines whether the files are randomised or played in file-list order. For a fixed sequence, leave it off. That setting is the direct control for keeping the order you have arranged; it does not control what happens when OBS restarts.
This is worth checking even if the first few files appear to play correctly. A shuffled playlist can begin with a plausible item and only reveal the problem later, when a familiar programme is followed by an unexpected file. Open the source properties before a live session and confirm that Shuffle Playlist is unchecked.
Do not confuse “shuffle off” with a guarantee that the current position will survive a shutdown. It controls how items are selected as playback proceeds through the list. Whether the source remembers a current item after a full restart is a separate behaviour, and whether it remembers the timestamp within that item is more specific still.
For a channel with a fixed daily order, make the setting part of a short pre-broadcast check along with confirming the scene and audio levels. Keep a note of the expected first file and one or two later transitions. That makes it easier to detect a shuffled list during a local test, rather than discovering it after viewers are already watching.
Set looping for the ending you want
Loop Playlist controls what happens after the last file in the list. Turn it on when the sequence should begin again after its final item. Leave it off when the playlist should stop at the end. This is an end-of-list choice, not a restart-recovery setting.
Suppose a set has an opening, several programme blocks, and a final prayer. With looping enabled, playback starts the sequence over after that closing item finishes. With looping disabled, the list does not automatically cycle back to the opening. Neither selection means that closing and reopening OBS will resume precisely where it stopped.
Think about whether a loop boundary makes sense for the content. A rain ambience station may be designed to repeat indefinitely. A local news or community notice loop may also intentionally return to its first item, though you should listen to the transition from the last file back to the first. A sequence with a time-sensitive announcement may need an operator to review its content rather than leave it cycling without attention.
For a longer continuous stream, also consider whether the file sequence itself is suitable for repetition and whether its transitions are audible or visible. Looping cannot repair a black frame, a long silent gap, or a file that no longer exists at its saved path. Those are media and source checks, separate from both order and restart continuity.
Consider the Media Playlist Source plugin cautiously
If the requirement is to return to the file that was playing when OBS restarted, the community Media Playlist Source plugin is worth evaluating. Its OBS forum resource listing says that it saves the currently playing file so it will be played when OBS restarts. Read the plugin’s listing directly, including its stated OBS version and platform information, and verify compatibility with your own installation before depending on it.
Scope that claim carefully: the listing describes restoring the currently playing file, not the exact timestamp within that file. Do not infer that a restart will continue from the interrupted second, or that every interruption mode behaves the same way. The distinction is important if the content contains a spoken item that should not repeat, a timed news segment, or an uninterrupted musical performance.
The built-in VLC Video Source remains the straightforward documented choice for an ordered list. The plugin may be relevant when resuming the current file is a separate need, but it is a community add-on rather than evidence that the built-in source restores exact position. As with any add-on, consider how you will maintain it, whether it is compatible with your OBS version, and how you will recover if it stops working after an update.
A forum discussion about updating a VLC playlist being sent through OBS to YouTube illustrates a practical operator concern: whether changing the list affects a live broadcast and whether OBS or YouTube needs relaunching. It is a user discussion, not a universal technical guarantee. Read the OBS forum thread about updating a live VLC playlist as an example of the question, then test changes in your own scene before making them during an important broadcast.
StreamNeo can remove the need to keep a local OBS playlist running on a computer overnight when the actual requirement is to broadcast an uploaded video continuously, but it is YouTube-only and does not turn a playlist into a timestamp-resume guarantee. If you need a changing sequence managed inside OBS, keep testing the source and plugin behaviour that your workflow depends on.
Test order and restart behaviour locally
Before sending the setup to viewers, test it in a duplicate scene collection or an otherwise safe local session. Add a few representative files, confirm the order, check that shuffle is off, and set looping to match the intended ending. Watch enough of the sequence to verify transitions, audio, and whether each file starts as expected.
Then test the restart question explicitly. Note which file is playing and roughly where it is when you close OBS. Reopen OBS, load the same scene collection, and observe what happens. Record whether the playlist returns to its first item, the same file, or something else. If exact position matters, observe it, but do not treat a result from one test as proof that every later restart will behave identically.
Repeat the check after the changes most likely to affect your setup, such as changing the playlist, moving media files, updating OBS, or installing the plugin. Keep a written note of the versions and source settings used in the test. This is not a guarantee, but it gives you a practical baseline and helps separate a missing-file issue from a restart-position issue.
Do not experiment by restarting the production broadcast without a plan. A test can interrupt your programme or expose a blank scene to viewers. Use an unlisted or otherwise appropriate test stream if you need to confirm the end-to-end YouTube path, and consult current YouTube Help guidance for live-stream setup and status. For a more detailed 24/7 workflow, consider whether a prerecorded YouTube stream on a low-cost Linux VPS fits your operational needs; that is a different way of running a stream and not a fix for OBS playlist recovery.
Keep your recovery plan modest and specific. If restarting at the beginning is acceptable, document that expectation and confirm the opening item is suitable to repeat. If the current file should be selected after restart, evaluate the plugin claim in your own version. If the precise timestamp is essential, plan for manual review or a workflow you have tested for that exact requirement rather than assuming a control that the documentation does not promise.
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 Shuffle Playlist off guarantee the same file after an OBS restart?
No. It keeps playback in file-list order rather than randomising the files. It does not establish which file or timestamp OBS will restore after a full restart.
Does Loop Playlist make the playlist resume after a restart?
No. Loop Playlist determines whether playback starts over after the final file in the list. It is not a restart-resume control.
Will Media Playlist Source restore the exact point in a video?
The plugin listing says it saves the currently playing file so it will be played when OBS restarts. It does not promise the exact playback timestamp, so test the behaviour you need and do not assume position recovery.
Should I use VLC Video Source or Media Source?
Use VLC Video Source when you need a playlist of files, and ordinary Media Source when you need a single file. Install VLC for the VLC source and check OBS’s current documentation for its requirements.