VLC can repeat a showroom video or a list of clips, but repetition is only the playback part of a YouTube Live setup. You also need an encoder that sends YouTube a compatible live feed, and the connection must stay active as VLC moves between items.
The important distinction is that a VLM loop controls which media VLC plays; it does not by itself establish a YouTube broadcast. VideoLAN documents loop for repeating a broadcast's input list and, in a VLC Desktop 3.0 example, uses sout-keep to help streaming continue when a playlist item ends. Treat that example as a starting point to verify, not as a guarantee of seamless YouTube transitions.
Separate VLC playback from YouTube ingestion
Think of the workflow as two jobs. VLC reads and repeats the showroom media. An encoder packages the resulting audio and video and sends them to YouTube using an ingest method supported by both the encoder and the settings in your Live Control Room. If either job stops, the viewer may see a frozen picture, a disconnected live feed, or an unexpected end to the presentation.
VLM is VideoLAN's mechanism for defining broadcasts, their inputs and their output. Its loop option concerns the input list: after the last input finishes, the list starts again. YouTube's ingest documentation addresses a separate question: how a compatible encoder connects to a live event. The documentation does not establish that every VLC version can publish directly to YouTube using today's RTMPS settings, nor does it document a complete VLM-to-YouTube showroom workflow.
So answer “Can VLC stream a video on repeat to YouTube Live?” carefully: VLC can provide repeat playback, but you must verify that the outgoing encoder path supports YouTube's chosen protocol and remains connected across item changes. If you are weighing a local machine against a hosted workflow, the practical difference is who must keep playback and encoding available; this guide to streaming prerecorded videos from a Mac considers the local-computer side of that decision.
Prepare the showroom video list
First decide whether your channel needs one long file repeated or a sequence of separate clips. One file is simpler to reason about: you can check its opening, ending and restart point in one place. A sequence is useful when the showroom needs a changing set of product demonstrations, offers or room views, but every boundary becomes something to test.
Make a written playlist in the order you want viewers to see it. Give files distinct names and keep a separate copy of the list so an edit does not silently change the running order. Check that each file opens and plays to its end in the VLC version you will use. Listen to the start and end of audio, and look for black frames, abrupt changes in volume, aspect-ratio shifts or a slate that is not meant to appear between clips.
Consider the experience of somebody joining part-way through. A viewer may arrive in the middle of a product demonstration and wait for the next useful moment, so make the sequence understandable without relying on a one-time introduction. If a price, promotion or availability statement can become stale, decide how the file will be reviewed and replaced. A loop repeats the content, including anything that has become outdated.
Keep the media in a stable location and avoid renaming or moving files after you have configured the list. VLC needs to find each input when the broadcast starts and when it returns to that item on a later pass. Local playback also means the computer, its power and the network connection remain part of the operating arrangement. If you are calculating the cost of leaving a small computer running, this Raspberry Pi electricity guide can help frame that separate decision without changing the need to test the broadcast itself.
Configure VLM loop behaviour
VideoLAN's VLM reference describes a broadcast with one or more inputs and a loop setting. When playback reaches the end of the final input in a loop-configured broadcast, the input list starts again. This is the part that addresses “How do I loop a playlist in VLC?” It tells VLC what to play next; it does not say that YouTube has accepted a live feed.
Use the VLM reference and the documentation for your installed VLC version when building the broadcast definition. Syntax, available controls and interface details can vary between releases, so do not assume a command copied from a guide for a different version will work unchanged. In particular, check that the definition identifies the intended files, includes the full list in the right order, and applies loop behaviour to the broadcast you are actually starting.
Test repetition before involving YouTube. Start the broadcast locally or use a suitable test receiver for the output you have configured, and confirm that the first item plays, each later item follows, and the list returns to its first item after the last one. Watch the moment of restart rather than just confirming that the VLC window still appears active. If the input list is wrong or a path cannot be opened, a configured loop cannot repair the missing media.
Do not treat a VLM example as a universal recipe. The output configuration is tied to the intended receiver and encoder path. A local demonstration can prove that VLC repeats its inputs while leaving unanswered whether the same output is accepted by YouTube or whether the transition remains healthy after encoding.
Use sout-keep to maintain playlist streaming
VideoLAN's VLC Desktop User Documentation 3.0 includes a VLM playlist example that uses sout-keep. The example explains its purpose as preventing the stream from breaking when a playlist item ends. That makes the concept relevant to a multi-clip showroom: the media item can change while the streaming output is intended to remain active.
Keep the scope of that example clear. It demonstrates a local HTTP stream receiver, not YouTube ingestion. It does not prove that every VLC release uses the same syntax, that a YouTube-compatible RTMPS connection will remain open at a clip boundary, or that there will be no visible or audible gap. The loop controls repetition of the input list; sout-keep concerns keeping the streaming output from breaking as playlist items change. They address related but distinct parts of the workflow.
Use the example as a reference to understand the idea, then verify the appropriate configuration against your VLC version and the protocol your encoder must send. Where VLC does not provide the outgoing encoder path you need, use an encoder documented to support the protocol selected in Live Control Room and connect the repeated playback to it through a method you have independently verified. The reviewed documentation does not specify a particular bridge application or a validated wiring method between VLM and another encoder.
For a channel that must keep running while your own computer is off, a local VLC playback-and-encoding arrangement leaves that machine's availability as an operating concern. StreamNeo addresses that particular burden by taking an uploaded video and running it as a YouTube live stream without relying on your computer to stay on. It is YouTube-only; it does not change the need to prepare the file and channel correctly.
Get the current RTMPS URL and stream key
For RTMPS, follow YouTube's current RTMPS setup instructions from the channel's Live Control Room. YouTube describes RTMPS as RTMP carried over TLS/SSL and instructs creators to use an encoder that supports RTMPS. Do not copy a server address from an old tutorial into a permanent checklist: use the URL shown for your event and current settings.
In Live Control Room, open the stream settings and reveal or copy the RTMPS server URL as directed there. Copy the stream key into the encoder's credential field. Treat it like a password: do not put a real key in a screenshot, a public command example, a shared playlist file or a note visible to showroom staff who do not need it. If you share configuration for troubleshooting, replace the key with a clear placeholder first.
The encoder must support RTMPS; VLC's ability to play the file or repeat a playlist is not evidence that its configured output supports the protocol. If the connection fails, compare the protocol and server address in the encoder with the current values in Live Control Room, then follow YouTube's troubleshooting advice for the error. The stream key error guide may help you think through credential mistakes, but the current official instructions should take precedence over any older walkthrough.
YouTube also documents HLS as another ingest route. It is not a loop feature, and it requires an encoder with HLS support and compliance with YouTube's HLS-specific requirements. YouTube notes that HLS has higher latency than RTMP because it sends segments rather than a continuous stream. For HLS, its documentation specifies TS segments of 1–4 seconds and a rolling playlist with no more than five outstanding segments, alongside other format and delivery requirements; use the official HLS requirements rather than trying to infer them from a VLC loop example. Choose the route your encoder supports and your use case can accommodate.
Send and preview the encoded feed
Before making the event public, run a controlled test using the appropriate private, unlisted or other available test workflow for your channel. Start the VLC broadcast and the outgoing encoder path, then look in Live Control Room for the incoming preview. This checks more than whether VLC plays: it lets you inspect what YouTube is receiving after encoding.
Check picture shape, orientation, visible detail and any cropping of product text or labels. Listen for audio even if the showroom is meant to be quiet; an unexpected source, hiss or sharp level jump can become tiring during a long presentation. Confirm that the preview starts, remains present through a clip change and continues when the list returns to its first item. The aim is to verify the whole path, not to infer success from a local VLC window.
If the preview does not appear, work from the boundary between stages. Confirm that VLC can play the chosen input and that its configured output is active. Then confirm that the encoder receives that output and that its protocol, current YouTube URL and key are correct. Avoid changing several settings at once: a single change followed by another preview gives you a better chance of locating the failing stage.
A successful preview is useful evidence for the setup you tested, not a guarantee that the system will remain available overnight. Keep a written start-up checklist with the file location, playlist order, version-specific settings, encoder protocol and a reminder to check the current stream key securely. Do not include the key itself in a checklist that might be copied or shared.
Test item transitions and monitor health
The most revealing test is often the point where one clip ends and another begins. A playlist can appear fine while the first item is running and still interrupt the outgoing feed when VLC changes inputs. VideoLAN's sout-keep example is relevant because it addresses output continuity at item ends, but your own end-to-end test must establish what happens with your files, VLC version and encoder path.
Watch at least one full pass through the intended list, including the final-to-first transition, before scheduling the public event. If the sequence is long, test each boundary during setup rather than assuming that all files behave alike. Note whether the preview freezes, disappears, changes aspect ratio, loses audio or shows an unintended gap. If there is a problem, first determine whether VLC stopped playback, the stream output restarted, or YouTube stopped receiving the feed; those are different symptoms and call for different checks.
During an operating session, check the Live Control Room preview and status when starting, after a playlist change and when responding to a report that the picture has stopped. If the channel relies on a local computer, include power, network and machine sleep settings in the operational checklist. A loop only repeats while the playback and encoding chain remains available.
If you are designing the list so that a change of programme does not end the live event, the boundary problem is similar to keeping a 24/7 stream active while changing episode titles: distinguish a change in the content from a stop in the live feed. Keep notes about which transition you observed and under what settings, so a later update to VLC or the encoder prompts a fresh test instead of relying on memory.
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 VLC stream a video on repeat to YouTube Live?
VLC can repeat media, but that alone does not establish a YouTube Live broadcast. You need an outgoing encoder path compatible with the ingest protocol shown in Live Control Room, and you should verify that path at clip changes.
Will the live stream stop when a video ends?
It depends on how playback and streaming output are configured. VLM loop behaviour restarts an input list, while VideoLAN's VLC Desktop 3.0 example uses sout-keep to help keep streaming when an item ends; test your version and full YouTube path rather than assuming either setting guarantees continuity.
Does VLC support YouTube RTMPS?
The sources here do not establish that a particular VLC version directly supports YouTube's current RTMPS ingest. Check the output capabilities and documentation for your installed version, and use an encoder documented to support RTMPS if that is the selected route.
Is HLS another way to send a live feed?
YouTube documents HLS as an ingest option for an encoder that supports it and meets the platform's requirements. YouTube says it has higher latency than RTMP because it delivers segments, so check the current HLS instructions before choosing it.