To loop one recorded video on YouTube Live using OBS, add it to a scene as a Media Source, select the file and enable Loop. Then connect OBS to a YouTube encoder stream, start sending the feed, check the preview in Live Control Room and start the YouTube event when it is ready.
Check your channel’s eligibility and live-stream activation before choosing a broadcast date. Looping in OBS repeats the file, but does not activate live streaming, connect to YouTube or start the event for you.
Check eligibility and activation timing first
YouTube’s live-stream requirements include a verified channel, no live-streaming restrictions in the preceding 90 days, and a streamer who is at least 16. First-time activation can take up to 24 hours, so do not assume you can create a channel and go live immediately on the same day. Check your current status in YouTube Studio before you build the rest of the plan. YouTube’s live-streaming eligibility guidance is the primary reference; requirements and Studio screens may change, so check the current page rather than relying on an old screenshot.
If this is your first broadcast, request or enable live streaming early enough to allow for activation. The up-to-24-hour window is a planning caution, not a promise that approval will arrive by a particular time. If your channel is restricted or not verified, OBS settings cannot bypass that requirement. Resolve the issue through YouTube’s official channel and plan a test for after the feature is available.
A useful distinction is between preparing the broadcast and being able to start it. You can prepare a scene, select a local file and configure an encoder while you wait. You still need an eligible channel and an active YouTube live workflow before the audience can watch a live event.
Create or locate the YouTube encoder stream
Open YouTube Studio and enter Live Control Room. Create a stream or schedule one, depending on whether you want to announce the event in advance. For a scheduled broadcast, set up the event in Studio and return to its stream settings to find the connection details. YouTube’s encoder streaming instructions explain the workflow and the distinction between sending a feed and starting the event.
You need the server URL and stream key shown by YouTube. The key is credential-like information that lets an encoder send a feed to your channel. Treat it as private: do not show it in a screen recording, paste it into a public chat or leave it visible in a shared screenshot. If you believe it has been exposed, reset it in YouTube Studio and update OBS with the replacement.
You may see an option in OBS to select YouTube directly. If so, follow the connection prompts and use the stream information associated with the event you intend to run. Alternatively, choose a custom service and paste the server URL and stream key from Studio into OBS. Keep the stream details for the correct event together; a key or event selected for a different broadcast can send your test feed to the wrong place.
Before moving on, identify whether you are preparing an immediate stream or a scheduled event. The OBS feed can be active while a scheduled event is still waiting for you to start it in YouTube. That separation is useful for inspection, but it also means the OBS Start Streaming button is not the same as YouTube’s Go live control.
Add the recorded video as an OBS Media Source
In OBS, choose the scene you want to use, then add a Media Source in the Sources panel. Give the source a recognisable name, such as “Main loop” or “Evening bhajan”, so it is easy to identify if the scene has other elements. OBS describes Media Sources as a way to play media files; its Media Sources documentation lists supported file types and explains the source properties.
A Media Source is suitable when one file should repeat. It plays the local file directly as part of the OBS scene. That makes it a straightforward choice for a single devotional recording, ambience video, recorded product guide or other clip that you want to repeat without changing files during the broadcast.
Once the source appears in the scene, check that it is visible in the preview canvas. The source may be larger or smaller than the canvas, or positioned partly outside it. Use OBS’s fit-to-screen transform if needed, then inspect the frame edges. A recording in a different aspect ratio from your canvas can leave unused space or require cropping; decide which matters more before broadcasting, rather than discovering a cut-off title after the event has started.
If your scene includes a logo, title or other overlay, check the order of sources. OBS layers sources in the list: an overlay intended to appear over the video must be above the Media Source. Keep the layout simple for a first test. Each additional source is another thing to inspect for visibility, timing and audio interaction.
Select the file and enable Loop
Open the Media Source properties and use the local file control to select the recording. Check that the displayed file path points to the intended video. OBS supports common formats including MP4, TS, MOV, FLV, MKV, AVI, GIF and WebM, though a file’s extension alone does not guarantee that every codec inside it will play as expected. If the preview is blank or playback fails, try a known-good export in a supported format and test it in OBS before using it for a public broadcast.
Tick Loop in the source properties. The setting tells OBS to play the file again after playback completes. It does not create a YouTube event or make the broadcast continuous by itself: OBS must remain connected and sending the scene, and YouTube still needs the feed and event to be active. After enabling Loop, close the properties and watch at least one full start-to-end transition when practical. Confirm that the file returns to its beginning without a black gap, abrupt scene change or unexpected silence.
Check the source’s audio as well as its picture. If the recording has sound, OBS’s mixer should show activity during playback. Listen on headphones or speakers at a sensible level and confirm the sound is not coming from a second source at the same time. A duplicate desktop-audio capture can make an otherwise clean recording sound doubled or introduce room noise. If the video is intentionally silent, verify that the stream will not pick up unintended microphone or desktop sound.
The first frame matters. Some files take a moment to load, and a scene change or OBS restart may leave the source waiting for playback. Test what viewers would see when the scene is first selected, not only after the video has been playing for a while. For a station that uses several recorded programmes, a playlist is a different requirement: OBS’s VLC Video source supports a looping playlist, but VLC must be installed for that source type to be available. For one file, Media Source with Loop is the simpler setup.
| What you need | OBS source | What to check |
|---|---|---|
| Repeat one recorded video | Media Source with Loop | File loads, picture fits, audio is right, playback returns to the beginning |
| Repeat a sequence of files | VLC Video with Loop Playlist | VLC is installed, playlist order is correct, transitions and audio are checked |
Do not switch to a playlist just because it sounds more capable. If the same clip should run again from its beginning, one Media Source has fewer moving parts. If you need multiple recordings in sequence, a playlist avoids manually replacing a source, but adds playlist and VLC setup to test.
Enter the stream URL and key in OBS
Open OBS Settings and select Stream. If you chose a custom service, enter the YouTube server URL and stream key from Live Control Room in the matching fields. If you selected YouTube through OBS’s service list, confirm that the account or event shown is the one you intend to use. The labels can differ slightly between software versions, so match the purpose of each field rather than relying on an old tutorial’s exact screen layout.
Use care when handling the key. It should not be part of your scene, title or public instructions to a helper. If another person is operating OBS, share access in a way that does not expose the key beyond what the task requires. A key that has been copied into notes or chat may remain there after the broadcast; remove any copies you no longer need.
Do not change video output settings at random to solve a connection problem. First check that the correct server URL and key are entered, that the channel is eligible and that YouTube Studio is showing the intended stream. Then review the OBS status and YouTube’s stream-health messages. If the warning is about bitrate, use the channel’s actual output settings and YouTube’s current guidance; our bitrate warning troubleshooting guide covers that narrower issue.
A laptop or desktop running OBS remains part of this arrangement. It must stay powered, connected and running OBS for the file to continue looping through this local-file workflow. If the computer sleeps, loses its connection or OBS closes, the feed may stop even though Loop remains checked. For a long unattended channel, consider whether maintaining that computer and connection is acceptable; the practical considerations for running a continuous stream without maintaining a server explain a different operating approach.
Preview in Live Control Room, then start the event
When the scene and stream settings are ready, start sending from OBS. This begins the encoder feed; it does not necessarily make a scheduled event public. Return to Live Control Room and wait for the incoming preview. Inspect the actual preview there, not only the OBS canvas, because YouTube’s view confirms that a feed has reached the event.
Before starting the event, check that the picture is the intended recording, the framing is acceptable and the audio is present at the expected level. Look for a black screen, a frozen frame, the wrong scene, clipped text or unexpected microphone sound. Wait for YouTube’s stream health to settle enough to assess the feed. If there is a problem, correct it before clicking Go live. YouTube’s stream setup guidance describes the encoder process; follow the current Studio prompts for the event type you created.
For a scheduled stream, use Go live in Live Control Room only after reviewing the preview and event details. Starting OBS and starting the event are separate actions. For an immediate workflow, Studio may present different controls, but you should still confirm that the feed is reaching the intended broadcast before announcing it to viewers. When ready, monitor both the OBS status and Live Control Room rather than assuming that a checked Loop box means the whole path is working.
If you are testing a long repeat, keep an eye on the loop boundary and on the stream-health display. A good local preview confirms only that OBS can play the file; YouTube’s preview confirms reception; neither guarantees that an internet connection or computer will remain uninterrupted overnight. If the channel relies on a dependable hand-off between operators, document which event to open, where to check the preview and who is authorised to start it. The OBS WebSocket settings guide for remote control is relevant if you are exploring remote operation, but remote controls do not remove the need to verify the event itself.
At the end, stop or end the event in YouTube Studio and stop sending from OBS as appropriate to that stream workflow. YouTube says encoder streams under 12 hours are automatically archived; do not assume the same archiving outcome for a stream at or above that duration. Check the recording in Studio after ending if you need an archive, rather than treating a successful live session as proof that the replay is available. For a long-running channel, decide separately how often you will replace or review a file; a looping source can repeat indefinitely while also repeating a mistake in the recording.
A recorded video used in a public live broadcast also raises a separate question from technical setup: whether you have the rights to broadcast that recording. The steps here do not establish that permission. Check the terms that apply to the specific file and any music or other material it contains before you schedule it.
If you want a more unattended workflow because leaving a computer and OBS running is impractical, StreamNeo addresses that particular operating burden by turning an uploaded video into a YouTube live stream without keeping your own computer on.
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 enabling Loop start a YouTube Live event?
No. Loop repeats the selected file inside OBS after playback completes. You still need to connect OBS to YouTube, send the feed and start the event in Live Control Room when the preview is ready.
Can I go live on the day I enable live streaming for the first time?
Possibly, but do not plan on immediate activation. YouTube says first-time live-stream activation may take up to 24 hours, and channel eligibility requirements still apply; check Studio ahead of broadcast day.
Should I use Media Source or a playlist?
Use Media Source with Loop when you want one recording to repeat. Use OBS’s VLC Video source with Loop Playlist for a sequence of files, and confirm VLC is installed and the playlist order works before you go live.
Will OBS keep the stream running if I turn off my computer?
Not in this local-file workflow: OBS is playing the file and sending the feed from the computer, so it needs to keep running with power and connectivity. If you need the broadcast to continue with your computer off, choose an operating arrangement designed for that requirement.