A YouTube product demo will not keep playing simply because the live broadcast is still open. Send the demo through an encoder such as OBS Studio, turn on Loop for its Media Source, and keep the encoder sending content for as long as the broadcast should continue.
The important distinction is that looping the file repeats the programme, while the encoder maintains the live feed. If the file ends and the source is not set to loop, or if OBS stops sending, the YouTube stream can stop even though your original broadcast plan was longer.
Why the broadcast stops when the file finishes
A prerecorded YouTube Live broadcast has two separate parts. The first is the media: your product demonstration, screen recording, voice-over, slides, or a sequence of clips. The second is the live connection from the encoder to YouTube. YouTube receives what the encoder sends; it does not take a finished file and automatically repeat it for you.
When a single video reaches its final frame, the result depends on how the source and encoder are configured. A media source may remain present in the scene but stop producing new frames. An encoder may still be open but sending a frozen frame, silence, a blank scene, or no useful content. In another setup, the encoder may stop altogether. These are different failure modes, but they can all look to a viewer like the stream has ended.
The fix for a repeating product demo is therefore made in the encoder. You configure the media source to start again when playback completes, then keep OBS connected and streaming. YouTube is the destination for that feed, not the part of the setup that repeats the file.
This also explains why a file that plays correctly in a normal media player is not necessarily ready for an always-on stream. A media player can close when playback finishes. An encoder scene needs a source that continues producing a programme. If the stream should show the same demonstration again, the repeat instruction must be attached to the source used by OBS.
If your wider concern is a dropped connection rather than a finished file, treat that as a separate problem. A loop does not reconnect a broken broadcast. You may need a recovery plan such as the one described in how to restart a YouTube live stream automatically when it disconnects.
Add the product demo as an OBS Media Source
Open OBS Studio and create or select the scene that should show during the live broadcast. In the Sources panel, add a Media Source. Give it a clear name, such as Product demo, so that you can identify the correct item later if the scene contains a logo, background, camera, or other overlays.
In the Media Source properties, choose the local video file. The file should be available to the computer running OBS for the whole broadcast. Do not select a file from a removable drive that may be disconnected, or from a folder that will be renamed or moved before the stream begins. OBS can only replay a source it can still access.
The Media Source is suitable when one complete file should repeat. It keeps the arrangement straightforward: the scene contains the demo, and the source controls what happens at the end. You can still add other sources around it, such as a lower-third, a product logo, a background, or a small camera view.
Check the source properties before you close them. The setting you need is named Loop. OBS documents Media Source controls, including the option to replay the file after playback completes, in its Media Sources documentation. The option is not the same as restarting the whole scene or starting a new YouTube broadcast.
For several prerecorded segments, consider the content structure before choosing the source. A single Media Source with one long file is easier to inspect and test. If the channel should rotate through multiple clips, OBS also supports a VLC Video source with a loop playlist. That route requires VLC to be installed, so it introduces another dependency that should be tested on the computer used for the broadcast.
A playlist can be useful for a shop demonstrating several products, for example. It can also make it less obvious to viewers that the channel is repeating one clip. It does not remove the need to keep OBS connected to YouTube. The playlist is still only the content being sent into the encoder.
Turn on Loop and verify the replay
Select the correct Media Source and enable Loop. OBS lists this option as off by default for a Media Source, so do not assume that adding a file has enabled repetition. Save the setting, then watch the scene long enough to see what happens at the end of the file.
Do not rely only on the file duration shown in an editor or media player. Play the source in the actual OBS scene. Watch the last few seconds, the transition back to the beginning, and the first few seconds of the next pass. A product demo may have a fade to black, an end card, or a spoken closing line that makes the repeat feel abrupt. That is a content and presentation issue rather than proof that the stream has failed.
Check the audio at the loop point as well. Listen for a sudden cut, a repeated sentence, a click, or a silence that is longer than intended. OBS can repeat the source, but its Loop setting does not promise that every file will transition seamlessly in both picture and sound. If the change feels distracting, edit the file, alter the scene, or use a sequence of shorter segments and test again.
While previewing, confirm that the source does not disappear from the scene when it reaches the end. The image should continue into the next pass, and the audio meter should behave as expected. If the video stops, return to the properties for the specific Media Source used in the live scene. It is common to enable Loop on one source while OBS is actually displaying another copy in a different scene.
A useful test has three stages:
- Start with the demo in OBS and confirm that it plays from the beginning.
- Leave it running through the end and verify that it starts again without manual input.
- Keep OBS streaming while the second pass begins, then check the YouTube preview and watch page.
Testing the source alone is not enough. The file may loop in OBS while the YouTube connection has a separate issue. Conversely, YouTube may show a healthy connection while the source has stopped producing the intended programme. Test both parts of the chain.
For a multi-clip channel, test the entire playlist rather than checking only one file. Confirm the order, filenames, audio levels, aspect ratios, and behaviour when the final item finishes. A playlist that repeats correctly is still not a substitute for monitoring the encoder feed.
Connect OBS to YouTube Live
In YouTube Studio, create or schedule an encoder-based live stream. YouTube provides a stream URL and a stream key for the encoder connection. Enter the required connection details in OBS under the stream settings, then select the intended scene before starting the feed.
Treat the stream key as a credential. YouTube describes it as the information that tells YouTube where to accept the feed, so do not publish it in a screenshot, description, tutorial, or public support request. If you think it has been exposed, replace or reset it in YouTube Studio before using the stream again. The YouTube encoder setup instructions cover the connection workflow and the steps for ending an encoder stream.
Before going live, use the Live Control Room preview. YouTube recommends checking the preview and monitoring audio and video quality during the event. Look for the actual product image, readable text, correct cropping, and audio that is neither missing nor unexpectedly loud.
YouTube's start and stop settings can affect how a reused stream behaves. If you reuse an earlier configuration, check the auto-start and auto-stop choices rather than assuming they are unchanged. Those settings control how the YouTube broadcast responds to the encoder; they do not configure the Media Source to repeat.
Start the stream from OBS only when the scene and connection details are ready. Then confirm the status in YouTube Studio and, where practical, open the public watch page in a separate browser or on another device. The watch page confirms what viewers receive, not merely what appears in the OBS preview.
If the live event is not discoverable, do not confuse that with a loop problem. A stream can be receiving a repeating feed while its visibility, scheduling, or watch-page settings need attention. The checks in your live stream is live but nobody can find it address that audience-facing situation separately.
Keep the encoder sending the feed
Once the stream is live, OBS must remain open, connected, and configured to send the scene. The Media Source Loop setting handles the repeated product demo. OBS handles the encoder feed. YouTube receives that feed and presents it as the live broadcast.
Keep the computer awake if it is running OBS locally. Prevent sleep, hibernation, automatic restarts, and updates from interrupting the programme during the intended run. Also make sure the local video file remains available and that another application will not take exclusive control of the audio or video device.
Watch the status indicators in OBS and YouTube Studio. A looped source can hide a problem if you only glance at the picture: the same frame may remain on screen while the connection has stopped updating. Check that the encoder is still sending, that YouTube shows the stream as healthy, and that the public watch page continues to receive changing video and audio.
For a long-running channel, decide who will respond if the feed fails. A person can check the broadcast at agreed times, or you can use a setup with monitoring and restart behaviour designed for unattended operation. The key is to separate two needs: repeating the content and recovering from a connection or computer failure.
If the computer must stay on all night only to keep a prerecorded demo moving, a cloud-based workflow can remove that particular local-computer requirement. StreamNeo lets you upload the video, enter your YouTube stream key, and keep the broadcast running while your computer is switched off, with monitoring and automatic restart if the feed drops. It remains your responsibility to choose appropriate content and check the current YouTube requirements.
This does not make the stream immune to problems. Review the actual broadcast, check the source file, and confirm that the YouTube stream is receiving the intended scene. For another view of the local-computer trade-off, compare the practical options in the cheapest way to keep a prerecorded YouTube Live stream running in India.
Test the complete run before viewers arrive
A short source check can tell you whether Loop is enabled. A complete rehearsal tells you whether the whole run-of-show works. Use the same OBS scene, stream settings, file location, audio sources, and network connection that you intend to use for the real broadcast.
Start the encoder and wait for the YouTube preview. Confirm the title, visibility, thumbnail, description, and scheduled time if those details matter to the launch. Check the preview before starting publicly, then view the watch page as a viewer. YouTube's live streaming tips recommend testing, checking the preview, verifying watch-page access, and monitoring the stream.
Let the demo reach its final seconds. Observe whether the video restarts, whether the audio returns correctly, and whether the YouTube preview continues to update. If there is a delay between OBS and YouTube, allow for that when judging the result. The test should answer a practical question: does the encoder continue sending a valid, repeating programme after the original file has ended?
Write down the exact scene and source names used in the test. This matters when a channel has several versions of a demo, several scenes, or old stream profiles. A repeat failure is often a configuration mismatch rather than a limitation of YouTube.
If the test fails, work from the source outward. First check that Loop is enabled on the Media Source displayed in the active scene. Then confirm that the file is accessible and playable. Next check that OBS is still streaming and that YouTube is receiving the feed. Only after those checks should you change connection or broadcast settings.
Do not use a hardware encoder, capture card, webcam, or playback appliance as a substitute for this setting. Such equipment may be useful for a different production, but buying it does not by itself make a finished file repeat. The required behaviour comes from the source configuration and the continuing encoder feed.
Decide how and when the broadcast should end
Looping is correct when the live broadcast should continue with the same demo or a repeating sequence. It is not correct when the event has finished and viewers should be sent to a different programme. YouTube Live Redirect can direct viewers to a Premiere or another live stream after the current stream ends, but it does not keep the current product demo running or replay the same broadcast indefinitely.
If you want to hand viewers to another programme, prepare that destination first and check its settings. YouTube's live stream settings guidance explains relevant live options, including Live Redirect. Treat the redirect as an ending plan, not as a replacement for OBS Loop.
When the product demo should finish, stop the encoder feed from OBS and end the stream in YouTube Studio as appropriate. YouTube's encoder instructions describe stopping content from the encoder as the way to end an encoder stream. Do not confuse stopping the media file with ending the broadcast: the first can be an error during a continuing stream, while the second is an intentional shutdown.
Plan the recording separately from the live run. YouTube states that streams under twelve hours are automatically archived, while its DVR guidance says rewind may be limited or unavailable for streams longer than twelve hours. Do not promise viewers a complete archive or full rewind for a very long broadcast. If the demonstration is valuable as a recording, keep a clean master file and publish or schedule it separately where that suits your channel.
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
Will YouTube repeat my product demo automatically when it ends?
No. YouTube receives the feed sent by the encoder and does not automatically repeat a finished encoder file. Configure the demo source to loop in OBS, then keep OBS sending the feed.
Is turning on OBS Loop enough to keep the live stream running?
No. Loop repeats the file inside the OBS scene, but the encoder must still be connected and sending content to YouTube. Check both the source playback and the live connection during your test.
Should I stop OBS when the demo reaches its final frame?
Not if the broadcast should continue. With Loop enabled, the source should begin again; stop the encoder only when you intend to end the live broadcast or move viewers to another programme.
Can I repeat several product demos instead of one file?
Yes. Use a playlist-based source such as OBS's VLC Video source and enable its playlist loop option, with VLC installed as required. Test the order, transitions, audio, and final-to-first-clip transition in the complete live setup.