A 24/7 lecture stream in OBS is built from local video files, not from a YouTube playlist. Add the files to OBS's VLC Video Source, put them in order, enable Loop Playlist, and send the encoder feed to YouTube.
The computer running OBS must remain available for the stream to continue. YouTube may offer pause or rewind controls in some live streams, but a long-running broadcast has separate DVR and archive limits, so do not promise viewers a complete rewind of the day's lectures.
Local lecture files are not a YouTube playlist
There are two different things people call a playlist here. A YouTube playlist is a collection of videos hosted on YouTube and played through YouTube's own pages. The method in this guide is an OBS playlist: a set of lecture files stored on your computer and played by OBS before the resulting video is sent to YouTube as one live broadcast.
That distinction affects the whole setup. You do not paste a list of YouTube video URLs into VLC Video Source. You prepare ordinary local files, add them to one OBS scene, and let OBS move from one file to the next. YouTube receives the output as a live encoder stream rather than as a sequence of separate uploaded videos.
This approach suits a college, coaching centre, study channel, or teacher who owns or has permission to use a collection of recorded lectures. It also lets you choose the order precisely. For example, you might place Introduction to Algebra first, followed by Linear Equations, Worked Examples, and a revision lecture, then repeat the sequence from the beginning.
If what you actually need is for several existing YouTube videos to play continuously, that is a different workflow. The guide on making a YouTube playlist play continuously on a live stream covers that distinction. For local files and OBS, continue with the steps below.
Before building the scene, put the lecture files in a stable folder. Do not keep them on a removable drive that may be disconnected overnight. Give files clear names such as 01-introduction.mp4, 02-algebra.mp4, and 03-revision.mp4; this makes the intended order easier to check later.
You also need the right to stream every lecture, including music, diagrams, guest material, screen recordings, and any third-party clips inside them. YouTube says it scans live streams for copyrighted content, and a match can lead to an interruption, placeholder image, or termination. If a rights owner has licensed material to you, check whether the channel also needs to be allowlisted through Content ID. The current guidance is in YouTube's copyright information for live streams.
Confirm that the channel can go live
Do this before spending time arranging the playlist. YouTube's live-streaming guidance says the channel must be verified and must not have had a live-streaming restriction during the previous 90 days. Its getting-started guidance also says a person must be at least 16 to livestream. These are platform requirements, not settings that OBS can fix.
Open YouTube Studio and choose Create, then Go live. If the channel has not used live streaming before, YouTube may require activation or verification before the encoder option is available. Allow for that process rather than discovering it when your lecture stream is supposed to begin.
For a scheduled broadcast, create the event with a useful title, description, thumbnail, visibility, and start time. Make clear in the description that the broadcast contains recorded lectures if that is the format. A scheduled stream gives you a Live Control Room page where you can inspect the incoming feed before choosing Go live.
Treat the stream key as a password. Anyone who obtains it may be able to send video to the channel through the encoder connection. Do not publish it in a screenshot or paste it into an untrusted form. If you believe it has been exposed, YouTube provides a reset control in its live-stream settings. You can also review YouTube's encoder setup instructions when the Studio labels differ from those shown here.
Add a VLC Video Source in OBS
Install VLC before opening OBS. The VLC Video Source depends on VLC's libraries, so the source may not appear if VLC is missing. On 64-bit OBS, use 64-bit VLC. If OBS was already open while VLC was installed, close and reopen OBS before checking the source list.
Open OBS and create a new scene for the lecture channel, or select the scene you intend to use. In the Sources panel, select the plus button and choose VLC Video Source. Give it a name such as Lecture playlist, then confirm the source.
The source properties include a playlist area where you can add files. Use the file picker to select the first lecture, then add the remaining files. The exact appearance of the properties window can change between OBS versions, but the important control is the VLC source's playlist rather than a separate Media Source for each lecture.
Resize the source in the preview so the lecture fills the intended canvas. If the files use different aspect ratios, decide how you want the mismatch handled before going live. A wide lecture recording may fit a wide canvas, while a portrait phone recording may leave empty space or need a designed background. Check a few files rather than assuming every lecture has identical dimensions.
The VLC source is useful here because it can play multiple files in sequence and repeat the playlist. For one lecture file only, OBS's ordinary Media Source also has a Loop checkbox. For several files, VLC Video Source is the more direct path because the order and repeat behaviour live in one source. OBS documents these source options in its Media Sources guide.
Check the audio meters while a lecture is playing. A video that looks correct but produces no movement in the mixer is not ready for YouTube. If a file has very quiet audio, compare it with another file and inspect the file itself before raising OBS levels aggressively. Excessive gain can create clipping that is harder to repair after publication.
Put the lectures in playback order
Add the files in the order you want viewers to experience them. If the source window lets you select an item and move it up or down, use those controls to correct the sequence. Do not rely only on the order in which files happen to appear in a folder; operating systems may sort names differently from the order you had in mind.
A simple preparation table helps when the collection is large:
| Position | File name | Topic | Expected transition check |
|---|---|---|---|
| 1 | 01-introduction.mp4 |
Course overview | Confirm opening audio and title frame |
| 2 | 02-algebra.mp4 |
Linear equations | Confirm the first frame follows the introduction |
| 3 | 03-worked-examples.mp4 |
Practice problems | Check that audio does not start late |
| 4 | 04-revision.mp4 |
Summary | Confirm the playlist returns to position one |
The table is for your operating notes, not something viewers need to see. It also gives you a reference when a student reports that the wrong lecture is playing. Keep the actual files and the notes together in a folder that is easy to back up.
After adding the files, play the first one in OBS and watch the transition into the second. A file can play correctly on its own but fail at the hand-off because of a damaged ending, unusual codec, or an audio track that starts in a different way. Test at least one transition between every pair if the stream is important.
Keep the playlist deliberately small if the lectures are still changing. It is easier to replace a clean, numbered collection than to troubleshoot a folder containing old exports, test clips, and duplicates. When you revise a lecture, use a new filename until you have confirmed which version is in the OBS playlist.
OBS also has source visibility behaviour that matters if you use more than one scene. Depending on the selected setting, a media source may stop and restart, pause and resume, or continue playing when its scene is hidden. For a single-scene lecture channel, keeping the source visible is simplest. If you add an intermission scene or a branded holding scene, test what happens when you switch away and back.
Enable Loop Playlist
In the VLC Video Source properties, enable Loop Playlist. This tells OBS to return to the beginning after the final file finishes. Without it, the playlist can reach the end and stop, leaving the stream on a frozen final frame or an empty source, depending on the source state.
Leave shuffle disabled when the lectures must follow a teaching sequence. Shuffle may be useful for a genuinely random ambience channel, but it is confusing for a course where Lecture 2 should follow Lecture 1. Read the source settings after saving them and make sure the repeat option applies to the playlist, not merely to one selected file.
Save the scene and test the end of the list. If the recordings are long, you do not need to wait through every lecture before testing the mechanism. Make a temporary copy of two short clips, add those copies to a test source, enable Loop Playlist, and watch the second clip return to the first. Then configure the real files in the production scene.
The loop is local to OBS. It does not create a recurring YouTube playlist, add videos to the channel's Video tab, or give viewers a library of individual lecture entries. YouTube sees one continuous encoder broadcast. If you want named lecture uploads as well, publish them separately or plan a separate upload workflow.
Connect OBS to the scheduled YouTube stream
Return to YouTube Studio's Live Control Room and open the stream you created. YouTube supplies a stream URL, sometimes described as a server URL, and a stream key. In OBS, open Settings, then Stream, select the appropriate service or custom server option, and enter the values in the matching fields.
Do not confuse the stream's public viewing link with the server URL. OBS needs the encoder connection details. Copy each value carefully, and avoid adding spaces at the beginning or end. If you use a scheduled stream, confirm that the selected event in Studio is the one whose details you copied.
Start the playlist in OBS, then select Start Streaming. Wait for YouTube to receive the feed. In Live Control Room, inspect the preview, title, audio, picture, and stream-health messages. For a scheduled stream, use the preview stage and choose Go live when the feed is ready, following YouTube's current prompts.
The OBS-to-YouTube connection does not make the computer optional. The local machine must keep OBS open, retain access to the source files, stay connected to the internet, and continue encoding. A restart, sleep setting, power cut, operating-system update, or network failure can interrupt the broadcast.
Before an overnight run, set the computer not to sleep while plugged in and prevent routine updates from restarting it at an inconvenient time. Keep the lecture folder on a reliable local drive. These are operational precautions, not a guarantee that the stream will remain live.
If keeping a computer running is the part you want to avoid, a managed service such as StreamNeo removes the need to leave this OBS machine running by taking an uploaded file and the YouTube connection into a separate cloud-based workflow. That is a different operating model, so compare playlist editing, recovery responsibilities, rights, and current terms rather than assuming it behaves exactly like OBS.
For a broader comparison of the machine, server, and managed approaches, see this explanation of 24/7 streaming on a VPS versus a managed service. It is especially relevant if the channel is becoming a daily operation rather than a small experiment.
Test playback and monitor the stream
Run a representative test before announcing the channel. Use the same scene, files, resolution, audio arrangement, and internet connection you expect to use overnight. YouTube's encoder guidance covers settings such as resolution, frame rate, and bitrate; choose settings your upload connection can sustain rather than copying a high setting that causes dropped frames.
Watch both sides of the connection. In OBS, look at the dropped-frame indicator, CPU load, preview, and audio mixer. In YouTube Live Control Room, inspect stream health, the received preview, and any warnings. A clean local preview does not prove that YouTube is receiving a stable feed.
Test the practical failures as well. Pause the source briefly, switch scenes if you plan to use them, and observe whether the playlist resumes or restarts. Check what happens when the final file ends. Confirm that the first lecture begins again and that its audio is present. If the channel uses a branded holding frame, check that it does not accidentally cover the lecture source.
YouTube recommends setting up an encoder in advance, running a representative test, previewing the stream, and monitoring its health. Follow the current YouTube encoder settings guidance because interface labels and recommended technical settings can change.
Keep a simple overnight checklist beside the computer:
- Is OBS open on the intended scene?
- Is the VLC playlist visible and set to loop?
- Is the computer connected to power and prevented from sleeping?
- Is the upload connection active?
- Does the YouTube preview show moving video and audio?
- Is the stream health indicator free of a current warning?
- Do you know who will check the channel if playback stops?
A local recording can help you diagnose a problem, but it also uses storage and processing resources. YouTube's archive guidance says streams shorter than 12 hours can be automatically archived, while streams longer than 12 hours may not be captured at all. Do not treat a 24/7 YouTube replay as a dependable complete record of every lecture. If the lectures must be preserved, keep a separate local copy of the source files and consider a planned local recording where the computer can handle it.
Viewer rewind is a separate question. YouTube says DVR can let viewers pause and rewind live streams, but it may be limited or unavailable for streams longer than 12 hours. A viewer also cannot seek to a point before the live broadcast began. Therefore, this OBS loop does not give viewers a guaranteed way to rewind to yesterday's Lecture 1 or browse the entire 24/7 run. If rewind matters, publish individual lectures or shorter sessions separately and verify the current YouTube DVR behaviour for the channel.
If YouTube reports a rights problem, stop and identify the material rather than repeatedly restarting the encoder. Keep permission records for lectures and embedded content. If a claim is incorrect, use YouTube's process carefully; the guide on disputing a Content ID claim on a YouTube live stream explains the issue in more detail.
For a devotional or educational channel that also uses music, the same rights check applies. A lecture may be yours while its intro music, stock clip, presentation template, or guest recording is not. Resolve those components before scheduling a long broadcast.
When OBS is the right fit
OBS is a sensible choice when you want direct control over the scene, local files, overlays, audio, and playlist order. It is also useful when someone can check the computer and respond to a failed source or connection. You can change the collection without uploading the lectures to a third-party system, although every change needs a new test.
The trade-off is operational responsibility. The computer, OBS, VLC, local storage, power, and internet connection all form part of the live chain. A cloud workflow can be a better fit when no one should leave a personal computer running, while a self-managed server can suit an operator comfortable with command-line administration. Neither choice removes the need to confirm rights and YouTube's current rules.
Choose based on the problem you are actually trying to solve:
| Need | Local OBS playlist | Managed cloud workflow |
|---|---|---|
| Arrange local lecture files | Direct control in OBS | Upload and arrange through the provider's workflow |
| Keep a personal computer off | Not with this method | This is the intended advantage of the model |
| Edit scenes and overlays | Flexible while OBS is running | Depends on the provider's current features |
| Recover from a local power or network failure | You must respond locally | Recovery is handled according to the provider's terms |
| Avoid recurring provider terms | No managed-service plan is involved | Check current pricing, limits, and conditions |
The table describes operating responsibilities, not promised uptime or performance. Before changing methods, run a short test with the real lecture files and confirm what happens at the end of the playlist, after a connection interruption, and when you need to replace a file.
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
Is this the same as streaming a YouTube playlist?
No. This workflow plays files stored on your computer through OBS's VLC Video Source. YouTube receives one live encoder feed; it does not receive a YouTube-hosted playlist of separate lecture videos.
How do I loop several lecture files in OBS?
Add a VLC Video Source, add the files to its playlist, arrange them in the required order, and enable Loop Playlist. VLC must be installed for this source to be available, and 64-bit OBS should use 64-bit VLC.
Can viewers rewind the complete 24/7 broadcast?
You should not promise that. YouTube's DVR behaviour can be limited on streams longer than 12 hours, and viewers cannot seek to before the broadcast began. Publish individual lectures separately if students need reliable access to earlier material.
What happens if the final lecture ends?
With Loop Playlist enabled, OBS should return to the first file and continue the sequence. Test the transition with short sample files before relying on the setup overnight.