Switchboard Live can schedule a YouTube broadcast event, but it does not store or play the prerecorded playlist for you. You need an encoder that plays your video and sends a live feed; when that feed is ready, you start the broadcast from Switchboard.
There are two routes: create the scheduled event through Switchboard, or use a YouTube event you have already made and connect it using a Custom RTMP destination if your account workflow calls for it. The older Switchboard guide documents that workaround, but its note about direct support may have changed, so check the current controls before settling on a route.
Understand the division of work
Think of the process as three separate jobs. YouTube provides the viewing destination and event page; Switchboard organises the broadcast event and sends the incoming programme to its destinations; an encoder plays the prerecorded file and supplies the live video and audio feed. Scheduling an event is not the same as scheduling playback of a file.
Switchboard’s FAQ says that it does not store prerecorded videos and that an encoder must support streaming prerecorded material. Its examples include OBS, Ecamm, and Switcher Studio. The file remains in the environment where you manage and play it, so keep a working copy and make sure the encoder can access it at broadcast time.
This distinction matters if you are preparing a bhajan loop for overnight viewing, a study playlist for the morning, or a local news package. Creating an event page may let viewers find out when the broadcast is planned, but it does not mean Switchboard will wake up and play the first file. You still need the encoder output and a person or process to start the broadcast.
If you are new to terms such as stream key, encoder, and RTMP, the guide to live streaming terms in plain English is a useful reference. A stream key is a credential that lets the encoder send video to the intended destination. Treat it as private: do not put it in a public document or share it in a screenshot.
Prepare a prerecorded-video encoder
Choose an encoder that can play your video or playlist continuously and transmit it as a live stream. OBS is one example named by Switchboard; its FAQ also names Ecamm and Switcher Studio. The right choice depends on the playback and operating system you use, how you manage transitions, and whether you can leave that machine running for the whole broadcast.
Before you schedule an event, test the actual programme rather than a short sample with different settings. Confirm that the encoder can read the files, that the image is not cropped unexpectedly, and that audio is present at a sensible level. If the playlist is meant to repeat, check what happens at the end: some setups return to the beginning, while others stop or leave a gap unless configured to loop.
Also test what viewers will see during a file change. A brief black screen or silent pause may be acceptable for a one-off programme, but it can look like a failure in a devotional or ambience channel that is meant to run without interruption. Review the transition in the encoder preview, and listen to the source audio through the encoder’s monitoring path. For an OBS setup where audio monitoring creates a duplicate signal, see the echo troubleshooting guide.
The encoder sends its output into the Switchboard workflow; it does not send a file for Switchboard to store and play later. Switchboard’s FAQ describes RTMP ingest support. In practical terms, keep the computer or other encoder environment available, the media accessible, and the encoder configured to send the feed to the workflow you intend to use.
A long broadcast also needs a plan for interruptions. Check that the source file is complete, the playlist order is correct, and the encoder does not depend on a temporary desktop window or removable media that may disappear. If you are using a computer, disable sleep for the planned run and avoid applying a system update just before going live. Those are operating precautions, not a guarantee that a stream cannot drop.
Create or identify the YouTube event
First decide where the event page should be created. Switchboard’s Scheduled Events guidance describes creating an event from a workflow with Create New and then Scheduled Event, or creating one through the Events Page Manager with New Event. The labels may differ as the product changes, so use the corresponding current controls in your account.
Fill in the title, description, scheduled date and time, and thumbnail if you want one. Then add the destinations you need and save the event. Switchboard says it creates a YouTube event page for YouTube Partner Destinations. Once the page exists, you can retrieve its share link from the YouTube destination’s broadcast information in the workflow or from the event page itself.
The other route starts in YouTube Studio. Create the scheduled YouTube event there if you specifically need to manage its event details in YouTube first, or if the event already exists. You will need the event’s stream URL and stream key for the documented Custom RTMP route described below. Do not assume that a YouTube event created in one place will automatically appear in the other or that titles and descriptions will synchronise.
Use the route your current account supports and that matches where you want to manage the event page. Switchboard’s older guide to creating a scheduled YouTube event and going live describes direct scheduled-event support as unavailable at the time it was written, and gives Custom RTMP as a workaround. More recent Switchboard material describes scheduled events and YouTube event pages, but the available documentation does not settle every account’s current behaviour. Check the destination choices visible in your workflow, and consult current Switchboard support material if the expected YouTube option is missing.
| Workflow | Where the YouTube event page starts | What to check |
|---|---|---|
| Switchboard-created event | Switchboard’s Scheduled Events workflow, for a YouTube Partner Destination | Confirm YouTube appears as a destination and note where the share link is provided. |
| YouTube-created event with Custom RTMP | YouTube Studio | Copy the event’s stream URL and key; enter them in a named Custom RTMP destination in Switchboard. |
These are not interchangeable in every detail. In the Custom RTMP workflow, the older guide warns that the title and description entered in Switchboard do not populate the custom destination. Make sure the public YouTube event contains the details viewers need, and do not count on metadata syncing unless your current interface explicitly confirms it.
Add an existing event as a Custom RTMP destination
If you already created the event in YouTube Studio, the documented fallback is to add its stream endpoint to Switchboard as a Custom RTMP destination. In YouTube Studio, open the event’s streaming setup and copy the stream URL and stream key. Keep the key private, and verify you have copied the values for the intended event rather than another broadcast.
In Switchboard, add a destination of the Custom RTMP type, enter the URL and key in their respective fields, and give the destination a recognisable name, such as “YouTube morning programme”. Save it, then confirm that it is associated with the workflow or event you will use. The label helps distinguish this destination from other YouTube channels or test endpoints if you manage more than one.
Do not use this route to assume that Switchboard will create or edit the YouTube event page. The event remains the one created in YouTube Studio, and the connection simply gives Switchboard the destination details needed to send its broadcast feed there. According to the older guide, title and description entered into Switchboard are not pushed to a Custom RTMP destination; check the YouTube page separately before sharing it.
Because the source guide’s direct-support note may be stale, treat Custom RTMP as a documented workaround, not a claim that direct event selection is currently unavailable. If your Switchboard account now offers a direct scheduled YouTube destination for the event, compare the current instructions and use the route that fits your workflow. Avoid creating a second public event simply because the older guide describes a different path.
Copy the event link and check the key
With a Switchboard-created event, find the YouTube event link in the workflow’s broadcast information or open the event page and copy its public URL. With a YouTube-created event connected through Custom RTMP, get the event page link from YouTube Studio. These public links are what you share with viewers; the stream URL and stream key are not substitutes for the public event link.
Before promoting the event, check its title, description, scheduled time, and thumbnail on the page viewers will actually see. If you are using Custom RTMP, check the details in YouTube Studio, because the older Switchboard instructions say its title and description fields do not sync to that destination. A short private test can help you identify the correct event and destination before you circulate the link.
Be cautious when changing destinations after sharing a Switchboard scheduled event. Switchboard’s help article warns that removing a YouTube destination can delete the public event page, break a link already shared, and remove Notify Me subscriptions. If you need to alter the setup, review the event controls and current guidance before removing a destination; where possible, understand the effect on viewers first.
If you are linking the broadcast from a channel that already has other scheduled videos, keep the event page distinct from a playlist of archived uploads. A live event is a scheduled broadcast destination, while the encoder supplies what is being played. For a channel whose format is a continuously changing set of recordings, the guide on replacing videos in a live church YouTube playlist covers a related but different publishing problem.
Start the encoder and confirm its feed
At the planned operating time, open the encoder and load the intended video or playlist. Verify the source, order, loop behaviour, and audio, then connect the encoder to the Switchboard workflow. Start sending the feed before you expect viewers to see the programme, so there is time to confirm that the right picture and sound are arriving.
Look for incoming video in the Switchboard workflow and check the preview rather than relying only on the encoder’s own preview. If you have a YouTube event page open separately, remember that a waiting screen before the broadcast is not proof the encoder feed has reached Switchboard. Confirm the feed in the receiving workflow and verify that the selected destination is the one attached to your scheduled event.
Switchboard’s Scheduled Events help article says the Start Streaming control becomes available when encoder video is present, with its instructions describing availability from 30 minutes before the scheduled time. Product timing rules can change, and the current product page has described a later start window. Do not plan a fixed operation around either timing statement without checking the current controls and guidance for your account.
If the preview is blank, check the basics in order: is the encoder sending, is it pointed at the correct workflow, is the correct source selected, and are the event and destination connected? If video appears without sound, inspect the encoder’s audio source and levels before starting the public broadcast. The YouTube RTMP no-sound troubleshooting guide can help you work through a missing-audio problem without confusing it with event scheduling.
Start the broadcast from Switchboard
Once Switchboard shows the incoming programme and you are satisfied that it is the right feed, use Start Streaming in the scheduled event workflow. This is the operator action that takes the event live to its destinations; creating the event and starting the encoder are separate steps. Confirm the event is live at the YouTube destination, then check the public page from a viewer’s perspective if practical.
If you are running a long programme, keep an eye on both sides of the chain: the encoder must continue playing and sending, and Switchboard must continue delivering the event. A connection that was healthy at the start does not prove the source playlist will continue through every file change. Arrange a sensible way to notice a stopped encoder or a missing feed, particularly if nobody is sitting beside the machine overnight.
Keep the source media and the event credentials under your control. Switchboard’s FAQ says it does not archive the prerecorded source, so do not treat the scheduled event as a backup of your video. Likewise, if you need to change the YouTube key, update the matching destination carefully and test the incoming feed again before using Start Streaming.
For a creator who has been managing a playlist by leaving a local machine on all night, moving the broadcast workload away from that machine can remove the specific burden of keeping that computer awake and connected. StreamNeo turns an uploaded video into a 24/7 YouTube live stream, so it may suit a different workflow where you want the computer switched off; it is YouTube-only and does not change how a Switchboard event is configured. Choose based on whether your need is a scheduled event with a live encoder feed or a continuous file-based channel.
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 Switchboard play a prerecorded video automatically at the scheduled time?
No. Switchboard’s FAQ says it does not store prerecorded videos; an encoder must play the file and send a feed. You then start the broadcast from Switchboard when the feed is arriving.
Can I connect an event I already created in YouTube Studio?
Switchboard’s documented workaround is to add a Custom RTMP destination using that event’s stream URL and key. The guide’s statement about direct scheduled-event support may be out of date, so check the current destination controls and instructions before choosing a route.
Will the title and description I enter in Switchboard appear on a Custom RTMP event?
The older Custom RTMP guide says those details are not pushed to the custom destination. Set and verify the public event information in YouTube Studio when using that route.
What happens if I remove YouTube from a shared scheduled event?
Switchboard’s help article warns that removing the destination can delete the public event page and break the shared link, including Notify Me subscriptions. Check the current event controls and the effects of removal before changing a promoted event.