Use OBS Studio with VLC installed to play several local video files as one YouTube live stream. Add the files to OBS’s VLC Video source, choose the order or shuffle behaviour, enable playlist looping, then send the encoder feed to YouTube Live.
This repeats the media, not the whole broadcast system. A local computer, power supply, OBS, VLC and a stable upload connection must continue working, so test the exact setup before treating it as a continuous channel.
What a continuous multi-file stream involves
The workflow has three separate parts. Your video files form a playlist, OBS reads and plays that playlist, and YouTube receives OBS’s encoded output as a live broadcast. The playlist can return to its first file after the last one, but that setting does not repair a failed computer, frozen application, power cut or lost connection.
A simple example might contain an opening ident, several devotional recordings and a closing slate. With the files entered in that order and shuffle disabled, OBS plays them in that order. When the final file ends, Loop Playlist sends playback back to the first file. If shuffle is enabled, OBS chooses a randomised sequence instead of following the entered order.
The files should be prepared before you build the scene. Give them clear names, check that they open normally, and decide whether the sequence should be predictable. A prayer service, lesson series or local news bulletin usually needs a fixed order. A lofi, ambience or music station may be more suitable for shuffled playback, although you should still listen to the result before going live.
Repeating a playlist is different from maintaining an uninterrupted YouTube broadcast. OBS may stop because the computer sleeps, restarts, overheats or runs out of resources. VLC may fail to read a damaged file. A router or broadband connection may drop. YouTube may also report an ingest problem. Playlist looping addresses only the point at which the source reaches the end of its media list.
If your channel depends on switching between prepared blocks rather than simply repeating one list, read about switching YouTube livestream playlists without changing the stream key. It covers a different operating pattern, but the distinction between the YouTube broadcast and the media being sent to it is useful here as well.
Install and prepare OBS and VLC
Install OBS Studio and VLC Media Player on the computer that will run the stream. OBS’s VLC Video source depends on VLC being installed. The OBS Media Sources documentation also notes that a 64-bit OBS installation requires 64-bit VLC, so match the installations rather than mixing architectures.
Open both applications once after installation. This gives you an opportunity to complete any first-run prompts and confirm that VLC can play each file. Do not wait until the planned broadcast to discover that a file uses a format or codec your machine cannot decode correctly.
Create a folder for the stream’s media and keep the files in a stable location. If you later move a file, rename its folder or disconnect the storage device, OBS may no longer find the playlist item. A local internal drive is generally easier to manage than a removable drive that can be unplugged or mounted under a different path.
Prepare a written list of the intended order. Include the filename and, if useful, the expected duration. This is not a replacement for testing, but it makes it easier to spot a missing item or accidental duplicate when you add the files in OBS.
You also need a YouTube channel that can live stream. YouTube says that live streaming requires channel verification and no live-streaming restrictions in the previous 90 days. Its live-streaming eligibility guidance says first-time activation may take up to 24 hours, so activate the feature before your intended start rather than on the morning of the broadcast.
Before building a long playlist, play representative files locally. Check speech, music and quiet sections, not only the first minute. Listen for missing audio, unexpected silence, clipped levels, black frames and aspect-ratio problems. A file that plays on one computer is not automatically proof that the complete OBS scene will behave as expected.
Add a VLC Video source and playlist
Open OBS and create a scene for the broadcast. In the Sources panel, select the add button and choose VLC Video. If that source is not available, check that VLC is installed and that its architecture matches OBS before trying to rebuild the scene.
Add the video files to the VLC Video source’s playlist. You can select the files from their local location and then review the entries inside the source properties. Arrange them in the intended sequence. Use descriptive filenames as a second check, but rely on the visible playlist order rather than alphabetical assumptions.
The VLC Video source supports common video formats including MP4, TS, MOV, FLV, MKV, AVI, GIF and WebM, as documented by OBS. That does not mean every file will perform identically. Container, codec, frame rate, resolution and audio characteristics still affect decoding and output, so use the exact files in a test broadcast.
Fit the source to the scene so that the picture fills the intended canvas without unwanted cropping. If the files have different shapes, decide whether you prefer borders, cropping or a consistent background. Changing this after the stream begins can confuse viewers and makes it harder to compare the live preview with your planned layout.
Keep the scene simple for the first test. Add overlays, logos or currently playing text only after the playlist itself works. If you want titles on a radio-style channel, first establish reliable media playback, then consider a separate guide to displaying currently playing song titles on YouTube radio.
Save the OBS profile and scene collection once the source is configured. A saved configuration is useful after a restart, but it is not a recovery system by itself. Keep a note of the media folder location and the key source settings so you can diagnose a missing playlist without guessing.
Set playback order and playlist looping
The three settings that matter most are the playlist entries, Shuffle Playlist and Loop Playlist. Treat them as separate controls:
| Setting | Off | On | Suitable use |
|---|---|---|---|
| Playlist order | OBS follows the entered list | Not applicable | Use the visible list for a planned sequence |
| Shuffle Playlist | Files play in listed order | Files play in a randomised order | Use on when repetition should not follow a fixed sequence |
| Loop Playlist | Playback stops when the list ends | The source restarts after the last file | Use on for a repeating media cycle |
For a fixed sequence, leave Shuffle Playlist off and arrange the files manually. For a randomised station, turn Shuffle Playlist on and still inspect the list for missing or duplicate files. Random playback may be useful for ambience, but it can place two similar items together or put an introduction after a longer programme, so judge the result against the channel’s purpose.
Turn Loop Playlist on when you want the source to restart after the final item. OBS defines this setting as controlling whether the source restarts after it has run out of media files. It does not promise a seamless transition, and it does not keep OBS running if the application or operating system has failed.
Pay attention to the boundaries between unlike files. One video may have a different frame rate, loudness, aspect ratio or opening frame from the next. The change may be acceptable, or it may create a visible pause or a sharp audio difference. YouTube receives the output of OBS, not the original files, so inspect the transitions in the OBS preview and in the YouTube watch page.
Do not remove the final file merely because it is a short slate. A short end card can make the loop’s boundary easier to identify during testing, while a long black section can look like a fault to viewers. If the files are from a church, school or local business, make the purpose of each opening and closing segment clear before arranging the list.
Connect OBS to YouTube Live
In YouTube Studio, open the Live Control Room and create or schedule an encoder stream. YouTube’s encoder setup instructions explain where to find the stream URL and stream key. Copy those values into OBS’s stream settings, selecting the appropriate YouTube service or entering the supplied server details.
Treat the stream key as a password. Do not publish it in a screenshot, paste it into a public document or send it through an untrusted chat. If you believe it has been exposed, reset it in YouTube Studio and update OBS before starting the encoder.
YouTube recommends RTMPS where supported. Match the output resolution and frame rate to the material and to what your computer and upload connection can sustain. For H.264, YouTube’s current encoder guidance lists 1080p at 30 frames per second with a 5 Mbps minimum and 14 Mbps recommended bitrate. Those figures describe YouTube’s encoder guidance, not a guarantee that your particular broadband connection will sustain the feed without interruption.
Choose a practical output rather than automatically selecting the largest setting. If the source is an older 720p recording, sending a larger canvas does not create additional detail and may increase the work for the computer and connection. Conversely, reducing a high-quality source too far can make text or devotional artwork difficult to read.
Start with a private or unlisted test if the channel’s workflow allows it. In Live Control Room, examine the preview and stream health before making the broadcast public. Confirm that the expected scene is visible, audio is present and the title, description and visibility settings are correct.
The live connection is an encoder connection from OBS to YouTube. It is not the same as uploading the files to YouTube in advance. If you need a different playlist later, keep the broadcast and its key organised separately from the media list, and avoid changing several moving parts during a live session.
Test and monitor the local setup
Test the exact playlist, not a shortened substitute, before announcing the stream. A short test should include at least one transition between files and enough time to observe audio, picture and the connection status. For a long unattended run, also test what happens after the computer has been left alone for the relevant period.
Watch the OBS preview first. Look for a frozen frame, a black source, incorrect cropping, missing audio or a scene that has become hidden. Then watch the YouTube preview and, once live, open the public watch page on another device. A phone on mobile data can reveal problems that do not appear when you watch from the same local network.
YouTube recommends testing before starting the live stream and monitoring stream health. Keep Live Control Room open during the first part of the broadcast and read its messages rather than assuming that a green-looking OBS status means viewers are receiving a healthy picture.
Check the computer’s practical dependencies:
- Prevent sleep, hibernation and automatic updates from interrupting the stream during the planned run.
- Keep the computer connected to stable power and make sure ventilation is not blocked.
- Avoid running unrelated applications that consume substantial CPU, memory, storage or network capacity.
- Confirm that the media folder remains available and that the files are not being edited or moved.
- Measure whether the upload connection remains usable when other people or devices are active.
- Keep a way to reach the computer if you are monitoring it from another room or location.
A local setup is attractive because you control the files, scene and timing. The trade-off is that you also own the failure points. A dedicated hardware encoder can separate the broadcast from your main computer, but it introduces another device to configure and maintain. A hosted workflow can remove the need to leave your own computer running; StreamNeo is designed for the specific case where you upload a video, provide the YouTube stream key and let the broadcast continue without your computer, with automatic monitoring and restart handling.
That does not remove the need to check YouTube’s current requirements or to test the content. It changes which part of the operation you are responsible for. If you choose to keep the local route, write down the restart steps: open the media folder, launch OBS, confirm the scene, check the source playlist, paste or select the current stream details, and verify the YouTube preview.
If the stream shows a black screen, troubleshoot the chain in order: confirm the VLC source has a visible file, check that the OBS scene is active, inspect the preview in YouTube Studio, and then check the connection and encoder messages. The guide on why YouTube shows a black screen for an RTMP video loop may help when the feed reaches YouTube but the picture is not visible.
Plan around YouTube’s under-12-hour archive behaviour
YouTube says streams under 12 hours are automatically archived. That matters when you describe a stream as continuous. A repeating playlist may keep sending media for longer, but the archive plan is a separate question from the live output.
If the recording is important, decide how you will preserve it before starting. You may choose shorter scheduled broadcasts, retain the original files locally, or create a separate recording workflow. Do not assume that a long-running live broadcast will produce one archive you can always access in the form you want.
The 12-hour statement should also shape your metadata and viewer expectations. A devotional channel might prefer separate sessions with clear start times. A study channel may want each lesson block to stand alone. A local business may need the public replay to contain a particular announcement rather than many repetitions before the viewer reaches it.
Review YouTube’s current encoder guidance before relying on a duration or archive behaviour, because platform rules and product interfaces can change. In every case, distinguish three things in your plan: how long the local playlist runs, how long YouTube receives the encoder feed, and what replay or recording you need afterwards.
Choose the operating method deliberately
OBS and VLC are a sensible route when you need direct control over local files, scene design and playback order. They are also practical when someone can check the computer and connection. The software itself does not make the channel unattended.
A local computer is less suitable when the machine must be switched off, when the internet connection is unreliable, or when nobody can respond to a stalled application. A hardware encoder may be worth considering if you want a separate physical device, but it still needs power, a source and a network connection. A hosted service may suit an unattended workflow, but compare its current features, support, reliability terms and cost on the vendor’s own site before committing.
For a first run, keep the decision narrow. Prepare the media, build one VLC playlist, verify the loop, test the YouTube ingest and observe the system through a complete representative cycle. Only then add more scenes, overlays, devices or automation.
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
Can I play several local videos continuously with OBS?
Yes. Install VLC, add an OBS VLC Video source, place the files in its playlist and enable Loop Playlist. The files will repeat when the source reaches the end, but the computer, OBS, VLC, power and internet connection still need to keep working.
Should Shuffle Playlist be on or off?
Leave it off when the files must play in the order you entered. Turn it on when a randomised sequence is wanted, then test the resulting combinations because shuffle does not understand the editorial meaning of your files.
Does Loop Playlist guarantee a 24/7 YouTube broadcast?
No. It only tells the media source to restart after the final file. It does not recover a crashed application, failed computer, power cut, missing file or lost upload connection.
Will YouTube archive a stream that runs for longer than 12 hours?
YouTube states that streams under 12 hours are automatically archived. For a longer broadcast, plan recording and replay requirements separately and check the current official encoder guidance before relying on a particular archive outcome.