A prerecorded product launch presentation reaches YouTube Live through an encoder feed; YouTube Live does not loop the video for you. To repeat it, prepare the file, enable repeat playback in an encoder that supports it, connect that encoder to a stream in YouTube Studio, then test and monitor the broadcast.
The important distinction is between playback and broadcast controls. The encoder repeats the presentation; YouTube Studio manages the live event, its preview, and the action that starts or ends the public broadcast. Plan both sides, including when viewers should arrive and who will watch stream health.
Prepare the launch presentation for repeat playback
Start with a finished video file that your chosen encoder can play. Export it in a format the encoder supports, then play it locally from beginning to end before building the live event. If the encoder cannot read the file reliably, the YouTube connection will not fix that problem. Check the chosen encoder’s current documentation for supported formats rather than assuming that every video file will work.
Design the opening for someone who may arrive halfway through a loop. Put the product name, the essential benefit, and the store address where they can be understood without having watched an earlier introduction. If an offer has an end time or conditions, make those details clear in the presentation and in the event description. A viewer joining midway should not have to wait for the video to restart to learn what is being launched.
Check the final seconds against the opening. A hard cut from a closing slide to a loud intro, a blank frame, or a different audio level can make the repeat obvious. If that feels wrong, revise the edit or use a short transition in the video itself. Do not assume the encoder will smooth over a poor join.
Watch the whole file, not just the first minute. Confirm that product images are legible on a phone, text stays on screen long enough to read, narration and music are balanced, and there are no accidental pauses or export artefacts. Check that the shop URL is correct and that any price or offer shown matches what customers will see at the store when the event airs.
Make sure your store has the necessary rights to the music, images, clips, product imagery, and other material in the presentation. This is a content check, not a guarantee of how YouTube will assess a stream. Keep a clean final export and a copy of the project file somewhere separate from the machine used for encoding, so a last-minute change does not leave you with only a damaged or incomplete version.
Choose an encoder with repeat playback
The encoder takes the presentation as media and sends its outgoing audio and video to YouTube. YouTube’s guide to creating a live stream with an encoder describes the platform connection, while repeat playback is a feature of the encoder you choose. Check its current documentation for media input and repeat or loop support; do not infer a setting from another program’s interface.
A computer with a software encoder can suit a single launch when someone can leave it running and watch the event. It also means the computer, encoder application, power, and internet connection must all remain available. A dedicated hardware encoder with scheduled prerecorded playout may better suit a more unattended event, but it adds dedicated equipment and configuration to evaluate. A live presenter over the repeating presentation adds a microphone, a person to speak, and someone to watch chat; it is useful only if commentary or questions are part of the launch.
| Setup | Useful when | What to verify | Main trade-off |
|---|---|---|---|
| Computer with software encoder | You have an operator present for a launch | File support, repeat behaviour, upload capacity, and computer stability | The computer and encoder must keep running |
| Hardware encoder with prerecorded playout | You need scheduled playback with less dependence on a general-purpose computer | Media support, repeat or schedule controls, remote monitoring, and a backup plan | More dedicated equipment and setup |
| Presenter over the video | Commentary or live questions are part of the event | Microphone, presenter hand-off, chat monitoring, and how the video will be mixed | Adds live production work; it is not needed for a prerecorded presentation alone |
YouTube’s encoder documentation names AJA HELO Plus and describes its PlayToStream feature for scheduled prerecorded media. Treat that as an example to investigate, not a requirement or endorsement; verify the current capabilities and suitability with the manufacturer’s product page. A USB microphone is relevant only if someone will speak live. It does not make the presentation repeat and is unnecessary for a presentation with no live narration.
If you are weighing whether to operate a computer throughout the event, a continuous YouTube stream setup guide discusses the practical considerations of keeping a stream running. A product launch need not use the same format as a music channel, but the dependency on a running encoder is still worth planning for.
Enable repeat for the presentation
Add the prepared video as a media source or playout item in the encoder, following that encoder’s instructions. Turn on its repeat, loop, or equivalent playback behaviour if it provides one. The name and location of the control differ across encoders, so check the current interface and documentation for the one you have selected. YouTube Studio does not provide a substitute repeat switch for the incoming encoder feed.
For a single presentation, confirm that repeat applies to that media item and not merely to a playlist or scene. For a playlist, inspect the order and verify whether repeat applies to each item, the whole list, or neither. Those details are encoder-specific. Do not build instructions around a particular button label unless you have verified that label in the current version of the chosen encoder.
Run a local playback check with the encoder open. Let the file reach its end and observe whether it starts again, whether the transition is clean, and whether sound continues at the right level. If the encoder pauses or moves to another item instead, correct its playback configuration before connecting the public event. A repeat option that appears enabled in a settings panel is not enough; observe an actual end-to-start transition.
Keep the presentation itself self-contained. If the video is intended to repeat for several hours, a final slide that says “thanks for watching” followed by the opening announcement may confuse customers. Consider a neutral closing that leads naturally into the first frame. If you want live commentary between repeats, decide how that fits into the encoder’s actual capabilities and test it; do not assume the loop will wait for a presenter.
A guide to rotating multiple replay videos can help you think through the difference between repeating one item and rotating a sequence. For a launch, a single, self-contained presentation is often easier to check, but use a playlist only if its order and repeat behaviour are clear in your chosen encoder.
Create the YouTube Live event in Studio
In YouTube Studio, open the live creation flow and create or schedule a stream. YouTube’s encoder guide describes the stream setup and the controls available in Live Control Room. If you schedule ahead, the event page can be shared in advance; set the title, description, thumbnail, and visibility deliberately. Make the product and launch time clear, and check the store link in the description before sharing it.
Set the event timing around the customer experience, not only the video duration. Decide when the event page should be available, when the encoder should start sending its feed, when you intend to make the stream public, and when someone will be present to monitor it. A scheduled event may have a separate Go Live action after the encoder preview appears. Follow the current Studio flow and do not assume that starting playback automatically makes a scheduled stream public.
Choose visibility with care. A private test and a public launch serve different purposes; an unlisted event may be useful for sharing a test link with a small group, while a public event is discoverable. Check the current YouTube options and audience settings in Studio, since defaults can differ. If you schedule an event, test the link and access permissions with the people who need to check it.
The launch presentation should not be the only place customers can find the product page. Put the store address in the event description and in the video where appropriate, and make sure the page is live before the stream begins. If you plan a promotional code, test it yourself and ensure its terms are consistent across the video, description, and checkout. The stream can send viewers to a page, but it cannot correct a broken link or an unavailable product.
For a long-running broadcast, decide in advance how you will preserve the recording. YouTube states in its encoder guidance that streams under 12 hours are automatically archived. If the planned event may exceed that limit and the complete archive matters, verify current platform behaviour and make a separate recording plan rather than assuming the entire broadcast will be retained.
Connect the encoder using the server URL and stream key
Once the stream exists in Studio, retrieve its server URL and stream key from the live stream’s settings. In the encoder, select YouTube if that is a supported destination. Otherwise, put the server URL in the encoder’s server field and the stream key in its key field. YouTube’s encoder settings guidance covers connection settings and recommends RTMPS for an encrypted connection where available.
Treat the stream key like a password. Do not show it in public screenshots, recordings, shared documents, or a screen-share during the launch. If the encoder offers a way to save the key, restrict access to the account and machine used for the event. If you think the key has been exposed, use Studio’s current controls to replace or reset it, then update the encoder before going live.
Check that you have connected the intended event, particularly if you have created a separate private test. A valid key for a different stream can send the encoder feed to the wrong event. Keep a note of the event title and scheduled time, but avoid copying the key into that note. Confirm the connection status in the encoder and wait for the preview in Live Control Room before making the broadcast public.
The encoder’s output settings should match what your connection and system can sustain. YouTube publishes recommendations for resolution, frame rate, bitrate, and other encoder settings; consult its current live encoder settings page rather than treating any one setting as universal. The platform’s figures are recommendations, not proof that a particular home or shop connection can sustain the stream. Choose a quality you can test reliably, and avoid raising it merely because the presentation file has a high resolution.
Test playback and timing before launch
Run a test with the same presentation, encoder, connection, and approximate event settings you plan to use. YouTube advises testing audio and movement similar to the planned stream and checking upload capacity. A still title card is not a representative test of a presentation with narration, animation, and music. Keep the test separate from the public event so a false start does not become the launch itself.
Check the full path: the encoder opens the file, the video and sound reach the Studio preview, and the presentation returns to its opening after the final frame. Watch the preview on another device if possible. A local monitor can sound fine while the delivered stream is muted, out of sync, or too quiet. Ask a colleague to check the test link and confirm that text and product details are readable on a phone as well as a larger screen.
Rehearse the clock as well as the media. Write down when you will start the encoder, when you expect the preview to appear, who will click Go Live if Studio requires it, and when the product page or offer becomes available. If the launch is scheduled for a particular time, allow enough working time before it to discover a wrong key, a missing file, or an upload problem. The precise buffer depends on the setup; there is no universal lead time that removes the need to test.
Use a simple run sheet with responsibilities. One person can check the picture and sound, another can confirm the store link and offer, and a named operator can manage the Studio event. If one person is handling all of these tasks, reduce the number of last-minute changes and keep the key screens and recovery steps ready. If a scheduled event has a separate Go Live action, agree who owns it rather than leaving that decision until the preview is waiting.
Test the failure you can reasonably prepare for. Know how you will respond if the encoder stops, the computer restarts, or the connection weakens: who can restore the feed, where the current stream key is held securely, and whether an alternate connection or device is available. These are contingencies, not guarantees. A useful slow-connection streaming guide can help you think through connection constraints, but your own test is the evidence that your setup can carry this presentation.
Monitor stream health during the event
Keep Live Control Room and the encoder status visible to the person responsible for the broadcast. Before the public start, check that Studio has received the feed and that the preview shows the correct event. During the stream, watch for warnings, dropped or stalled video, missing sound, and a loop that fails to return to its beginning. YouTube’s stream-health feedback can help identify delivery problems, but it does not replace watching the actual output.
Use a second device and a separate viewer session to check what customers see. Confirm the public event is available at the expected time, the picture moves, the sound is audible, and the description contains the right product link. A preview in the operator’s own setup does not verify every viewer’s experience. If you cannot watch continuously, assign someone else to do so and make the hand-off explicit.
If the stream health changes, diagnose before making several changes at once. Check whether the encoder is still playing and connected, whether Studio still receives the feed, and whether the local internet connection is under unusual load. If the problem is a wrong event or key, correct the connection; if the outgoing feed has stopped, restore playback and check the preview again. Follow current Studio guidance for warnings and errors rather than guessing at an unfamiliar status message.
Do not treat a healthy status at the start as a promise that the event will remain healthy. Keep the machine powered, prevent avoidable sleep or restarts, and avoid large uploads or other demanding network use during the launch. If the event includes live questions, have a person monitor chat separately from the person watching the stream output. The presentation can keep repeating while no one notices that the store link is wrong, so check both the broadcast and the customer path.
When the launch is over, end the event in Live Control Room and stop the encoder feed. Confirm that the stream has ended rather than leaving a live slate or repeated closing slide running unintentionally. Check the resulting archive if you need a replay, and retain a separate copy of the presentation and any planned recording. For practical considerations around keeping an ongoing stream running, a guide to reducing computer load may be useful, although a single product launch has different demands from a continuous 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
Does YouTube Live repeat a prerecorded presentation automatically?
No. YouTube receives the outgoing encoder feed; the repeat behaviour must be set in an encoder that supports it. Test the end-to-start transition in that encoder before the event.
Do I need a microphone to loop a launch video?
No microphone is needed if the presentation is fully prerecorded and there is no live commentary. Add one only if a presenter will speak, and test it as part of the complete stream.
Should I use a computer or a hardware encoder?
A computer with a software encoder can be practical when an operator can keep it running and monitor the event. Dedicated hardware may suit scheduled prerecorded playout, but compare its supported media, controls, monitoring, and setup needs before choosing.
Does turning on repeat mean the launch will run smoothly?
No. Repeat controls playback, not the YouTube event, internet connection, or stream health. Test the whole path before launch and monitor the preview and live output while the event is running.