A dependable way to rotate sermon recordings on YouTube Live is to use OBS Studio with its VLC Video source. Add the recordings in order, enable Loop Playlist, and send the resulting programme to YouTube with an encoder stream.
This setup can run from a church computer, but it is not self-proving. VLC must be installed with the same 32-bit or 64-bit architecture as OBS, and you should test the complete playlist before relying on it overnight.
Decide how the broadcast should run
The arrangement is straightforward: VLC provides the ordered media playlist inside OBS, OBS encodes the picture and sound, and YouTube Live receives that feed. The files remain on the computer running OBS, so that computer needs access to them for the entire broadcast.
This is different from uploading each sermon as a separate YouTube video. A live stream gives viewers one continuing watch page, while the playlist determines what OBS sends next. If the computer loses power, the network connection fails, or OBS stops, the YouTube broadcast can also stop. There is no setting that removes the need to monitor the complete path.
For a local setup, make a short operating note before you begin. Record where the sermon files are stored, which account owns the YouTube channel, who holds the stream key, and who can restart the computer or encoder. Keep the stream key private because it gives whoever has it the ability to send video to the channel.
The local approach is often the simplest starting point for a church that already has a suitable computer. A hosted workflow can remove the need to keep that computer running, but it introduces a service dependency and a different recovery process. If you are comparing local and hosted operation, begin with the practical differences in the options for reducing data usage on an OBS 24/7 stream, rather than choosing only by the word “24/7”.
Install VLC and check its architecture against OBS
OBS’s VLC Video source depends on VLC being installed. Without VLC, or with an incompatible installation, the source may not work as intended. Install VLC before building the scene, then check whether both applications are 32-bit or both are 64-bit.
On Windows, you can usually identify the VLC architecture from its installed programme details or installer name. Check OBS’s own system information as well. Do not assume that a 64-bit operating system means every installed application is 64-bit. The relevant comparison is the architecture of OBS and the installed VLC application.
If you already have OBS open, close it before installing or changing VLC. Install the matching VLC version, reopen OBS, and then look for the VLC Video source. If the source is absent, fails to load, or cannot read the playlist, stop and correct this compatibility issue before configuring YouTube.
Keep the media files in a stable folder rather than on a removable drive that may be disconnected. Use simple file names while testing, such as sermon-01.mp4 and sermon-02.mp4. This makes the order easier to inspect and reduces the chance of selecting an old export by mistake.
OBS’s Media Sources documentation describes the relevant source types and supported examples, including MP4, MOV, MKV, WebM, MP3, AAC and WAV. A format being listed does not mean every file will have the same picture, sound or transition quality, so inspect the actual recordings in VLC before adding them to the broadcast.
Add a VLC Video source in OBS
Open OBS and create a scene for the sermon stream. Give it a clear name, such as Sermons - live playlist, so an operator can identify it later. In the Sources panel, select the plus button and choose VLC Video.
Name the source something equally clear, such as Sermon playlist. The exact labels can differ slightly between OBS versions, but the important point is to choose VLC Video rather than Media Source. Media Source is useful when one file should play, and it includes a Loop option for repeating that single file. It is not the playlist control described here.
The VLC Video properties contain a playlist area. Use the control to add files, then check that the entries appear in the source’s list. If the preview is black or silent, check the file in VLC first, then confirm the VLC installation and architecture match. Do not proceed to YouTube until OBS can play at least one selected recording.
Set the source to fill the intended canvas without stretching faces or text. A sermon recording made for a mobile phone may be vertical, while the OBS canvas may be horizontal. You can fit the source inside the canvas, crop it deliberately, or change the presentation around it, but check the result in the preview rather than relying on the file’s name or resolution.
Audio deserves its own check. Watch the OBS mixer while speech is playing and listen for clipping, a very low level, or an unexpected second audio path. If the file contains a long silent opening, that silence will also be sent to YouTube. The guide to keeping audio playing between videos is useful when your programme includes separate music beds or other audio sources, but do not add extra sources until the basic sermon playlist works.
Add sermon files in the intended order
Add every recording to the VLC Video playlist in the order in which viewers should hear it. Do not rely on alphabetical order unless the filenames make that order unambiguous. Numbering files with a consistent pattern is safer than correcting the sequence later in a crowded source panel.
For example, a Sunday rotation might be:
| Order | File | What to check |
|---|---|---|
| 1 | sermon-01-welcome.mp4 |
The opening frame and introduction are present |
| 2 | sermon-02-faith.mp4 |
The previous recording ends cleanly |
| 3 | sermon-03-family.mp4 |
Speech begins at a sensible level |
| 4 | sermon-04-closing.mp4 |
The final frame is not an accidental edit screen |
Use the playlist controls to move an item up or down rather than assuming the order in which you selected files will always be the order you want. Save a written copy of the intended order for the person who operates the stream. If a recording is replaced, update both the folder and the operating note.
Play the end of each file and the beginning of the next one. Look for a hard cut, a black frame, a burst of silence, or audio that starts before the picture. These may be acceptable for your channel, but you should know they are present. If the recordings were made in different rooms or on different devices, their speech levels may also vary.
Do not add a separate transition video merely to hide an unknown problem. First establish whether the issue is in the source file, the playlist order, or the OBS scene. A short branded slate can be useful when it is part of the intended programme, but it should not conceal a failed handoff that has not been tested.
Keep Loop Playlist enabled
In the VLC Video source properties, leave Loop Playlist enabled when the complete list should start again after the final recording. OBS describes this setting as controlling whether the source restarts after it has run out of media files. In the normal playlist workflow, that means the first file follows the last file when the source reaches the end of the list.
Check the setting visually before every major broadcast change. It is easy to confuse Loop Playlist with a single-file loop. The former repeats the ordered list; the latter is associated with the Media Source workflow for repeating one file.
A loop does not repair a bad file. If one recording cannot be opened, has a damaged ending, or causes OBS to stop presenting media, the playlist may not behave as you expect. Test with the actual files that will be used, not with four short sample clips and then a different collection overnight.
If your recordings have different aspect ratios, frame rates or audio formats, watch the complete sequence at least once. The loop control only describes what happens when the list runs out. It does not promise that every change between files will look or sound continuous.
Connect OBS to YouTube Live
In YouTube Studio, create or schedule an encoder-based live stream. YouTube provides a stream URL and a stream key in the Live Control Room. In OBS, open Settings, choose Stream, select the relevant YouTube service or custom server arrangement, and enter the details supplied by YouTube.
Treat the stream key like a password. Do not paste it into a public document, send it in a group chat, or include it in a screenshot. If you believe it has been exposed, use YouTube’s controls to replace or reset it before the next broadcast.
Start OBS and confirm that the VLC source is visible, the audio mixer is moving, and the stream status shows a connection. YouTube’s encoder guidance explains the process of sending an encoder feed and checking the preview in Live Control Room: YouTube’s live encoder instructions.
Wait for the YouTube preview before making the stream public. Check the channel page and the watch page as well, because the picture seen by the operator in OBS is not the same as the final viewer experience. YouTube recommends monitoring audio and video quality during an encoder stream rather than assuming that a successful connection means everything is correct.
Keep upload capacity above the stream bitrate. YouTube’s guidance recommends retaining about 20% upload-bandwidth headroom, so the broadcast is not using every part of the available upstream connection. If your connection is shared with other users, account for their activity rather than measuring only when the building is quiet.
You can use the OBS bitrate checklist for a 24/7 YouTube stream when choosing settings. The right value still depends on the output resolution, connection and computer, so treat the checklist as a starting point and confirm the result in YouTube’s stream health information.
Test the handoff and playlist restart
The essential test is not whether the first sermon plays. It is whether the end of one sermon reaches the beginning of the next, and whether the final sermon returns to the first one with the expected picture and sound.
Start with two short copies or use a small test playlist made from the real files. Let one item reach its end without manually changing scenes. Watch OBS and the YouTube preview at the same time if possible. Then allow the last item to finish and confirm that the first item begins again. This is a test of your current files and settings, not a guarantee for a later revision.
During the test, check these points:
- The final spoken words are not cut off.
- The next sermon does not begin with an unexpected black frame or silent section.
- The picture does not resize or become stretched between files.
- Audio does not jump sharply in loudness.
- The playlist restarts at the intended first file.
- OBS remains connected when the source changes.
- YouTube’s preview and watch page show the same intended programme.
If the handoff is poor, edit the source files or adjust the presentation before going live. Do not use a second VLC source as a workaround until you understand the first source, because extra sources make it harder to identify which one is producing the audio or picture.
Start the encoder ahead of the public start time so you can inspect the preview. YouTube’s event guidance recommends starting the encoder at least 15 minutes before an event and checking the preview. The practical value is time: a missing file, wrong scene or exposed desktop can be corrected before viewers arrive.
Plan for long-running operation and archives
A local OBS stream needs more than a playlist. Keep the computer awake, prevent automatic updates or sleep from interrupting the session, and make sure the media folder remains available. Arrange for someone to check the stream rather than treating the absence of a complaint as proof that it is working.
Monitor the YouTube stream health indicators and listen to the programme occasionally. A frozen picture, missing sound or disconnected encoder may not be obvious from the room where the computer sits. If the stream is important, decide in advance who checks it, how they contact the operator, and what they do after a power or network interruption.
Archive planning matters because a single very long broadcast has limits. As listed on YouTube’s site in October 2026, streams shorter than 12 hours are automatically archived, while streams longer than 12 hours may not be captured. If a replay is important, plan separate sessions that finish before that point and retain a local recording as a backup.
DVR has a similar planning issue. As listed on YouTube’s site in October 2026, DVR may be limited or unavailable beyond 12 hours, and viewers cannot seek back to before the live stream began. A viewer joining late may therefore have less ability to rewind than you expect.
For India-based channels, a connection that looks adequate during office hours may behave differently overnight. Keep the headroom recommended by YouTube, and consider whether other users share the connection. The guide to reducing buffering on a 24/7 mantra stream covers related connection checks that also apply to sermon playback.
If keeping a computer awake, maintaining files and responding to failures is not practical, StreamNeo removes the need to keep your own computer running for this YouTube-only workflow: upload the prepared video, provide the YouTube stream key, and let the cloud broadcast handle the playback while you monitor the channel. Check the exact playlist and recovery behaviour that your programme requires before changing an established process.
Rights, monetisation and programme content
Confirm that the church has permission to stream every sermon recording and every element inside it. This includes worship music, performances, photographs, video clips, readings and background material. The fact that a recording was made by the church does not automatically settle the rights for every included work.
YouTube scans live streams for third-party copyrighted material. Its response can include replacing the stream with a placeholder, interrupting or terminating the broadcast, or placing a claim on an archived stream. YouTube’s live-streaming terms and conditions say that you represent and warrant that you have the necessary rights for the live content on Google services.
Check the current official YouTube guidance for your circumstances. Permission to rebroadcast a recording is also separate from monetisation eligibility. YouTube’s channel monetisation policy addresses original and authentic content, and repetitive or mass-produced programming may be ineligible even where you have permission to use the material.
If the channel is monetised, ads may appear during live streams, but ad delivery is not guaranteed. Do not describe the stream to viewers as uninterrupted if advertising or other platform controls can interrupt the viewing experience.
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 use OBS Media Source instead of VLC Video?
Yes, Media Source is suitable when one sermon should repeat, because it has a Loop control. For an ordered collection of several sermon files, use VLC Video and enable Loop Playlist, provided VLC is installed and its architecture matches OBS.
What happens if VLC is missing or the architectures do not match?
The VLC Video source may be unavailable or may fail to load and play the playlist correctly. Install VLC and match its 32-bit or 64-bit architecture to OBS before continuing, then test the source again.
Does Loop Playlist guarantee a continuous YouTube broadcast?
No. It controls what the OBS source does when it reaches the end of the media list. Power loss, network failure, an unreadable file, an OBS problem or a poor handoff can still interrupt the broadcast, so test the full sequence and monitor it.
Should I use one stream for an entire day?
Plan around YouTube’s archive and DVR guidance rather than assuming a single long session is best. As listed on YouTube’s site in October 2026, streams over 12 hours may not be archived and DVR may be limited, so separate sessions and a local recording may be better when replay matters.