If a local clip should repeat while its OBS source remains visible, enable Loop on the Media Source. Restart playback when source becomes active is a separate control: it starts the clip from the beginning when the source becomes active in the current scene.
Neither setting controls YouTube’s delivery of the broadcast, and neither promises a perfectly gapless boundary between plays. Set the source according to the behaviour you want, then test the actual clip and stream output before relying on it overnight.
Loop and restart-on-active solve different problems
These controls answer two different questions. Loop asks what should happen when the file reaches its end. Restart playback when source becomes active asks what should happen when the source becomes active in a scene. One concerns completion; the other concerns activation.
That difference matters when you use a clip as a background, a devotional visual, an ambience scene, or a repeating information slide. If the source stays visible, Loop is the setting that tells OBS to play the file again after it finishes. Restart-on-active does not substitute for it: activation might happen only once, whereas the file can reach its end many times during a long broadcast.
OBS’s Media Sources documentation describes Loop as replaying the file once playback has completed. It describes restart-on-active as restarting a file when its source is in the current scene and visible. The same documentation lists Loop as off by default and restart-on-active as on by default. Check the properties in your installed version rather than assuming those defaults have not changed.
| What you want | Control to inspect | What it affects |
|---|---|---|
| Repeat one local file after it finishes | Loop | Playback completion for that Media Source |
| Start a file again when its source becomes visible in the active scene | Restart playback when source becomes active | Activation of that source |
| Play a sequence of files | A playlist-capable source, such as VLC Video | Playback of a playlist rather than one file |
For a single clip that should run continuously in one scene, start with Loop enabled. Choose the activation setting separately, based on what should happen when you leave and return to that scene. If you need a playlist rather than one repeating file, OBS documents a VLC Video source and a Loop Playlist option; VLC must be installed, and OBS notes that 64-bit OBS requires 64-bit VLC. Consult the current documentation before changing software or relying on a particular source feature.
Enable Loop on a local Media Source
Add the clip as a Media Source in OBS, open that source’s properties, and select Loop. If the clip is already present, open its properties rather than adding a second copy just to change playback behaviour. The setting belongs to that source; changing it does not alter other clips elsewhere in your scene collection.
The practical first test is simple: play the source and wait until it reaches the end. If Loop is enabled, OBS is instructed to replay the file after completion. That is the relevant control for a visible source that should keep repeating. With Loop off, playback reaches the end and does not repeat by virtue of the restart-on-active setting alone.
Check the other source properties as well. Make sure the intended file is selected, the source is not muted if its audio matters, and the source is visible in the scene you are testing. Property names or available options can differ with source type and OBS version, so use the Media Source’s own properties rather than assuming that a setting on a different source controls this clip.
Do not infer seamlessness from the checkbox. The documentation says the file plays again after completing; it does not specify a frame-perfect video join or an inaudible audio transition. A clip with a quiet tail, a fade to black, or a natural pause may make the change less noticeable, but that is a property of your media and playback path, not a promise made by Loop.
If your use case is a long collection of bhajans or ambient tracks rather than one prepared video, a playlist may fit better than repeating a single file. In that case, check the source’s playlist and repeat options, and confirm that the media files are available and play correctly on the machine running OBS. A playlist is a different arrangement from looping one Media Source, so test the transition between separate items as well as the return to the first item.
Decide what activation should do
Restart playback when source becomes active is useful when a source should begin at its opening frame whenever you make it active. For example, you may have a short opening visual in one scene and a separate always-on ambience scene. Returning to the opening scene can make its clip start from the beginning instead of resuming partway through.
That behaviour can be unwanted for a clip that should carry on through scene changes. If you hide the source or switch to a scene where it is not active, its playback state is relevant. OBS’s current Media Source implementation describes restarting on activation when the option is enabled and stopping playback on deactivation. The OBS source implementation is a technical reference, but implementation details can change; for everyday setup, confirm the observed behaviour in your installed release.
A useful decision is to ask what the viewer should see after a scene change. If returning should show the clip from its start, leave restart-on-active enabled. If returning should continue where the source left off, test the result with that option disabled. Loop still handles what happens at the file’s end; changing activation behaviour does not turn Loop on or off.
For a 24/7 channel, a scene transition may be rare, but scheduled changes, manual troubleshooting, and source visibility changes still count. A devotional channel switching between an aarti visual and a title card, for instance, may intentionally restart the aarti when it returns. A lofi station that should preserve a moving background may prefer not to restart it on every activation. Decide from the viewing experience you want, not from a belief that both settings must always be enabled.
Test completion and scene changes separately
Test the two events independently. First, leave the source visible and let the clip finish. This checks the end-of-file behaviour controlled by Loop. Then trigger the scene or visibility change you actually expect to use. This checks activation behaviour. Combining both tests into one quick transition can make it unclear which setting caused the result.
A practical test plan is to use a short copy of the intended clip or a convenient test file, while keeping the same source type and relevant properties. Confirm that it starts, reaches the end, and behaves as expected after a scene change. Then repeat the check with the actual file and the scenes used by the broadcast. A short test file helps you observe the sequence sooner, but it cannot prove that a different final file has identical timing or transition quality.
Watch OBS’s preview and listen to the audio rather than judging only from the source properties. If you can, also make a local recording or inspect the live player from another device. The preview can show you the source’s visual behaviour, while a recording or remote playback gives a more useful check of what passes through the output path. The point is not to measure a benchmark; it is to catch a visible pause, repeated opening, black frame, or audible discontinuity in your own setup.
If you automate hide-and-show actions close to the end of playback, do not assume that an immediate toggle will always land in the same state. An OBS issue report for OBS 30.2.0 on Windows 11 describes a failure to restart when a hide/show action happened immediately at the end; the reporter said a delay of at least one second worked in that case. This is one report tied to a particular version, platform, and timing, not a universal minimum delay or a guaranteed fix. If your scene automation has this pattern, test it on your own setup and adjust its timing only if the observed result calls for it.
For a channel where the computer must remain unattended, record the test outcome and settings somewhere you can find them. Note the OBS version, source name, whether Loop and restart-on-active are enabled, and which scene changes you tested. That small record is more useful than relying on memory after an update or after someone else has edited the scene.
Why a loop boundary may not be gapless
A loop instruction says to play the file again after playback completes. It does not say that the last decoded frame and first frame will meet without any pause, nor that audio samples will join without a click or momentary silence. The available OBS documentation does not make a gapless guarantee, and the research reviewed for this article found no authoritative benchmark for loop smoothness.
The boundary you hear or see depends on the media and the playback path. A clip may have silence, a fade, or a few quiet frames at either end. Its encoding, frame timing, and the way its sound and picture end can also make a transition more or less noticeable. The safe approach is to judge the actual asset rather than expect the Loop option to repair its edit.
If the join is distracting, first inspect the file itself. Listen around the end and beginning with headphones, and watch the final and opening frames. If the clip was designed to loop, check that its content and timing support that use. You may need to revise the edit or choose a different file. Do not make a promise of seamless playback simply because the source repeats in OBS.
Also separate a local loop boundary from an interruption in the live broadcast. If the OBS preview looks right but a remote viewer sees a freeze, missing video, or a stalled player, that may be a delivery or connection issue rather than the source reaching its end. Conversely, if the source itself pauses at the join in the preview and a local recording, changing a YouTube delivery setting is not a direct fix for the source’s restart behaviour.
Keep YouTube delivery settings separate
A YouTube stream key and latency choice concern the path from your encoder to YouTube and the delay before viewers see the broadcast. They do not configure whether an OBS Media Source repeats a file or starts again when visible. YouTube’s live streaming help explains the live-stream setup and delivery context; it should not be read as a control panel for local OBS source playback.
This distinction helps narrow troubleshooting. If the clip fails to repeat in OBS’s preview, inspect the Media Source properties and whether playback reached the end. If the clip looks and sounds right in OBS but the YouTube player behaves differently, investigate the encoder connection and delivery path separately. The guide on why YouTube Live can say “No data” while OBS is streaming is relevant to that second class of symptoms, not a replacement for enabling Loop.
Keep the stream key private and use the current YouTube controls for stream setup. Do not rotate a key or alter latency merely to make a local clip restart; those actions address a different part of the system. If you are troubleshooting scene changes that also affect what reaches viewers, compare OBS preview, any local recording, and the remote player to identify where the difference first appears.
If your goal is a YouTube channel that continues broadcasting when your own computer is off, that is a separate operational choice from how a local OBS source loops. A guide to recorded-video overnight streams can help you think through the overall playback arrangement. For music-led channels, the album-art guide for YouTube internet radio covers a different presentation detail; neither changes the two OBS controls discussed here.
Choose a setup that matches the channel
For one clip that remains visible, enable Loop and test its join. Set restart-on-active according to whether activation should return the clip to its opening. For a sequence, use a playlist-capable source and test both transitions between items and the return to the beginning. These choices are about playback behaviour; YouTube delivery settings remain separate.
For a stream that relies on manual OBS operation, keep the source and scene arrangement simple enough to check before going live. For automation, test the exact sequence and timing rather than assuming a hide/show action at the file’s end will behave identically across versions. In either case, make changes in one place at a time so you can identify which one altered the result.
If the requirement is continuous broadcast without keeping your own computer on, OBS source properties alone do not provide that operating arrangement. StreamNeo addresses the specific burden of leaving a computer running for an uploaded video-based YouTube stream: you upload the video and provide the stream key, and your computer can be off while the broadcast runs. It is YouTube-only, and it does not change what Loop means for a local OBS Media Source.
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
Should I enable Loop or Restart playback when source becomes active?
Enable Loop when you want a local file to repeat after it finishes. Use restart-on-active only if you want the file to begin again when the source becomes active in the current scene. They are separate settings, so choose each for its own purpose.
Does Loop guarantee a seamless YouTube Live loop?
No. OBS documents that the file plays again after completion, but that is not a promise of a frame-perfect or inaudible join. Test the actual file through your playback path and adjust the media if the boundary is distracting.
Do the stream key or latency setting change when OBS restarts the file?
No. Those settings relate to YouTube stream delivery, not local Media Source playback. If OBS preview shows the wrong source behaviour, check the source properties first; investigate delivery separately if the preview is right but the remote player is not.
Why does my clip start over when I return to a scene?
Restart playback when source becomes active may be enabled, and OBS treats the source as active when it is in the current scene and visible. Check that property and test a scene change in your installed version. If you want the clip to resume rather than restart, disable the option and verify the result.