Prepare the hymn files in OBS, set the media source to loop, and connect OBS to YouTube Live Control Room with the stream URL and key. Then check the preview, audio, and stream health before you publish the broadcast.
The technical loop is only one part of the job. You also need permission for the hymn compositions and for the particular recordings you plan to play, and YouTube may interrupt a live stream after detecting third-party content even when you believe the use is licensed.
Prepare the hymn playlist in OBS
Start with the actual files you intend to broadcast. These might be recordings made by the church, authorised backing tracks, or other files for which the church has the necessary permission. Do not build the stream around a playlist first and investigate its rights later. The source files determine what permissions need checking.
OBS documents local media sources that can use formats including MP3, AAC, OGG, WAV, MP4, MOV, MKV, and WebM. The exact file type matters less than whether OBS can open it reliably and whether the church is permitted to stream it. You can check the current OBS Media Sources documentation if the installed interface differs from the labels used here.
Open OBS and create a scene for the hymn broadcast. Give it a clear name such as Hymns - overnight. A simple scene may contain a still image, a church logo, and the hymn media. If you add lyrics, artwork, photographs, or video, check those elements separately. Permission to play a recording does not automatically clear every image or lyric display placed around it.
For a single long file, add one Media Source. For separate hymn files, you can either make a combined file before importing it or use OBS's VLC Video Source and its playlist controls. The VLC option depends on VLC being installed and available to OBS. If that source is missing, install or repair VLC before testing the broadcast rather than discovering the problem when the stream is due to start.
The choice between one combined file and a playlist is mostly operational. A single file can be simpler to inspect, while separate files make it easier to replace one hymn or change the order. A playlist also gives you a clearer way to see which item is playing, but it introduces more points to check, including file paths and transitions.
Keep the media in a stable local folder. Avoid building the scene from files on a removable drive, a phone, or a synchronised folder that may change while OBS is running. If the computer restarts, the same paths should still exist when OBS opens again.
For a wider comparison of software approaches, see this guide to OBS versus FFmpeg for a 24/7 YouTube radio station. OBS is useful here because its interface exposes the source and playlist behaviour, which makes it practical for a church team that needs to inspect the setup rather than maintain a command by hand.
Enable Loop on the local Media Source
Right-click the Media Source in the Sources panel and open its properties. Turn on the Loop option for a single file. When the file reaches its end, OBS starts it again rather than leaving the source finished.
If you are using a VLC Video Source, add the hymn files to its playlist and enable the playlist loop option. OBS describes this source as able to restart its media after the playlist finishes. Save the source and watch it through at least one complete transition before treating the setup as ready.
A loop is performed by OBS before YouTube receives the broadcast. YouTube is not repeatedly opening your individual files. It receives the continuous output from OBS, so the computer running OBS must remain available for as long as the channel is intended to run.
Test the end of a file deliberately. Listen for a gap, click, sudden change in volume, or a black screen. A short silence may be part of the recording, but an unintended pause usually indicates a source or playlist issue. If the playlist has several files, test the transition from one item to the next, not only the return from the last hymn to the first.
Check the audio mixer in OBS while the source is playing. The meter should move when music is audible. If it does not, the file may be muted, the source may be hidden, or the audio monitoring and output settings may not be what you expected. Do not infer that YouTube will receive audio simply because the file opens on the computer.
Keep the visual layout modest if the broadcast is primarily devotional audio. A still image is easier to maintain than a scene with many animated elements. If you include a schedule, hymn title, or service information, verify that it remains accurate when the playlist repeats. A title that says “live worship” should not imply a live performance if the channel is playing a recording.
You can also review how looping prerecorded videos on YouTube Live works before choosing between a single file and a playlist. The important distinction is that the repeat behaviour must be configured in the encoder source, not assumed to be provided by the YouTube watch page.
Connect OBS to YouTube Live Control Room
In YouTube Studio, open Create and choose Go Live. Select the encoder workflow in Live Control Room. YouTube provides a stream URL and a stream key for the encoder connection. Copy those values into OBS's stream settings, taking care not to publish the key or include it in a screenshot.
The stream key works like a credential for sending a broadcast to the selected YouTube channel. Store it where the people responsible for the channel can access it, but do not paste it into a public document, church website, or shared social post. If you think it has been exposed, use YouTube's current controls to replace or reset it.
In OBS, open Settings, then Stream, choose the YouTube service if it is available, and enter the key. If your workflow asks for a custom server, use the server URL supplied by YouTube. Menu names can change between versions, so use the current YouTube encoder instructions if your account presents a different sequence. The YouTube Help guide for encoder streams is the appropriate reference for the account-side setup.
Before pressing Start Streaming, confirm that OBS is using the scene containing the hymn source. This sounds obvious, but a church computer may have several scenes for services, announcements, cameras, and tests. Starting the wrong scene can produce a perfectly healthy stream with the wrong content.
Start the encoder and wait for the preview in Live Control Room. Depending on the account and current YouTube interface, you may need to create or schedule the live event and then tell YouTube to go live after the preview appears. Follow the prompts shown in the current control room rather than assuming that starting OBS alone publishes the event.
If the stream is meant to run overnight, write down the event title, visibility setting, start procedure, and stop procedure. Another volunteer should be able to identify which event to open and how to verify it without guessing. This simple handover note is often more useful than adding another technical feature.
Check the preview and stream status
Do not use the OBS preview alone as proof that YouTube is receiving the intended programme. Open the YouTube preview and confirm the picture, hymn audio, title, description, and visibility. If the broadcast is unlisted or private for testing, confirm that setting before the real launch.
Check four things before leaving the stream unattended:
- the current scene contains the correct media source;
- the audio meter moves and the preview contains audible music;
- the playlist advances to the next item and eventually returns to the first;
- YouTube reports that the encoder is connected and the stream is receiving data.
Use a separate device to watch the public or test playback when practical. A phone on mobile data can reveal problems that are hidden on the same computer, such as a missing audio track or an incorrect visibility setting. Keep the test short if the material is not yet cleared for public broadcast, but make it long enough to observe a transition.
Watch the dashboard for warnings rather than dismissing them because the picture looks normal. YouTube may show copyright or stream-health notices separately from the basic connection status. Record the wording and time of a warning so the person handling permissions can investigate the relevant hymn or recording.
The computer and network still matter in a local OBS setup. The playlist can be perfectly configured and still stop if the computer sleeps, the application closes, the operating system restarts, or the connection fails. Disable sleep for the intended operating period, apply updates outside the broadcast window, and make sure someone knows how to inspect the machine if the stream stops.
If one file fails during a playlist, the behaviour may depend on the source and its settings. Test missing-file and end-of-file cases before relying on the stream overnight. The guide on keeping a YouTube playlist streaming when one video fails covers the broader continuity problem, although it does not replace testing your particular OBS scene.
For a church that does not want to keep a local computer running, StreamNeo removes the need to leave OBS open overnight by taking an uploaded video, connecting it to the church's YouTube stream key, and running the broadcast with automatic monitoring and restart. It is still the church's responsibility to confirm that the uploaded material and channel use have the necessary rights.
Confirm rights for the musical works and recordings
Treat the hymn and the recording as separate rights questions. The underlying musical work may have an author, publisher, translator, or arranger. The recording may belong to a church musician, choir, record label, worship publisher, or another rights holder. A permission to perform a hymn live does not automatically grant permission to play a commercially released recording in a YouTube broadcast.
Ask these questions for every item in the playlist:
| What you are checking | What to verify |
|---|---|
| Musical work | The hymn, arrangement, translation, and any adaptation are covered for the planned use |
| Sound recording | The church owns or has permission to use this exact recording, backing track, or multitrack |
| Visual material | Lyrics, photographs, artwork, video, and logos have the required permissions |
| Channel and territory | The permission covers online streaming, the church account, the relevant country or countries, and YouTube where required |
| Administration | The church knows whether it must report songs, display licence details, or keep records |
For churches in the United States, CCLI presents its Streaming License as covering online worship services using songs and hymns performed live by church musicians. CCLI separately describes Streaming Plus as extending to certain authorised master recordings, backing tracks, and multitracks. Those are CCLI's product descriptions, not a universal answer for every hymn, recording, country, or church arrangement. Check the current CCLI streaming licensing information and confirm the exact repertoire and terms before relying on it.
If a licence provider asks you to include licence or account details in the YouTube description, do that accurately. CCLI recommends including relevant Church Copyright License and Streaming License numbers for its covered use. The name on the licence, the covered songs, the source recordings, and the territory should match the broadcast you are planning.
Do not assume that an old service licence, a printed hymnal, a purchase receipt, or permission to use music inside the church covers an internet live stream. The same hymn can also have different issues depending on whether it is performed live, played from a church-made recording, or taken from a commercial album.
YouTube's live-stream terms place responsibility on the channel for having the necessary rights for the content it broadcasts, including relevant music rights. Read the current YouTube Terms of Service and the terms supplied by any licensing organisation before going live. This article cannot determine whether a particular church's playlist is cleared.
YouTube Creator Music is not a general solution for this workflow. YouTube's current help information says Creator Music licensing is for eligible long-form videos and does not support licensing live content. Do not select a track there on the assumption that the same permission covers a continuous hymn broadcast.
Understand content matching and possible interruptions
YouTube scans live streams for matches to third-party content. As YouTube Help states: “All live streams are scanned for matches to third-party content, including copyrighted content in the form of another live broadcast.” A match can lead to a warning, replacement with a placeholder, interruption, or termination if the relevant material remains.
This can happen even when the church believes it has obtained a licence. YouTube explains that a licensed rights holder may need to add the channel to an allowlist through its rights-management system. A licence is therefore not an automatic guarantee that an automated match will not interrupt the broadcast.
Read YouTube's current guidance on copyright issues with live streams before scheduling the event. Ask the rights holder or licensing organisation whether the church channel needs to be allowlisted, how that request is made, and what evidence the church should keep. Do not wait until the first overnight interruption to find out.
If YouTube displays a match, note the affected content and contact the relevant rights holder through the route specified by the licence. Do not simply delete a hymn from the playlist without checking whether a different recording of the same composition creates the same issue. Changing the recording may resolve one sound-recording claim while leaving the underlying composition question unchanged.
A channel can also receive a claim because another element is present in the scene. Background music in an opening video, a lyric video, a photograph with restricted use, or a recording embedded in a service announcement may be enough to create a problem. Keep an inventory of everything that OBS sends, not just the main hymn files.
There is a practical difference between a continuous stream and a continuous obligation to monitor it. Assign someone to check the YouTube dashboard during the first broadcast and after any change to the playlist. If the channel is intended to run at night, decide in advance who will receive an alert and what they are authorised to do if YouTube interrupts the stream.
The safest workflow is to separate technical readiness from rights readiness. First prove that OBS loops the files and YouTube receives them. Then confirm the permissions, channel allowlisting requirements, and description information. Only after both sides are ready should you make the broadcast public or leave it unattended.
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 repeat a church hymn playlist automatically?
Yes. A local OBS Media Source can be set to Loop, and a VLC Video Source can use playlist looping for multiple files. Test the transition and confirm that the computer remains awake, connected, and running OBS for the intended duration.
Does a church performance licence cover a recording played on YouTube Live?
Not necessarily. The musical work and the specific sound recording can involve separate rights, so check whether the permission covers live online streaming and the exact recording, arrangement, territory, and platform.
Can YouTube interrupt a stream even if the church has a music licence?
Yes. YouTube scans live streams for third-party matches, and an automated match may produce a warning or interruption. YouTube says a rights holder may need to allowlist the church channel, so ask the rights holder or licensing provider about that process.
Is Creator Music suitable for a continuous hymn live stream?
Do not treat Creator Music as a solution for this use. YouTube's current guidance says its licensing does not support live content, so confirm permissions through the relevant rights holder or licensing organisation instead.