OBS does not import a playlist hosted on YouTube and loop it as a live source. For the documented OBS workflow, you use local media files in a VLC Video Source, then send the output from your computer to YouTube Live.
That distinction matters for a 24/7 channel: OBS can repeat the files while it is running, but playback depends on the computer, the files and the internet connection staying available. Here is how to set it up and what to check before leaving it unattended.
A YouTube playlist is not an OBS media playlist
A YouTube playlist URL points to videos hosted and played by YouTube. A VLC Video Source in OBS instead plays media files available to the computer running OBS. YouTube Live receives the encoded output from OBS; it is not the source of the playlist in this arrangement.
To build the OBS playlist, first obtain the media files you have the right to use and keep them accessible on the streaming computer. Add those files to the VLC Video Source in the order you want them to play. Do not paste a YouTube playlist URL into that source expecting it to fetch and repeat the hosted videos.
This also means that a change to a YouTube playlist will not automatically update your OBS sequence. To change what viewers see, update the local file list in OBS. Check that each file plays properly from its stored location before relying on it for a long broadcast.
If your source is a single video, OBS's built-in Media Source is a simpler fit: enable its Loop option for that one file. For several files, use VLC Video Source. OBS documents the distinction and the available source options in its media sources guide.
Install VLC that matches OBS
The VLC Video Source depends on VLC being installed. Install the version that matches your OBS architecture: OBS specifies that 64-bit OBS requires 64-bit VLC. If the source is missing from OBS, check that VLC is installed and that you have not mixed 32-bit and 64-bit versions.
Download VLC from the VLC project's official site, and OBS from the OBS Project. Install both before arranging the scene. If you update or reinstall either application later, check that the VLC Video Source remains available and that your existing files still open.
You do not need to install VLC because it is a general streaming requirement. It is needed here because the chosen OBS source uses it to handle a list of local media files. A single file can use OBS's Media Source instead, so choose the workflow that fits the material you are playing.
Add a VLC Video Source to the scene
In OBS, select or create the scene that will be sent to YouTube. A scene is the composition OBS broadcasts; it may contain the playlist source by itself or combine it with overlays, a logo, text or other sources. Give the scene a clear name so you can identify it later.
Use the Sources panel to add a VLC Video Source. Name it something recognisable, such as “Main programme playlist”, then open its properties. Add your local media files there. If the source does not appear in the add-source menu, return to the VLC installation and architecture check rather than looking for a YouTube playlist import option.
Make the VLC source visible in the active scene. OBS documents visibility behaviour for this source: by default it stops when hidden and restarts when shown. If you switch scenes during the broadcast, this can interrupt playback or start the list again. Choose the source’s behaviour deliberately, or keep it visible in the scene being broadcast. Test any scene changes before you leave the stream running.
Check the preview after adding the source. Confirm that the video fits the canvas, that any overlays do not cover important content, and that audio is present at a sensible level. A source can be playing locally in the preview while the YouTube stream is not yet live; those are separate checks.
Add files in order and enable Loop Playlist
Add files to the VLC Video Source in the intended playback order. The list is your running order: for example, a devotional channel could arrange an opening visual, a set of locally stored bhajans, and a closing visual, then repeat the sequence. Confirm filenames and order in the source properties instead of assuming that a folder’s sort order matches your programme plan.
Leave Loop Playlist enabled if you want OBS to start the list again after the last item. Shuffle Playlist changes the order to random playback; OBS documents it as off by default. Keep shuffle off when sequence matters, and test a short playlist end-to-end to see how one file transitions to the next and how the list restarts.
The loop repeats the media files that OBS can access. It does not fetch missing files or keep playing a file after it becomes unavailable. Keep the files in stable locations, avoid renaming or moving them after setup, and check that the computer account running OBS can read them. If media is on a removable drive or network location, its availability becomes another dependency.
For a local news loop or shop information channel, review the sequence whenever details change. A repeating playlist can keep showing an outdated price, event notice or schedule just as reliably as it repeats current material. A short test is a good time to confirm both playback order and that the right version of each file is loaded.
Connect OBS to YouTube Live
In YouTube Studio, open Create → Go Live and use the Live Control Room to create or select a stream. YouTube supplies the stream URL and stream key in the encoder connection settings. In OBS, open the stream settings, select the appropriate YouTube service option, and enter the connection details as directed by the current OBS and YouTube interfaces.
Treat the stream key as a credential. Do not show it in a screenshot, share it in a public setup note or leave it visible while recording a tutorial. If you think someone else has seen it, use YouTube Studio's current controls to replace or reset it, then update OBS with the new key.
YouTube's official encoder setup instructions explain how to obtain and use stream connection details. Follow the current Live Control Room prompts, since labels and available controls can change. OBS handles the local scene and encoding; YouTube's Live Control Room handles the stream's YouTube-side setup and controls.
If this is your first time enabling live streaming, do that well in advance. YouTube says initial activation may take up to 24 hours. That is an enablement delay, not a promise that an individual stream will take that long or that a broadcast will stay connected once started.
Start the encoder and verify the live output
Before starting, check the scene, playlist order, loop setting, audio, and internet connection. Start streaming from OBS, then watch the Live Control Room preview and stream health. Confirm that YouTube is receiving the intended picture and sound, not just that OBS shows a local preview.
Use a test broadcast to check the whole path: file playback, OBS encoding, connection to YouTube, and the resulting viewer-facing stream. Listen for silence or clipping, look for an unintended black frame between files, and check that the scene remains the one you expect. If the content is intended to run continuously, let the playlist reach its end during testing so you can verify the loop.
When YouTube indicates that the stream is ready, use the Live Control Room's go-live flow as required. Starting the encoder and making the broadcast publicly live are not necessarily the same action. Check the status in YouTube Studio after launch and keep the key private while resolving any connection issue.
YouTube says streams under 12 hours are automatically archived. Do not assume that a broadcast longer than that will appear as one complete recording. If you need an archive, plan how to retain source files or create separate recordings, and check YouTube's current guidance for the behaviour that applies to your channel.
Plan for computer, media and internet interruptions
A local OBS playlist is continuous only while the computer running OBS is on and operating, OBS remains open and configured, the media files remain accessible, and internet access is available. A power cut, system restart, application crash, disconnected drive or network outage can stop or interrupt the broadcast. Neither the playlist loop nor YouTube's receipt of the encoder stream removes those dependencies.
Plan for likely failure points before scheduling a long run. Set the computer not to sleep during the broadcast, arrange power and network access suitable for the location, and check that the media drive will remain connected. Where a restart is possible, know who can reopen OBS and verify the stream. Do not treat a successful test as a guarantee against a later interruption.
The visibility setting is another small operational risk. If the playlist source is hidden by a scene change, its documented default behaviour may stop playback and restart it when visible again. Keep the source visible in the programme scene or select a suitable hidden-source behaviour, then test the exact scene changes you intend to use.
If you want automatic recovery, distinguish restarting OBS from recovering the entire broadcast. A restart arrangement can help after an application crash, but it cannot restore internet service, reconnect a missing drive or correct a broken media file by itself. A practical restart checklist for a stream after disconnects helps clarify which failure you are trying to recover from.
There is also a choice between managing playback on a local computer and handing off playout to a hosted service. YouTube's encoder guidance lists cloud services for 24/7 streaming, but that does not establish their current price, terms or fit for your channel. Compare responsibility for playback, scene control, recovery and verified cost. If you want to examine local versus hosted approaches, the OBS and FFmpeg looping comparison outlines a different local workflow; the guide to cloud playout without a local PC is relevant if keeping a computer running is the main concern.
For a one-file audio programme, the source choice and checks differ slightly from a sequence of videos. The Icecast MP3-to-YouTube OBS guide covers that adjacent case. For this playlist setup, though, the basic rule stays the same: OBS plays local media, and the computer and connection must remain available for the stream to continue.
If keeping the computer on and watching for interruptions does not suit the channel, a hosted workflow may remove that particular burden. StreamNeo turns an uploaded video into a YouTube live stream, so you do not have to leave your own computer running for that job.
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 paste a YouTube playlist URL into OBS and stream it continuously?
Not with the documented VLC Video Source workflow. That source uses local media files added to its playlist; it does not import and loop a YouTube-hosted playlist URL. Use files you can access on the OBS computer and connect OBS separately to YouTube Live.
Do I need VLC for one video file?
Not necessarily. OBS's built-in Media Source can play and loop a single file, while VLC Video Source is the direct fit for a sequence of local media files. If you choose VLC Video Source, install VLC with the same architecture as OBS.
Will the stream continue if my computer or internet goes down?
No. This local setup depends on the computer running OBS, accessible media files and internet access. If any of those become unavailable, playback or delivery can stop; plan how to notice and respond rather than relying on the loop setting to solve it.
Does a 24/7 stream always become one YouTube archive?
YouTube's cited guidance says streams under 12 hours are automatically archived. Do not assume a longer continuous broadcast will be saved as one complete recording; check YouTube's current guidance and make a separate recording plan if you need an archive.