If you replace a video without changing its folder or filename, an OBS playlist entry that points to that path can remain in place. That does not mean OBS or VLC will automatically reread the replacement; reload or recreate the source cautiously, then confirm the new video in preview before going live.
For a folder that changes regularly, a folder-aware plugin or script may suit you better than a built-in playlist. The important distinction is how each method refreshes its entries: a manual settings save, an event-driven scan, or a source reload are different behaviours, and none should be assumed without checking its documented requirements.
What happens when a playlist file is replaced
A playlist entry identifies media by its file location. Think of it as a note that says to open D:\\Channel\\evening-bhajan.mp4, rather than a promise to keep watching a folder for changes. If you put a new file at that same location with the same name, the entry still points to the location. If you rename or move the file, the old entry points to the old location until you update it.
There are two separate questions: does the playlist still refer to the intended path, and has the source reopened the contents currently stored at that path? Keeping the path stable addresses the first. It does not establish the second. OBS’s media sources guide describes the built-in Media Source and VLC Video source, including playlist support for VLC Video, but does not promise automatic rereading after an external file replacement.
This matters when you replace a devotional loop overnight, update a local news segment, or refresh a study-channel background. A playlist can look unchanged in its settings while the source still has not been verified with the new file. Treat the source settings and the visible output as separate checks.
OBS also has distinct source types. Media Source is for an individual media file; VLC Video supports playlists and depends on VLC libraries being available. If you use 64-bit OBS, OBS says you need 64-bit VLC. The VLC playlist guide lists loop enabled by default and shuffle disabled by default, but does not document a continuous directory watcher. Those defaults are useful to know, but they do not answer whether a replaced file has been reopened.
Keep the existing path and filename stable
When practical, replace a clip in place: use the same directory and exact filename. This keeps the existing playlist entry meaningful and avoids editing every reference that points to the old location. On Windows, check drive letter, folder names, and file extension; on macOS or Linux, check the full path and letter case where relevant. A file named MorningLoop.mp4 is not necessarily the same target as morningloop.mp4 on every system.
Do not delete the old file before the replacement is ready if the playlist is currently in use. Prepare the new export elsewhere, check that it opens, then replace the old file when you can pause or safely manage the broadcast. If you overwrite a file while a source is actively reading it, the result may depend on the source’s state and the operating system. The available documentation does not specify a universal hot-replacement result, so schedule the swap as a maintenance step rather than relying on it mid-playback.
If you must change the filename or location, edit the playlist entry to the new path. Then inspect the entry for an accidental duplicate, missing extension, or reference to a temporary export folder. A replacement that plays correctly on your editing computer may still fail on the streaming computer if you copied the playlist but not the media, or if the drive is mounted under a different letter.
For channels with several scheduled clips, keep a simple record of the final filenames and their purpose. A short naming scheme such as morning-aarti.mp4 and evening-aarti.mp4 is easier to audit than a chain of names like final-new-fixed-2.mp4. The same discipline helps when setting up different videos at set times in an OBS stream: schedule logic and file references should both be checked after an update.
Reload or recreate the source cautiously
After replacing the media, use a controlled reload workflow. OBS’s documentation confirms what its source types support, but does not specify a precise rule for refreshing a file externally replaced at the same path. So treat reloading or recreating the source as a practical step to make it reopen the media, not as a guarantee that a particular control will behave identically in every setup.
A cautious sequence is:
- Stop or pause the programme output if that is practical, and note the current source and playlist settings.
- Confirm that the replacement opens in a normal media player and that the file has finished copying or exporting.
- In OBS, use the source’s available reload control if present, or remove and recreate the source with the same intended settings. For a VLC Video source, confirm the playlist entries still point to the correct files.
- Check source visibility, audio settings, loop or shuffle choices, and any transforms or filters you rely on.
- Test in OBS preview before returning to the live programme.
If the source is part of a scene used in several places, recreating it can affect more than one scene depending on how it is shared. Check the scene collection and source list before deleting anything. You may prefer to duplicate the scene or record its settings first, particularly if a channel has an established layout with logos, captions, or audio processing.
For VLC Video, verify that VLC is installed and that its bitness matches OBS. The official OBS guide specifically calls for 64-bit VLC with 64-bit OBS. If the playlist source disappears, refuses to open, or behaves differently after an OBS update, check the current OBS documentation and installation requirements rather than repeatedly changing files at random.
For a long-running broadcast, choose a quiet change window and keep the previous file until the replacement has passed a preview test. A useful operational routine is to update, reload, preview, and only then remove the backup. This reduces the chance that an export error or a path typo leaves you with no playable version. If your difficulty is instead a scene transition interrupting the output, see how to keep a stream running when an OBS source changes.
Confirm the replacement in preview
Do not use the playlist entry itself as proof that the new media is playing. The source can still show a familiar name even if the file has not been reopened or if it points somewhere unexpected. Preview the actual picture and listen to the audio before putting the scene back on air.
Look for the first frames, not just a still image that resembles the old clip. Confirm that the beginning of the replacement is correct, that the aspect ratio and crop are acceptable, and that audio is present at a sensible level. If a clip has a blank lead-in by design, scrub or wait far enough to confirm the content later in the file. Check that the source is visible and not hidden under another source in the scene.
A small test scene is useful if the main programme cannot be interrupted. Add or duplicate the source there, load the updated path, and inspect it without changing the live scene. Be careful not to confuse previewing a duplicated source with validating the actual playlist that will run. When ready, test the real scene or source in the arrangement you intend to broadcast.
If the playlist contains multiple videos, verify more than the first item. Check that the order is correct, that the expected next item can be reached, and that loop and shuffle settings match the channel’s plan. OBS’s documented VLC defaults are loop on and shuffle off, but settings may have been changed by you or inherited from an earlier setup. The preview check should reflect the playlist’s real configuration, not just the defaults.
For picture continuity, consider the format and frame rate of replacement media as well as its path. An exported clip that differs from the rest of a loop may show a visible change even when it plays successfully. The guidance on frame rate choices for 24/7 loops can help you decide whether all clips need to match exactly or whether a particular variation is acceptable.
When to use a folder-aware method
If you add, remove, or rename files often, repeatedly editing a VLC playlist may be tedious. A folder-aware method can build entries from a selected folder, but check what it actually refreshes and what source type it requires. “Uses a folder” does not necessarily mean “watches the folder continuously”.
Media Playlist Source is an OBS resource that supports file and folder entries. Its documentation says that changing settings refreshes folder entries and describes saving settings again as a manual refresh workaround; automatic refreshing is not implemented in the described version. The resource’s version history says OBS 31 is required from version 0.1.0 onwards. Check its current resource page for current compatibility and installation instructions before relying on it.
PlayFolder describes a different approach: it scans a selected folder and dynamically updates its playlist on OBS events. Its resource specifies an OBS Media Source, not a VLC Video source, and says not to enable OBS’s internal looping because the script manages playback. These are the author’s listed features and requirements, not independent evidence that the script has been tested with your scene, operating system, or media. Review the PlayFolder resource page and test on a non-live scene before adopting it.
Another resource, NowPlaylisting, describes file and folder entries and editable playlists for Windows and OBS 30 or later. The resource information does not establish that it automatically refreshes folder contents, so do not infer that capability from the presence of folder entries. Check its resource page for current details, and confirm the refresh behaviour in your own setup.
A folder-aware tool is most useful when the folder is the source of truth and its refresh model matches your workflow. It may be less suitable if you need a particular playlist order, if files arrive while a live programme is using them, or if the tool requires a source type you do not use. For some channels, a curated list of fixed paths is simpler to review than an automatically changing folder. If you run a 24/7 music radio stream from a playlist, decide whether new tracks should enter immediately or only after a deliberate update.
A hosted file-based broadcast removes the need to keep an OBS computer on, but it does not remove the need to choose and verify the right file before replacing it. StreamNeo can take away the overnight concern of a local machine needing to stay powered while a fixed uploaded video runs; it is not a substitute for a folder-watching OBS playlist when your programme needs frequent live changes.
Compare documented refresh behaviour
Choose by refresh model and source compatibility, not by the word “playlist” in a tool description. The table summarises what the cited documentation says; it does not guarantee performance in a particular OBS installation.
| Method | What the documentation describes | Refresh expectation | Important constraint |
|---|---|---|---|
| Built-in VLC Video playlist | Playlist of media files, with loop and shuffle settings | No automatic reread of externally replaced files is promised; reload or recreate cautiously and preview | Requires VLC libraries; 64-bit VLC for 64-bit OBS |
| Media Playlist Source | File and folder entries | Save settings again to refresh folder entries; automatic refresh is not implemented in the described version | Resource says OBS 31 is required from version 0.1.0 onward |
| PlayFolder | Folder scan that dynamically updates on OBS events | Event-driven updates are claimed by the resource author | Uses an OBS Media Source; do not enable internal OBS looping |
| NowPlaylisting | File and folder entries with editable playlists | Folder auto-refresh is not established by the resource information | Resource lists Windows and OBS 30+; verify current requirements |
Version statements above are attributed to the respective resource descriptions, not treated as universal compatibility guarantees. Media Playlist Source’s update page lists version 0.1.3 dated 13 April 2025, while PlayFolder 1.3 lists an update date of 24 September 2026. Confirm the current page before installing: resources can change, and an update may alter support or instructions. For NowPlaylisting, the resource lists Windows and OBS 30 or later, but that alone does not establish a folder refresh feature.
In practice, write down three things before switching methods: the OBS source type, the folder or playlist path, and the documented trigger for refreshing. Then test what happens when a file is added, replaced, renamed, or removed. Test with a duplicate scene or a quiet maintenance window, and make sure the programme does not start an unintended item while you are checking. Do not base a live-channel change solely on a resource description or an old forum suggestion.
This approach is especially important for a channel that runs overnight. Check file paths, replacement timing, source visibility, and audio in preview; then observe enough of the sequence to understand what happens at the next transition. Keep a known-good copy until the revised setup has been used successfully in your own conditions. These checks cannot guarantee that a plugin or script will work indefinitely, but they make the failure mode easier to spot before it reaches viewers.
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
If I keep the filename, will OBS show the replacement automatically?
Keeping the filename and folder preserves the path in the playlist entry, but it does not prove that OBS or VLC has reopened the replaced file. Reload or recreate the source cautiously, then check the actual output in preview. The official OBS guide does not promise automatic rereading after an external replacement.
Should I use Media Source or VLC Video?
Use Media Source when you are adding an individual media file; VLC Video is the built-in source documented for playlists. VLC Video depends on VLC libraries, and OBS specifies 64-bit VLC for 64-bit OBS. Match the source to the workflow and test the version you intend to run.
Does Media Playlist Source watch a folder automatically?
The described version supports folder entries, but its resource page says automatic refresh is not implemented and recommends saving settings again to refresh folder contents. Check the current resource page for changes and version requirements before installing it. Do not assume folder selection means continuous watching.
Can PlayFolder update a VLC Video playlist?
The PlayFolder resource describes using an OBS Media Source, not VLC Video, and says the script handles playback so internal OBS looping should remain off. Its event-driven folder updates are the author’s stated functionality. Test it in a separate scene and check current instructions before using it on a live channel.