For a single local video, add an OBS Media Source and enable Loop. For a playlist, use VLC Video, check its playlist loop setting, and make sure VLC is installed; neither setting configures YouTube delivery or guarantees recovery if the stream stops.
Treat this as two jobs: make the source play as intended, then configure and test the stream that carries it to YouTube. A file repeating in OBS is not proof that YouTube is receiving it, that the stream is healthy, or that viewers can open the watch page.
Choose a single file or playlist
Start with the material you want to broadcast. If one video should repeat, use OBS’s built-in Media Source. If you need several files in sequence, or want OBS to shuffle multiple items, use VLC Video. The choice is about playback, not the encoder or YouTube settings.
| What you want to play | OBS source | Setting to check | Main consideration |
|---|---|---|---|
| One local video repeatedly | Media Source | Loop on | The source points to one file; playback repeats at its end. |
| Several local videos in a fixed order | VLC Video | Loop Playlist on; Shuffle off | VLC must be installed, and the playlist order matters. |
| Several videos in a changing order | VLC Video | Loop Playlist on; Shuffle on | Playback order varies, so review the result before going live. |
For example, a bhajan channel with one long programme can use Media Source. A study channel with separate topic videos may prefer a VLC playlist so the items follow a planned sequence. If you already use another method to rotate content, see the practical distinctions in scheduling YouTube playlist rotations; OBS source looping is not the same as scheduling changes to a live programme.
Check that you have the right version of the file and that it plays on the Windows 11 computer before building the scene around it. OBS’s Media Source reference lists common video formats including MP4, MOV, MKV, AVI and WebM, as well as audio formats such as MP3, AAC and WAV. A supported extension does not establish that every file will decode smoothly on every computer, so test the actual file and scene you intend to use. OBS: Media Sources
Configure Media Source Loop for one file
In OBS, add a Media Source to the scene that will be sent to YouTube. Choose Add Existing if the source already exists in the scene collection, or create a new one. In its properties, select Local File and browse to the video. Confirm the selected path and preview before changing other settings.
Turn on Loop. OBS documents this control as off by default; when enabled, it replays the media after playback completes. Start the source or watch the preview long enough to see it reach the end and begin again. For a very long file, test with a shorter representative clip as well, but do not assume that a successful short test proves the whole programme file is sound.
The other controls affect different playback circumstances:
- Restart playback when source becomes active is on by default. Leave it on if making the source visible again should start the video from the beginning. If you switch scenes and return, that behaviour may not be what you want, so test it in the actual scene layout.
- Show nothing when playback ends is on by default. OBS notes that this can prevent the last frame remaining on screen. With Loop enabled, the source should repeat rather than stay at an end frame, but verify the transition.
- Close file when inactive is off by default. Enabling it unloads the file while the source is hidden or off-scene, which can free memory; OBS warns that the source may take a short time to reappear when shown again. Leave it off if scene changes should not introduce a reload pause.
- Speed defaults to 100 per cent. Keep normal speed unless you deliberately need a different playback rate and have checked both picture and audio.
- Use hardware decoding when available is off by default. This concerns decoding the source media, not the encoder that sends the live stream. Its suitability depends on supported formats and the computer’s graphics hardware.
A reliable baseline is one correct local file, Loop enabled, normal speed and the restart behaviour chosen deliberately. Avoid changing several properties at once: if a transition or audio problem appears, you will have a clearer idea which setting to revisit. For audio-specific checks, the guide to diagnosing no sound on a 24/7 YouTube radio stream is useful, but first confirm that OBS’s meters move and that the source actually contains the audio you expect.
Configure VLC Video for a playlist
Use VLC Video when you need more than one playlist item. OBS says this source uses VLC libraries for extended media support and requires VLC to be installed before the source is available. Add the source, add the files in the intended sequence, and inspect the list before testing. A playlist with an item missing or in the wrong order can play continuously and still be the wrong broadcast.
OBS documents Loop Playlist as on by default and Shuffle Playlist as off by default. Keep shuffle off for a fixed order, such as a set of devotional programmes arranged by time or a series of lessons. Enable it only when changing the order is intentional. Do not rely on the default without checking the property: defaults can be changed in an existing source or scene collection.
Also review Visibility Behaviour. The documented default is to stop when the source is not visible and restart when it becomes visible. That can matter if you switch scenes, hide the source, or use it in a scene that is not currently active. Test the transitions you plan to use rather than leaving a hidden source’s behaviour to chance.
The source has a network caching control, documented with a 400 ms default, but that is not a universal prescription for every file or connection. Start with the default unless you have a repeatable playback issue that gives you a reason to investigate it. The source’s audio track and subtitle controls should also be checked if a playlist item has multiple audio tracks or embedded subtitles. Confirm that the right track is selected and that unintended subtitles are not displayed.
If you need to change content while keeping an existing broadcast running, playlist source behaviour is only part of the design. Consider whether a fixed sequence, a shuffled list, or a deliberate scene transition fits the programme. For a related approach focused on changing playlists during a live broadcast, see switching music playlists without ending a YouTube live stream. Test the exact transition, including audio, before using it in a long run.
Check VLC installation and file paths
If VLC Video does not appear in the OBS source list, check the dependency first. Install VLC from its official site, then restart OBS if it was open during installation. OBS’s reference specifies 64-bit VLC when you use 64-bit OBS. Match the VLC installation to the OBS architecture rather than installing a version at random. VLC official downloads
After the source appears, verify every playlist item’s path. A file that plays from a removable drive or a temporary downloads folder may not be available later if the drive is disconnected, renamed or moved. Keep the media in a stable local folder, and avoid reorganising it after you have tested the playlist. A Windows account change can also affect access to files, so test while signed into the account that will run OBS.
Use filenames that make the order easy to review, but do not assume alphabetical sorting is the same as your intended running order. Inspect the actual playlist in OBS. Open each file once, check its picture and sound, and verify that it starts at the expected point. If one file is shorter than the rest, its quick transition may be easy to miss in a brief preview.
A simple local test is to watch a boundary between two items and then the end of the playlist. Check that the next item begins, the audio does not unexpectedly stop or jump, and the source remains visible in the scene. If you are troubleshooting lag or stutter, reduce unnecessary scene complexity before changing codec or cache settings. A guide to streaming software lag on Mac covers a different operating system, but the general discipline of isolating sources and checking workload can still help; use Windows-specific OBS and system controls for any changes on this machine.
Set YouTube encoder output separately
Loop settings govern source playback. OBS’s streaming output governs the encoded signal sent to YouTube. Set those separately in OBS and compare the chosen codec, resolution, frame rate, bitrate and keyframe interval with YouTube’s current encoder guidance. YouTube recommends RTMPS and lists H.264, H.265 (HEVC) and AV1 for RTMP/RTMPS workflows. Recommendations vary with codec, resolution and frame rate, so do not take one bitrate as a universal setting. YouTube Help: encoder settings, bitrates and resolutions
For reference, YouTube’s current table gives H.264 recommended examples of 14 Mbps for 1080p30 and 17 Mbps for 1080p60. Those are platform recommendations for the named format, not a promise about what a particular Windows computer or internet connection can sustain. If you choose a different codec, resolution or frame rate, use the corresponding entry in YouTube’s table rather than copying one of these figures.
The same YouTube guidance recommends a two-second keyframe interval and says the maximum is four seconds. Match the setting in OBS’s output configuration to the current platform guidance. YouTube also lists AAC or MP3 audio for RTMP/RTMPS; its advanced recommendations include 44.1 kHz stereo audio for stereo output. Check your actual stream output rather than assuming that the source file’s properties are what YouTube receives.
In YouTube Live Control Room, use the stream setup associated with your event and enter its stream URL and key in OBS. Treat the key as a credential: do not publish it in a screenshot, share it in a public support post or leave it visible in a tutorial recording. YouTube says the Live Control Room can usually detect resolution and frame rate from the encoder; custom stream keys can involve manual resolution settings. Check what the event reports after OBS connects.
Your upload capacity must accommodate the total stream bitrate, including any additional traffic on the connection. YouTube recommends 20 per cent headroom and warns that network disruption can break a stream. A bitrate that looks suitable in OBS is not enough if other household or business traffic uses the same connection. If network interruptions are the main concern, a guide to YouTube streams that keep disconnecting can help frame troubleshooting, but confirm the cause on your own connection and in YouTube’s health messages.
Latency and DVR are separate YouTube stream options, not source-loop controls. YouTube notes that choosing lower latency can lead to more playback buffering. Pick settings for how viewers will use the channel, and verify playback on a viewer device rather than judging only from OBS’s local preview.
Verify preview, stream health, and watch-page access
A source preview is the first check, not the final one. Before relying on a long run, confirm that the selected source is visible in the scene, the intended video and audio are present, the loop or playlist transition behaves as expected, and OBS is sending the intended output. YouTube advises testing before starting a live stream and recommends that a test resemble the intended audio and motion. A still image test does not exercise the same path as a moving video with continuous sound.
Once connected, check the Live Control Room preview and the stream health messages. Allow the encoder and ingest to settle, then look for warnings about the signal rather than assuming that an OBS indicator alone tells the full story. Compare the detected resolution and frame rate with what you intended. Check sound on the YouTube preview as well as the OBS audio meter: a moving meter confirms input activity, not that the audience hears the correct mix.
Then check the watch page from a viewer’s point of view. Confirm that the event is accessible from the channel and that the watch page opens as intended. If the stream is unlisted or private for a rehearsal, make sure your test account has permission to view it; a successful private test does not establish public access. Recheck the event’s visibility and access settings before the intended audience arrives. YouTube’s live streaming tips cover preparation and monitoring; follow the current official instructions for the event type you use.
For a practical preflight, write down the source file or playlist, the OBS scene, the output settings, the event’s visibility and the person responsible for watching health messages. Test at the resolution and frame rate you plan to use. If a fault appears, separate the layers: does the file play locally, does OBS show the scene, does OBS connect, does YouTube report healthy ingest, and can a viewer open the page? This avoids changing source-loop settings to solve a network or access problem.
Understand the limits of source looping for recovery
Looping tells OBS what to do when media playback reaches its end. It does not define what happens if Windows restarts, OBS closes, the computer loses power, a file becomes unavailable or the network drops. VLC’s playlist loop and Media Source’s file loop describe playback; they are not an unattended recovery policy for those other failures.
Windows 11 is supported by OBS, but compatibility is not a guarantee that a particular computer can encode continuously at a chosen resolution, frame rate and scene complexity. OBS notes that CPU load varies with those choices. Test the whole setup for a meaningful period, monitor system load and check that the machine remains available under the conditions in which you expect to run it. Plan separately for updates, power interruptions and someone being able to investigate a warning.
You can reduce avoidable surprises: keep files in stable locations, disable unnecessary scene changes, check that the Windows power settings suit the intended run, and schedule operating-system maintenance deliberately. These are precautions, not guarantees of uptime. A restart after a failure may require manual attention, and behaviour depends on how the machine and software are configured. Do not infer from a successful overnight test that every future outage will recover in the same way.
If maintaining a local Windows machine through the night is the specific pain you need to remove, StreamNeo can take an uploaded video and run it as a YouTube live stream after you provide the stream key, without keeping your own computer on. It is YouTube-only, so it is not a way to send the same broadcast to other platforms; check whether that trade-off fits your channel and still verify the YouTube event and watch page.
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 Media Source loop a video automatically?
No. OBS documents Loop as off by default, so enable it in the Media Source properties for a single file. Preview the end-to-start transition before using the scene in a live event.
Do I need VLC for a playlist in OBS?
Yes, VLC Video depends on VLC being installed. OBS specifies 64-bit VLC for 64-bit OBS; if the source is missing, check the installation and restart OBS before troubleshooting the playlist itself.
Does a looping source keep a YouTube stream online?
No. It controls media playback, not Windows, OBS, network or YouTube availability. Monitor YouTube’s stream health and test recovery separately; no source setting guarantees unattended operation.
Why can OBS show the video while the watch page does not?
OBS preview shows the scene locally, whereas the watch page depends on YouTube ingest, event configuration and viewer access. Check the Live Control Room health messages and verify the event’s visibility and watch-page access from a viewer account.