YouTube Live does not take a list of prerecorded files and play them one after another inside a live event. To keep one broadcast running while the content changes, use OBS as the encoder and let its VLC Video source play the files in sequence.
This can produce a continuous output, but neither YouTube nor OBS promises a perfectly gapless transition at every file boundary. The reliable approach is to prepare compatible media, configure the playlist carefully, and test the actual sequence before relying on it overnight.
A playout playlist is not a YouTube playlist
There are two different kinds of playlist involved here. A YouTube playlist is a collection of videos arranged on a channel or watch page. It helps viewers find and watch separate uploads, but it does not instruct YouTube Live to change the content inside one incoming broadcast.
A playout playlist is the list used by the software producing your live feed. OBS opens the first local file, sends its picture and sound to YouTube, then opens the next file when the first one finishes. YouTube receives the resulting audiovisual feed as one live stream rather than receiving each file as a separate video.
This distinction matters because changing YouTube videos or live events is not the same as changing the source inside an encoder. If you stop one event and start another, viewers may see an interruption, a new watch page, or a period in which no broadcast is available. That is a different workflow from keeping OBS connected and changing the media source within the same output.
Google's documentation describes a broadcast as the event viewers watch and a stream as the audiovisual content sent to YouTube. You can read that distinction in the YouTube Live broadcasts and streams documentation. For this setup, the practical conclusion is simple: YouTube receives one continuous encoder feed, while OBS handles the order of the files.
The same arrangement works for a devotional loop, a set of bhajans, a sequence of local news segments, a study channel with changing lessons, or an ambience station with several scenes. The content can change without asking YouTube to start another live event.
Install VLC and prepare the media files
OBS's VLC Video source requires VLC to be installed. Download VLC from the official VideoLAN site and install it on the same computer as OBS. Restart OBS after installing VLC if the source does not appear in the source list.
Before opening OBS, put the files for this broadcast in a clearly named folder. Decide the order first and use names that sort predictably, such as:
01-introduction.mp4
02-morning-bhajan.mp4
03-temple-ambience.mp4
04-closing-prayer.mp4
The numbers are for your own organisation. OBS has its own playlist order, so you will still check the order inside the source settings later.
Inspect the media before adding it. Play each file from beginning to end, paying attention to the first and last seconds. A file that begins with silence, fades from black, uses a different frame size, or ends with a long empty section may create what looks like a playlist gap even when OBS has moved to the next item correctly.
Try to keep the files technically consistent. Matching dimensions, frame rates, audio channel layouts and general loudness make transitions easier to diagnose. A 1920 by 1080 video followed by a smaller portrait file may still be playable, but the change can produce unwanted scaling or a visible layout change. A clip with stereo audio followed by a clip with a different audio arrangement may also make the boundary more noticeable.
The files do not need to be identical. They do need to be tested as a group. A practical test folder might contain three short representative files rather than the complete overnight library. Include the file with the quietest ending, the one with the most demanding picture, and the one whose audio is most different from the others.
Keep a backup of the original files outside the working folder. If you later re-export media to make the boundaries more consistent, you should be able to return to the source material rather than repeatedly altering the only copy.
If this is part of a larger always-on project, first decide whether the content is suitable for a continuous live event. The guidance in Does YouTube allow 24/7 live streams of pre-recorded videos is useful here, particularly because a technical ability to loop files is not the same as a guarantee about how YouTube will treat every channel or broadcast.
Add a VLC Video source in OBS
Open OBS and create or select the scene that will be sent to YouTube. You can use a simple scene containing only the playlist, or add a logo, clock, lower-third or other persistent elements around it. The playlist source is the part that changes; anything else in the scene can remain in place.
In the Sources panel, select the add button and choose VLC Video. If VLC Video is missing, check that VLC is installed and that OBS was restarted afterwards. OBS documents this source in its Media Sources guide, where it is described as a playlist-capable source rather than a single-file media source.
Give the source a useful name, such as Main programme playlist. This is more helpful than leaving it as a generic source name when you later troubleshoot a transition or build another scene.
The VLC Video properties window contains the playlist area and playback controls. Add the prepared files using the add-file control, then review the entries visually. If you add a folder or multiple files at once, do not assume the resulting order is the one you intended. Move items up or down until the list matches your running order.
Use the preview in OBS to confirm that the first file appears in the scene at the expected size. If it is cropped, stretched or surrounded by an unexpected background, fix the source transform before testing the playlist. A source that is technically playing but badly framed is a production problem separate from the file transition itself.
The VLC source has different behaviour from OBS's ordinary Media Source. A single Media Source is useful when you want one file, while VLC Video is designed for a list of items. Do not create a separate scene for every file unless you have a specific reason to control each transition manually. For a fixed sequence, one playlist source is easier to inspect and keep running.
Set the order, looping and playback behaviour
Keep shuffle disabled when the files must play in a fixed order. With shuffle enabled, a devotional sequence, lesson order or news rundown may change from one pass to the next. Random playback can be useful for a station designed around variation, but it is not appropriate when viewers expect a known progression.
Enable Loop Playlist only when the list should repeat after the final item. If it is disabled, the playlist reaches its end and remains there according to the source's playback behaviour. That is not a continuous channel, even if the first pass worked correctly.
Looping the playlist is different from looping one file. A single repeated video may restart at its own boundary, while a playlist loop moves from the last item back to the first. Test the end-to-start transition because the first file may have a different opening level, colour, or title treatment from the files in the middle.
A useful configuration check looks like this:
| Requirement | VLC Video setting or action | What to verify |
|---|---|---|
| Fixed running order | Arrange files manually and leave shuffle off | The first pass follows the intended sequence |
| Repeating channel | Enable Loop Playlist | The final file returns to the first file |
| One continuous scene | Keep the playlist in the scene sent to YouTube | No accidental scene switch occurs at a boundary |
| Consistent presentation | Check source transform and media dimensions | No unexpected crop, stretch or blank canvas |
| Reliable audio | Listen through the end and start of each file | No source file begins with an unwanted pause or silence |
Do not use the loop setting as evidence that the result will be gapless. It only controls whether playback returns to the list. The visible result at a boundary depends on the actual media and how the source handles the change.
Save the scene collection once the basic settings are correct. Then make a small change, test it, and save again. If a later experiment introduces a problem, you will have a known configuration to return to rather than trying to remember which setting changed.
For long-running projects, write down the order and settings outside OBS as well. This is useful when you replace a file, rebuild the computer, or ask another person to check the channel. A note stating “shuffle off, loop on, files in numbered order” prevents a common mistake during a rushed restart.
Send one continuous OBS output to YouTube
Create or schedule the live event in YouTube Studio's Live Control Room. YouTube's encoder setup instructions explain where to obtain the stream URL and stream key for the event.
In OBS, open the stream settings and select the appropriate YouTube service or enter the stream details as instructed by YouTube. Paste the event's stream key carefully. Treat the key like a password: do not publish it in a screenshot, send it in a public message, or leave it visible in a tutorial recording.
Start the VLC playlist in OBS and confirm the scene is showing the intended file. Then start streaming from OBS. The encoder sends the scene output to YouTube, including the playlist source and any fixed overlays around it.
Do not start a new YouTube event for every file. Keep the encoder connected while the VLC source moves through the list. From YouTube's perspective, the important item is the incoming live feed, not the names of the local files that produced it.
Use the Live Control Room preview before making the event public. The preview gives you a chance to check the picture, audio, title, visibility and basic stream status without asking viewers to diagnose the setup for you. YouTube also recommends testing and previewing an encoder stream before an event.
Watch the output in OBS and in YouTube's preview at the same time during the first test. There can be a difference between what the local scene displays and what has reached the platform. If the local preview is already blank at a boundary, investigate OBS, VLC or the file. If the local preview is correct but the YouTube preview behaves differently, inspect the encoder and connection path as well.
YouTube's help pages also describe professional-grade hardware encoders as a recommendation for higher-production-value events. That does not make dedicated hardware necessary for this OBS and VLC workflow. It is a separate production choice for people who need a different operating model, additional inputs or hardware-based control.
Test the transitions with the actual media
A short test using the real files is more useful than a long test using placeholder clips. Make a copy of the final playlist, or use the complete list if it is small enough to inspect comfortably. Start with the first file, watch at least one middle boundary, and continue through the final-to-first transition if looping is enabled.
Use headphones as well as speakers. A picture can appear continuous while the audio briefly drops, starts late, changes level or contains an unwanted click. Listen to the last seconds of one file and the first seconds of the next. Check speech, music, ambience and any background noise separately because a problem can be obvious in one type of content and hidden in another.
Record what happens at each boundary:
- Does the next picture appear immediately after the previous picture ends?
- Is there a black frame, frozen frame or unexpected flash?
- Does the audio continue, pause, overlap or change level?
- Does the source stay visible in the OBS canvas?
- Does the YouTube preview show the same result after its normal delay?
- Does the final item return to the first item when looping is enabled?
A visible pause is not automatically a YouTube problem. If the media file contains a deliberate fade-out followed by silence, the source may be working exactly as encoded. Open the files independently and compare their last and first seconds before changing OBS settings.
Test under the conditions you will actually use. If the channel will run through the night on a particular computer, use that computer. If it will run with other applications closed, close them during the test. If the final broadcast includes a logo or alert source, include it. A test that omits the real scene can miss a source conflict or an accidental scene change.
A private or unlisted test can be appropriate while you inspect the result. Check the current visibility choices in YouTube Studio before starting. You should also leave enough time to observe the first transition after the stream reaches the Live Control Room preview rather than stopping immediately after the connection succeeds.
Do not describe the outcome as guaranteed gapless merely because one pass looked smooth. The official OBS documentation establishes that VLC Video can play a playlist and loop it. It does not establish that every combination of files will transition without a blank frame or audio pause. The honest result is an observed transition on a tested setup.
Diagnose a gap before changing the whole workflow
If a gap appears, isolate the boundary. Note the exact two files involved and test them as a two-file playlist. If the problem remains, inspect the end of the first file and start of the second. Re-exporting or replacing one incompatible file may solve the issue more directly than rebuilding the YouTube event.
Check that the media is not being loaded from a disconnected drive, synchronised folder or location with unusually slow access. A file that plays correctly when opened manually can still behave differently when another application is reading it during a live output. Keep the working playlist in a stable local location where the computer can access every item.
Check the OBS canvas while the transition happens. If the source disappears locally, the problem is in the playout path. If OBS remains correct but the platform preview shows trouble, inspect the stream status, encoder load and connection. For general symptoms, the guide to live stream lag versus buffering explains why a viewer-side delay is not always evidence of a source transition failure.
Also check whether the problem is actually a scene transition. A hotkey, automatic scene switch or another source may be changing the scene at the same time as the VLC playlist item changes. Temporarily simplify the scene to the VLC source and test again. Add other elements back one at a time.
If the computer is under strain, look at the local preview and system load during a transition. Reduce unnecessary applications and overlays before changing the media. Dedicated hardware may suit a higher-production event, but it does not replace the need to test the content sequence itself.
For a channel intended to run continuously, plan what happens after a restart. OBS must open the correct scene collection, the playlist must point to files that still exist, and the stream must use the intended event settings. A written restart procedure is more useful than relying on memory at three in the morning.
If leaving a computer powered on and watching the playlist is the pain you are trying to remove, StreamNeo can turn an uploaded video into a continuing YouTube stream after you provide the file and stream key, with the broadcast watched and restarted automatically if it drops. It is a different operating model from configuring OBS locally, so test the content and channel requirements before choosing how to run it.
Make the playlist maintainable
A playlist that works once can still become difficult to operate when the library grows. Keep a master list with the intended order, file names and any notes about opening or closing silence. When you replace a file, preserve its name where possible or update the OBS playlist deliberately rather than assuming the old path will follow the new media.
Use a small test playlist after every meaningful change. You do not need to watch the entire library each time to catch an obvious boundary problem, but you should test the changed item with the file before it and the file after it. If the changed item is the first or last item, test the loop boundary as well.
Keep the live scene simple enough to understand. A single main playlist source, a persistent branding layer and a small number of tested overlays are easier to troubleshoot than a scene containing many unlabelled sources. This matters particularly for devotional, study and ambience channels where the content may continue for hours without anyone touching the controls.
Monitor the first cycle after going live and check the YouTube status indicators. Viewers may experience normal delivery delay, so do not react to a problem based only on one immediate playback view. Compare the source, OBS output and YouTube preview before deciding whether a restart is necessary.
For broader planning, the complete 24/7 YouTube streaming guide covers the operating decisions around a continuous channel. The playlist itself is only one part of the job: media preparation, monitoring, recovery and the channel's presentation all affect how dependable the result is.
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 YouTube have a live playlist feature for prerecorded files?
Not in the sense used here. YouTube receives the encoder's live audiovisual feed, while OBS or another production tool decides which local media is currently in that feed. A YouTube channel playlist can organise separate videos, but it does not sequence files inside one live event.
Will OBS VLC Video guarantee no gap between files?
No. OBS documents VLC Video as a playlist-capable source with ordering and looping controls, but that is not a guarantee of frame-perfect transitions. Test the actual files, especially their final and opening seconds, before using the sequence for a public or overnight broadcast.
Should shuffle be enabled for a 24/7 channel?
Leave shuffle off when the order matters, such as a lesson series, prayer schedule or planned news sequence. Enable looping if the entire list should repeat. If variation is more important than a fixed order, shuffle may suit the format, but test that behaviour before going live.
What should I do if the screen goes blank at a transition?
First check the two files at that boundary and watch the OBS canvas while they change. If OBS also goes blank, inspect the media, VLC source and local file location; if OBS remains correct but YouTube differs, inspect the encoder and stream status. Simplifying the scene and testing the boundary with only two files can help isolate the cause.