First identify how the video is being sent: a source in Restream Studio, a scheduled pre-recorded single-video event, or a playlist. Each has a different repeat control, and playlists do not loop as playlists.
Also check what actually stopped. A video reaching its end is a playback issue; the entire live broadcast going offline points to a separate source or connection problem. Changing a media loop setting cannot repair a disconnected livestream.
Identify the Restream workflow
Before changing settings, locate the video in Restream and note how you started the broadcast. If you added a video to a Studio scene while hosting a live session, it is a Studio media source. If you chose a file and scheduled a broadcast to start later, it is a pre-recorded event. If you selected several files to make one scheduled broadcast, it is a playlist.
The distinction matters because a control that exists in one workflow may not exist in another. In Studio, the video source has its own Loop playback control. A scheduled single-video event instead has a loop count that you set for that event, subject to Restream's documented limit. A playlist has no playlist-level repeat setting: Restream says playlist looping is unsupported.
| What you started | How repetition works | What to check first |
|---|---|---|
| Restream Studio video source | Turn on Loop in that source's playback controls. | Confirm the control is enabled on the video in the active scene. |
| Scheduled single-video event | Set a loop count when creating or editing the event. | Check the event setting and whether your plan includes the feature. |
| Scheduled playlist | Playlists do not loop as playlists. | Arrange duplicate entries before the playlist goes live. |
| RTMP/SRT source that disconnects | A separate disconnect-protection feature may play a fallback temporarily. | Investigate the incoming source and connection; do not rely on the media loop. |
Restream's Studio video instructions and pre-recorded event instructions describe separate controls. Start with the workflow you actually used rather than assuming that a video ending means the stream itself ended.
If you are not sure, open the Restream home screen and look for the event card or the Studio session you used. A scheduled event has a saved date and time and can be edited from its card. A Studio source is part of the scene you assemble in the Studio. A playlist contains multiple entries arranged into a broadcast. Once you know which one applies, follow only that section below.
Loop a video in Restream Studio
For a video source in Studio, enable Loop in the playback controls. Restream supports looping for cloud-stored video and local video, but the way you add each kind differs.
For a cloud-stored video, add or select a scene, choose Media, then Video, and choose an existing file from Restream storage or upload one. Add it to the scene that will be on air. Select the video source and open its playback controls; switch Loop on. For a local file, add a scene, open Media, select the plus icon, choose Local video, and open the file. Then use that source's playback controls to enable Loop.
Do not confuse seeing the video in the preview with confirming the repeat setting. Start playback, wait for the file to reach its end in a controlled test, and check that it starts again from the beginning. If the source is hidden, replaced, paused, or removed from the active scene, the loop control will not make that different source appear. Confirm that the looping video remains the one being sent to the stream.
Local playback depends on the computer that is running Studio. Restream recommends Chrome and a powerful computer for local video playback; if the device is struggling, it recommends using a video from Restream storage instead. This is worth checking when a local source stutters, freezes, or fails to restart cleanly. A local file that plays well in a media player may still be a poor test of how it behaves alongside Studio and the live broadcast.
Restream notes that Studio's preview may be shown at lower quality for performance, while the outgoing stream retains the video's original quality. Match the source to your Studio output settings: for example, a 4K file sent through a 720p output setting may be reduced in quality. That is a quality mismatch, not evidence that Loop is off. If the picture looks soft, check the output and source settings separately from playback repetition.
Studio permits only one video from storage to play at a time. If your programme needs several prerecorded parts, decide whether you want to switch sources in Studio or use another workflow; do not expect several stored videos to play at once. For a continuous station that must keep running unattended, compare the broader setup considerations in this guide to streaming a radio station to YouTube from a VPS. The right choice depends on whether you need to operate the computer and Studio throughout the broadcast.
Set a loop count for a pre-recorded event
A scheduled pre-recorded event is a single uploaded video sent as a broadcast at its scheduled time. Its repeat behaviour is configured as an event loop count, not with Studio's on-air media control. When creating the event, choose Pre-recorded livestream, select Video, choose or upload the file, and complete the event details. Enable the optional loop count and choose the number of plays.
Restream documents a maximum of 10 plays for this event setting. Its current help material identifies Marathon and the Media add-on as plans that include looping, and describes looping as a paid feature. Plan names and entitlements can change, so check your account and Restream's current event controls if you do not see the setting. The limit is not an unlimited-repeat option: if the video has played the configured number of times, it has reached the end of that event's requested playback.
You can edit the loop count after creating the event. From the Home screen, use the event's three-dot menu and choose Edit event; edit the event's date or time settings, including its loop quantity, then save. The event card displays the loop quantity. Before the scheduled start, verify that the saved event shows the count you intended rather than assuming that a changed control was saved.
A scheduled event airs automatically at the chosen time, but destination behaviour can differ. Restream cautions that some destinations, including TikTok or Instagram, may require you to click Go Live on the destination platform after Restream starts the broadcast. If your YouTube broadcast is not visible, check the event status and the destination's live status independently before changing the video loop.
For YouTube-focused planning, the YouTube Live streaming setup guide can help you think through the destination and broadcast workflow. Keep the event file and schedule distinct: a correctly configured loop count controls how many plays are requested, while the event timing and destination determine when that broadcast begins and where it is sent.
Work around playlists that cannot loop
Restream says playlists do not currently support looping as a playlist. Do not look for a repeat toggle that is not available. Instead, duplicate the videos in the playlist in the sequence you want, before it goes live. Restream documents a maximum of 40 video entries and a playlist length of up to 24 hours.
For example, if your sequence is A, B, C, arrange A, B, C, A, B, C to play that sequence twice. This is a finite schedule of entries, not an endlessly repeating playlist. Count the entries and estimate the total programme length before starting, so the playlist ends when you expect it to. Do not assume that adding a duplicate will extend an already-running playlist: Restream says playlist contents can be added, removed, or reordered only before it goes live.
If the desired sequence is longer than the available entries or duration, divide it into separate broadcasts or choose a different way to keep content going. That choice has operational trade-offs: multiple events require scheduling and checking, while a Studio source requires someone to manage the Studio session. If you need a transition between items, this article on adding a countdown between videos in a YouTube Live playlist loop discusses a separate playlist-building concern; it does not change Restream's playlist loop limitation.
Restream's playlist help says playlists are available with its Upload & Stream Marathon or Media add-on tiers. Check the current plan details in your account before building a workflow around them. If you need live and prerecorded segments together, Restream points to Studio video sources rather than a playlist. Choose based on the programme, not merely on the word “loop”: a playlist is a fixed sequence, whereas a Studio session gives you source controls during the broadcast.
Check whether the whole stream disconnected
A video ending and a live source disconnecting are different failures. If only the picture or audio from one file ends while the live broadcast remains online, investigate that media source or event setting. If YouTube shows the broadcast as offline, the player stops receiving the live feed, or the Restream session reports a lost input, investigate the connection instead. A media loop cannot restore an RTMP or SRT input that has gone offline.
Restream documents a separate disconnect-protection feature for RTMP/SRT source drops. It can play a fallback video for a selected 5, 15, or 30 minutes, and must be configured before going live. Restream lists the feature for Business or custom Enterprise plans. If the source reconnects during the selected window, the fallback stops and the live feed resumes. If it does not reconnect before the window ends, Restream says the destination streams end and a new stream must be started. The fallback is described as a 17-second video that loops during that configured window; this is not the same as looping your programme video.
Use the timeline to narrow down what happened. Note whether the file reached its end, whether the scheduled event reached its configured end, and whether the input source reported a disconnection. Check the YouTube live status and Restream event or Studio status, then inspect the sending computer, encoder, network connection, and stream key where relevant. Avoid changing several things at once: a repeat setting will not diagnose a network interruption, and a reconnection will not extend a finite event's loop count.
If you are streaming from an encoder, separate encoding load from network loss. A slow or overloaded machine can stop producing a stable input, while network interruption can prevent a healthy encoder from reaching Restream. For an encoder-specific symptom, see this guide to fixing FFmpeg reconnect errors on a continuous YouTube stream. Treat it as troubleshooting context, not proof that FFmpeg is the cause of a Restream event ending.
Do not conclude that a particular Restream bug or outage caused the problem from the symptom alone. The documented controls explain what each workflow can do, but they do not diagnose an individual account. Record the event type, approximate time, source status and what YouTube displayed; those details are more useful if you need to contact Restream support or check the service's current status.
Test playback before the next broadcast
Test the exact workflow you intend to use, not a similar-looking one. For Studio, load the same file as a source, enable Loop, and observe the end-to-start transition. For a scheduled event, save the loop quantity and review the event card. For a playlist, inspect the full order and count the duplicate entries before making it live. These checks catch configuration mistakes without relying on a long broadcast to reveal them.
For scheduled uploads, check the file itself as well as its repeat setting. Restream lists MP4, MOV, M4V, or MKV containers, H.264 video, AAC audio, and a keyframe interval of 2 as mandatory pre-recorded video requirements. It recommends Full HD 1080p at 30 or 60 FPS and constant bitrate where appropriate; its recommended bitrate depends on the destination platform. These are file and performance checks, not a substitute for setting the event's loop count.
Restream also recommends adding 15–20 seconds at the beginning and end of an uploaded video to give destinations time to process the incoming stream. That recommendation does not mean a loop control is disabled if the file lacks those extra seconds. Keep mandatory requirements separate from recommendations, and verify current upload guidance before re-encoding a file unnecessarily.
A useful test note is simple: record the workflow, source file, repeat setting, output resolution, and what happened at the end of playback. If the video repeats but the broadcast goes offline later, you have evidence that the media loop worked and can focus on the source connection. If the event ends after its configured plays, you can decide whether a longer finite sequence or a different workflow is needed.
For a 24/7 channel, also decide who or what will notice if the stream stops overnight. Restream's Studio controls and scheduled event settings solve different playback tasks; neither statement should be treated as a promise that a broadcast cannot disconnect. StreamNeo removes the need to leave your own computer running for a file-based 24/7 YouTube broadcast by letting you upload the video once and provide your YouTube stream key, with monitoring and automatic restarts if the broadcast drops.
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
Why does my Restream video stop after one play?
First identify whether the file is a Studio source, a scheduled single-video event, or part of a playlist. Enable Loop for a Studio source, set the event's loop count for a scheduled video, or duplicate playlist entries because playlists do not loop as playlists.
Can I make a Restream playlist repeat forever?
No. Restream says playlist looping is unsupported. You can duplicate entries in the desired order before the playlist goes live, subject to the documented 40-entry and 24-hour limits.
Does turning on Loop keep a disconnected livestream online?
No. Loop repeats a media source; it does not restore a disconnected RTMP/SRT input or restart an offline destination broadcast. Investigate the source connection separately, and configure Restream's distinct disconnect protection before going live if it is available to your plan.
Why is the loop option missing from a scheduled event?
The event loop count is a separate feature from Studio's playback control, and Restream currently lists Marathon and the Media add-on for scheduled-event looping. Check the account's current eligibility and event settings in Restream's Help Center, since plan names and feature availability can change.