To repeat a prerecorded video during a YouTube Live broadcast, set the loop in the encoder or media source, then send its output to YouTube using the RTMP(S) address and stream key. OBS documents looping for a file or playlist; Restream and StreamYard document custom RTMP destinations, but that does not establish that either service loops prerecorded media itself.
The distinction matters because a destination setting answers where the broadcast goes, not whether the source repeats. For a straightforward loop, configure and test the source first, then connect it to YouTube. Add a relay or production studio only if you need its other features.
Separate media looping from destination setup
Think of the setup as two separate jobs. The source job is to play a file or playlist and repeat it at the end. The destination job is to send the resulting live programme to YouTube. A tool can handle one job without handling the other.
In a typical encoder workflow, a local file is loaded into OBS. A loop setting tells the media source to start again after playback finishes. OBS then encodes the picture and sound as a live signal and sends that signal to YouTube’s ingest address using the stream key. The audience sees a live broadcast, even though the underlying material was recorded earlier.
A custom RTMP destination is about the receiving end of that signal. The service asks you to enter a server URL and stream key, which identify where the broadcast is sent and which stream it belongs to. That input does not, on its own, select a video file, create a playlist, or tell a clip to start over. Check the service’s documentation for each capability separately.
This also helps when comparing unlike tools. OBS is an encoder with documented media-source options; YouTube Live supplies ingest details. Restream and StreamYard document custom RTMP destination workflows. Those descriptions are not evidence that their custom destination feature is a prerecorded-media loop feature.
For a one-file devotional stream, for example, you might use OBS to repeat a bhajan video and send its output directly to YouTube. For a changing playlist, you might prepare a set of clips and use a source that supports playlist playback. In either case, the repeat behaviour belongs at the source end of the chain. The guide to rotating playlists on a 24/7 YouTube channel covers the related question of how to structure a changing sequence rather than replaying a single file.
Choose OBS Media Source or VLC Video looping
OBS documents two relevant options: Media Source for a media file, and VLC Video for a playlist. The simplest choice depends on what you need to repeat. If you have one prepared video, Media Source is the direct route. If you have several files that should play in sequence, VLC Video can handle a playlist and restart it after the items have played.
For a single file, add a Media Source in OBS and select the file. Enable its Loop option so playback repeats when it reaches the end. OBS’s documentation describes Media Source as available on Windows, macOS and Linux. The source is local to the computer running OBS, so the file must remain accessible there while you stream. Moving or renaming it after configuration can break the source path.
For multiple files, OBS’s VLC Video source can play a playlist. VLC must be installed for this source to work. Add the files in the order you want, check the option to restart playback after the playlist runs out, and make sure the selected files remain available to the computer. OBS’s Media Sources documentation explains the source options and their controls.
A playlist and a loop are not quite the same thing. The playlist decides what plays and in what order; the restart option decides what happens when the final item ends. If you want a sequence of morning prayers followed by an evening programme, check that the order is intentional before enabling repeat. If you want only one uninterrupted visual and soundtrack, one file with looping may be easier to inspect.
There are practical trade-offs. A local OBS source gives you direct control over file selection and playback, but the computer and encoder must remain running for the broadcast to continue. A file stored on a computer that sleeps, disconnects or reboots is no longer a dependable source. Readers weighing a local computer against hosted approaches can also consider the constraints described in whether a free-tier VPS can host a nonstop prerecorded stream; the important point is to account for the complete operating arrangement, not just the loop checkbox.
Before sending a long stream, watch at least one full transition from the end of the media back to its beginning. Check the picture, sound, and whether the scene cuts or pauses in a way you find acceptable. A loop can be technically functioning while an abrupt musical cutoff or a blank frame still makes the result unsuitable for viewers.
Set up the YouTube RTMP(S) destination
Once the source repeats correctly, configure the encoder’s destination. In an encoder such as OBS, YouTube may be available as a service preset; if you need to enter the ingest information manually, use the server URL and stream key shown for the broadcast in YouTube Live Control Room. Treat them as a matched pair and copy them carefully.
YouTube documents RTMPS as RTMP sent over TLS/SSL, which encrypts the connection. Prefer the RTMPS address when your encoder or relay supports it. Plain RTMP is not the same security choice: do not assume the two protocols provide equivalent protection simply because both can carry a stream.
The configuration fields vary by tool, but the concepts are consistent. The server or URL field receives YouTube’s ingest address; the key field receives the key associated with the broadcast. Avoid pasting the key into a public note, screenshot, or message. Anyone with access to it may be able to send a stream to the associated destination, so handle it as a credential.
When using a custom destination in a relay or studio, its form may use different labels, but you are still providing the receiving platform’s URL and key. Check whether the service expects a full RTMPS URL, whether it offers a service preset instead, and whether a custom connection changes other features. Do not guess at a port, path, or key format where YouTube supplies exact values.
The YouTube Help guidance on encrypting a stream with RTMPS explains the secure ingest option. If you are testing the output before a public broadcast, inspect the encoded picture and sound rather than relying only on a successful connection indicator. The walkthrough for inspecting an RTMP stream locally before sending it to YouTube is useful when you need to diagnose the signal separately from YouTube’s event setup.
Copy the URL and stream key from Live Control Room
Open YouTube Studio and go to the Live Control Room for the broadcast you intend to use. The event’s stream settings provide the server URL and stream key. If you are creating a new scheduled event, make sure you are looking at that event’s settings rather than copying details from a different broadcast or an old setup note.
Copy the values directly into the encoder or destination form. Avoid retyping long strings: a missing character can prevent the connection, while using a key from another event can send the encoder to the wrong place. Keep the key private after setup. If it has been exposed, use YouTube’s current controls to manage or replace it, and update the encoder to match.
YouTube’s settings may present more than one ingest choice or connection detail depending on the event and account workflow. Use the values displayed for the event you are configuring, rather than assuming an address from an old tutorial still applies. This is especially important if you switch between a local encoder and a relay: each sending tool needs the same correct destination details for that event.
If you use YouTube’s own integration in a relay, the connection path may be different from manually entering a custom RTMP destination. For an existing scheduled YouTube event, Restream documents both its YouTube integration workflow and a custom RTMP route. The relevant decision is whether you need to preserve that event workflow and whether the relay’s chosen route supports the features you rely on. A working connection test is not a substitute for checking the event title, visibility and intended destination.
Compare custom RTMP destination support
The documentation reviewed establishes custom RTMP destination support for Restream and StreamYard, but does not establish that either one repeats prerecorded media. Their documented feature is destination configuration: entering a platform’s server URL and stream key. Compare them on that basis, and look elsewhere in the setup for a documented media loop.
| Tool or service | What the cited documentation establishes | What to verify for a repeating broadcast |
|---|---|---|
| OBS Studio | Media Source can loop a file; VLC Video can restart a playlist. | The source file or playlist is available, and the computer remains running. |
| YouTube Live | Live Control Room provides ingest details; YouTube documents RTMPS. | You have copied the current event’s URL and key and selected the intended event. |
| Restream | Custom RTMP channels accept a URL and key; an existing YouTube event workflow is documented. | The source loop is configured elsewhere. Check whether the custom route suits the event workflow you need. |
| StreamYard | A custom RTMP destination accepts a server URL and key. Its documentation also describes limitations for custom destinations. | The source loop is configured elsewhere; check which destination features are unavailable in that workflow. |
Restream’s help documentation says custom RTMP channels require a paid plan, as listed on Restream’s site in October 2026. It also documents a route for streaming to an existing YouTube event, either through its YouTube integration or by adding the event as a custom RTMP channel. These are destination workflows; the cited pages do not show Restream itself looping the prerecorded source. See Restream’s custom RTMP instructions and its guide to streaming to an existing YouTube event for current workflow details.
StreamYard likewise documents adding a custom RTMP destination with a server URL and stream key. Its help page says custom RTMP is available on a paid plan, as listed on StreamYard’s site in October 2026, and notes limitations for custom destinations. Check the page for the current feature restrictions before building your workflow around it. The cited documentation does not establish that StreamYard loops prerecorded media. Its custom RTMP destination guide is the appropriate source for the destination setup itself.
If you only need one looping feed to YouTube, a relay may add another configuration step without solving the media-repeat requirement. If you also need a relay’s multistream or routing workflow, evaluate that benefit separately and confirm that your chosen route can reach the scheduled event as intended. Do not infer a loop feature from the words “custom RTMP”.
For a stream that needs to run while your own computer is off, the source and operating arrangement need attention as well as the destination. StreamNeo can remove the specific burden of keeping a local computer running by taking an uploaded video and broadcasting it to YouTube; it is YouTube-only, so check that this fits your destination before choosing it. It does not change the underlying distinction: confirm the media and channel are ready, and verify the current YouTube event settings.
Verify the media repeats before going live
A loop setting should be tested as behaviour, not merely noticed in a menu. Start OBS with the intended media source, wait for playback to finish, and observe whether it begins again. For a playlist, confirm both that the items play in the planned order and that the final item returns to the beginning. Listen through the transition as well as watching it.
Check that audio does not disappear, double up, or start at an unwanted level after the restart. If the file contains an opening silence or a long closing tail, the repetition may create a pause that feels like a fault even when playback is correct. Trim or replace the source file if the transition is distracting; do not assume the destination service will repair it.
Then test the YouTube connection using the event you intend to broadcast. Confirm that YouTube receives the signal, that the picture and sound are present, and that the event is the correct one. If you are using a custom RTMP relay, test its destination separately from the source loop so you know which part to troubleshoot if the preview fails.
Finally, plan for the conditions after the test. A local OBS setup depends on the computer, power, network connection and media path staying available. For a 24/7 broadcast, consider what happens after a restart, a lost connection, or a file moving; a setup that works for a short check may not recover unattended. The troubleshooting advice on keeping a YouTube stream running when OBS loses its media source can help you think through that failure mode.
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 a custom RTMP destination make a video loop?
Not by itself. A custom destination specifies where an encoder’s output is sent, usually with a URL and stream key; configure repeat playback in a source or another tool that explicitly documents looping. The cited Restream and StreamYard custom-destination pages do not establish prerecorded-media looping.
Can OBS loop one file and a playlist?
OBS documents Media Source for looping a local file and VLC Video for playlist playback that can restart after the playlist ends. VLC must be installed to use the VLC Video source. Test the end-to-start transition before relying on either setup for a long broadcast.
Should I use RTMP or RTMPS for YouTube?
Use RTMPS when the sending tool supports it. YouTube describes it as RTMP over TLS/SSL, which encrypts the connection, so it is not accurate to treat plain RTMP and RTMPS as identical security choices.
Do Restream and StreamYard support custom YouTube destinations?
Both document custom RTMP destination support using a server URL and stream key, with paid-plan requirements described on their help pages. Check those pages for current terms and destination limitations, and configure the media loop separately.