OBS can play a recorded church service from your computer and send that scene to YouTube Live. For one recording, use a looping Media Source; for several, use a VLC Video source with a playlist. In either case, the local playback and YouTube’s live event are separate parts of the chain, and both need checking.
A loop in OBS does not guarantee that YouTube will remain live indefinitely or preserve a complete replay. Prepare the files, test the full path before announcing the event, and decide how you will handle interruptions and archiving.
Prepare the service recordings
Put the recordings you intend to use in a stable folder on the computer that will run OBS. Check that every file opens and plays from beginning to end, including its audio. If you are using a removable drive, confirm that it remains connected and does not go to sleep or get unplugged during the broadcast. A broken path or an unreadable file can stop local playback even while OBS itself remains open.
Choose whether the broadcast should repeat a single service or move through a sequence. For a single recording, make a note of its exact filename and location. For a sequence, settle the order beforehand and give files names that make that order clear. Avoid changing folders or renaming files after setting up OBS; if a source loses its file path, you will need to select the file again.
The OBS Project documents Media Source support for common video formats, including MP4, MOV, MKV and WebM. Compatibility can still depend on how a particular file was encoded, so do not infer that a file will play correctly from its extension alone. Check the actual recording in OBS and listen for the start, middle and end of the audio. See the OBS guide to media sources for its supported source types and options.
If the service includes music, readings, slides or other material created by someone else, check the rights needed for rebroadcast before going live. A church’s original recording does not automatically grant permission to retransmit every element in it. YouTube says it scans live streams for third-party content and may interrupt or terminate a stream if a match remains. Its copyright guidance for live streams explains the issue; its terms for live streaming place responsibility for necessary rights on the content provider. A licence may not prevent an interruption if the relevant rights owner has not allowlisted the channel through Content ID, so check the current YouTube guidance and address any rights questions before scheduling a public broadcast.
Create the YouTube Live event
In YouTube Studio, create or schedule a live event and choose the encoder workflow. That creates the YouTube side of the connection: the event, watch page and receiving endpoint. OBS supplies the encoded picture and sound, but creating a scene in OBS does not itself create a public live event.
Follow YouTube’s current encoder setup instructions to configure the event. Give it a useful title, description and visibility setting, then verify the schedule and intended audience in Studio. If the channel has not previously enabled live streaming, activation may take time; do not leave that check until the service is due to begin. The guide to live-stream activation is useful if you need to plan around channel eligibility and setup.
Keep the event details and OBS scene aligned. If you schedule a Sunday service but OBS is playing a different recording, viewers may see content that does not match the event description. Likewise, if you create multiple test events, identify the one you will use and confirm its status in Studio before copying connection details.
Add a Media Source for one service
Open the OBS scene that will carry the service. In the Sources panel, add a Media Source, give it a recognisable name such as “Sunday service recording”, and select the local video file. Make sure the source is visible in the active scene and positioned and sized as intended. A source can be present in the scene but hidden behind another source or cropped in a way that makes the picture appear missing.
Enable the Media Source’s Loop option if you want the same file to start again after it finishes. The loop applies to local playback in OBS; it does not create or control the YouTube event. Test the ending and restart of the file before streaming. Watch for a brief black frame, a pause, a change in sound level or a mismatch between picture and audio at the join. Whether those transitions are acceptable depends on the recording and how it was edited.
Do not rely on a filename or thumbnail as your verification. Use OBS’s preview and play through the actual source. Confirm that the opening frame is appropriate for viewers who join partway through the broadcast and that any title cards or announcements are still relevant. If the recording contains a personal prayer request or other content not meant for an extended public rebroadcast, remove or replace it before building the loop.
Build a playlist for multiple services
For several recordings in sequence, add a VLC Video source in the scene and use its playlist controls to add the files in the intended order. OBS’s VLC source depends on VLC being installed on the same computer. OBS notes that a 64-bit version of OBS needs 64-bit VLC; if the source is unavailable or does not play, check that dependency before troubleshooting the YouTube connection.
Arrange the playlist deliberately. Think about whether a viewer should hear a welcome or an announcement at the start, whether one service should follow another directly, and whether the sequence should feel coherent after it wraps around. Add only files that have been checked for picture, sound and permissions. If you need different artwork or a short transition between recordings, test it as part of the scene rather than assuming the playlist will supply it.
A playlist is different from one long combined recording: it moves among the individual files, and the source’s playlist behaviour governs what happens at the end. The VLC source has a Loop Playlist option; enable it if you want the sequence to start again after its final item. Make sure the playlist itself is visible and active in the live scene. OBS documents the VLC source and its settings in the same media sources reference.
For a more detailed comparison of playlist automation choices, see how to automate a YouTube Live playlist with OBS. That guide is about the playback workflow; here, the essential check is that every item in the selected playlist is actually available to OBS on the broadcast computer.
Enable looping and verify scene behaviour
Loop settings describe what the media source should do at the end of playback. For one file, check Loop on the Media Source. For a series, check Loop Playlist on the VLC Video source. Do not assume the option is enabled simply because the source begins playing. Confirm the setting in the source properties and perform a test long enough to see how the file or playlist ends and starts again.
Source visibility matters, particularly with VLC Video. If you hide a source by switching scenes or toggling its visibility, playback may pause or behave differently from what you expect when you bring it back. Keep the playback source in the active scene for the test and watch what happens when you change scenes, if scene changes are part of your plan. A simple single-scene setup is easier to check when you only need a fixed recorded service.
Also check the rest of the scene. If you have added a logo, lower-third or holding slide, make sure it does not cover the service picture or obscure subtitles. If the audio is duplicated by another source, remove the duplicate; two copies of the same sound can create echo. Use the OBS audio meters while the service plays, then listen from the YouTube preview on a separate device if possible. The output heard locally is not a substitute for checking what YouTube receives.
A useful way to think about troubleshooting is to separate the chain into two questions: is the intended recording playing correctly in OBS, and is OBS successfully sending that scene to the right YouTube event? If local playback fails, inspect the file, source and playlist. If OBS looks right but YouTube shows no incoming feed, check the encoder connection and event instead. That separation saves time when a late-night test fails.
Enter YouTube’s stream URL and key
In YouTube Studio’s encoder settings for the event, find the stream URL and stream key. In OBS, open the streaming settings and choose the appropriate service or custom connection method, then enter the URL and key as YouTube’s instructions specify. The URL identifies where the feed is sent; the key associates it with the event. Keep the key private, because it is a credential that allows an encoder to send video to your channel.
Copy the values carefully, without adding spaces or substituting details from another event. If you create a fresh key or select a different event, update the OBS settings accordingly. YouTube explains the connection in its stream settings help. Treat the event and key as a pair: a correctly configured local scene can still be sent to the wrong event if you have copied an old key.
Use a connection and output profile suitable for the computer and internet connection you actually have. YouTube’s encoder guidance recommends RTMPS for secure ingestion and lists H.264, constant bitrate encoding and a recommended two-second keyframe interval, with a four-second maximum. These are encoder recommendations, not a promise that a particular resolution or bitrate will work on every church connection. Choose output quality based on the upload capacity available at the venue, leaving headroom for normal variation rather than consuming the whole connection.
If you need a settings walkthrough focused on a long-running event, use the OBS settings guide for a YouTube replay stream alongside YouTube’s current encoder settings page. Confirm the settings against the current official page before the event, since interface labels and recommendations can change.
Preview, start and monitor the live feed
Before the public broadcast, test the whole path with representative video and audio. Start the OBS stream output, then open the event in YouTube Studio’s Live Control Room. Wait for the incoming feed and inspect the YouTube preview, not only the OBS canvas. Confirm that the event is the right one, the picture is framed correctly, sound is audible, and the preview shows the content you intend viewers to receive.
YouTube advises starting the encoder ahead of an event, previewing before going live and monitoring stream health. Use its live streaming tips and encoder settings guidance as the current reference. When the preview is satisfactory, use the control in Live Control Room to start the event if that is required by the workflow shown for your event. Starting the encoder in OBS and making the event live in YouTube are distinct actions; check the status shown in Studio rather than assuming one action completed both.
During the broadcast, keep an eye on OBS’s connection indicators and YouTube’s stream health. If the feed drops, determine whether the source stopped, OBS lost its connection, the computer or internet connection failed, or YouTube flagged an issue. A loop only restarts media playback at the file’s end. It cannot restart a computer, repair a network outage or guarantee that YouTube keeps the event live indefinitely. If you cannot monitor the computer throughout, plan for who will respond and how they will check the channel.
For a local workflow, OBS must remain running on the computer, and the computer must stay powered and connected. This is a practical trade-off for using local files and local controls. If keeping a computer on through the night is the specific problem, StreamNeo removes that particular burden by running the uploaded recording as a YouTube live stream without your computer switched on; you still need to check the channel, content rights and the live event itself.
Plan for the replay and interruptions
A continuous broadcast and a saved replay are different outcomes. YouTube’s archive guidance says that streams under twelve hours can be automatically archived, while a stream exceeding twelve hours may not be captured at all. The guidance is not a guarantee of a complete archive, even for a shorter event. If preserving a service matters, make a local recording or another appropriate backup and check the resulting file rather than depending on the live stream alone.
For a replay that must be available on the channel, consider ending and restarting the live event within YouTube’s stated archive window, while accounting for the interruption this creates for viewers. See YouTube’s archive guidance before deciding how to handle a long broadcast; its warning is that a stream over the stated duration may not be captured. This is a planning constraint, not a reason to promise that a restart will produce a complete saved replay.
You should also decide what viewers will see if the media file ends unexpectedly or the connection fails. A simple slate with a contact or service schedule may be more appropriate than a frozen frame, but it only helps if the computer and stream remain available to show it. Write down the practical recovery steps: check OBS playback, verify the connection and event status in Studio, and resume only when you know which part failed. A tested plan is more useful than assuming the loop will take care of every failure.
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 single recorded church service?
Yes. Add the file as a Media Source, select it, and enable Loop in its properties. Test the restart in OBS and then check the YouTube preview, because successful local playback does not prove that the live event is receiving it.
How do I play several services one after another?
Use a VLC Video source, add the recordings to its playlist in the order you want, and enable Loop Playlist if the sequence should repeat. VLC must be installed, and OBS notes that 64-bit OBS needs 64-bit VLC. Check that the source stays visible in the active scene and that each file plays correctly.
Does looping in OBS keep YouTube live indefinitely?
No. Looping controls the local media source, not the computer, network connection or YouTube event. Monitor the feed where practical and plan how someone will respond if playback or the connection stops.
Will YouTube save the replay of a continuous stream?
Do not rely on an automatic archive for a very long broadcast. YouTube says a stream over twelve hours may not be captured at all, and even an eligible stream is not a guarantee of a complete replay. If the archive matters, record locally as a backup and check YouTube’s current archive guidance.