“Restart automatically” can mean three different things: YouTube starting or stopping a broadcast when an encoder connects or disconnects, Castr switching to a backup when the primary input fails, or Castr replaying prerecorded content continuously. They are separate behaviours, so there is no single restart switch that covers every ended YouTube event.
For an encoder-driven broadcast, check Auto-start and Auto-stop in YouTube Studio. For a failed input, review Castr’s Backup options; for a prerecorded video that should keep repeating, use Infinite Loop. Pick the control according to what should trigger the action and what content should be on air afterwards.
First identify what should restart
Before changing settings, write down what is supposed to happen and what event should trigger it. “The stream went offline” is not specific enough: it may mean the encoder was stopped normally, the network dropped, the input failed, or a prerecorded broadcast reached its end. Each case calls for a different control.
A useful distinction is between the broadcast and its input. YouTube’s live broadcast is the event viewers see; an encoder or Castr source supplies the video and audio feed. Starting that feed, covering its loss with another feed, and replaying a file are different operations. Treating them as one restart problem can leave you with a configured backup when what you need is a loop, or a loop when your actual encoder has stopped.
| What happened or what you want | Control to investigate | What it addresses |
|---|---|---|
| Your encoder starts or stops sending a live feed | YouTube Auto-start and Auto-stop | Lets the encoder initiate or stop the YouTube stream |
| The primary input drops but another source or file should take over | Castr Backup/failover | Maintains the feed by using a configured backup mode |
| A prerecorded video should run repeatedly | Castr Infinite Loop | Streams the selected video continuously |
| One scheduled prerecorded start is needed | Castr Schedule Date Time | Starts the selected content at a chosen time |
The table is a first diagnosis, not a promise that a setting can recover every interruption. A backup only helps if an appropriate backup has been configured and is available. Auto-start does not recreate an encoder that has stopped running, and looping a file does not restart an unrelated live encoder.
If you are building a devotional channel where different recordings are meant to take turns, consider the content plan as well as the connection settings. A loop of one video is not the same as a playlist that changes between bhajans and aarti; the distinction is explored in how to make a 24/7 devotional stream switch between bhajans and aarti.
For an encoder feed, check YouTube’s controls
When an encoder sends a live feed through Castr to YouTube, Auto-start and Auto-stop are YouTube-side stream settings. Open the relevant stream in YouTube Studio or the Live Control Room and check the stream settings. YouTube’s labels and interface can change, so confirm the current location in YouTube’s live stream settings guidance rather than relying on an old screenshot.
Enable Auto-start and Auto-stop if you want YouTube to let the encoder start and stop the live stream. These controls do not make Castr’s input keep running: the encoder still has to send a feed. They also do not instruct YouTube to restart any event that has ended for any reason.
Next, check how Castr is connected to the YouTube destination. Castr documents both account/API connection and a server-and-stream-key connection; the details can differ, so use the instructions for your connection type in its guide to connecting YouTube with Castr. A stream-key connection may require editing stream description details in YouTube’s dashboard. Keep the key private: anyone with access to it may be able to send a feed to the destination.
These settings are most relevant when the encoder itself is the thing that starts and stops streaming. They are not a substitute for configuring your encoding software to run, or for solving a computer or internet connection that fails overnight. If the encoder is on your own computer, a power cut, operating-system restart, or lost connection can stop the source regardless of YouTube’s Auto-start setting.
For readers comparing ways to produce an uninterrupted file-based feed, the practical difference between local and hosted playback is described in how to stream a playlist to YouTube Live from a Linux VPS using Docker. That approach involves managing the playback process yourself; Auto-start alone does not automate it.
Understand what Auto-start and Auto-stop change
YouTube describes these controls as allowing you to start or stop streaming from the encoder when the settings are on. In practical terms, they affect how YouTube responds to the encoder’s stream state. They do not restart the encoder, supply missing media, or repair an input connection.
Auto-start is useful when you expect the encoder’s connection to initiate the YouTube broadcast without separately starting it in the Live Control Room. Auto-stop is useful when stopping the encoder should also stop the YouTube stream. Think of them as a way for the encoder to control the YouTube event, not as a watchdog that watches for every possible failure and brings the whole system back up.
That distinction matters when you run separate broadcasts repeatedly. Castr’s guidance recommends turning destinations off while the source is offline, then enabling them again when the encoder source is live. This is a manual destination workflow, not a documented automatic restart of an ended YouTube event. If you use it, make the order part of your operating checklist: verify that the source is live, then enable the destination as directed by the current Castr interface.
Do not infer behaviour from a successful test in only one direction. Confirm both what happens when the encoder begins sending and what happens when you stop it deliberately. The result can depend on which YouTube event and destination you have selected, so check the intended stream rather than assuming a setting carries across every event in your channel.
For input loss, review Castr Backup
If the primary encoder or feed drops and you want another source to carry the broadcast, look at Castr’s Backup tab. Castr describes Backup as a way to keep a stream running if the primary encoder fails. The available modes in its documentation are Encoder Level and File Level. This is failover: it responds to loss of the primary input by using a configured alternative, rather than restarting the failed encoder.
With Encoder Level, a second encoder must be pointed at the backup ingest URL. This is appropriate when you have another live feed ready to take over, but it means maintaining a second source and making sure it is prepared to send the right content. A backup destination that has never been tested is not a reliable plan just because it appears in a settings screen.
With File Level, Castr plays a backup VOD when the live input drops. This can be useful if a static holding video is preferable to a blank or interrupted feed while you restore the primary source. It is not the same as automatically restarting your live encoder, and a backup file will not supply the changing live content that viewers expect from a news or events channel.
Castr’s instructions say to open the Backup tab while the stream is disabled, enable Backup, and select the mode. They also note that backup cannot be toggled while the stream is live or with a Linked source, and that enabling it changes the stream keys. Follow Castr’s current live-stream setup instructions and plan for the key change before you configure the destination. Do not leave an old key in an encoder and assume it is still the correct one after changing the backup configuration.
The trade-off is operational complexity. A second encoder requires a second prepared feed; a file backup requires suitable prerecorded material and an understanding of how it will appear to viewers. Decide what viewers should see during the interruption, and make sure the backup is appropriate for that channel. For a music stream, a clearly labelled holding visual and approved audio may be acceptable; for a local news loop, a prerecorded update can become misleading if it appears current when it is not.
For prerecorded content, configure Infinite Loop
If the intended behaviour is to keep a prerecorded video on air repeatedly, use Castr’s Infinite Loop mode rather than Auto-start or Backup. Castr says that an uploaded video goes live immediately when Infinite Loop is enabled and streams 24x7. That describes continuous prerecorded playback, not recovery of an encoder stream that has failed.
Before enabling it, make sure the file is the right content for an indefinite repeat. Check the beginning and end, including any spoken introduction, credits, or announcement that would sound awkward each time the video cycles. Consider whether the material remains accurate over time: a dated offer, a one-day event notice, or a breaking-news caption can become stale even if playback itself continues normally.
Castr also documents Schedule Date Time for a single scheduled start. The scheduler uses the device’s time zone, so verify the intended local time on the device used to configure it. A scheduled start is useful when a file should begin at a particular time; it is not equivalent to an endlessly repeated loop. For further approaches and trade-offs, see best software for looping prerecorded videos on YouTube Live.
If your aim is a rotation of several files rather than the same video repeating, confirm that the selected mode supports the sequence you need. Do not assume Infinite Loop will build a playlist, change programmes at planned times, or remove a clip that has become outdated. The Castr guide to prerecorded live scheduling modes is the place to check the current mode names and behaviour.
Test the behaviour before relying on it
Test privately or as an Unlisted stream before you depend on the setup overnight. Castr advises checking the source in its preview with destinations turned off, then testing the YouTube destination as Unlisted or Private and monitoring Analytics > Input Health. Its pre-broadcast testing guide gives the current steps. The point is to verify the chain you intend to use, not just that a preview image appeared once.
For encoder start and stop, begin with destinations disabled and confirm that the source reaches Castr’s preview. Then test the YouTube destination with Auto-start enabled, using a non-public visibility setting. Check whether starting the encoder produces the intended live state, and stop the encoder deliberately to confirm what Auto-stop does. If the stream does not behave as expected, note which stage changed: encoder, Castr input, destination, or YouTube event.
For backup, test the failure you actually want to cover while the stream is not public. Confirm the backup source is ready, then simulate loss of the primary input in a controlled way and check what viewers would receive. Restore the primary feed and confirm you can return to it cleanly. Do not make the first test a real overnight outage, and do not assume the backup mode has taken effect merely because it was enabled.
For Infinite Loop, verify that the video begins, reaches its end, and starts again in the way you expect. Check the audio transition and any opening or closing material. A successful first play does not prove the repeat point is suitable for a public channel. If you are testing a schedule, check the device time zone as well as the selected start time.
After each test, record the settings and the observed result. That small note saves time when a stream behaves differently later: you can distinguish a change in YouTube’s stream settings from a changed Castr key, a source failure, or an unsuitable file. Keep keys out of shared notes and screenshots.
Choose the control that matches the failure
Use the trigger and the content source to decide what to configure. If the encoder is expected to start and stop the YouTube event, use YouTube’s Auto-start and Auto-stop. If the primary input may fail and you have an alternate live source or a suitable backup VOD, consider Castr Backup. If the channel is meant to repeat prerecorded content continuously, use Infinite Loop. These choices are not interchangeable, and using more than one does not make them equivalent.
| Situation | Best starting point | Check before going live |
|---|---|---|
| Encoder starts and stops normally | YouTube Auto-start / Auto-stop | Test both start and stop with a non-public broadcast |
| Primary feed fails but a prepared alternate exists | Castr Backup | Confirm mode, backup readiness, and any updated keys |
| One file should repeat continuously | Castr Infinite Loop | Inspect the repeat transition and whether the content stays current |
| A file should begin at a chosen time | Castr Schedule Date Time | Verify the device’s time zone and intended start |
| A broadcast event has ended and must be recreated | Check the specific YouTube and Castr workflow | The reviewed documentation does not establish a universal automatic event restart switch |
If what you really need is for a file to carry on while your computer is off, an encoder restart setting will not remove the burden of keeping the encoder running. StreamNeo addresses that specific operational pain by letting you upload a video and connect your YouTube stream key so the broadcast can continue from the cloud without your computer running. It is YouTube-only, so decide first whether file-based continuous playback is the right model for your channel.
If the YouTube destination will not connect or a key fails, Castr’s troubleshooting guide recommends deleting and re-adding the destination, or generating a new key in YouTube Live Control Room and updating the Castr connection as appropriate. Keep the server URL and key private. For a channel that depends on key changes, stream key rotation on a 24/7 channel can help you plan the update without confusing an authentication problem with a restart setting.
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 Castr have one switch to restart any ended YouTube stream?
The documentation reviewed here does not establish a single switch that restarts every ended YouTube event. Auto-start and Auto-stop let the encoder initiate or stop a stream, Backup responds to primary input loss, and Infinite Loop repeats prerecorded content. Start by identifying which event you need to handle.
Does YouTube Auto-start restart my encoder after a network drop?
No. Auto-start is a YouTube stream setting that allows the encoder to start the stream; it does not restart an encoder or restore a failed internet connection. If the primary input drops, assess whether a configured Castr Backup mode can provide a suitable alternative feed.
Is Infinite Loop the same as failover?
No. Infinite Loop is for continuously streaming prerecorded video, while Backup is intended to cover loss of a primary input with an encoder-level or file-level alternative. Choose based on whether the desired source is a repeating file or a backup for a live feed.
What should I test first?
Check that the intended source appears in Castr preview, then test the chosen YouTube destination privately or as Unlisted. Exercise the relevant behaviour—encoder start and stop, backup takeover, or file repeat—and check what viewers would see before relying on it in a public broadcast.