If your podcast episodes are already saved on your computer, you can play them continuously on YouTube Live with OBS Studio and its VLC Video source. You add the files to an OBS playlist, choose their order and loop behaviour, then send the encoded feed to YouTube Studio.
This setup plays the files you add to the playlist. It does not automatically monitor a folder for new episodes, so you must update the playlist when your library changes. Continuous playback also does not mean that YouTube will create a separate, easy-to-navigate archive for every episode.
Install VLC and prepare the episode files
Start by putting the episodes you want to broadcast somewhere easy to find. A single folder is useful for organisation, but OBS will use the media items you add to its playlist rather than treating that folder as a live input. If you later copy a new episode into the folder, it will not automatically appear in the existing playlist.
Use files that your computer can open reliably and that you have permission to broadcast. Rights still apply to prerecorded audio, music, clips, interviews and any advertising included in an episode. YouTube notes that third-party content can affect a live stream and that Content ID claims may be made after a broadcast if it is archived. Check the current YouTube guidance on live-stream copyright before treating an old podcast library as cleared for public rebroadcast.
Give the files names that make the intended order obvious. A naming pattern such as 001-episode-title.mp4, 002-episode-title.mp4 and 003-episode-title.mp4 is easier to maintain than names based only on recording dates. This does not force OBS to sort them correctly, but it makes mistakes easier to spot when you add them.
If your episodes are audio-led, consider adding a title card, cover image or other suitable visual in OBS. Viewers should be able to tell what they are hearing and whether the broadcast is active. A visual element is useful for presentation, but it does not replace testing the audio, encoder settings or YouTube preview.
Install OBS Studio and VLC before creating the source. OBS documents that its VLC Video source depends on VLC being installed. On a 64-bit OBS installation, use the compatible 64-bit VLC build specified in the OBS media sources documentation. If the VLC Video source is missing after installation, close and reopen OBS after checking that VLC is installed in a compatible form.
Create a VLC Video playlist source in OBS
Open OBS and create a scene for the podcast broadcast. A scene is the layout OBS will send to YouTube. You can keep it simple: the VLC Video source for episode playback, plus any visual elements you want viewers to see.
In the Sources box, select the add button and choose VLC Video. This source is different from the ordinary Media Source because it can contain multiple media items in a playlist. OBS describes it as a playlist source, similar in purpose to an image slideshow, rather than a single-file player.
Give the source a useful name such as Podcast playlist. A clear name matters once you have separate scenes for a starting screen, an offline message or a scheduled programme. In the source properties, use the playlist area to add your local episode files.
The source needs to be visible in the scene for its video and audio to be sent by OBS. If the preview is blank, check that the source is enabled, that the selected file can be opened locally and that the scene is active. If the video appears but there is no sound, use the OBS audio mixer to check whether the source is producing audio and whether it is muted.
Do not confuse a playlist with a directory watcher. The documented VLC Video source setup describes adding media items to a playlist. It does not establish that OBS will scan a folder, notice a new file and add it while the stream is running.
Add files in the intended order
In the VLC Video source properties, add the episode files you want to play. Add them in the order you want listeners to hear them, then review the list from top to bottom. For a series that should play from the beginning, this is normally release order. For a devotional, educational or local programme channel, it might be a hand-picked sequence instead.
The order in the OBS playlist is the important one. The alphabetical order of the folder is not a substitute for checking the playlist itself. A file copied into the folder after setup is not necessarily part of the broadcast, and a file renamed on disk can make the displayed list harder to recognise.
After adding the files, click through the list and confirm that each path points to the intended episode. Remove duplicates and files that were only used for editing. If an episode was moved to another drive or folder, update its playlist entry rather than assuming OBS will find it.
A local playlist also depends on the computer remaining available. The files must stay on a connected drive, OBS must continue running, and the computer must not enter sleep mode or lose its network connection. A laptop that closes its lid overnight, a removable drive that disconnects, or an automatic system update can interrupt the broadcast even when the playlist itself is configured correctly.
For that reason, make the local machine part of the operating plan. Disable sleep for the period you intend to stream, keep the episode storage connected, and avoid using the computer for demanding tasks at the same time. If you need a more detailed approach to automatic startup, the guide on automatic startup for an FFmpeg YouTube stream on Raspberry Pi covers a different encoder path, but the operational lesson is similar: a long-running channel needs deliberate recovery planning.
Set shuffle and playlist looping deliberately
Shuffle and looping solve different problems. Shuffle changes the order in which the files are selected. Loop Playlist tells the source what to do after it reaches the end of the queue.
OBS documents shuffle as off by default and Loop Playlist as on by default for this source. Check both settings rather than relying on their current state, especially if you have copied a scene or opened an older OBS configuration.
| Intended broadcast | Shuffle | Loop Playlist | Result |
|---|---|---|---|
| Episodes once in release order | Off | Off | The queue plays from top to bottom and then ends |
| Repeat the same sequence | Off | On | The queue starts again after the final item |
| Randomised listening station | On | On | Items are selected in a changing order and the queue repeats |
| One planned pass with varied order | On | Off | The queue is shuffled for that pass and then ends |
For a numbered podcast series, leave shuffle off. With shuffle enabled, a listener may hear a later episode before an earlier one, which can make a narrative series difficult to follow. Shuffle may be suitable for independent interviews, prayer recordings, music programmes or a back catalogue where chronology is not important.
Enable Loop Playlist only when replaying the queue is genuinely intended. If you are testing with a short set of files, looping can make the source appear healthy because it keeps producing media, but it can also hide a missing episode or an accidental duplicate. Run through the queue once during testing before relying on repeated playback.
Looping the playlist does not guarantee a continuous, healthy broadcast. It only controls what the source does at the end of its listed items. OBS can still stop, the computer can sleep, the network can fail, an input file can cause trouble, or YouTube can report an ingest problem. If your channel keeps dropping, use the checks in why a 24/7 YouTube live stream keeps disconnecting rather than treating the loop setting as a recovery system.
Connect OBS to a YouTube Studio stream
In YouTube Studio, open Create and then Go live. Use the Stream workflow to create or select the broadcast. If you want viewers to see a watch page before the start, schedule the stream from the relevant YouTube Studio area instead of starting without notice.
YouTube provides an ingest server URL and a stream key for the encoder. In OBS, open Settings, select Stream and enter the service details supplied by YouTube. Treat the stream key as a credential. Do not publish it in a screenshot, paste it into a public document or leave it in a message that other people can access.
YouTube says that enabling live streaming for the first time may take up to 24 hours. Complete that activation before you plan an overnight broadcast. If the account is not enabled, OBS cannot make a working live feed simply because its local playlist is ready.
Start OBS when the scene, source and stream settings are in place. Depending on the YouTube workflow, YouTube Studio may first show the incoming encoder preview and then require you to select Go live. A scheduled broadcast may have an additional preview step. Follow the controls displayed in YouTube Studio rather than assuming that starting OBS alone makes the public page live.
YouTube lists supported encoder settings and recommends matching the output to your available upload capacity. The relevant YouTube encoder settings and bitrate guidance includes guidance on resolution, bitrate and keyframes. The practical point is to choose settings your connection can sustain, not the largest setting your computer happens to offer.
A local OBS setup has a direct advantage: you control the playlist and the files. It also has a direct cost in attention. The computer, storage, OBS process and internet connection all remain part of the chain. A cloud-hosted encoder may suit you better if the channel must continue while your local computer is switched off, but compare whether it accepts your file and playlist workflow, how it handles restarts, how it schedules broadcasts and what storage or usage charges apply. Do not assume that a service described as continuous streaming automatically imports a changing local folder.
If keeping a personal computer running is the specific problem, StreamNeo removes that part of the workflow by letting you upload the finished video, provide the YouTube stream key and run the broadcast without leaving your own computer switched on. It still does not change your responsibility for episode rights, the YouTube channel or the archive strategy.
Inspect the preview and stream health
Before committing to a long broadcast, test with representative material. Use an episode with the normal spoken-word volume, any music or inserted advert, and the visual layout you expect to show. A short test that contains only a silent intro or a static placeholder will not reveal the problems viewers are likely to encounter.
YouTube recommends testing before starting a live stream and checking stream health. In YouTube Studio, inspect the preview and the health indicators after OBS begins sending data. Confirm that the correct scene is visible, the episode is advancing, audio is present and the incoming feed is not reporting an unstable connection.
Listen on another device if possible. The OBS mixer can show movement while the broadcast still sounds too quiet, distorted or out of balance to a viewer. Check the public or preview playback with headphones, especially if the source contains speech over music. Verify that the title card does not cover captions or important visual information.
Watch the transition between two files. The end of one episode and the start of the next can reveal a longer gap, an unexpected black frame or a file that OBS cannot decode. If you are using Loop Playlist, test the transition from the last item back to the first. This is where a nominally repeating queue can fail as a practical listener experience.
Check your upload capacity while the test is running. A connection that works for browsing or occasional uploads may not sustain an encoder feed for many hours. If stream health deteriorates, reduce the output burden in line with YouTube's current guidance, improve the connection or choose a different operating arrangement. The bitrate testing checklist can help you make that check before committing to an overnight run.
Keep a simple monitoring routine after launch. Look at the YouTube Studio status, listen to the stream from outside the broadcasting computer and check that the playlist is moving. For an unattended channel, decide who will respond if the computer stops, the connection drops or an episode file fails. A playlist is content scheduling, not a complete monitoring plan.
Plan what continuous means for the archive
A queue that repeats can keep sending media, but it should not be treated as an unlimited replay archive. YouTube says streams under 12 hours are automatically archived. If you need distinct episode VODs, separate broadcasts or upload the episodes separately so that viewers can find them without searching through one long recording.
This matters particularly for podcasts. A listener looking for episode three may not want to scan a single long live replay that contains episode one, episode two, several repeats and a partial final pass. Decide whether the main purpose is live listening, a radio-style station or an archive of individual episodes. The playlist setup is suitable for the first two purposes, but it does not create episode chapters or separate uploads by itself.
If the library changes frequently, set a maintenance step. Add each new episode to the OBS playlist, place it deliberately, test that it opens and save the scene collection. If you want new episodes to enter the stream without touching OBS, the basic VLC playlist workflow is not enough; you need a different scheduling or automation arrangement and should verify exactly how it handles local files, failures and restarts.
You may also want a separate starting scene. Use a short visual and audio holding item before the first episode, then switch to the playlist once YouTube's preview is ready. This can make the public stream easier to understand, but it adds another scene transition to test. Keep the number of moving parts low until the core playlist has completed a full test pass.
For channels aimed at viewers in India or elsewhere across several time zones, publish the listening schedule in the channel description or stream details. State whether episodes play in order, whether the queue repeats and where individual episodes can be found. Clear information reduces the expectation that a repeating live feed is the same thing as a permanent episode archive.
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 OBS play a folder of podcast episodes on a YouTube livestream?
OBS can play multiple local media files through its VLC Video playlist source. You add the files to the playlist yourself; the documented setup does not make OBS watch a folder for newly added files.
How do I loop a playlist on YouTube Live?
Open the VLC Video source properties in OBS and enable Loop Playlist if the queue should start again after the final item. Keep shuffle off when the episodes must remain in a fixed order. Looping controls playlist playback, not the health of the computer, network connection or YouTube ingest.
Will YouTube save a 24/7 stream as a replay?
Do not assume that one uninterrupted broadcast becomes a complete, convenient archive. YouTube says streams under 12 hours are automatically archived, so use separate broadcasts or separate uploads when individual episode replays matter.
Do podcast episodes need separate rights for a live repeat?
You need the appropriate rights for the content you broadcast, including music, clips, guest material and inserted adverts. A repeat live stream can still be affected by third-party claims, and an archived broadcast can receive claims after the stream ends.