To repeat several church videos or recordings in an OBS YouTube stream, install VLC, add an OBS VLC Video source, load the files in the right order, and enable Loop Playlist. The repeat setting controls playback inside OBS; it does not connect OBS to YouTube or keep a stream running by itself.
The documented OBS and YouTube steps are general, not a separate India-specific workflow. You will also need to configure YouTube's encoder connection, check the preview, and test the playlist before relying on it for a service.
Install compatible OBS and VLC versions
Install OBS Studio and VLC on the computer that will run the broadcast. The VLC Video source depends on VLC being present; if it is missing from OBS's source menu, confirm VLC is installed before changing other settings. OBS's Media Sources documentation says that 64-bit OBS requires 64-bit VLC, so match the architecture rather than assuming that any VLC installation will work.
Use the official download pages and check the current installation instructions for your operating system. This guide describes the OBS desktop workflow; the names and layout of controls can change between software versions. After installation, close and reopen OBS if VLC was installed while OBS was already running, then check whether VLC Video appears in the Sources add menu.
A church may run OBS on a computer that is also used for slides, audio, or administration. Before the service, avoid installing updates or changing drivers immediately before a broadcast. A test with the same machine and files you intend to use is more useful than assuming a configuration on another computer will behave identically.
The location of a media file matters too. Keep the playlist files in a known folder that remains available to the computer, rather than on a removable drive that might be unplugged. OBS can only play media it can access; moving or renaming a file after setting up the source can leave an item unavailable. Keep a separate copy of the source files as a practical precaution.
Add a VLC Video source
Open the OBS scene that should display the playlist. In Sources, select +, choose VLC Video, and create a new source. Give it a recognisable name, such as “Service playlist”, so that you can distinguish it from a camera, title graphic, or other media source when checking the scene.
In the source properties, add the playlist files using the file-list controls. VLC Video is intended for multiple items, much like an image slideshow; it is the appropriate OBS source when you need several files in sequence. If you are using only one video, OBS's separate Media Source has its own Loop control and may be simpler. The difference is useful when troubleshooting: a one-file Media Source and a multi-file VLC Video playlist do not use identical property names.
Once created, check that the source fits the scene as intended. Use the preview to see whether the video fills the canvas, has black bars, or sits behind another source. If the video is supposed to run beneath service titles or scripture slides, ensure the source ordering in OBS is deliberate: sources higher in the list can cover sources below them.
Do not infer that a visible preview proves YouTube is receiving the image. At this stage, OBS is only playing media into its local programme output. The streaming connection is configured separately, later in the setup.
Add files in the intended order
Add each clip or recording in the sequence you want the congregation to see it. For example, you might place a welcome slide video first, then a sequence of authorised worship recordings, then a closing notice. The playlist order is an operational choice: adding the right files but in the wrong order can still produce an awkward service.
After adding files, inspect the list rather than relying on memory. If the source properties allow reordering, move items into their intended positions and remove accidental duplicates. Avoid filenames that are nearly identical, such as “opening-final” and “opening-final-2”, unless you have checked which one is correct. A short test of the first transition catches many mistakes before viewers encounter them.
Use media that OBS and VLC can decode on the actual computer. If a file does not play in the preview, test it directly in VLC and confirm the file path and format. A successful playback in VLC does not prove every OBS setting is right, but it helps separate a file problem from a YouTube connection problem.
If the service uses a fixed order, do not treat Shuffle as a convenient way to save arranging the list. A shuffled playlist can put a closing or announcement clip at an unintended point. For a general approach to planning a recurring devotional sequence, see how to schedule a bhajan channel playlist; the OBS source itself still needs its own ordered list.
Enable Loop Playlist and check Shuffle
Open the VLC Video source properties and enable Loop Playlist. OBS documents this option as controlling whether the source starts over after it has run out of media files. That is the repeat control for a multi-file playlist. It does not mean each file necessarily repeats individually before the next one; test the actual sequence to verify how the whole list behaves.
Shuffle Playlist is separate. Leave it off when the church needs a fixed order, such as an opening, songs, and notices. Turn it on only when random order is genuinely acceptable. If items appear in an unexpected sequence, inspect Shuffle before rebuilding the playlist.
The source also has visibility behaviour settings. These determine what happens to playback when the source is not visible in the active scene, such as when you switch from the playlist scene to a camera scene. Choose a setting that matches the service plan and test a scene change: depending on the selected behaviour, playback may continue, pause, or stop while hidden. If the playlist should continue underneath another scene, verify that explicitly rather than discovering the effect during worship.
Keep the concepts distinct. Looping repeats OBS source media; it does not set YouTube's watch-page playlist to repeat, start an encoder feed, or reconnect after a computer or network interruption. If your broader goal is a channel that recovers after a power cut, that is a separate problem from playlist order; see how to restart a YouTube stream after a power outage.
Connect OBS to YouTube with URL and key
In YouTube Studio, open Live Control Room and create or select the event or stream you intend to use. YouTube provides an encoder stream URL and a stream key. In OBS, open Settings, then Stream, select the YouTube service or the appropriate custom configuration, and enter the connection details in the fields shown by your current version. Follow YouTube's encoder setup instructions for the current Live Control Room process.
Treat the stream key as a credential. YouTube describes stream keys as like the stream's password and address. Do not put it in a scene, show it in a screen-share, post it in a chat, or leave it visible in a screenshot. If you think it has been exposed, use YouTube Studio's current controls to replace or reset it, then update OBS with the new key.
The playlist and the encoder connection are independent parts of the workflow. OBS plays the playlist into its programme output; the URL and key tell OBS where to send that output. You can have a repeating local preview with no YouTube feed, or an active YouTube encoder feed carrying the wrong scene. Check both sides rather than assuming one setting covers the other.
Before scheduling a public service, confirm that the channel is eligible to livestream under YouTube's current rules. The YouTube live streaming eligibility guidance states current account requirements, which may change. YouTube's general guidance includes channel verification and account standing requirements; do not rely on an old setup or another channel's eligibility as proof for yours.
For the music and video in the playlist, establish that the church has the rights required for the planned livestream and any archive. YouTube's Terms of Service place responsibility for necessary rights, including music rights, on the person providing the content. The answer depends on the particular recordings, permissions, territory and intended use, so check the relevant rights rather than treating a successful OBS test as clearance.
Check preview and start the stream
Start streaming from OBS when the scene and encoder details are ready. For a scheduled YouTube event, wait for the encoder feed to appear in Live Control Room and inspect its preview; then use YouTube's Go live control there when the event is meant to begin. This is a separate confirmation from pressing Start Streaming in OBS.
Check the preview for the actual programme: correct video, visible titles, audible sound, and no accidental desktop or settings window. Listen with headphones or another monitoring path, because a moving video preview does not confirm that the congregation can hear it. Check the audio level and whether the first and last seconds of each file are clipped or silent.
YouTube recommends preparing the encoder in advance and checking the preview. Its live streaming tips also advise leaving upload-bandwidth headroom: the available connection needs to accommodate the outgoing stream bitrate. Avoid treating a speed test taken at another time as a guarantee of stable service during the event. If the preview buffers or the stream drops, check the current upload connection and OBS output settings, and test again.
Run a private or unlisted rehearsal if appropriate for the event. Verify that the correct stream is selected, OBS is sending to it, the preview updates, and the stream reaches the intended visibility. Know which person will watch Live Control Room during the service, especially if the person operating OBS is also managing slides or sound.
A quiet overnight loop can fail in a different way from a service with an operator: the picture may keep moving while audio has stopped. For a church devotional stream, the checks in how to prevent a devotional stream from going silent overnight are relevant to monitoring, but they do not replace this source and encoder test.
Test repeat playback before relying on it
Do a complete test of the playlist behaviour before the service. Let the final item finish and confirm that the first item begins again. A quick glance at the preview immediately after enabling Loop Playlist is not enough, because it does not demonstrate what happens at the end of the list. If the list is long, use a short test playlist with representative files first, then confirm the real list's order and contents.
Check the following in a rehearsal:
| Check | What to verify | If it fails |
|---|---|---|
| VLC Video appears in Sources | VLC is installed and its architecture matches OBS | Install a matching VLC version, then reopen OBS |
| Files play in order | The visible file list matches the intended sequence | Reorder the list and check Shuffle Playlist is off |
| Playlist repeats | The first item starts after the last item ends | Reopen source properties and enable Loop Playlist |
| Preview reaches YouTube | Live Control Room shows the OBS programme | Confirm selected stream, URL, key and encoder feed |
| Scene switch behaves correctly | Media continues, pauses or stops as planned | Review the source visibility behaviour setting |
If playback ends instead of repeating, first check Loop Playlist in that VLC Video source's properties. If a file is skipped, verify its path and playback in VLC. If the order changes, check Shuffle Playlist. If a scene switch interrupts the media, inspect the visibility behaviour. These checks isolate likely causes without changing the YouTube stream key unnecessarily.
If YouTube does not show a preview, do not change the repeat setting first: confirm OBS is sending, then verify the selected YouTube stream and the URL/key fields. Conversely, a working preview does not show that the playlist will loop, so test the end-of-list transition as its own check.
For a single video file, use Media Source and its Loop option rather than building a one-item VLC playlist simply because the word “repeat” appears in a tutorial. For several files, VLC Video provides the playlist controls. If you are comparing broader ways to keep a channel online, software choices for a 24/7 YouTube radio stream addresses a different operational decision; it does not change how Loop Playlist works in OBS.
OBS looping is not a guarantee of continuous operation. The computer still has to stay on, OBS must remain open, the network must carry the encoder feed, and YouTube must accept it. For an always-on channel, make a separate plan for power, internet interruptions, monitoring and recovery instead of assuming that repeating files handles those risks.
If you want to avoid leaving a church computer running for a pre-recorded 24/7 channel, StreamNeo removes that specific need by turning an uploaded video into a YouTube live stream that runs with your computer switched off; it is separate from the OBS VLC playlist procedure above.
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 India have a different OBS playlist-repeat setting?
The OBS and YouTube documentation covered here describes a general workflow, not a separate India-only repeat feature. Use the same VLC Video source controls, and check current YouTube account and Live Control Room requirements for your channel.
Does Loop Playlist connect OBS to YouTube?
No. Loop Playlist repeats the media source in OBS after its files run out. You still need to configure YouTube's stream URL and key in OBS and send the encoder feed.
Why is VLC Video missing from OBS?
The source depends on VLC being installed, and OBS's documentation says 64-bit OBS requires 64-bit VLC. Confirm the architecture match and reopen OBS after installing VLC.
What should I do if the playlist plays once and stops?
Open the VLC Video source properties and check that Loop Playlist is enabled. Also confirm that the intended files are in the source list; if you are using one file with Media Source instead, check that source's separate Loop setting.