To loop a recorded trade show booth demo on YouTube Live, send it through an encoder such as OBS: use a Media Source with Loop for one clip, or a VLC Video source with Loop Playlist for several. You also need to create an encoder stream in YouTube Studio, connect OBS with the stream URL and key, and check the preview before selecting Go live.
The loop controls repeat media; they do not ensure the broadcast stays online indefinitely. Test the playback and connection before the event, and plan who will monitor the stream and respond if the encoder, computer or network fails.
Check that your channel can go live
Before preparing the media, confirm that live streaming is available on the YouTube channel you will use. YouTube says a channel needs to be verified and must not have live-streaming restrictions in the past 90 days. Check the channel’s current status in YouTube Studio rather than assuming an older successful broadcast means this event is ready.
If this is the first time the channel has enabled live streaming, YouTube says activation can take up to 24 hours. That is a reason to check well before the trade show, not on the morning the booth opens. YouTube’s live-streaming tips explain eligibility and preparation. If verification is the sticking point, see our guide to YouTube phone verification errors.
Think about the purpose of the broadcast as well as access. A public stream can be found by viewers, while an unlisted stream is accessible to people with its link; private access has different sharing constraints. Choose the setting that fits whether the demo is intended for passers-by, customers who have the link, or a closed audience. Do not rely on an event link as an access control without checking the current YouTube visibility settings.
A scheduled stream can give viewers a page to visit before the broadcast begins. It also gives you time to confirm the title, description, thumbnail and visibility. If you are not ready to publish a scheduled event, a test stream with an appropriate visibility setting can help validate the encoder without directing the public to unfinished material.
Add one demo as an OBS Media Source
For a single recorded demo, the straightforward route is OBS Studio’s Media Source. Open OBS, choose or create the scene you want to use, then add a Media Source and select the local video file. Give the source a useful name such as “Booth product demo” so you can identify it later if the scene contains other elements.
Enable the source’s Loop setting. When playback reaches the end of the file, OBS starts it again. This repeats the file; it does not repair a broken or unavailable media file, and it does not reconnect a dropped YouTube broadcast. OBS documents Media Source controls in its Media Sources guide.
Check how the video fits the scene canvas. If the recording is widescreen but your intended stream layout includes a logo, title or call to action, arrange these elements deliberately and confirm that none obscure product details. A booth recording can include small labels or interface text that is easy to crop accidentally. Watch the preview at the same canvas dimensions you intend to broadcast.
Use a file stored locally on the computer running OBS, not a removable drive that might be disconnected during the event. Keep a separate copy of the original recording somewhere safe. Before starting OBS, open the file and confirm it plays from beginning to end with its expected audio. A corrupted or incomplete file can loop perfectly and still deliver a poor demonstration.
For a seamless-looking repeat, consider the edit as well as the OBS setting. If the last frame cuts abruptly to the opening logo, that transition will happen again every time the clip finishes. You may want a short end card or an edit that makes the restart feel intentional. This is production judgement rather than a guarantee from the software; watch the actual transition in the OBS preview.
Choose between one clip and a playlist
The choice depends on what a booth visitor should see. A single Media Source is easiest when one polished overview contains the whole message. A playlist is useful when you have distinct product demonstrations, language versions or feature clips to rotate. These are not interchangeable controls: Loop on a Media Source repeats one file, while Loop Playlist repeats a sequence in a VLC Video source.
| Need | OBS source | Repeat control | Main check |
|---|---|---|---|
| Repeat one recorded demo | Media Source | Loop | Inspect the ending-to-opening transition |
| Rotate several recordings in order | VLC Video | Loop Playlist | Confirm files and their order in the list |
For a playlist, plan the sequence before you add it. For example, a booth might show a short product overview, then a feature demonstration, then a customer-use case, and return to the overview. Give filenames clear labels and arrange them in the intended order. If the videos contain different aspect ratios, inspect each one in the scene so one does not appear unexpectedly smaller or cropped.
The first clip matters because viewers may join at any point. Do not assume an audience has watched the sequence from the beginning. Each segment should make sense on its own, or the title card and transitions should establish context. If the purpose is to explain a product feature, consider adding a visible label to each clip rather than relying on spoken introductions that a viewer may miss.
If OBS stops when a playlist ends, check the source’s playlist and repeat options instead of assuming the YouTube stream itself is at fault. A loop configured on the wrong source will not give the sequence you expect. Our guide to an OBS stream stopping at the end of a playlist covers that specific failure mode. A longer-running channel has other scheduling concerns too; the playlist schedule guide explains how to think beyond one repeating booth sequence.
Install VLC before adding a VLC Video source
OBS’s VLC Video source depends on VLC being installed on the same computer. If VLC is absent, or its architecture does not match OBS, the VLC Video option may not appear or may not work as expected. OBS specifically notes that 64-bit OBS requires 64-bit VLC. Install the appropriate VLC version first, then restart OBS if needed and look for the VLC Video source in the source-add menu.
This dependency is worth checking early, particularly on a booth laptop that has been locked down or prepared by another team. Do not build the whole scene around VLC Video before confirming it is available. If installing VLC is not practical, you can instead use separate Media Sources for clips and manage which one is visible, though that changes how you operate the sequence and requires rehearsal.
When you create the VLC Video source, add the files to its playlist and arrange them in the intended order. Enable Loop Playlist to repeat the whole list. Play the source and verify that each file loads, that it advances to the next clip, and that it returns to the first one after the final item. A missing file or a path that only works on another user’s computer can interrupt the presentation.
Keep playlist files in a stable folder on the streaming computer. If you move a file after adding it, OBS may no longer find it at the recorded location. Before the event, reopen the project or scene on the actual computer and check the whole sequence there. A playlist that worked on a staff member’s editing workstation is not proof that the booth machine has access to the same files.
Create or schedule the encoder stream in YouTube Studio
In YouTube Studio, open Go Live and create an encoder stream, or schedule one for the event. YouTube’s encoder setup guide describes the process and the information used to connect software encoders. For a scheduled event, YouTube recommends configuring the encoder at least two hours beforehand and starting it at least 15 minutes before the scheduled time. Those are preparation recommendations, not a promise that a stream will be ready without testing.
Open the Live Control Room stream settings and copy the stream URL and stream key into OBS’s stream settings. Treat the key as a credential: do not show it on the booth display, include it in a public screenshot or send it to people who do not need to operate the broadcast. YouTube recommends RTMPS, the encrypted form of RTMP; use the RTMPS URL shown in the Live Control Room settings. Its RTMPS instructions explain the connection option.
The encoder needs output settings that YouTube accepts and that suit your source and upload connection. YouTube’s current encoder settings documentation lists supported video and audio formats and gives recommendations for settings such as bitrate and keyframe interval. Choose settings based on the resolution and frame rate of the demo, then test rather than copying values blindly: a high-resolution source does not help if the available upload connection cannot sustain the outgoing stream.
You do not necessarily need dedicated streaming hardware for a local-file demo if a software encoder on a suitable computer meets the task. Hardware can make sense if the event has operational requirements that a computer-based setup cannot meet, but it is not an automatic requirement for repeating a video. Decide based on the equipment already available, the required output and who can recover the setup if something stops.
Once OBS has the stream details, start streaming from OBS so YouTube receives the encoder feed. Starting the encoder does not necessarily mean the public broadcast has begun: check the Live Control Room and use its Go live control when you are satisfied with the preview and event settings. Keep the distinction clear for anyone helping at the booth, especially if the stream is scheduled.
Preview picture, sound and sequence before going live
Wait for the stream preview in Live Control Room. Confirm that the picture is present, correctly framed and moving, and that audio is audible at an appropriate level. Then compare the preview with OBS: confirm the intended source is visible, the overlay is legible, and no desktop notification or unrelated window has appeared. Only proceed to Go live after the checks match what viewers should see.
Do not check only the first few seconds. For a single file, watch the end and the return to the opening. For a playlist, let it pass through every item and verify the order, transitions and final return to the start. YouTube recommends checking the preview before going live and testing with audio and movement similar to the event. If the booth demo is mostly still screens, use a section with real motion to confirm the stream is not frozen.
Listen on a second device if possible. The OBS audio meter can move while the actual stream audio is muted, too quiet or distorted. Check the captured sound in YouTube’s preview, and make sure music, product audio and narration are balanced. If the demo is meant to run silently, verify that there is no unexpected background audio from the computer or room.
Before the event, test for the duration you expect to operate, not just long enough to see that a connection starts. That gives you a chance to notice a file that stops, an audio track that ends early, a laptop that sleeps, or an unreliable upload connection. YouTube advises streamers to monitor stream health and audio and video quality while live; a preview is a useful gate, not a substitute for monitoring.
Have a named person responsible for the stream during the event. Agree what they should check if the image freezes or the broadcast drops: OBS status, Live Control Room status, local file playback and the network connection. A loop only controls media playback; it cannot keep a failed encoder or internet connection online. For sustained broadcasts, the advice in our guide to preventing buffering in a worship stream is relevant to thinking about connection stability, even though a booth event has a different programme.
Also check that you have permission to use the video, logos, music and any people shown in the recording. YouTube’s stream settings documentation flags rights considerations for stream trailers, but that is not a complete determination of rights for a trade show demo. Review the relevant permissions for your materials and check YouTube’s current rules rather than treating a successful preview as a rights clearance.
If nobody can remain at the booth computer, plan how an operator will be alerted and regain access if something fails. A cloud-based route can remove the need to leave your own computer running for the broadcast; StreamNeo addresses that specific operational burden by taking an uploaded video and running it as a YouTube live stream. It remains YouTube-only, and you still need to prepare the file, connect the channel and make an operational plan appropriate to the event.
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 OBS loop a video after it reaches the end?
Yes. Add the file as a Media Source and enable Loop. Check the transition from the final frame back to the beginning in the preview, because the setting repeats playback but does not smooth an abrupt edit.
Can I loop several booth demo clips in order?
Yes. Add them to an OBS VLC Video source playlist and enable Loop Playlist. VLC must be installed for that source, with its architecture matching OBS; test every file and the full sequence on the computer that will run the event.
Does pressing Start Streaming in OBS make the event public?
Not necessarily. OBS sends the encoder feed to YouTube, where you should check the Live Control Room preview and event settings before selecting Go live. For a scheduled event, follow the controls shown for that stream in Studio.
Will a loop keep the broadcast online indefinitely?
No. Looping repeats the media, not the encoder connection or internet service. Test for the planned duration, monitor stream health while live, and have someone ready to respond if playback, OBS or the network fails.