A holding slide between prerecorded church services is an OBS scene that you send as part of one continuous YouTube Live feed. It is not YouTube’s pre-stream trailer: the trailer appears before a scheduled stream starts, while an OBS scene change happens after the broadcast is already live.
The practical workflow is to prepare a scene for each service and one for the holding slide, connect OBS to the scheduled YouTube event, and switch scenes without stopping the encoder feed. Rehearse the complete hand-off privately before using it for a service.
What a holding slide does in a continuous live feed
Think of the stream as one programme with several segments. The first prerecorded service plays from a service scene; when it finishes, you transition to a holding-slide scene; when the next service is ready, you transition to that service’s scene. Viewers remain on the same live watch page throughout. There is no need to end the event and start a new one just to display the slide.
The slide might say “The next service will begin shortly”, show the congregation’s name, or give a brief notice. Its purpose is to make the interval intentional and legible, rather than leaving viewers with a frozen final frame, a blank picture, or an unexplained pause. You choose the wording and how long to leave it on screen. OBS’s scene-transition controls do not themselves determine the interval’s length; an operator decides when to move to the next scene.
The distinction from a YouTube trailer matters. YouTube describes a trailer as content that plays on the watch page before a scheduled live stream begins. It is not a feature for inserting a holding screen between segments of a broadcast already in progress. For the event and trailer details, see YouTube’s live-stream settings guidance. Do not build an between-services plan around the trailer option.
This guide uses OBS Studio because it gives a volunteer a visible way to change scenes while the encoder remains connected. YouTube describes encoder streaming as suitable for more advanced productions and explains that an encoder sends the feed to YouTube. If your church already has a production desk and hardware encoder, the same principle applies: the programme feed must contain the service, slide and next service in sequence.
Create or select the scheduled YouTube Live event
In YouTube Studio, create or select the scheduled live event that the congregation will use. Check the event title, start time, visibility and other details before sharing its watch-page link. A scheduled event keeps the intended destination clear for the operator and gives you an opportunity to test the stream before the service begins.
Open the event’s streaming setup and locate the stream URL and stream key. YouTube Help describes stream keys as “like your YouTube stream’s password and address”. Treat the key as a credential: do not publish it in a notice, send it to a broad volunteer group, or include it in a screenshot shared publicly. If you need to pass setup details to another operator, use a private channel and limit access to people who need it.
The event destination and key are related but not interchangeable. The URL tells the encoder where to send the feed; the key identifies the stream connection. Use the values shown for the event you intend to broadcast. YouTube’s encoder setup instructions explain how the URL and key are used to connect streaming software or hardware.
Before the service day, confirm who can open the event in Studio and who can operate the computer running OBS. Keep the public watch-page address separate from the stream key. If a key has been exposed, use YouTube’s current controls to manage or replace it rather than assuming that changing the event title affects it.
Connect OBS to the event
In OBS, open the stream settings and select YouTube or the available custom RTMP option, depending on the version and connection method in use. Enter or select the URL and key associated with the scheduled event. Interface labels can change between releases, so use the current OBS interface and YouTube’s instructions rather than relying on an old screenshot.
Once connected, OBS is the encoder sending the programme feed. Keep that distinction in mind: YouTube hosts the event and receives the feed, while OBS determines what picture and sound are in that feed at a given moment. Changing the active scene in OBS changes what viewers receive, but does not create a separate YouTube event.
Do not stop the stream between the first service, holding slide and second service. The transition should be made in OBS while the same live connection continues. The same stream key should be used only for the event and workflow you have configured; if you are comparing this process with another streaming service, review the practical cautions in using a YouTube stream key with different services.
A small church may be comfortable with OBS running on a familiar computer. A church that already uses a hardware encoder may prefer to stay with its established production system, particularly if volunteers know its switching controls. The relevant question is not which category sounds more professional, but who can reliably prepare the media, see the programme output and make the transitions without interrupting the feed.
Prepare service and holding-slide scenes
Create a scene for the first service, a separate scene for the holding slide, and a scene for the next service. Name them in the order they will be used, such as “Service 1”, “Between services” and “Service 2”. Clear names reduce the risk of a volunteer choosing a similarly named source or the wrong service under pressure.
In each scene, arrange the video or image sources and any audio sources using the controls available in your installed OBS version. The exact setup depends on where the media is stored and how it is being played. The OBS documentation describes scenes and transitions, but the details for a particular media source or still-image duration can vary with the installed version and source settings. Check those controls on the actual production computer and test them rather than assuming a setting from another setup will behave the same way.
Make the slide readable on the full programme canvas. Use a short message, strong contrast and enough space around any church name or service time. A slide designed for a phone screen should still be checked on the OBS canvas and on YouTube’s preview. Avoid including a notice that will be out of date if a service starts early or runs late.
Prepare the scene sequence as an operator’s checklist, not just as a collection of graphics. For example: start on the opening service scene, move to the holding slide when the service ends, then move to the next service after the operator confirms that its video and audio are ready. A printed checklist beside the computer can be more dependable than asking a volunteer to remember an informal plan.
OBS Studio Mode can help with this work. Its interface separates the scene currently being sent live from an edit scene that you can prepare. The OBS Project’s overview guide explains that Studio Mode lets you change scenes in the background without viewers seeing the preparation. This is useful when you need to select or adjust the next scene before taking it live.
Add and check the prerecorded service source
Put each prerecorded service in the scene intended for it, using the media or playback source appropriate to the installed OBS version. Confirm that the file opens, shows the expected picture and produces sound through the output you intend to send. Do not wait until the live service to find out that a file path points to a folder on someone else’s computer or to a removable drive that is not connected.
Check the beginning and end of each recording. Confirm that the first visible frame is appropriate to show, that audio starts when expected, and that the final section does not leave an unintended blank or an awkward frozen image. If there is a long lead-in or tail, decide whether it is part of the service or whether the operator should transition to the holding slide at a planned point. The content and timing are church decisions; scene switching cannot resolve an unclear programme plan.
A file that plays correctly in a rehearsal should be available in the same location on the day of the broadcast. If you move or rename it, test again. Keep a copy of the media and graphics where the operator can find them, and avoid changing folders after you have confirmed the scene. For longer-running setups, storage performance can matter when video must be read continuously; see the checks in how to check storage speed for a 24/7 YouTube stream.
If the service video includes its own audio, check that OBS is not also sending an unintended microphone or desktop audio source. Listen to the rehearsal through the same output path that viewers will hear, not only through the computer’s local speakers. A level meter moving in OBS is useful, but it does not prove that the audience will hear balanced, intelligible sound.
Transition between the service and holding slide
Use OBS Studio Mode to prepare the holding-slide scene while the service is live. Check that the edit side shows the intended slide and that the live side still shows the service. When you are ready, select Transition. The prepared scene then becomes the live scene without ending the YouTube broadcast. Repeat the same process to prepare and take the next service scene live.
OBS offers Fade and Cut at launch, and its guide describes other available transitions, including Swipe, Slide, Fade to color and Luma Wipe. The choice is mainly presentational. A cut is direct; a fade makes the change gradual. You can adjust a transition’s duration in OBS, but do not choose a complicated effect just because it is available. A simple cut or fade is easier to rehearse and easier for a volunteer to use consistently.
The transition is not the same as the holding interval. A fade or cut controls how one scene gives way to another; the operator controls how long the holding slide remains on air by waiting before taking the next scene live. If you expect a short interval, agree who will give the cue and how it will be communicated. If the service overruns, the operator can leave the slide up until the next recording is ready rather than taking a scene with missing media.
Practise the hand-off in both directions. The operator should be able to move from the service to the slide, verify the next service in the edit view, and then take that scene live. The OBS overview also notes that a Stream Deck can be mapped to shortcuts, but a separate controller is not required for scene transitions. A keyboard and the OBS interface are sufficient for this basic workflow.
Preview, start and monitor the stream
Run a private or unlisted rehearsal before the actual service. Check the sequence from the opening service through the holding slide to the next service. Confirm that the YouTube event receives the feed, that the picture is framed correctly, that audio is present, and that the scene change is visible on the watch page. A rehearsal tests the whole chain, including the computer, files, network connection and the person operating OBS.
For the live event, open the correct scheduled event in Studio and confirm that the incoming preview shows the expected programme. Start the stream using the event’s configured workflow, then check that the event is receiving the encoder feed before the congregation is directed to watch. Keep the operator at the controls for the scene transitions; do not assume that a transition will occur merely because the next video file exists in another scene.
During the service, watch both the OBS programme output and YouTube’s stream status. Keep the stream running when changing scenes. If the picture or sound is wrong, return to a known working scene or hold the slide while you diagnose the issue; stopping the broadcast should not be the first response to a scene mistake. For troubleshooting the status display itself, this guide to OBS not showing YouTube stream health while a loop runs may help distinguish a monitoring issue from a playback issue.
If no one can remain at the controls, decide in advance whether this manual workflow suits the service. OBS scene transitions depend on someone preparing and taking the right scene live. StreamNeo can remove the need to leave a church computer running for an uploaded video by turning that file into a YouTube live stream, but the specific scene hand-offs described here are an OBS workflow. Keep the choice aligned with who will operate the broadcast and what parts of it need to be live-managed.
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
How do I add a holding slide between church services on YouTube Live?
Create a holding-slide scene in OBS alongside a scene for each prerecorded service. While the event remains live, use Studio Mode to prepare the slide and select Transition to put it in the feed; later, transition to the next service scene.
Is YouTube’s scheduled-stream trailer the between-services slide?
No. YouTube describes the trailer as playing before a scheduled live stream begins. An between-services slide must be part of the feed your encoder sends while the stream is already live.
Can I switch OBS scenes without ending a YouTube livestream?
Yes. Keep OBS connected to the event and change the live scene using its transition controls. Rehearse first so you know that the video, audio and intended scene are reaching the event.
Do I need a Stream Deck to change scenes?
No. It is an optional shortcut controller, not a requirement for OBS scene switching. A volunteer can use OBS’s own controls, provided they have practised the transition and can identify the correct scene.