If you have a recorded webinar and want customers to watch it through YouTube Live, use OBS Studio to play the local file as a Media Source with Loop enabled, then send OBS’s output to a YouTube encoder stream. The repetition happens in OBS, not in YouTube.
This makes a recording available as a live broadcast; it does not turn it into a newly performed or interactive webinar. Customers can watch the stream, but the recording will not respond to questions or change in response to viewers. Plan the event and its wording accordingly.
Prepare the recording and confirm the rights
Start with the final recording on the computer that will run OBS. Play it from beginning to end before scheduling the event. Check that the opening and closing are appropriate for repeat playback: a spoken sign-off followed by several minutes of silence can make each restart feel like a fault, while a closing slide that says “thanks for joining” may confuse customers who arrive later.
Check the whole file for picture, sound, and content that you are entitled to broadcast. A customer webinar may contain a guest’s presentation, licensed music, third-party clips, product demonstrations, or slides that include material from another source. Having permission to show something during the original webinar does not necessarily mean you have permission to rebroadcast it publicly or on demand. Confirm the relevant rights with the people or organisations that supplied it.
YouTube’s live streaming guidance says live content must follow its Community Guidelines and Terms of Service. Its terms for live streams also require the provider to have the rights needed to use the content on Google services. Check the current official guidance and your own permissions before you broadcast; no encoder setting settles rights questions for you.
Also consider what viewers should understand when they arrive. A simple title or opening slate can say that this is a recorded session and give its original date, if useful. Avoid language suggesting that a presenter is currently on camera or answering questions. If customers need support, give them a separate contact route and state when someone will respond.
Create or schedule the YouTube Live event
In YouTube Studio, open the Live Control Room and create an encoder stream, either to start when ready or to schedule for a later time. A scheduled event gives your team a watch page to share ahead of the broadcast. Review the title, description, visibility, thumbnail, and scheduled start time before sharing it with customers. Scheduling is not the same as starting the stream: OBS supplies the video feed, and you use the Live Control Room to preview and start the event.
Before you set a date, check that the channel is eligible to stream. YouTube’s current help page says the channel must be verified and must not have live-streaming restrictions in the preceding 90 days. First-time live-stream activation may take up to 24 hours. These are YouTube’s platform requirements, not a guarantee that an event will be ready by a deadline, so do the checks before promising a broadcast time.
Once the event exists, find its encoder details in the Live Control Room. You will need the stream URL and stream key when configuring OBS. The URL identifies the receiving endpoint; the key identifies your stream. YouTube describes the key as a password and address for the stream. Keep it private, do not paste it into public event notes, and reset it if you believe someone else has access.
If you are comparing a one-off event with an all-day customer resource, decide what the audience needs before choosing the schedule. A single long event is not automatically equivalent to a permanent replay page, and the official archive guidance has limits discussed below. For other approaches to repeated video playback, see this guide to running a playlist on YouTube Live; it covers a different workflow, so do not assume its steps replace this event’s encoder setup.
Add the webinar file as an OBS Media Source
Open OBS and select the scene you intend to send to YouTube. In the Sources panel, choose +, then Media Source. Give it a recognisable name, such as “Customer webinar recording”, so you can distinguish it from a camera, logo, or other source later. In the source properties, select the local webinar file.
OBS’s Media Sources documentation describes the local-file source and its playback properties. It supports common video formats, but formats and playback behaviour can vary with the file and the version installed. If OBS does not play the file as expected, test a copy of the recording in your installed version and consult OBS’s current documentation rather than assuming YouTube is the cause.
Make sure the source fits the canvas. A recording with a different aspect ratio from the OBS video canvas can show black bars or be cropped if you alter the transform. Right-click the source and use a fit-to-screen transform if you want the whole frame visible, then inspect the preview for cut-off text, slides, or captions. Do not stretch the image merely to fill the canvas if that distorts people or graphics.
If the scene includes an opening slate, logo, or customer contact details, add those as separate OBS sources and check their position against the webinar. Keep overlays away from important slides and captions. A label can clarify that the session is prerecorded; it should not imply live participation that is not taking place. If you need a broader introduction to encoder choices, the YouTube streaming software guide can help you compare software workflows without making hardware a requirement for this setup.
Enable Loop on the Media Source
In the Media Source properties, turn on Loop. OBS documents this setting as controlling whether a media file starts playing again after playback completes. It is off by default, so confirm the setting rather than assuming a source will repeat. With Loop enabled, OBS repeats the file at its end; YouTube simply receives the continuing stream that OBS sends.
Test the transition at the end of the recording. Watch the last moments, the transition back to the beginning, and the first moments after the restart. If the file has a long black frame, silence, or an abrupt ending, those will repeat too. You can edit the recording before the event if the transition is distracting, but keep a separate unaltered source copy so your team can recover the original.
A loop does not make one webinar feel like a continuous live conversation. Customers who join at different times will see different parts of the same recording, and returning viewers may recognise repeated sections. Set expectations in the event description and consider whether repeating the full session suits the subject. For example, a product introduction can be useful as a repeatable reference, while a time-sensitive announcement can become misleading once its details change.
For an alternative local-file approach, the article on creating a seamless loop with FFmpeg discusses a different tool and editing concerns. OBS’s Media Source loop is the direct workflow here; do not add file-processing steps unless you have a reason, such as needing to revise the transition.
Configure YouTube URL and stream key in OBS
In OBS, open Settings, then Stream. Choose YouTube if the available connection flow suits your setup, or select the option that lets you enter a server and key manually. Use the stream URL and stream key shown for the specific event in YouTube Live Control Room. Match the event and credentials carefully, particularly if you have multiple scheduled streams.
Treat the key as confidential. Avoid screenshots that show it, remove it from shared documents after setup, and do not send it in customer communications. If it is exposed, use YouTube’s controls to reset or replace it, then update OBS. The stream key grants access to the configured stream feed, so protect it as you would a password.
Check the output settings against your connection and the content. A webinar with slides and a talking presenter usually does not benefit from blindly selecting the highest possible video settings. YouTube recommends leaving upload capacity above the total stream bitrate; its guidance specifies 20% headroom. This is a planning recommendation, not a promise that the connection will remain stable. If other people or devices use the same connection, account for their traffic as well.
You can compare a software encoder with a hardware encoder if your production team already has dedicated equipment or needs a particular onsite workflow. YouTube documents both paths. For a local prerecorded file with an OBS loop, a software encoder is a straightforward fit; a hardware purchase is not a prerequisite. Whatever you use, confirm that the chosen encoder can replay a local file and send the intended output to the event.
Preview the scheduled stream before starting it
Allow time for a complete test before the customer-facing start. In OBS, start sending the stream output, then open the event in Live Control Room and wait for its preview. Check that the preview shows the correct scene and that YouTube is receiving the expected picture and sound. A scheduled event should be started from the control room when the preview is ready; starting OBS alone sends the feed but does not substitute for the event’s Go Live control.
Use the preview as a real pre-event check, not a glance at a still frame. Confirm the webinar is the right file, the first frame is sensible, slides are readable, and the audio is audible without clipping or unexpected silence. If possible, check the customer watch page on a phone as well as the control-room preview. YouTube recommends checking the stream before going live and setting up encoder streams ahead of time.
If the event is scheduled, tell customers when the watch page will be available and avoid describing the session as interactive. A separate email or support channel can collect questions, but make clear that questions will not be answered inside the prerecorded broadcast. If customers expect a live presenter, change the event plan or the description before sending the link.
For a practical rights checklist on music and other protected material, see how to avoid copyright claims on a devotional YouTube Live stream. The context differs, but the underlying need to check the material in your broadcast is relevant to a webinar too.
Monitor playback, audio and the end of the event
During the broadcast, keep an eye on both OBS and the Live Control Room. Confirm the Media Source continues playing, the audio meter responds during speech, and YouTube’s preview remains current. If the source stops or the connection drops, the audience may see a frozen picture, silence, or an interruption. Decide in advance who is responsible for watching the stream and who can act if something goes wrong.
Listen to the audio on a separate device if possible. The OBS meter can show that sound is present, but it does not tell you whether speech is clear, too quiet, or masked by music. Be alert around the loop point, where silence or a sharp level change may be more noticeable. If you change audio routing or source settings, verify the result in the YouTube preview before the event is started.
A long-running event needs an end and archive plan. YouTube says streams under 12 hours can be automatically archived; streams exceeding 12 hours may not be captured at all. Do not promise that a long broadcast will produce a complete YouTube replay. Keep a local recording if you need an archive, and test that recording process separately. The cited guidance does not establish that a single event can run indefinitely, so check the current controls and policies before planning a continuous schedule.
| Planning choice | What it means for this workflow | Check before committing |
|---|---|---|
| One scheduled event | OBS loops the file while that event is active. | Who monitors it, when it ends, and whether customers need a replay. |
| A longer broadcast | The same recording may repeat for an extended period. | YouTube’s archive guidance, local recording, and the current event controls. |
| A live, interactive session | A presenter can respond to viewers in real time. | This is not what a prerecorded Media Source loop provides. |
When a recorded session will be watched on demand as often as live, consider whether a YouTube video or an embedded replay better fits the customer need. A live event may be useful for a scheduled shared viewing, but the recording itself remains fixed. Explain that distinction in the title, description, and any invitation you send.
If your broader use case is a channel that runs continuously rather than one customer event, the guide to running a nonstop sermon stream from a computer discusses the separate operational problem of keeping a channel going. Do not treat a single scheduled webinar event as proof that a stream can run without interruption or indefinitely.
For this OBS workflow, the Media Source Loop setting and the stream key are two points that require an operator to stay attentive. If keeping a computer on and watching for a dropped broadcast is the part you cannot reliably cover, StreamNeo can take the uploaded recording and run it as a YouTube stream while your computer is off, with monitoring and automatic restarts if it drops. It is YouTube-only, so it does not change the distinction between a recorded broadcast and an interactive webinar.
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 loop the webinar recording?
No. In this workflow OBS plays the local file and its Media Source Loop setting repeats it when playback ends. YouTube receives the encoder feed; it is not repeating the file on the channel’s behalf.
Can customers ask questions during the broadcast?
They may be able to use YouTube’s available chat or other channel features, but the prerecorded webinar will not respond to them. If someone will monitor questions and answer separately, explain that clearly in the event description and say when customers can expect a reply.
Will YouTube save the whole broadcast as a replay?
Do not assume so for a long stream. YouTube says streams under 12 hours can be automatically archived, while streams over that duration may not be captured. Keep a local recording if a complete archive matters, and check YouTube’s current archive guidance before planning the event.
What should I do if this is the channel’s first live stream?
Check YouTube’s current eligibility and activation guidance before announcing a date. YouTube says first-time activation may take up to 24 hours, and the channel must meet its verification and restriction requirements. Test the full OBS-to-YouTube path and wait for the preview before starting the scheduled event.