First identify what owns the playlist: an OBS VLC Video source is a list of media items, while an HLS .m3u8 file is a manifest that points to stream segments. They are not interchangeable, and a safe edit for one can interrupt the other.
If a built-in OBS playlist edit restarts playback, OBS does not document a guaranteed live-reload method. For HLS, keep the manifest and its referenced segments consistent. YouTube’s HLS ingest rules matter only if your encoder is sending HLS to YouTube, not for ordinary local-file playback in OBS.
First identify what owns the playlist
Start in OBS, not in the file editor. Select the source that is meant to play the material and check its type and properties. OBS distinguishes its VLC Video source from Media Source; VLC Video can hold multiple media items, whereas Media Source is configured around an individual media item. The OBS media sources guide documents the VLC Video playlist feature, but it does not promise that editing a playlist file externally will be picked up without interrupting playback.
Then inspect the file you changed. A text file containing paths to local video or audio files may be a VLC playlist. An .m3u8 file containing HLS tags and segment references is a streaming manifest. The extension alone is not conclusive: .m3u is also used for ordinary media lists, and the word “playlist” is used loosely in many workflows. Check the source configuration and a copy of the file before deciding what rules apply.
Record the exact symptom as well. Did the current video start again, did OBS show a blank source, did the stream disconnect, or did playback continue until it reached the changed part? Those outcomes point to different stages: source reload, file access, encoder output, or YouTube ingest. Do not assume the viewer-facing stream stopped merely because an editor or OBS preview refreshed.
If you cannot tell which source owns the file, do not edit it while a live event depends on it. Save a copy, note the source name and format, and test the copy in a separate scene or OBS profile. That small identification step avoids applying HLS advice to an ordinary VLC list, or treating an HLS manifest like a queue of video files.
OBS VLC Video playlists and HLS manifests
A VLC Video playlist is a set of media items that OBS presents through a VLC-based source. You can configure playback behaviour such as looping or shuffling in the source settings. The OBS documentation describes making a playlist of items, similar to an image slideshow. It does not define a transaction for replacing the playlist file while the current item is playing, nor does it guarantee preservation of the playhead when the list changes.
An HLS media playlist is part of a streaming protocol. It tells a client which media segments form the stream, along with timing and other metadata. HLS clients periodically reload a live media playlist to find new segments. The IETF’s RFC 8216 describes client reload behaviour and continuity checks; it is not an OBS VLC playlist manual.
This distinction matters when diagnosing a 24/7 YouTube broadcast. If OBS reads local files and sends its normal encoder output to YouTube, changing a local list is a source-playback issue. If a process generates an HLS manifest and YouTube receives HLS, manifest rules and YouTube’s ingest requirements are relevant. Confirm the path from source to encoder to YouTube rather than guessing from the file extension.
The two approaches also put different work on you. With a VLC source, you manage media paths and the order in which OBS plays items. With HLS, you or your generating software manage segment creation, manifest updates, and the availability of referenced segments. Neither format by itself tells you whether a live edit is safe; that depends on the application reading it and the timing of the change.
What can happen when an OBS playlist changes
When the built-in VLC Video source is active, changing its playlist may cause the source to reload or restart an item, but the exact result depends on how the list is changed and how the source reads it. OBS documents playlist configuration and playback settings, not an atomic hot-reload procedure. An external text editor may save by replacing the file, writing it in place, or using another method. The result can differ across applications and circumstances, so there is no universal safe sequence to recommend.
A restart of the current item is not necessarily the same as a YouTube stream disconnect. The encoder may continue sending output while the source begins again, producing a visible repeat or gap in content. Conversely, a missing file, inaccessible path, or source error may leave the scene without the expected video. Watch the OBS source and encoder status, then verify the actual YouTube output from a separate viewer if the distinction matters.
Before editing, identify what would be costly to lose: the current item’s position, a seamless transition, or the broadcast connection itself. If a restart is acceptable between items, schedule the change for a transition and keep the old list available for rollback. If restarting the current item is not acceptable, do not treat the built-in VLC source as if it had a documented edit-without-restart guarantee.
For continuous operation, also make sure paths remain valid. A list that refers to moved or renamed files can fail independently of reload behaviour. Keep a known-good copy, avoid changing filenames while they are in use, and confirm that the OBS account can still read the files. For a broader view of how sources fit together in a dedicated loop, see how to organise an OBS scene collection for a YouTube loop stream.
Consider an edit-tolerant OBS playlist source
If you need to reorder or replace items while another item is playing, a third-party OBS source may be worth testing. The author of the Media Playlist Source plugin says it can apply playlist edits without restarting the video, including when items are reordered. That is the plugin author’s feature claim, not a guarantee from OBS Project and not proof that it works with every OBS release, operating system, or media setup.
Check the resource page for its current compatibility information before installing it. Confirm the supported OBS versions and any stated requirements, and consider whether your VLC, media codecs, and scene collection are affected. A plugin that works on one machine may not be suitable on another. Do not infer compatibility merely because it appears in OBS’s resource forum.
Test with the same kind of playlist, media files, and OBS version you use for production. Save your existing scene collection and preserve the current playlist file first. In a test scene, start an item, make a small change such as reordering a later item, and observe whether the current item and next transition behave as expected. Repeat with the kinds of edits you actually need; adding a file is not necessarily equivalent to removing the active entry.
If the test does not behave predictably, revert to the saved list and plan edits around a controlled transition instead. The plugin is one possible way to address a specific interruption, not a reason to skip a test or assume every playlist update will be seamless. If you need an always-on broadcast while your own computer is off, separate that operational concern from the playlist question: keeping an ambient video stream live without a PC covers that broader choice.
Keep HLS segment references valid
For an HLS workflow, treat the manifest and its segments as one changing set. A manifest entry points to a segment the player expects to retrieve. If you remove, rename, or overwrite that segment while it is still referenced, a client may be unable to fetch the media it needs. The exact safe file-update method depends on the server or process creating the HLS output and on the player’s behaviour; RFC 8216 sets protocol expectations but does not prescribe one file operation for every host.
A live HLS client reloads the media playlist to learn about new segments. The protocol also relies on continuity checks across reloads. That means a valid update is more than writing syntactically correct text: the sequence of references and the corresponding available media need to make sense to the client. Keep older segments available for the period required by your serving setup, and avoid changing the identity or content of a segment that an active playlist still names.
If software such as FFmpeg generates the manifest, check its playlist type and output mode before changing the file manually. FFmpeg documents EVENT playlists as append-only and VOD playlists as unchanging. Those modes imply different expectations from a live editor. The FFmpeg format documentation is the place to check how the selected options behave; if the output is generated automatically, changing the generation settings may be safer than hand-editing a file that the process will rewrite.
Keep a copy of the previous manifest and note which segment files it referenced before a change. Validate that the new manifest points to files that exist and can be served, then test with the actual client. Do not copy a VLC playlist edit workflow into an HLS directory: the former orders media items for a source, while the latter coordinates a rolling set of stream segments.
When YouTube HLS ingest settings matter
YouTube’s HLS ingest guidance applies when your encoder sends HLS to YouTube. It does not apply to every OBS stream, and it does not repair a restart caused by editing a local VLC playlist. If OBS is sending a non-HLS encoder output, focus on source playback, encoder status, and the relevant output protocol instead.
For HLS ingest, YouTube’s official HLS ingestion guidance specifies transport and playlist constraints. It calls for TS segments lasting 1–4 seconds, HTTPS POST/PUT requests, and a rolling playlist with no more than five outstanding segments. Treat these as requirements for the stated HLS ingest path, not general rules for local media playlists or all live encoders. Check the current YouTube guidance before changing a production configuration.
If you are unsure whether YouTube receives HLS, inspect the encoder’s output configuration or ask the person who configured it. An .m3u8 file somewhere on the computer does not establish that YouTube is ingesting HLS; it could be used by a local player, another relay, or a preview. Resolve that path first, then apply the matching documentation. For planning a stream around pre-recorded media, the H.264 and H.265 format differences for YouTube Live are a separate encoder choice, not a playlist reload fix.
Test changes without risking a live event
Set up a test that mirrors the production path but does not carry an audience-dependent programme. Use a copy of the media and playlist, the same OBS version and source type, and the same relevant output mode. If you use HLS, include the process that writes the manifest and segments. A test with a static file cannot tell you how a live manifest update will behave.
Before testing, write down the expected result: should the active item continue, should the next item use the new order, and is a short content interruption acceptable? Start playback, make only one type of change, and watch both the source and the output. If the active item restarts or disappears, record exactly what changed and restore the known-good file. This is more useful than making several edits at once and being unable to identify which one caused the interruption.
For a YouTube-facing check, use a private or otherwise appropriate test broadcast and verify the received output independently of the OBS preview. A preview can look normal while the outgoing stream behaves differently, and a continuous encoder status does not prove that the intended media is reaching viewers. Check the current YouTube Live requirements and account status as needed; no test can guarantee that a later production configuration will behave identically.
Plan a rollback before making a production change. Keep the previous file, know how to restore it, and choose a time when a restart would be least disruptive. If you have to change a live HLS manifest, ensure its referenced segments remain available and have a way to revert the generator or manifest. If you have a VLC playlist, a controlled transition may be more predictable than editing the active source and hoping it reloads cleanly.
For a stream that relies on a computer staying available overnight, the playlist is only one part of continuity. You need to decide who will watch for a source failure and how it will be restarted. StreamNeo removes the need to keep your own computer running for a file-based YouTube broadcast: you upload the video and set the stream details, while the stream is monitored and restarted if it drops.
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 my 24/7 YouTube stream stop when I edit the playlist file?
The word “playlist” may refer to an OBS VLC list of media files or an HLS manifest, and the cause depends on which one you edited. OBS does not document a guaranteed live reload for the built-in VLC Video source; an HLS client instead reloads a manifest and expects its segment references to remain valid. Check the source type and file contents before choosing a fix.
How can I update an OBS playlist without restarting the video?
The built-in VLC Video source documentation does not promise that an edited playlist will preserve the current playback position. You can schedule edits for a controlled transition, or evaluate the third-party Media Playlist Source plugin, whose author claims it can apply edits without restarting the active video. Check compatibility and test your exact setup before relying on it.
Do YouTube’s HLS settings apply to every OBS stream?
No. The HLS ingestion requirements apply when the encoder sends HLS to YouTube. They are not instructions for an OBS VLC source playing local files or for a different encoder output; confirm the actual ingest path and consult YouTube’s current official guidance.
What should I check before editing an HLS manifest?
Confirm which process generates it, what playlist type and output mode it uses, and whether every referenced segment remains available. Avoid removing or renaming active segments without understanding how the server and clients handle updates. Test the change away from a production broadcast and keep a rollback copy.