If an OBS VLC Video Source playlist stops after a file path changes, first inspect the saved playlist entries and update any that still point to the old location. Then check whether the playlist should loop, whether the source is being hidden by a scene change, and whether VLC is installed in the architecture OBS expects.
A changed path is one plausible cause, not proof of an OBS bug, and correcting it will not explain every kind of stop. Work through the checks below in order, changing one thing at a time so you can see whether the behaviour changes.
1. Confirm the source and the symptom
Start by confirming that the source in question is OBS’s built-in VLC Video Source. In the Sources list, open the source’s properties and check that it is the playlist-capable VLC source, rather than an ordinary Media Source or a separate playlist plug-in. The settings differ, so VLC-specific assumptions may not apply to a different source type.
OBS describes the VLC Video Source as using VLC libraries for extended media support over the built-in Media Source. Its Media Sources help page also says VLC must be installed for the source to appear in OBS. That is useful both when diagnosing a playlist and when the source is missing altogether.
Next, pin down what “stopping” means on your setup. Does playback stop as soon as you edit or reopen the properties, when it reaches the changed item, at the end of the list, or when you switch scenes? Note the last item that played and whether playback resumes after you show the source again. These distinctions point towards different checks; they are more useful than treating every stop as the same failure.
If the problem appeared while you were changing scenes or rebuilding a continuous broadcast, keep visibility behaviour separate from playlist health. You may also find it useful to compare this desktop workflow with ways to run a 24/7 lo-fi Hindi beats channel, which covers the wider job of keeping a channel going rather than diagnosing this particular source.
2. Trace each saved path to its current location
Open the VLC Video Source properties and inspect every playlist row, not just the item that seemed to trigger the stop. Compare the displayed path with where that file lives now. A folder rename, a file moved into a new folder, a changed drive letter, an unmounted external drive, or a network location that is no longer available can leave an entry pointing somewhere the computer cannot reach.
Follow the path in the operating system’s file manager. Check that the file exists at that exact location, that its name and extension match, and that you can open it locally. A file that opens from a recent-items list may still be opening from a different folder than the one stored in OBS. If the media is on removable or network storage, confirm that it is mounted or connected before testing the playlist.
Pay attention to whether several entries share a parent folder. If you moved a whole collection, multiple rows may now be stale even though only the first broken item is obvious during playback. Conversely, if only one file was renamed, avoid rebuilding the whole list before checking that entry. Keeping the diagnosis narrow makes it easier to tell whether an edit helped.
OBS’s VLC source implementation rebuilds its file list from the source settings and includes handling for missing files, including a replacement path when one is supplied. That supports inspecting and repairing the saved entries; it does not establish why a particular user’s playlist stopped. The source implementation is technical background, not a substitute for checking the path on your own machine.
3. Repair invalid entries carefully
Once you have identified an outdated entry, use the source properties to point it at the current file, or remove and re-add that playlist item if direct editing is not available in your version. Select the actual media file rather than its containing folder unless the interface specifically asks for a folder. Confirm the resulting entry is the intended one before applying the properties.
If the file is genuinely gone, do not leave a dead entry in the list and expect playback to continue reliably. Remove it, or restore the file to the intended location, then check the order of the remaining items. A playlist that previously had a particular sequence may behave differently after an item is removed, so review the list from top to bottom.
For multiple broken entries, repair them in small batches and test after each batch. This is slower than changing everything at once, but it can identify whether one particular file, path, or item boundary is associated with the stop. Keep a note of the old and new locations if the playlist is important; it makes a later rollback or migration less error-prone.
Do not assume that changing a path in the file manager changes the path saved in OBS. The source’s playlist settings are the record to verify. Likewise, a path that is valid while you are logged in may not be available after a reboot or a drive remount. If the channel runs overnight, test the same storage arrangement you expect it to use then.
For a channel built from long prerecorded loops, it can help to distinguish the source problem from the publishing method. This article on live streaming versus pre-recorded video explains the format trade-offs, while the checks here remain specific to the playlist entries stored in OBS.
4. Check loop and visibility behaviour
If the playlist plays through its items and then stops at the end, check Loop Playlist in the VLC Video Source properties. OBS documents this setting as controlling whether playback restarts after it runs out of media files. It is not the same as repairing a broken path: looping an incomplete or invalid list does not make a missing file reachable.
If the stop coincides with switching scenes, inspect Visibility Behaviour. OBS documents a default behaviour of stopping when the source is not visible and restarting when it becomes visible. That setting concerns whether the source is shown in the active scene; it does not determine whether its saved file paths are valid.
Try a controlled scene test. Keep the source visible in one scene and observe it through an item transition. Then, if your usual setup hides it during a scene change, reproduce that change and see whether the stop follows the visibility change rather than a particular playlist row. Avoid changing loop and visibility settings together at first: otherwise, a successful test will not tell you which setting mattered.
These options matter especially if you use scenes for adverts, schedules, or temporary holding screens. Decide what you want to happen when the VLC source is hidden. If playback should continue in the background, the relevant visibility choice may differ from a setup that should restart media when the source returns. Make the choice deliberately, then test it in the scene arrangement you actually use.
5. Confirm VLC installation and architecture
If VLC Video Source does not appear in OBS, or the source is unavailable after a change to the computer, verify that VLC is installed. OBS’s Media Sources documentation states that the VLC source requires VLC to be installed to show up as an available source. OBS also specifies that 64-bit OBS should use 64-bit VLC.
Check the architecture of OBS and VLC rather than relying on the application names alone. If OBS is 64-bit, install the matching 64-bit VLC version as OBS instructs. Then restart OBS and check whether the VLC source is available. This installation check addresses source availability and compatibility; it is not evidence that a particular playlist path has been fixed.
If the source is already visible and can play some of the playlist, VLC installation is less likely to explain one stale entry than the path itself. Still, when the problem began after reinstalling or moving applications, confirm both the installation and the saved media locations. They are separate things: VLC enables the source, while the playlist rows identify the files it should play.
For another kind of always-on stream, the failure point may be downstream of OBS rather than inside a playlist. If your broadcast also loses sound after a reconnect, use the separate audio and FFmpeg timestamp troubleshooting guide rather than assuming a missing media path explains that symptom.
6. Test after correcting paths
Apply the repaired playlist settings and run a small, observable test before relying on the source overnight. Watch it play the corrected item, advance to the next item, and reach the end of the list if you expect it to loop. If the stop used to coincide with hiding the source, test a scene change separately. Record which action produces the failure, if any.
For a useful test, keep the playlist order and source settings stable while checking the paths. If you change a row, loop behaviour, visibility behaviour, and scene layout all at once, you may get a working result without learning what caused the original stop. That may be acceptable for a quick recovery, but it leaves you with less confidence when the same symptom returns.
Test the storage conditions that apply to your real broadcast. If files live on an external drive, use the drive in the state you expect during the stream. If they are on a network share, check that the share is available when OBS needs the next item. A file that plays immediately after you browse to it is not necessarily proof that the whole list will continue through later entries.
If you need your own computer switched off while a prerecorded channel continues, StreamNeo removes the specific burden of keeping this desktop VLC source and computer running for that broadcast: you upload a video, provide your YouTube stream key, and the service runs the stream from the cloud with monitoring and automatic restart if it drops. It is YouTube-only, so it does not replace the local OBS repair if you need this particular playlist on your own machine.
7. Escalate after local causes are checked
If the paths are valid, the items open locally, loop and visibility settings match your intent, and the source still fails to continue, gather details before changing software. Record your OBS version, operating system, VLC version, source type, the last item played, and whether the failure follows a scene transition or occurs at an item boundary. A short reproduction sequence is more useful to someone helping you than “playlist stopped”.
You can then check whether the behaviour is specific to the built-in VLC Video Source and your version, or whether it points to a different source or plugin. One separate option is the third-party Media Playlist Source plugin, which is distinct from OBS’s built-in VLC Video Source. Its listing describes an alternative based on Media Source internally and says playlists can be edited during playback, including when items are reordered. That makes it worth investigating only when those capabilities address your need, not as a general cure for stale paths.
Check the plugin’s current compatibility with your OBS version and platform before installing it. The author’s release history includes version-specific requirements and changes to Windows installation details. Its 0.1.3 release notes, dated 13 April 2025, describe fixes for continuation after a transition and when the next item has the same video path. Those notes concern that plugin’s behaviour; they do not verify a fix for path changes in the built-in VLC source.
If you report the issue to a support forum, include a minimal test list and explain exactly how the path changed. Do not include private stream keys or account credentials. If a plugin is involved, name it and its version so helpers do not mistake its properties for the built-in VLC source settings. This keeps diagnosis focused on the setup you actually have.
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 did the playlist stop after I moved a video?
A saved playlist row may still refer to the old location, so OBS cannot find the file at the path it has stored. Check the row in VLC Video Source properties and confirm the replacement file opens from its current location. A move can also coincide with other changes, so test the playlist after repairing the entry rather than assuming this is the only cause.
Will turning on Loop Playlist fix a changed path?
No. Loop Playlist controls whether playback starts again after the list runs out of media; it does not repair an entry that points to a missing file. Correct the path first, then use looping if you want the list to repeat.
Why does playback stop when I switch scenes?
The VLC source’s visibility behaviour can stop playback while the source is hidden and restart it when visible, which OBS documents as the default behaviour. Check that setting and test the scene transition separately from path validity. A stop at a scene change is a different clue from a stop when a particular file should play.
Should I install Media Playlist Source instead?
Only consider it after checking the built-in source’s paths, loop setting, visibility behaviour, and VLC installation. It is a separate plugin, with its own compatibility requirements; check those against your OBS version and platform. Its release notes describe plugin-specific continuation fixes, not a verified repair for every built-in VLC playlist stop.