To keep an ended broadcast from appearing between church services, leave the YouTube broadcast live and switch your encoder output to a prepared holding scene. When the next service begins, switch back to the camera or programme scene without ending the event.
This is an encoder workflow, not a special YouTube holding-screen feature. It keeps viewers on the same live event during the interval; if you want a separate watch page for each service, schedule another event and consider Live Redirect instead.
Why an ended broadcast appears between services
A live broadcast has an active phase and an ended state. If you end the YouTube event after the first service, viewers who open that event afterwards see that it has ended. A holding slide cannot change that state: it is a picture or video sent by your encoder as part of an event that is still live.
That distinction helps diagnose the problem. If viewers need to see something other than an ended event during the break, the first question is whether the church wants one continuous watch page or a separate page for every service. The answer determines the workflow.
For one continuous page, the encoder remains connected and sends a holding scene between services. For separate pages, you end one event and use another scheduled event for the next service. Reusing a stream key does not, by itself, turn separate events into one continuous broadcast. YouTube’s guidance on creating a live stream with an encoder covers the event and encoder workflow; it does not prescribe a church-specific intermission scene.
There is a third issue that can look similar: an old service replay remains visible on the channel after the event has ended. That is an archive-visibility question, not a between-service live image. YouTube says streams shorter than 12 hours are automatically archived, and Studio provides controls to change an archive’s visibility or delete it. Those options affect the replay after the event; they do not provide a live holding image during a break.
Keep the YouTube event live during the break
For a continuous watch page, treat the interval as a change of programme output, not as the end of the broadcast. Leave the YouTube event active, keep the encoder sending video, and put the holding scene on air. The event has not been ended; only what viewers see has changed.
This recommendation follows from YouTube’s documented encoder workflow. YouTube Help advises stopping the encoder after the event has stopped on YouTube. In the continuous-event approach, the event does not stop at the break, so you do not stop the encoder then either. This is an operational inference from the instructions, rather than a YouTube feature or a promise about how every encoder behaves.
Set expectations with the team: one event means one watch page and one continuing live session. People who join during the break see the holding material, not the previous service as a completed replay. If the service is long, decide in advance who will monitor the encoder and YouTube status, and agree what to do if the connection drops. This workflow is not a guarantee of uninterrupted delivery.
For the source material, a useful companion is this guide to looping a single video on YouTube Live with FFmpeg. It addresses a prerecorded loop, whereas the church workflow here uses a holding scene in the encoder and switches back to a live programme. The shared point is to test the media and output path before relying on it during a real broadcast.
Prepare a holding slide or loop in the encoder
Create a scene before the service rather than building one in the middle of the interval. Depending on your encoder, the scene might contain a still image, an announcement video, a camera view of the sanctuary, or a combination. YouTube’s cited pages do not define the design, length or content of a holding scene; those are production decisions for your church.
Keep the information useful and current. A slide might say that the next service will begin shortly, identify the service or language, and direct people to the church’s usual information page. Avoid text that depends on a precise start time unless someone will update it when plans change. If the break is longer than expected, a static message can become misleading.
Choose audio deliberately. Muting the holding scene is often simpler than leaving an open microphone or an unattended music source on air. If you use background audio, confirm that the church has permission to use it in a livestream and that it is routed as intended. A picture can look ready while an encoder continues sending the previous microphone feed, so test the audio transition separately from the visual one.
In an encoder with scenes, name them plainly, such as “Service” and “Between services”. Put the required image or video source in the holding scene and check its fit, crop and playback behaviour. If it is a video loop, confirm that it returns to the beginning cleanly and does not expose a desktop, editing window or end card. The controls differ between encoders, so rehearse in the software the church actually uses.
If you are using a prerecorded video rather than a still image, the guide to streaming prerecorded videos to YouTube Live from Google Drive may help with the media side. It is not a substitute for configuring the encoder scene transition. Confirm that the chosen file plays through the encoder and that the live event is receiving the intended output.
Switch from the service scene to the holding scene
Decide on a clear hand-off. At the end of the service, the operator should switch the programme output to the holding scene, verify that it appears in the encoder preview or programme monitor, and confirm that the sound is appropriate. Only then should the team clear the platform, move microphones or prepare the next service.
The exact button or transition depends on the encoder. Some setups use a scene cut, others use a transition, and a production system may route a separate output. The principle is the same: change the output being sent while leaving the YouTube event active. Do not assume that selecting a scene in a preview panel also puts it on air; check the actual programme output and, where practical, the YouTube preview.
A simple spoken hand-off can prevent mistakes. The operator might call, “Holding scene is live,” and another team member can confirm what appears on the public event. If the church works with one operator, use a checklist or an on-screen status view to reduce reliance on memory. Avoid ending the stream merely because the room has become quiet.
YouTube’s live streaming tips include checking and monitoring the stream. Apply that habit to the transition: test the holding scene before the service, then verify the public output after switching. The source does not specify a particular church scene-switch method, so the rehearsal is important.
Return to the next service without stopping the feed
Before the next service begins, check that the camera or programme source is ready, the microphones are routed correctly and the encoder is still sending the holding scene. When the service is ready to go live, switch the output back to the service scene and confirm the result. Keep the same YouTube event active throughout.
Plan for more than the picture. A camera may be framed for the first service but moved during the break; a microphone may have been muted or reassigned; a video source may still be playing. Confirm the scene and audio routing together. If another operator is responsible for sound, agree who confirms that the microphones are open before the return transition.
A short sound check can happen off air only if the production has a way to monitor it without sending that test to viewers. Otherwise, keep the holding output live until the team is ready. Make the decision explicit rather than switching to the service scene early and leaving an open microphone, an empty lectern or private conversation on the event.
The same careful hand-off applies to a recurring or long-running channel. Guides such as setting up a continuous YouTube stream with Restream on a VPS discuss continuity at a different operational level, but they do not remove the need to monitor what viewers receive. For this church workflow, a person should still check the public event and the encoder output around each transition.
When the final service is over, the situation changes. End the YouTube event and then stop the encoder in line with YouTube’s instructions. Decide separately whether the resulting replay should stay public, be unlisted or private, or be deleted. Do not use archive settings as a substitute for the between-service scene.
When to schedule a separate event and use Live Redirect
A continuous event is not right for every church. Separate scheduled events make sense when each service needs its own watch page, title, description, reminder or replay. They can also suit a programme in which one service has ended and the next is managed by a different team. The trade-off is that viewers may need to move to another page unless you use an available hand-off feature.
YouTube Live Redirect can send viewers from an ended live stream to another live stream or a Premiere, subject to YouTube’s eligibility and setup rules. YouTube’s documentation says to set up the Premiere before the live stream when using a Premiere as the destination. Read the current Live Redirect instructions before planning around it. Do not assume it will carry viewers to an arbitrary destination or work beyond the documented next live stream or Premiere use.
The choice is easier when you compare what viewers and the church need:
| Question | One event with a holding scene | Separate scheduled events and possible redirect |
|---|---|---|
| Watch page | Same page through the break | A different page for each service |
| What viewers see between services | Encoder’s holding output while the event remains live | The first event has ended; viewers may be redirected if the destination and setup qualify |
| Replay management | The event produces one archive to manage | Each event has its own archive to manage |
| Main operational task | Rehearse scene and audio changes | Schedule the next event and set up the hand-off |
Do not choose based only on the stream key. YouTube allows encoder streams to use stream keys, including reusable custom keys, but key reuse does not establish event continuity. The event setup and what viewers should experience matter more than whether the encoder can reconnect with familiar settings.
For a congregation that expects one URL to work through the whole morning, a continuous event with a prepared holding scene is usually the more direct fit. For services that need separate pages and replays, separate scheduled events may be better. Keep the archive decision separate: YouTube Studio’s controls manage completed videos, not the live scene shown during an interval.
Operational checks before the break
A dependable transition is mostly a matter of preparing for ordinary failure points. Rehearse once with the actual encoder, output path and account used for the service. Confirm that the holding media is available, that the scene can be put on air, and that the service scene can be restored without ending or restarting the YouTube event.
Use a short run sheet that names the person responsible for each check. It can sit beside the encoder or in the team’s service notes:
- Confirm that the correct YouTube event is live and that the encoder is sending to it.
- Check the holding scene in the encoder and verify both picture and audio.
- Agree the spoken hand-off and who confirms the transition on the public event.
- Before returning, verify camera framing, microphone routing and any video sources.
- At the final close, end the event, stop the encoder, then review the archive’s visibility.
If the church has a backup operator, make sure they know which scene is the holding output and how to recognise the live programme output. A rehearsed fallback can be a static image rather than a loop, provided its audio behaviour is understood. The goal is not elaborate production; it is to avoid an accidental ended event, unintended microphone audio or an empty output while the team prepares.
Network or encoder interruptions can still occur. Monitor the event rather than treating a successful rehearsal as proof that delivery will never fail. YouTube’s encoder guidance explains how to start and stop the workflow, while the scene switching itself varies by encoder. If the feed drops, follow the current YouTube and encoder status, and communicate clearly with viewers through the church’s usual channels where appropriate.
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
Should we end the YouTube stream between services?
Not if your goal is to keep the same event and watch page live through the interval. Leave the event active and switch the encoder to a prepared holding scene. End the event after the final service, unless you have chosen a separate-event workflow.
Is the holding screen a YouTube feature?
No. The holding image or loop is content your encoder sends as its output while the event remains live. YouTube’s cited help documents encoder operation and event management, not a dedicated holding-screen feature.
Can Live Redirect take viewers to the next church service?
It may be suitable when you end one event and have another live stream or a Premiere as the destination, subject to YouTube’s current setup and eligibility rules. Follow YouTube’s instructions, including setting up a Premiere before the live stream when that is the destination. Do not plan on redirects to other kinds of destinations or beyond the documented use.
How do we stop an old service replay appearing on the channel?
After the event, open the archive in YouTube Studio and change its visibility or delete it if that is what the church wants. This manages the completed replay, not the live image between services. Decide on archive settings separately from the encoder’s holding scene.