For a church stream built from prerecorded sermons, worship music or notices, OBS’s VLC Video Source can play a playlist while OBS sends the finished scene to YouTube. Install VLC with the same architecture as OBS, load and order the files, then set looping, shuffle and visibility to match the programme you want viewers to see.
That configures playback, not an uninterrupted broadcast: the computer, OBS, network connection and YouTube ingest still need attention. YouTube also warns that a stream longer than 12 hours may not be captured as an archive, so plan separately if you need a complete recording.
Install VLC to match OBS
Install VLC before adding the source in OBS. The VLC Video Source relies on VLC being present, and OBS specifies that 64-bit OBS requires 64-bit VLC. If you use another OBS architecture, check the matching VLC build rather than assuming that any installed copy will work.
On Windows, a common symptom of a missing or incompatible installation is that VLC Video does not appear in OBS’s Sources add menu. Confirm which OBS build is installed and install the matching VLC architecture; then restart OBS and check again. OBS supports the VLC Video Source on Windows, macOS and Linux, but exact package and menu details can vary by operating system and software version. Use the current OBS guide to media sources for its requirements and source options.
If you are setting this up on a church computer that also runs slides or sound software, keep the installation simple: install from VLC’s official site, avoid changing unrelated system settings, and make a note of the versions and architecture that work together. Do not treat the source appearing in the menu as proof that every file will play correctly. Test the actual media you plan to use.
A VLC Video Source is useful when the scene needs a playlist rather than one file. OBS’s standard Media Source is aimed at an individual media file; VLC Video can use a playlist and VLC’s broader media support. That distinction matters if a service stream alternates between a sermon recording, a worship item and a notice loop. For a single clip that never changes, a simpler source may be enough.
Add VLC Video to the intended scene
Open the OBS scene that will carry the prerecorded programme. In Sources, select the add control and choose VLC Video. Give the source a name that makes its purpose clear, such as “Sunday recordings” or “Overnight worship loop”. If the source is called “VLC Video 2”, it becomes harder for another volunteer to tell which playlist is on air.
The new source needs to be placed and sized within the scene. Select it in the preview and fit or transform it to the canvas, checking that the image is not cropped or stretched. If the church uses a logo, captions or a background behind the video, check the source order in the Sources list: sources higher in the list can appear over sources beneath them. A playlist can be playing correctly while a title card or other layer covers the image.
Create the source in the scene that is meant to use it, not just in whichever scene happened to be selected. If there are separate scenes for a sermon, a holding screen and a live camera, decide which ones should contain the VLC source. OBS scene collections can make this confusing when volunteers switch between services or events, so confirm the collection and scene names before editing.
Once the source is on the canvas, test it with one representative file before loading a long playlist. Watch the OBS preview and check the mixer for audio activity. If you see no picture or hear no sound, troubleshoot the file, track and source settings before connecting the full programme to YouTube. A small, controlled test is easier to diagnose than a playlist with many items.
Load and order the sermon playlist
In the VLC Video Source properties, add the files that make up the programme to its playlist. Choose the actual media files on the computer, then arrange their order deliberately. For a service sequence, that might be an opening notice, a sermon, a closing prayer and a quiet holding item. The sequence should reflect what viewers will encounter if they join midway, not only the order in which the files were recorded.
Keep the media in a location that the OBS computer can access consistently. If files are moved, renamed or stored on a removable drive that is unplugged, the playlist may no longer resolve them. Before a long run, open the source properties and confirm that each intended item is still present. A brief play-through of the start of each file can catch a wrong export, silent audio or an outdated notice.
The VLC Video Source has an Audio Track setting; OBS documents track 1 as the default. A file can contain more than one audio track, and the first track may not be the one the church expects. Select the intended track if necessary, then listen in OBS rather than relying only on the meter. A meter indicates signal; it cannot tell you whether the language, mix or content is correct.
If you are planning a continuous rotation, think about where the programme begins for someone joining at an arbitrary time. A fixed playlist gives a dependable order, but a viewer may join in the middle of a sermon. If the service needs a title or context, include it in the video itself or in an OBS overlay. This is a separate presentation decision from how VLC loops the files. For other scene ideas, the guide to displaying the current sermon title on a church stream can help you consider how programme information reaches late-arriving viewers.
Choose looping and shuffle intentionally
Enable Loop Playlist if the sequence should start again after the final file. OBS describes this setting as restarting the source when it runs out of media; it is documented as on by default. Verify the checkbox in the source properties rather than relying on a remembered default, particularly if a different volunteer created the scene.
Shuffle is independent of looping. It is documented as off by default. Leave it off when order matters: a sequence that ends with a closing prayer and then returns to an opening notice is easier to understand when it repeats consistently. Enable shuffle only where the church wants items in an unpredictable order, and consider whether that is acceptable for sermons, announcements or worship selections.
| Choice | What viewers get | When it can fit |
|---|---|---|
| Loop on, shuffle off | The ordered list repeats from its beginning | A planned service or a sequence where context and order matter |
| Loop on, shuffle on | The list repeats, with items played in an unpredictable order | A collection of interchangeable background items |
| Loop off | Playback reaches the end of the list and does not restart through the loop setting | A one-time programme where the next action is managed separately |
This table describes source behaviour, not what YouTube does with the broadcast. If the file list ends and looping is off, OBS may still be sending a scene, but the video source itself has no further playlist item to show. Decide what should be visible then: a holding slide, a camera scene or a deliberately ended programme. If your goal is to keep the YouTube broadcast open after a video finishes, the separate guide on keeping a YouTube livestream from ending when a file finishes addresses that broader distinction.
Looping can make a long programme feel continuous, but it does not repair missing files, a stalled source, a closed OBS session or a lost network connection. Watch a complete transition in a test session. Confirm that the last item ends cleanly, the first item begins as expected, and the sound does not become unexpectedly loud or silent at the boundary.
Set visibility and scene behaviour
OBS provides visibility behaviour for VLC Video Source that determines what happens when its scene or source is not visible. The available choices include stopping and restarting when it becomes visible, pausing and resuming, or always playing even while hidden. These are distinct behaviours; select one based on how the church uses scenes, then test an actual scene switch. The OBS documentation for VLC Video Source describes the source settings, including playlist and visibility controls.
| Visibility behaviour | While the source is hidden | When it becomes visible again |
|---|---|---|
| Stop when not visible | Playback stops | Playback starts again from the beginning |
| Pause when not visible | Playback pauses | Playback resumes from the paused point |
| Always play | Playback continues in the background | The source appears at its current point |
For one scene that remains on air, the visibility choice may have little practical effect. In a multi-scene service, it can change the programme substantially. For example, if a volunteer switches from a sermon scene to a holding slide and later returns, stop-and-restart can replay the sermon from its beginning; pause-and-resume can return to the same moment; always-play can show a later part of the recording. None is universally correct.
Choose according to the intended service flow. If returning to a sermon from the start is desired, stopping and restarting may suit. If a temporary switch should not lose the current point, pause and resume may be more appropriate. If the playlist is meant to progress regardless of which scene is shown, always-play may match the plan. Always confirm that the audio does not continue unexpectedly when its video is hidden; hidden does not necessarily mean silent.
A practical test is to start a clip, switch away briefly, then switch back and note whether the source stopped, paused or continued. Repeat with the actual scenes used by the church. This exposes errors that a still image in the preview will not reveal, such as a hidden audio feed continuing under a different scene or a sermon restarting when the operator expected it to resume.
Configure YouTube as a separate destination
The VLC playlist is the content source; YouTube is a separate streaming destination. In YouTube Live Control Room, create or select the intended stream, then enter the server URL and stream key in OBS’s stream settings. YouTube’s encoder setup guidance explains how to connect an encoder. Treat the stream key as private: anyone with access to it may be able to send a broadcast to that destination.
Before going public, check the stream’s title, visibility and audience settings in YouTube. A church may prefer an unlisted test so volunteers can check playback without announcing the test to the full audience. Confirm that the watch page is the intended one and that a second device can open it. Do not assume that starting OBS has created the right public event or that the stream is visible to the intended viewers.
Choose encoder output that the church’s upload connection can sustain. YouTube advises leaving 20% bandwidth headroom beyond the total streaming bitrate and recommends selecting settings appropriate to the available connection. If the upload capacity varies, a lower, stable output may be more useful than a high-quality setting that repeatedly struggles. Review the current YouTube encoder settings and bitrate guidance for the chosen resolution and frame rate rather than applying one bitrate to every setup.
For YouTube’s general RTMP/RTMPS encoder recommendations, H.264 is supported, bitrate encoding should be CBR, and the keyframe interval is recommended at two seconds and should not exceed four seconds. These are configuration references, not a guarantee of delivery. Internet performance, local equipment and the receiving service all affect the actual stream. If your upload route has had trouble, the practical checklist for YouTube health warnings when Indian broadband upload speed drops is relevant before you rely on the connection overnight.
Test audio, motion and stream health
Test before the service or scheduled run, using content that resembles the real stream. YouTube recommends testing with similar audio and movement and monitoring stream health during the event. A static title slide cannot reveal the same problems as a sermon with speaking, music and a moving camera. Use a short, unlisted or otherwise controlled test to check the complete path from VLC, through OBS, to YouTube’s incoming preview.
Check the picture in motion. Look for a wrong aspect ratio, black frames between files, a frozen image, text cut off at the edges or transitions that cover the programme. Check the audio in the OBS mixer and on the YouTube preview. Listen on a second device with its volume set sensibly, because a meter alone will not reveal distortion, poor balance or the wrong track. If sound is distorted, the troubleshooting guide to distorted audio in an always-on YouTube stream offers relevant checks.
During a real broadcast, keep the YouTube Live Control Room health information available and arrange for someone to check it. YouTube says connectivity disruption can break a stream; a looping source only repeats local media and cannot prevent that. OBS also needs to remain open and the computer needs power and a working network connection. A volunteer should know what to check if the preview freezes or the stream health indicator reports a problem, rather than treating a playlist as unattended infrastructure.
Use a simple handover checklist: confirm the correct OBS scene and VLC playlist, hear the intended audio, verify the YouTube preview and watch page, and make sure the person responsible knows how to pause or end the broadcast. Keep the stream key out of printed public instructions. If there is a test event and a real event, label each clearly so a volunteer does not start or share the wrong one.
StreamNeo can remove the need to leave the church’s own computer running simply to replay an already prepared video, which is useful when keeping that computer available overnight is the particular burden; it is YouTube-only and does not replace checking the playlist, destination or archive needs.
Plan separately for recordings and media rights
Do not rely on YouTube to preserve a single nonstop broadcast as a full archive. YouTube says streams shorter than 12 hours can be automatically archived, but a stream exceeding 12 hours may not be captured at all. That is a possibility, not a precise cutoff promise for every stream. If you need a complete record, make a separate local recording plan and confirm that the recording is actually being written and has enough available storage.
A local recording is a distinct task from sending the live output. Decide who checks the recording, where it is stored, how it is labelled and how it will be copied or retained. Test the recording workflow before relying on it, including whether the intended audio and scene are included. The OBS guide to recording your screen and other tools gives background on recording workflows, but verify the controls and file location in the version you use.
Also check that the church has the necessary rights for every item in the live playlist, including recorded songs, sermon video and other media. YouTube’s livestream terms place responsibility on the content provider to have the rights required for live content, including applicable music rights. Which permissions apply depends on the material and territory; this article cannot determine a church’s particular obligations. Check current official guidance and the relevant rights holders rather than assuming that a song used in a service can automatically be rebroadcast online.
Prepare a repeatable handover
A setup is more useful when another volunteer can understand it without reconstructing the original decisions. Keep a short internal note with the OBS scene name, VLC source name, playlist order, loop and shuffle choices, visibility behaviour, selected audio track and YouTube event to use. Do not include the stream key in a shared note. Record where the approved media files are stored and who can update them.
After software updates or a change of computer, recheck the VLC source and test the destination again. An update may change menu wording or expose a compatibility issue; a copied scene collection may refer to media paths that only existed on the previous machine. The point is not to avoid all changes, but to repeat the checks that connect the source, OBS scene and YouTube event.
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
Does OBS’s VLC Video Source keep a YouTube stream running by itself?
No. It can loop a local playlist, but OBS, the computer, network connection and YouTube destination remain separate parts of the broadcast. Test them together and monitor stream health rather than treating Loop Playlist as an uptime feature.
Should a church turn on shuffle?
Leave shuffle off when the order carries meaning, such as a sermon sequence or a planned service. Turn it on only when the files are interchangeable and an unpredictable order is acceptable. Shuffle and Loop Playlist are separate settings.
Will YouTube archive a stream that runs all day?
Do not assume that it will. YouTube says a stream longer than 12 hours may not be captured at all, so use a separate tested local recording plan when a complete archive matters.
What should we do if VLC Video is missing from the Sources menu?
Check that VLC is installed and that its architecture matches OBS; OBS specifically requires 64-bit VLC for 64-bit OBS. Restart OBS after installing VLC and confirm the current version-specific requirements in OBS’s documentation.