Switchboard Live distributes a live encoder feed; it does not store or play your prerecorded videos. To use it for a 24/7 YouTube stream, choose an encoder that can play your file continuously, send its output to the endpoint shown in your Switchboard workflow, then verify the picture before taking the YouTube destination live.
The distinction matters when you are planning an unattended channel. Your encoder is responsible for playback, while Switchboard receives and routes the feed to connected destinations. YouTube is where viewers watch the broadcast, and its live-stream archive is a separate concern from keeping the channel on air.
What Switchboard Live does in this workflow
Think of the setup as three separate jobs. The encoder plays your prerecorded material and creates a live output. Switchboard receives that output and distributes it to the destination you have connected. YouTube accepts the feed as a live broadcast. Switchboard’s FAQ says it does not store prerecorded videos, and that you need a separate encoder that supports playback of them.
That means uploading a video to Switchboard is not the way to prepare a loop. You instead load or schedule the file in an encoder, configure the encoder to send its feed to the active Switchboard workflow, and manage the YouTube destination from Switchboard. The controls and terminology can differ by encoder, but the division of responsibility remains the same.
Switchboard names OBS, Ecamm and Switcher Studio as examples of encoders with prerecorded-video playback support. Treat those as examples, not a promise that every version, operating system or workflow will behave identically. Before building your channel around one, check that it can play the files you have and send a live feed using the endpoint and protocol presented by your Switchboard workflow.
For a channel that should stay on overnight, the feed path also needs to be understood by whoever will troubleshoot it. If the picture stops, first establish whether playback stopped in the encoder, transmission to Switchboard failed, or the YouTube destination was not started. A clear hand-off between those jobs makes faults easier to isolate than treating the whole chain as one application.
Choose an encoder for prerecorded playback
Start with playback rather than brand preference. Confirm that the encoder can open your source file, repeat or schedule it in the way your channel needs, and continue outputting a live feed while unattended. A program that can stream a webcam is not automatically suitable for a continuous prerecorded channel: you need a playback source and a way to keep it running.
Switchboard’s named examples—OBS, Ecamm and Switcher Studio—are useful starting points for investigation. Compare the actual functions available in the version you plan to use. Can it loop the file without a manual restart? Can it recover sensibly if playback stops? Can you inspect its output remotely or record a local copy? Can it send to the protocol selected in Switchboard? Those details matter more than a feature list that only says “live streaming”.
| Choice | What to verify before relying on it | Practical trade-off |
|---|---|---|
| Software encoder | Prerecorded playback, looping or scheduling, compatible output protocol, recovery and monitoring | Flexible to test and adjust, but playback depends on the computer and software remaining operational |
| Dedicated hardware encoder | Scheduled prerecorded playback and the output path required by your chosen workflow | May reduce dependence on a general-purpose computer, but confirm the exact functions and integrations before purchase |
| AJA HELO Plus | YouTube’s verified encoder listing describes PlayToStream for scheduling prerecorded media directly to YouTube Live | Investigate it as a separate equipment route; the cited information does not establish integration with Switchboard |
YouTube’s encoder guidance and verified encoder list can help you investigate hardware options. It names AJA HELO Plus and describes PlayToStream scheduling prerecorded media for YouTube Live. That is not evidence that the product works with Switchboard in the same workflow described here, so do not assume it does: confirm the required output and integration with the relevant documentation before buying.
A software encoder can be a practical choice if you already have a suitable computer and want to test a channel before investing in dedicated equipment. The trade-off is that the computer becomes part of the broadcast path. If it sleeps, restarts for an update or loses power, playback can stop. Disable sleep where appropriate, plan how updates are handled, and decide who can check the setup when you are away.
If you are comparing unattended operation options, consider whether a cloud-based workflow better fits your needs. StreamNeo takes away the need to leave your own computer running for the broadcast, which is useful when local playback hardware would otherwise be the part you worry about overnight. It is a YouTube-only route with its own workflow, rather than a claim about Switchboard’s video storage or encoder functions.
Prepare and play the video in the encoder
Before connecting destinations, test the source material in the encoder. Open the file and check that picture and sound play as expected from beginning to end. If the file is intended to repeat, let it reach the end and confirm that the next playback begins without a long gap or an unwanted desktop, slate or blank frame. Do this before viewers are relying on the channel.
A long playlist needs the same attention as a single file. Check that the order is right, that transitions do not leave silent gaps, and that any opening or closing material does not interrupt the intended loop. If your channel mixes devotional songs, for example, listen through the joins rather than assuming that a playlist which looks correct in a file browser will sound continuous on air.
Video shape and audio level are worth checking at this stage. Compare the encoder preview with the source to catch cropping, stretching, missing audio or an unexpected resolution. For portrait source files, the practical choices are explained in this guide to preparing portrait videos without stretching them. For general picture and connection issues, keep the live-stream quality settings and fixes nearby as a troubleshooting reference.
For a 24/7 schedule, distinguish between “the file repeats” and “the channel will always be live”. A loop can run correctly while a computer or network fails. Decide whether someone will check the output, whether the encoder can restart playback after an interruption, and what you will do if the machine needs attention. Test the actual unattended interval you expect, rather than inferring it from a short preview.
Keep a source copy and, if preserving a recording matters, plan a separate recording path. Switchboard says it does not archive video. YouTube may automatically archive streams under 12 hours, but streams longer than 12 hours may not be captured at all. YouTube’s archive guidance recommends a local recording as a backup; for a continuous channel, consider shorter broadcast sessions or another deliberate way to retain the material.
Connect YouTube in Switchboard
Before the planned first broadcast, check that the YouTube channel can live stream. YouTube says a channel must be verified and have no live-streaming restrictions in the preceding 90 days. First-time activation can take up to 24 hours, so enable the feature early rather than discovering the delay at the time you intend to launch. Check the current YouTube live-streaming eligibility instructions because channel status and requirements are matters for YouTube to confirm.
In Switchboard, follow the destination connection flow for the relevant Stream Group. The documented sequence is to open Add Destinations, choose Connect More, select YouTube, authorise the intended channel and then enable it in the group. The steps are described in Switchboard’s guide to connecting YouTube to Switchboard Connect. Check the channel name during authorisation; a Google account with access to more than one channel can make it easy to choose the wrong destination.
Connecting a destination is not the same as starting a broadcast. It makes YouTube available to the Switchboard workflow, but the destination is not ready to go live until Switchboard detects incoming video. Keep that distinction in mind during tests: authorisation confirms access, encoder transmission supplies the feed, and the Go Live control starts the destination broadcast.
If the channel is part of a group, check which destinations are enabled and which settings apply to that group. Do not assume that a connection configured for one group is automatically present in another. It is worth having a short written checklist with the channel, group and intended playlist so that a person covering the channel can verify the same setup.
Use the displayed endpoint and protocol
Once the destination is connected, open the workflow that you will use and inspect the ingest details it displays. Switchboard’s documented workflow provides an ingest URL and stream key, and the available protocol choices may include RTMP, RTMPS or SRT. Switchboard’s FAQ describes RTMP ingest, while its workflow documentation shows the protocol choices; the safe instruction is to use the endpoint and protocol shown for the workflow you have actually configured, not a value copied from an old guide.
In your encoder, locate its streaming output settings and enter the displayed endpoint and stream key in the corresponding fields. Select the same protocol that Switchboard presents. Do not infer the endpoint from a screenshot or choose a protocol simply because another encoder tutorial used it. The encoder’s field names may differ, so consult its current documentation if it asks for a server address, key or connection type in a way that is unclear.
Treat the stream key as a credential. Do not place it in a public post, screenshot, shared document or recording of your setup. If you suspect it has been exposed or reset it, update the encoder with the replacement key before the next broadcast. Keep access limited to people who need to operate the stream.
The protocol choice is part of the configured connection, not a universal promise that all combinations work. If the workflow offers SRT, that does not mean every encoder or account supports it. Select only an option the encoder can use and that is displayed in the Switchboard workflow. If the feed does not arrive, verify the selected protocol and endpoint first, then check the key and encoder status rather than changing several settings at once.
You may find descriptions of particular protocols elsewhere, but for this setup the live workflow display is the operational reference. Documentation changes, and a protocol listed in a general FAQ may not be presented in every workflow. Record the protocol you used alongside the encoder configuration so that anyone asked to restart the feed can reproduce the working setup without exposing the key.
Verify the confidence monitor and go live
Start playback in the encoder and let it send the feed. In Switchboard, look at the confidence monitor and confirm that it shows the expected picture; check that incoming status is active as well. A still image, black frame, wrong programme or silent source is not a successful check just because the encoder says it is connected. Confirm the material you expect viewers to see.
Switchboard’s documented flow keeps destination Go Live controls inactive until it detects incoming video. If the control is unavailable, treat that as a useful signal: the feed has not yet reached the point where Switchboard can start the destination. Check the encoder is sending, the displayed endpoint and key match, and the protocol selection agrees. Wait for receipt to be reflected in the monitor before proceeding.
When the monitor is correct, select the connected YouTube destination and press Go Live. Then check the destination status and, where practical, view the public stream from another device or browser. The confidence monitor confirms Switchboard is receiving the feed; a separate viewer-side check helps catch a destination or playback issue that the preview alone cannot show.
Switchboard includes an Auto-Start setting for Stream Groups. If you use it, configure it before sending video and test its behaviour with a non-critical broadcast. Do not make an unattended channel depend on a setting you have not observed working in your own workflow. For a first launch, a person present to confirm the YouTube destination is live is a safer operational check than assuming the encoder starting will also start YouTube.
If you need a programme with defined segments, a simple running order can make handovers easier. This study-session scheduling guide is one example of planning what appears at different times. For a continuous music channel, the equivalent is a clear playlist, a tested repeat point and a note of who checks the monitor.
Plan for archives, rights and monetisation separately
A 24/7 broadcast and an archived replay are different outcomes. YouTube says streams under 12 hours can be automatically archived, while a stream longer than 12 hours may not be captured at all. If viewers need to replay the programme, do not rely on a single unbroken broadcast to create a complete archive. Schedule shorter sessions where that suits the channel, or record locally and retain the files you need.
Also separate technical delivery from monetisation eligibility. A stream can reach YouTube successfully without being eligible for monetisation. YouTube’s policy focuses on original and authentic material; repetitive or mass-produced videos may be ineligible, and reused material needs meaningful original commentary, substantial changes or educational or entertainment value. Review the current YouTube channel monetisation policies for the full policy and apply it to the channel as a whole. Live status does not guarantee ads or revenue.
Check rights for every part of the programme before you broadcast it. That includes the video, music, images and other included elements. YouTube’s live-stream terms place responsibility on the provider to have the necessary rights, including music licensing rights, and to follow applicable laws and YouTube guidelines. A track that is available for personal listening or appears in another online video is not, by that fact alone, cleared for your live channel.
For an unattended channel, write down what to do when the feed drops: who can inspect the encoder, whether the source file is available locally, how the stream key is updated, and how you will confirm the destination is live again. Keep this operational plan separate from any claim about guaranteed uptime. A tested recovery routine cannot prevent every interruption, but it can stop a routine restart from becoming a long, unexplained outage.
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
Does Switchboard store or play my prerecorded videos?
No. Switchboard’s FAQ says it does not store prerecorded videos. Your encoder must play the source material and send the resulting live feed to the Switchboard workflow.
How do I stream prerecorded videos on YouTube 24/7?
Use an encoder that can play the prerecorded material continuously, connect YouTube as a destination in Switchboard, and configure the encoder with the endpoint and protocol displayed for that workflow. Confirm the expected picture in the confidence monitor before taking the YouTube destination live.
Will YouTube save my 24/7 live stream?
Do not rely on one unbroken stream longer than 12 hours to produce a complete archive. YouTube says streams under 12 hours can be automatically archived, while longer streams may not be captured; plan shorter sessions or a local recording if preserving a replay matters.
Can prerecorded content be monetised just because it is live?
No. YouTube’s monetisation rules still apply to live streams, and repetitive or reused material may not qualify. Review the current policy, make sure the content offers the necessary originality or value, and confirm that you have rights to all included material.