For one local video, add it as an OBS Media Source and enable Loop in its properties. For a playlist, use VLC Video and enable Loop Playlist; either setting repeats playback, but neither promises a frame-perfect, gap-free join on every file and system.
If viewers must not see or hear a pause, test the exact asset and the actual broadcast near the boundary before relying on it. A clean-looking preview is useful, but it does not prove that YouTube viewers will receive an uninterrupted join.
Add a Media Source for one local video
In OBS, open the scene that should carry the video. In the Sources panel, add a Media Source, give it a name that will make sense later, and choose the local video file in its properties. The source can sit alongside other scene items, so check the preview to confirm it is visible and sized as intended.
The file should be available to the machine running OBS. If you move it or rename it after configuring the source, OBS may no longer find it. Keep a stable copy in a known folder rather than selecting a file from a temporary download location that might later be cleared.
Once the source is added, test normal playback before changing the loop setting. Confirm that the video starts, picture and sound are present, and the clip reaches its end. If it fails at this stage, looping will not fix the underlying file or path issue.
For a long-running devotional channel, for example, you might use a single approved bhajan video with a static opening slate and an audio fade already edited into the file. The source can replay that file, but any end-card, silence, or black frames baked into it will replay too. If you need to prepare a file for streaming, it helps to understand what transcoding changes and why it matters; changing a file's format does not by itself remove an intentional pause at the end.
Enable Loop in source properties
Select the Media Source and open its properties. Turn on Loop, then apply the change. OBS documentation describes this property as controlling whether the file plays again once playback has completed; its documented default is Off. The setting applies to this source's playback, not to YouTube's live delivery settings.
Keep Loop distinct from Restart playback when source becomes active. Loop repeats the file at end-of-playback. Restart playback when source becomes active resets playback when the source is in the current scene and visible. If you switch away from the scene and return, that restart behaviour may matter; it is not a substitute for enabling Loop.
Also consider Close file when inactive. OBS notes that when a source is shown again after being inactive, there may be a small period when nothing is displayed while the file reloads. For an always-on channel that changes scenes, decide whether the reduced inactive file use is worth the possibility of a brief blank on reactivation. If the source stays visible continuously, this setting is less likely to affect the loop boundary itself.
After enabling Loop, let the clip reach the end in OBS and watch it restart. That is a setup check, not a continuity guarantee. Inspect the final frames and the opening frames, and listen to the same boundary. A clip can replay correctly while still containing a black frame, silence, an abrupt musical cut, or a visible jump that is part of the media itself.
Use VLC Video and Loop Playlist for multiple files
If the channel rotates several clips, add a VLC Video source instead of making a separate Media Source for each file. Create or select a playlist in the source properties, arrange the clips in the required order, and enable Loop Playlist. This repeats the playlist after it finishes rather than repeating just one selected file.
VLC Video depends on VLC being installed. Match its architecture to OBS: 64-bit OBS requires 64-bit VLC. If OBS does not offer the VLC source or cannot load its playlist, check that VLC is installed and that both applications use the compatible architecture before rebuilding the scene.
A playlist introduces more boundaries to check. The transition from the final file back to the first is one join; the transitions between every neighbouring pair are additional joins. Different frame rates, audio sample rates, durations, or edit points can make one transition behave differently from another. Do not assume the final-to-first join is the only one worth testing.
| Playback pattern | OBS control | Dependency | What to test |
|---|---|---|---|
| One local clip | Media Source Loop | OBS Media Source | End of clip back to its first frames and audio |
| Several clips | VLC Video Loop Playlist | VLC installed with architecture matching OBS | Every clip change, including last back to first |
Neither row is a promise of more seamless playback. Choose by whether you have one file or a playlist, then evaluate the actual media and stream. If the question is whether an out-of-sync result is caused by a different issue, use the checks in the guide to correcting audio and video delay in a VLC YouTube Live stream.
Understand what loop controls do not guarantee
A repeat control tells OBS what to do when playback completes. It does not document a universal guarantee that the last decoded video frame will be followed immediately by the first, or that audio samples will join without a pause, click, or change in level. The result can depend on the edit, media encoding, frame timing, audio, source behaviour, and the computer doing the playback.
There is a difference between a gap in the file and a delay at the join. If the editor left a second of black picture or silence at the end, the loop is faithfully repeating that material. If the file itself has no deliberate gap, playback can still show a discontinuity that is more apparent with motion or continuous music. The checkbox cannot repair a cut that needs editing.
There is also a difference between source playback and delivery. OBS plays the media source into the programme; YouTube receives the encoded live output. A loop setting changes the former. Encoder configuration and connection quality affect the latter. YouTube's live encoder guidance recommends testing before streaming and using representative movement and audio, but those delivery recommendations do not turn on an OBS source loop or certify a loop boundary.
Do not treat a YouTube latency choice as a remedy for a source-level pause. Latency is the delay between capture and playback, and lower latency may involve more buffering. It does not remove black frames or silence contained in the media, nor does it establish a gap-free join. For a separate explanation of those choices, see YouTube Live latency settings for loops.
Test the join for video and audio gaps
Start with the exact file you intend to stream. In OBS, allow it to play through the boundary while watching the programme preview. Look for a black or frozen frame, a jump in position, a flash, or a pause before the opening image returns. Repeat the test rather than judging from a single pass, especially if the issue is intermittent.
Listen as well as watch. Music may click, dip in volume, stop briefly, or restart mid-beat even when the picture looks continuous. Speech, bells, aarti, or a station ident may be more sensitive to an abrupt cut than a quiet ambience loop. If audio and video have separate edit points, inspect both at the same time and note whether the apparent pause is in one or both.
A local recording from OBS gives you a way to review what OBS produced without depending on your own live playback view. Scrub around the boundary, then listen through it at normal speed. Frame-by-frame inspection can reveal where the cut falls, but normal-speed listening and viewing matter too: a technically adjacent cut may still feel abrupt to an audience.
Then test a private or otherwise controlled live session if available to you, and watch the playback side as a viewer. YouTube recommends testing with movement and audio similar to the planned event and reviewing stream health messages. Its guidance is about the live feed as a whole, so apply it alongside—not instead of—the source-boundary check.
Write down what you observed and what you changed. If the join is poor, edit or replace the file, adjust its opening or ending, or choose a different playback arrangement; then run the test again. Avoid changing several unrelated settings at once, because that makes it harder to tell whether the source, media, or delivery change affected the result.
Check stream behaviour in YouTube Live
Once the source behaves as expected in OBS, confirm that the YouTube live preview and the viewer-facing playback show the same section of the stream. A local preview may be smooth while an upload issue, encoder interruption, or playback buffering affects what arrives at YouTube. Conversely, a viewer may notice latency and mistake the delay between capture and playback for a gap at the loop boundary.
Check the stream health messages during the test, and use a representative scene rather than a static placeholder if the real channel has movement. YouTube's encoder documentation covers output settings such as rate control, keyframe interval, and transport. Use settings appropriate to your resolution, frame rate, encoder, and upload connection, and follow the current official recommendations rather than assuming that a loop-specific setting exists there.
YouTube's documentation recommends a two-second keyframe interval and says not to exceed four seconds; it also recommends testing upload bitrate with a speed test. These are delivery configuration recommendations, not evidence that a source join will be seamless. If the stream drops or reports health problems at the same time as a loop, address those delivery issues separately from the file's transition.
For a long-running channel, a single test at the start is not the whole operating plan. Check the stream after making scene or file changes, and keep an eye on it during a first full cycle. If you manage a channel from a modest home connection or a small business, separate what you can control locally—the edit and OBS source—from what depends on the live connection and YouTube playback.
Troubleshoot playback and source issues
If the video does not start, verify the selected file path and try opening the file outside OBS. Confirm that the format is supported by the source and that the file itself is not damaged. If a playlist does not appear, verify VLC installation and architecture before changing unrelated stream settings.
If the file plays once but does not repeat, reopen the source properties and confirm Loop is enabled for Media Source or Loop Playlist for VLC Video. Do not rely on Restart playback when source becomes active to repeat at end-of-file. Check that the source is still active and visible in the intended scene, especially if scene changes are part of the broadcast.
If a black interval appears only after a scene switch, inspect whether Close file when inactive is enabled and whether the source needs to reload when shown again. The OBS documentation specifically warns that reactivation can leave a small period with nothing displayed while the file reloads. Test the scene-switch route as well as the end-of-file loop, because they are separate events.
If the picture repeats but sound does not, confirm that the source's audio is reaching the OBS mixer and is not muted or routed differently from the rest of the programme. Check the recording or test stream rather than relying only on mixer movement. For music or speech that still feels out of sync, diagnose delay as its own issue; a loop checkbox is not an audio synchronisation control.
If OBS appears to loop cleanly but the YouTube viewer sees an interruption, review the recording, stream health, and viewer playback before concluding that the source transition caused it. A connection or encoding interruption can coincide with the join by chance. Keep the test narrow: replay the same boundary, observe both picture and sound, and consult YouTube's current live settings guidance where latency or playback settings are involved.
For a channel that should keep playing when your home computer is off, the operational problem is different from configuring OBS on your own machine. StreamNeo can take an uploaded video and run it as a YouTube live stream without leaving that computer on; the file still needs to be checked at its join, because changing where it runs does not make a media transition inherently seamless.
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 OBS loop a Media Source automatically?
No. OBS documents the Media Source Loop property as Off by default. Enable it in the source properties if you want the file to replay after playback completes.
Is Loop the same as Restart playback when source becomes active?
No. Loop repeats the file after it finishes, while Restart playback when source becomes active starts it over when the source becomes visible in the current scene. A source can need one setting, the other, or both depending on how scenes are used.
How do I repeat several videos in OBS?
Use a VLC Video source, add a playlist, and enable Loop Playlist. VLC must be installed, and 64-bit OBS requires 64-bit VLC; test each transition in the sequence, not only the return to the first clip.
Will Loop remove every pause on YouTube Live?
No. It instructs OBS to repeat playback but does not guarantee a frame-perfect or audio-perfect join for every file and setup. Test the real file in OBS and a controlled live stream, watching and listening around the boundary.