To repeat a prerecorded church service in a YouTube Live broadcast, add the local recording to an OBS scene as a Media Source and enable Loop in its properties. OBS repeats the file in the encoder feed; YouTube’s watch-page Loop control only changes playback for the individual viewer and does not create or repeat a live broadcast.
This guide covers the local recording, OBS setup and YouTube Live connection. Before you schedule the broadcast, also check that your channel can livestream, that the recording is suitable for repeated playback, and that the people responsible for the service have confirmed the necessary rights.
Choose the right kind of church-service loop
For one service recording, an OBS Media Source is the direct route: point it at the file on the computer running OBS, then tell that source to loop. When playback reaches the end, OBS starts it again. The video feed sent to YouTube therefore contains repeated copies of the recording, rather than a single video that viewers must replay themselves. OBS describes the setting in its Media Sources documentation.
A single-file loop makes sense when you want the same sermon, worship service or recorded prayer programme to repeat in the same order. It does not add new material between repetitions, so think about how the transitions will feel to someone who joins partway through. If the opening greeting or closing prayer is abrupt at the cut, viewers will encounter that moment repeatedly.
If you want to rotate several recordings, that is a playlist task rather than a single-file loop. OBS documents a VLC Video source and a Loop Playlist setting; that workflow requires VLC installed, with the appropriate 64-bit version for 64-bit OBS. A playlist gives you more variety, but adds another component to verify and makes the order of files part of the broadcast plan.
| Need | OBS approach | What to check |
|---|---|---|
| Repeat one service recording | Media Source with Loop enabled | File path, playback and the transition at the end |
| Cycle through several recordings | VLC Video source with Loop Playlist | VLC installation, playlist order and each file’s audio |
Do not assume a particular purchase is necessary for the loop described here. The documented OBS workflow is a software setting. YouTube’s encoder directory includes hardware workflows for scheduled prerecorded streaming, but that does not establish that a listed device repeats a file. Choose based on the workflow you actually need, rather than treating a hardware encoder as a requirement for this setup.
A related bhajan playlist setup using PRISM Live Studio may help if your material is a sequence of devotional tracks rather than one church-service recording. The principles differ: a playlist needs deliberate ordering and transitions, while this guide focuses on making one local file repeat in OBS.
Add the recording as an OBS Media Source
First, keep the recording in a stable location on the computer that will run OBS. Avoid moving or renaming it after you have selected it as a source. If OBS can no longer find the file, the scene cannot play the intended recording. A dedicated folder makes the file easier to identify and reduces the chance that an operator selects an older edit with a similar name.
Open OBS and select the scene that will carry the service. In the Sources panel, add a Media Source, give it a clear name such as “Sunday service recording”, and choose the local video file. Source names are useful when a scene has several elements: a title card, a logo, a camera or a separate audio source. A clear name reduces the chance of changing the wrong item during a service.
OBS lists common video formats such as MP4, TS, MOV, FLV, MKV, AVI, GIF and WebM in its documentation. A listed format is not a guarantee that every particular file will play correctly: codecs and file condition matter too. Load the recording and let it play in the OBS preview before building the rest of the scene around it. If the picture appears but the sound does not, check the source’s audio behaviour and the OBS mixer before proceeding.
Check how the video fits the scene canvas. A recording made in a different aspect ratio can leave empty space or crop important parts of the picture if you stretch it. In the preview, inspect faces, subtitles, lyrics and any text at the edges. Prefer a layout that preserves the recording’s proportions; if you add a background or logo, ensure that it does not cover captions or service details.
Listen to the recording through OBS as well as through a normal media player. Confirm that speech and music are audible and that the mixer responds when the file plays. A clean local playback does not by itself confirm that the outgoing stream will contain sound, so the later test should include listening to YouTube’s preview or a private test broadcast.
If the recording is large, loading it once before the scheduled service gives you time to notice a slow start or decoding problem. Keep the file available throughout the broadcast; this is not a workflow in which OBS uploads a copy to YouTube and then becomes unnecessary. The computer running OBS must continue sending the live feed for the broadcast to continue.
Enable Loop in source properties
Select the Media Source, open its properties and enable Loop. In OBS, the setting is off by default. The wording and position of controls can change between software versions, so if your interface differs, use OBS’s current Media Sources guidance rather than relying on an old screenshot. The essential check is that Loop is enabled for the source playing the service file, not merely that the scene remains selected.
Test the end of the recording before going live. If the file is short enough, play it through; for a longer service, inspect the closing and opening sections and carry out a full repeat test in a private or otherwise suitable rehearsal. Verify that the first frames appear again and that the sound restarts cleanly. A still image at the end, a blank interval or a jarring change in loudness can be easy to miss if you only test the beginning.
Looping does not edit the file. If the recording ends with a long silence, OBS will repeat that silence along with the rest of the programme. If the last line is followed immediately by the opening greeting, that abrupt restart will recur. Make an edited version if you need a smoother hand-off, then select that finished file in the Media Source and test it again.
The loop also does not correct a source that fails to play. A file can be moved, become unavailable, or fail to decode; Loop only tells OBS what to do after successful playback reaches the end. Keep the scene simple enough that you can tell at a glance whether the media source is active and whether the mixer is receiving audio.
For multiple recordings, use the documented VLC playlist route rather than adding several independent sources and hoping they advance in the intended order. Check the playlist sequence and whether its own loop option is enabled. OBS notes that VLC must be installed for the VLC Video source to be available, and that 64-bit OBS requires 64-bit VLC. If installing or maintaining VLC is not suitable for your operator, a single Media Source is the less involved choice.
Connect OBS to YouTube with the stream URL and key
Before connecting the encoder, confirm that the channel is eligible to livestream. YouTube says the channel must be verified and must not have had live-streaming restrictions during the previous 90 days. Its getting started with live streaming guidance explains current eligibility requirements. Check the official page for the channel you will use, because account status and interface details can change.
In YouTube Studio, create or open the intended live stream and locate its connection details. In OBS, select YouTube as the streaming service or configure the connection with the stream URL and stream key supplied by YouTube Studio. The exact labels depend on the selected service and interface version, but the key point is that OBS must send the encoder feed to the correct live event.
Treat the stream key as a password. YouTube explains that stream keys identify and connect an encoder to a stream; anyone with access to the key may be able to send a feed to that destination. Do not share it in a public message, screenshot, document or recording. If you believe it has been exposed, reset it through YouTube Studio and update OBS with the replacement. See YouTube’s live stream settings guidance.
A stream key and a broadcast schedule are separate things. Selecting a key does not, by itself, mean the correct title, audience setting, start time or visibility is in place. Check the live event you intend to use before starting the encoder. For a church broadcast, ensure the people managing the channel know whether the event should be public, unlisted or private, and who is authorised to start and end it.
Keep the computer and its network connection running for the full broadcast. OBS is producing and sending the feed locally; enabling Loop does not turn the setup into an unattended cloud stream. If the computer sleeps, OBS closes, or the connection is interrupted, the live feed can stop or be affected. For a service that must continue without someone present at the computer, plan how it will be monitored and restarted rather than assuming the source loop alone handles that responsibility.
A separate guide to testing a YouTube stream key from an Ubuntu VPS covers a different operating environment. It can help you think through connection checks, but it does not replace confirming the OBS scene and local file on the machine you will actually use.
Check the Live Control Room preview
Start the encoder early enough to inspect YouTube Studio’s Live Control Room preview before the intended public start. YouTube’s live streaming tips recommend preparing ahead and checking the stream. The research guidance gives a practical schedule: set up at least two hours before the event and start the encoder at least 15 minutes beforehand. Treat those as YouTube’s published recommendations, not as a guarantee that every issue will be found in that time.
Look at the preview for the expected picture, framing and motion. Then listen for speech, music and any unexpected noise. If the picture is present but audio is missing, check OBS’s mixer and the source audio configuration; if the preview is wrong, verify the selected scene and the file path. Correct problems in OBS and allow the preview to update before you make the event public.
Check that the event details are right: title, description, visibility, audience and schedule. These settings are independent of whether the loop works. A perfectly repeating file can still appear under the wrong event or be visible to the wrong audience if those choices are not checked.
YouTube recommends verifying access from the channel and watch pages and on mobile as part of preparation. Where practical, ask another person to confirm the viewer experience on a separate device or connection. Confirm that they can open the intended page and hear the same programme. This catches issues that may not be obvious from the encoder preview alone, including a viewer opening an old event link.
Plan what the stream should do when the service recording ends. With Loop enabled, it should begin again in the live feed, but viewers may join at any point in the service. Decide whether that is appropriate for your congregation and channel; add an opening slate or explanatory text if it helps viewers understand that the service is recorded and repeating. Do not imply that the live stream is a new service happening in real time if it is a replay.
For a long-running broadcast, do not mistake DVR for an archive plan. YouTube says DVR can let viewers pause, rewind and resume during a live stream, but may be limited or unavailable on streams longer than 12 hours. Viewers cannot seek back to before the stream began. Check YouTube’s DVR guidance for the current behaviour, and keep a local copy of the source recording if you need one. DVR settings do not establish that a complete archive will be available immediately.
Distinguish encoder looping from viewer playback looping
The word “loop” refers to two different actions here. In OBS, Loop is a property of the Media Source: it repeats the local file in the feed being sent to YouTube. On YouTube’s watch page, a viewer can use the Loop command to repeat playback for themselves. That viewer-side control does not create a live broadcast, restart your encoder, or make the recording repeat for everyone watching.
This distinction matters when someone asks you to “put the service on loop”. If they mean a channel that continues to show the recording as a live stream, enable Loop on the OBS source before sending the feed. If they mean a viewer wants to replay a video on their own device, the watch-page control is relevant only when that viewer is watching a video or playlist that supports it. Neither action substitutes for the other.
The YouTube Help page on looping videos or playlists documents the viewer playback control. Keep this explanation simple when answering viewers: the broadcast operator controls the outgoing feed in OBS; each viewer controls their own playback separately. Do not promise that a viewer setting affects the channel’s live output.
For a related, but different, production method, see sending a devotional video loop over RTMP with FFmpeg. That article concerns a command-line encoder workflow. If you are following this guide, stay with the OBS Media Source and verify the scene you configured rather than mixing steps from a different encoder.
Test the recording and broadcast before going live
Use a rehearsal to check the whole path, not only whether the file opens. Start the OBS scene, confirm that the Media Source plays, then confirm that the Live Control Room receives the picture and sound. Check the watch page as a viewer would see it, preferably on a second device. YouTube also advises checking the local archive files as part of preparation; keep your own recording and confirm that it is usable if you need to retain the service.
Watch a transition from the end of the recording back to the start. Confirm that the OBS preview returns to the first frame and that the sound continues as expected. If you cannot wait through an entire long service during rehearsal, test a representative segment and inspect the end and beginning carefully, then make sure the actual broadcast is monitored when it reaches the transition.
Make a short written handover for whoever may operate the stream: which scene to select, which live event to use, where the source file is stored, and whom to contact if the feed fails. Do not include the stream key in an openly shared checklist. A second operator should know how to identify a missing picture or silent feed without needing to guess which source to change.
If a service is intended to repeat unattended, decide how a person will check it during the broadcast and what they should do if OBS or the connection stops. A loop setting is not a monitoring plan. A local OBS workflow depends on the computer, the file and the network remaining available; there is no universal configuration that makes every local system run unattended for an arbitrary duration.
If keeping a computer awake and watching a local encoder is the specific burden you are trying to remove, StreamNeo can take an uploaded video and run it as a YouTube Live stream without leaving your own computer on. It is YouTube-only, so it is not a replacement for the OBS instructions above when you need a locally controlled scene or a live camera alongside the recording.
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 YouTube’s Loop button repeat my live service for everyone?
No. The watch-page Loop control changes playback for the individual viewer; it does not create a live broadcast or repeat the recording for all viewers. To repeat the file in the outgoing live feed, enable Loop on its OBS Media Source.
Can OBS loop more than one church recording?
Yes, OBS documents a VLC Video source with a Loop Playlist setting for a sequence of files. VLC must be installed, and the VLC architecture must match OBS as described in OBS’s documentation. Test the order and audio of each item before using the playlist in a live service.
Does Loop mean the broadcast will keep running if I leave the computer?
No. Loop repeats a file while OBS is playing and sending it; the computer and network still need to run, and the stream needs monitoring. Decide who will respond if the encoder or connection stops.
What should we check about rights before rebroadcasting a service?
YouTube’s livestream terms place responsibility for necessary rights on the provider, including music licensing rights. Confirm that the church has permissions for the recording’s music and other content to be rebroadcast to the intended audience and territory, and check YouTube’s current official terms before going live.