To loop recorded Advent readings on YouTube Live, use OBS Studio as the encoder: choose Media Source for one file or VLC Video for a playlist, then connect OBS to a stream created in YouTube Studio. The loop happens in OBS, not in YouTube; check the Live Control Room preview before you begin and do not assume the broadcast or its archive will run without interruption.
This approach suits a church that already has recordings and wants the same image and audio to continue while a computer runs OBS. You will need a verified YouTube channel with live streaming available, the recordings stored locally, and a reliable upload connection. If you are still deciding how to alternate prerecorded items and breaks, the guide to switching between prerecorded videos and scheduled breaks covers a related format choice.
Choose one recording or a sequence
Start by deciding what the congregation or online audience should hear after the final reading. If one recording contains the whole sequence, a single-file loop is straightforward: OBS plays the file and starts it again when it reaches the end. If each reading is a separate file, you can arrange them as a playlist and repeat the playlist. Those are different OBS sources with different setup requirements, so settle the format before building the scene.
A single file is easiest to review as one piece. You can listen from beginning to end, check that the opening is not abrupt, and confirm that the final moments lead sensibly into the first moments. A sequence gives you more control over order: for example, an opening reading, a pause, a second reading and a closing prayer can be separate items. It also means checking every transition and playlist entry, not just the first file.
Write down the intended order and whether you want silence, music or a title card between readings. Do not assume that a playlist source will add a pause or crossfade; confirm how the selected files actually behave in OBS. If the recordings have different loudness levels, listen to them in order on ordinary speakers as well as headphones. A quiet reading followed by a much louder recording can be uncomfortable even when each file sounds acceptable alone.
Check that you have permission to broadcast the material. The church is responsible for rights to the recording, the translation or text, music, and any third-party material it contains. YouTube scans live broadcasts for potential matches, and a match can lead to a placeholder image, an interruption or termination, or other action. A licence does not necessarily mean the rights holder has added your channel to a Content ID allowlist. Review YouTube’s guidance on copyright issues with live streams and confirm permissions for the specific works and channel; no general workflow can determine which permissions cover your materials.
Prepare the channel, files and timing
Check channel eligibility before you plan the service around a live broadcast. YouTube’s current help guidance says a channel must be verified and must not have had live-streaming restrictions in the previous 90 days. First-time activation can take up to 24 hours, so enable the feature well ahead of the event rather than discovering the delay on the day. The YouTube live-streaming eligibility page is the place to confirm current requirements.
Put the final versions of the recordings in a location that will remain available while OBS is running. Avoid moving or renaming files after adding them to a source: OBS may no longer find a file at its previous path. Use clear filenames, such as 01-opening-reading.mp4 and 02-evening-reading.mp4, so the playlist order can be checked at a glance. Keep an untouched copy of the originals elsewhere; your broadcast setup should not be the only copy.
Test with the same content and connection you intend to use. A still title card is not a complete test if the actual broadcast includes spoken audio or changing video. Listen for clipped beginnings, silence at the end, unexpected gaps and audio that is too low or too high. If you plan to show a static image alongside audio, verify that the image stays visible for the whole recording and that OBS is not also sending an unwanted desktop or camera source.
YouTube recommends preparing the encoder at least two hours before a stream and starting it at least 15 minutes before the scheduled event. Treat these as planning recommendations, not a guarantee that a broadcast will connect. Set aside time for a private or unlisted test where practical, and confirm who will watch the preview and who will monitor the computer during the service.
Set up an OBS scene
In OBS, create or select a scene specifically for the Advent broadcast. A scene is the composition OBS sends to the encoder; for this workflow it might contain the reading video, a church name or a simple background. Give the scene a recognisable name, such as Advent readings, so you can confirm the right output is active before connecting.
Add the source that matches your chosen format. For one file, add a Media Source. For several files, add VLC Video only after VLC is installed on the same computer. The VLC Video source depends on VLC being present; installing OBS alone does not make that source available. If you do not want to install VLC, make one combined recording in advance or use another workflow you have tested rather than expecting the VLC playlist control to appear.
Set the video dimensions and position deliberately. If the source does not fill the canvas, decide whether a border, background or crop is appropriate instead of stretching text or faces out of proportion. View the scene in OBS at the same size you expect to send to YouTube. Check that reading text remains legible on a phone-sized screen, particularly if the recording includes a page of text or captions near the edges.
Keep the scene simple. A camera, capture card or hardware encoder is not required simply to play an existing recording. Extra sources can be useful if you intend to show a speaker or a live welcome, but each additional source creates another item to test and another possibility of covering the recording accidentally. Lock sources once their position is right, and keep the intended playback source above background elements in the source order.
Loop a single file with Media Source
For a single recording, add a Media Source from the Sources panel and browse to the local video file. OBS supports common formats including MP4, TS, MOV, FLV, MKV, AVI, GIF and WebM; use a format you have tested rather than converting simply because another format is available. The OBS Project’s Media Sources documentation describes the source controls.
In the Media Source properties, turn on Loop. This setting makes the file replay after playback completes. It is separate from playlist looping: Media Source handles the one selected file, while a VLC Video source can repeat a list. Start playback in OBS and watch it reach the end during rehearsal. Confirm that it returns to the beginning, that the first frame appears as expected, and that the audio restarts cleanly.
The Restart playback when source becomes active option can be useful if the source is hidden and shown again, but be conscious of what it does in your scene. If you switch scenes during a service, reactivating a source with restart enabled may take the recording back to its beginning. For a continuous reading broadcast, avoid unnecessary scene changes and test the precise behaviour before going live.
Do not infer that a file is looping correctly because the preview shows a frame. Let the clip finish once in the rehearsal, or use a short test copy with the same source settings. Check that OBS audio meters move during speech and that the playback device is audible. If the source is silent, confirm that audio is enabled for it in OBS and that the correct monitoring or output path is selected; a visible picture does not prove that YouTube is receiving sound.
Loop several readings with VLC Video
When separate readings need to play in sequence, add a VLC Video source and add the files to its playlist in the intended order. This source is available only when VLC is installed; if OBS does not offer VLC Video, install VLC and restart or reopen OBS, then check again. VLC installation is a requirement for this source, not an optional way of describing an OBS-only feature.
Inspect the playlist before broadcast. Check filenames and order against the service plan, remove duplicate entries, and make sure an unintended test file has not been left at the beginning or end. OBS documents Loop Playlist as on by default and Shuffle Playlist as off by default, but inspect the actual source properties rather than relying on remembered defaults. For a church service, shuffle is usually not the desired order; leave it off unless you have a specific reason to randomise the readings.
The distinction is practical: Media Source repeats one file, whereas VLC Video advances through playlist entries and can repeat the playlist. If you need one uninterrupted combined recording, Media Source avoids maintaining a list. If each reading must remain a separate file or you expect to update one item without remaking the whole recording, a playlist may be easier to manage, with the added VLC installation and playlist-checking steps.
Play the sequence through at least one transition. Verify that the first item starts where intended, the next file follows, and the last item returns to the first in the expected way. Some files may have different dimensions, frame rates, audio levels or periods of silence. That variation will be visible or audible in the outgoing scene unless you correct it in the source files or account for it in the scene design.
Connect OBS to YouTube Live Control Room
In YouTube Studio, open Live Control Room and create a new encoder stream or select the stream prepared for the service. YouTube provides a stream URL and a stream key for the encoder. In OBS, open Settings, choose the Stream section, select YouTube as the service where available, and enter the connection details using the method shown by your version of OBS. The YouTube encoder setup instructions explain the current process.
The stream key is password-like: someone who has it may be able to send a broadcast to your channel. Do not put it in a public document, send it in a group chat, include it in a screenshot, or leave it visible during a screen share. If another person needs to operate the stream, use a secure handover and remove access when it is no longer needed. For another practical view of credential exposure, see how to keep a YouTube stream key out of command history.
Choose the encrypted RTMPS connection where it is offered. Keep the stream key out of notes or scripts that may be shared, and do not paste it into unrelated tools. If you believe it has been exposed, reset it in YouTube Studio and update OBS with the replacement before the event. YouTube’s streaming tips also cover encoder preparation and network considerations.
Once the service and credentials are set, use OBS’s start-streaming control to send the output. Starting the encoder is not the same as confirming the public event is ready: keep Live Control Room open and check its connection status and preview before treating the setup as complete. The stream’s public visibility, scheduled start and any audience-facing details should be checked in YouTube Studio as well.
Check the preview and protect the stream
Wait for the Live Control Room preview to appear and inspect both picture and sound. Look for the correct scene, readable text, the right reading, visible movement if expected, and a clean audio level. Listen from another device if possible, because monitoring the OBS computer alone may not reveal what the audience receives. Check the channel or watch page from a separate device or account when appropriate, including a mobile device.
Use the stream health indicators and listen while the broadcast is live. A healthy preview at the start cannot promise that a network, computer or platform will remain available throughout. YouTube recommends leaving around 20% of upload bandwidth available above the total stream bitrate. Measure or test the outbound connection rather than relying on download speed, and account for other people or devices using the same connection. The upload-speed guide for live streaming explains why available upload capacity matters more than a headline download figure.
If you see buffering or a health warning, check the upload connection and whether other traffic is competing for it. Do not make repeated changes to bitrate, resolution and encoder settings at once; change one item, observe the result, and make sure the replacement setting remains within YouTube’s current guidance. For a specific warning, the article on diagnosing a YouTube bitrate warning on a Hindi news playlist offers a related troubleshooting method.
Plan what the operator should do if OBS stops, the computer sleeps, or the connection drops. Disable sleep and automatic restarts that would interrupt the scheduled session where appropriate, keep the computer powered, and have a person available to respond. A looping file does not itself protect the encoder or internet connection. Likewise, a YouTube archive should not be treated as guaranteed: YouTube’s encoder guidance describes automatic archiving for streams under 12 hours. For a longer continuous broadcast, confirm current YouTube handling or plan a shorter session rather than assuming an archive will be available.
Make the broadcast manageable overnight
A church may schedule readings for a long period, but a longer broadcast also lengthens the time during which someone may need to respond to a problem. Decide who has access to the YouTube channel, who can see the OBS computer, and how they will contact one another if the picture freezes or sound disappears. Keep the run sheet close to the operator, including the planned end time and the order of readings.
If a single workstation must stay on, test power, network and audio behaviour under the same conditions expected during the event. Prevent the operating system from sleeping, and avoid relying on a laptop lid being left open or a display setting you have not tested. Do not assume a restart will restore the right scene and connection without checking it. The simplest rehearsal is to run the actual OBS scene, connect to a private test stream, and let it continue long enough to observe a file boundary or playlist transition.
For a church that does not want its own computer to stay on for an always-on file-based broadcast, StreamNeo removes that specific need: you upload the recording once, connect your YouTube stream key, and the cloud broadcast can run with your computer switched off. You still need to check that the recording and channel are ready, and YouTube remains the destination; this does not change rights responsibilities or promise uninterrupted playback.
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 OBS loop a recording without VLC?
Yes. OBS Media Source can loop one local file without VLC installed. VLC is needed for the VLC Video source when you want to play a playlist of separate files.
Does YouTube loop the recording for me?
In this workflow, OBS plays and loops the file or playlist, then sends the resulting video to YouTube as an encoder stream. YouTube is not selecting the next reading from your local files, so keep OBS running and check the Live Control Room preview.
Can I assume YouTube will save the whole broadcast?
No. YouTube’s encoder setup guidance describes automatic archiving for streams under 12 hours, but that is not a guarantee that every broadcast or archive will be uninterrupted or available. Confirm the current platform guidance, particularly if the planned stream is longer.
What should I check before the service starts?
Confirm channel eligibility, rights, file order, loop behaviour, audio, stream key and upload capacity. Start OBS early enough to check the Live Control Room preview and the stream health indicators before the scheduled time.