If a Streamlabs Desktop video source starts the same clip again, first check whether it is a single-file Media Source or a playlist-capable source. A Media Source’s Loop setting repeats its selected file; it does not advance to another video.
For a sequence, the source must contain multiple items in a playlist and its order and repeat settings must match what you want. The detailed controls described below are documented by OBS, so check your Streamlabs Desktop version and its actual source properties rather than assuming the labels are identical.
Identify the source type in the scene
Open the scene where the repeat happens and inspect the source list. Select the relevant item and open its properties. The important question is not whether the scene contains several video sources, but whether the particular source whose playback you are watching holds one file or a playlist of files.
A scene can contain multiple separate Media Sources, each with its own file. That is different from one source containing several playlist entries. If the first source finishes and nothing changes, the other sources may simply remain in the scene without being activated or shown. A stack of sources is not automatically a queue.
Write down the exact source name and type shown in the properties panel, then note how many media items are listed there. If only one file path or one item appears, treat it as a single-file source until you verify otherwise. If the interface offers a playlist and lists several files under the same source, you have a playlist workflow to inspect.
This distinction matters because the same symptom can have different causes. One file starting over points first to a repeat setting or source activation behaviour. A playlist starting again at its first item could reflect playlist-loop settings, ordering, or a scene/source being reactivated. Do not change several settings at once; establish the source type first so you can test one explanation at a time.
If you are following OBS instructions, keep their scope clear. The OBS Project’s media sources guide describes both Media Source and VLC Video Source behaviour. It is useful for understanding the difference, but it does not prove that every Streamlabs Desktop release exposes exactly the same source types, labels or controls.
Understand what Media Source Loop does
In OBS documentation, Media Source selects a media file, and its Loop option repeats that selected file when playback completes. If the source is set to a single devotional song, for example, Loop makes that song play again; it does not make the source look for a second song elsewhere in the scene.
This is often the whole explanation for “it restarts instead of continuing”. The source is behaving consistently with a single-file repeat configuration, while the intended behaviour is a sequence. Turning Loop off is appropriate when that one clip should play once. It will not, by itself, configure a next-file transition.
Also inspect any setting concerning what happens when the source becomes active. OBS documents Restart playback when source becomes active for a Media Source. A source can become active when it is visible in the active scene; if it is repeatedly hidden and shown, playback may restart as a result. That is a different mechanism from a file reaching its end. In Streamlabs, verify the equivalent setting and its exact wording before applying this explanation.
A useful test is to leave the source visible while the clip runs to its end, then observe whether it starts again. If it does so without a scene change, a repeat option is a likely place to look. If it restarts after switching scenes or toggling visibility, activation behaviour deserves attention. These observations narrow the cause, but they are not a substitute for checking the source properties.
| Intended behaviour | Source contents | Setting to inspect | What to expect |
|---|---|---|---|
| Play one clip once | One media file | Single-file Loop off | The clip should not be configured to repeat itself |
| Repeat one clip | One media file | Single-file Loop on | The selected file repeats; there is no next item |
| Play clips in a fixed sequence | Multiple playlist items | Playlist shuffle off; inspect playlist loop | Items follow the configured list order, subject to source behaviour |
| Play clips in a varied order | Multiple playlist items | Playlist shuffle on | Order is not fixed; this is unsuitable for diagnosing a specific sequence |
The table describes the distinction in the documented OBS controls, not a guarantee about Streamlabs labels or transitions. Treat “what happens when hidden or active” as a separate check from whether one file or a full playlist repeats.
Check whether the clips are configured as a VLC Video Source playlist
OBS describes VLC Video Source as a source that can hold a playlist of items, unlike Media Source, which selects a media file. For a sequence of videos, this is the documented multi-item option in OBS. Its guide also notes that VLC must be installed for VLC Video Source to appear as an available source in OBS. That requirement is specific to OBS guidance; check Streamlabs’ current documentation or the software itself rather than assuming it applies unchanged.
In your Streamlabs scene, inspect the source-type menu and properties for a playlist-capable source. If the source is identified as VLC Video Source, look for a list of entries and confirm that every intended clip is present. If the source is identified as Media Source and shows only one selected file, adding other Media Sources to the scene has not made that particular source a playlist.
If you cannot find a playlist source or the controls do not resemble the descriptions here, do not force an OBS tutorial onto your installation. Record the Streamlabs Desktop version and the source type shown in the properties panel. Source availability and interface details can change across releases, and the research behind this article does not verify exact parity between current Streamlabs and OBS controls.
Keep similarly named features separate. Streamlabs Cloudbot Media Share guidance concerns videos requested by viewers, not a local file source advancing through a playlist. Browser Source controls concern web content in a browser source; they are not controls for a local video playlist. Streamlabs explains those separately in its Browser Source article.
Review playlist ordering and source settings
Once you have confirmed that the source really contains several items, check the list itself. Make sure the files appear in the intended order and that the list has no duplicate entry where you expected a different clip. If the source has shuffle enabled, turn it off for diagnosis. A shuffled playlist is not a reliable way to determine whether a particular next item is configured correctly.
Check Loop Playlist separately from any single-file loop control. In OBS, Loop Playlist concerns repeating the list, while Shuffle Playlist concerns the order of items. They solve different problems: a playlist can be ordered and then repeat from its beginning, or it can play in a shuffled order. These controls should not be treated as interchangeable, and their existence in OBS does not verify identical wording in Streamlabs.
For a sequence that should play once from first item to last, use the equivalent controls available in your version to avoid shuffling and avoid repeating the entire list. For a sequence intended to repeat as a block, playlist looping may be appropriate. In both cases, confirm what happens at the end of the list in a short test; do not infer it from a setting name alone.
Review visibility and activation settings as well. A scene transition, a source being hidden and shown, or switching between scenes can affect when playback starts, depending on the source and its settings. If the first clip repeats only after one of those actions, record exactly which action preceded the restart. If it repeats immediately at its own end while continuously visible, focus first on loop configuration.
A source’s filename and the playlist entry are also worth checking. If a file was moved or replaced, confirm that the listed item resolves to the intended media. Where possible, use a short, clearly distinguishable test clip for each playlist position, so it is obvious whether the transition followed the list or returned to its first item.
Preview playback at the transition point
A static view of the source properties cannot show what the application does at the end of a clip. Preview the actual sequence and watch the transition point. Use short test files if the real videos are long; label them or choose visibly different content so you can identify the next item without relying on filenames.
Keep the source in the same scene and visible during the first test. Observe whether the current file ends, whether the next file starts, and whether the first file starts again. Then repeat the test after a scene change or visibility toggle only if those actions occur in your real setup. Separating these tests helps distinguish end-of-file looping from restart-on-activation behaviour.
For a playlist, begin with shuffle disabled and note the first few items in the configured order. If the result differs, return to the properties and compare the entries rather than changing scene transitions, audio filters and other unrelated settings. Change one relevant setting, repeat the preview, and write down what changed. That simple record prevents a successful adjustment from being lost among several simultaneous edits.
Listen as well as watch if the stream includes audio. A video can appear to advance while its audio track behaves differently, or the transition can produce a brief gap. The purpose here is diagnosis, not a promise of seamless playback: neither a playlist setting nor the source type alone guarantees an uninterrupted transition.
Test the sequence before going live
Use a controlled scene and test the complete behaviour you intend to rely on. Confirm the initial item, at least one transition, and what the source does when the last item ends. If the planned broadcast runs overnight, a quick test of the first transition will not establish what happens at the end of the full playlist or after a scene is switched.
Keep the test local to the source where possible. You can preview in Streamlabs before sending a public broadcast, and you can use an unlisted or otherwise appropriate test arrangement if you need to inspect the YouTube output. Check YouTube’s current live-stream guidance before relying on a specific test workflow. Do not expose material publicly merely to find out whether a source advances.
A useful test note records the Streamlabs Desktop version, source type, number and order of playlist items, loop and shuffle states, and whether the source was hidden or activated before the restart. If playback differs from the expected behaviour, these details make troubleshooting more precise than “the video repeated”. Streamlabs lists support ticket and community routes; include the exact version and a screenshot of the source properties when asking for version-specific help.
If your actual goal is a long-running YouTube channel rather than a one-time scene test, also think through what happens when the local computer or broadcast session needs attention. The electricity and cloud operating-cost comparison helps frame that operational choice without changing the source-level diagnosis. For a channel built around recurring recordings, the guide to replacing a video in a running YouTube playlist is relevant to content maintenance, though it is a separate workflow from configuring a Streamlabs source.
Reconfigure based on the intended playback behaviour
Choose the configuration by describing the desired result in plain language. If one clip should play once, keep a single-file source and disable its repeat option if the corresponding control is available. If the same clip should repeat, enable the single-file loop and expect that same file to begin again. Do not expect either arrangement to advance to another file.
If several clips should play consecutively, use a source that supports a playlist in the version you are running, add the files to that playlist, and verify the list order. Disable shuffle when a fixed sequence matters. Decide separately whether the complete playlist should repeat. Preview the end of an item and the end of the list before using the scene in a live broadcast.
If your version does not expose a suitable playlist source, you can investigate alternatives, but be clear about the added complexity. Multiple individual sources may need explicit scene or playback control to make them take turns; simply adding them does not create a queue. The comparison of OBS alternatives for a 24/7 fireplace stream may help you evaluate a different workflow, while the 24/7 meditation music setup guide covers broader channel planning rather than a Streamlabs-specific fix.
If you want the uploaded video to keep broadcasting without leaving your own computer running, StreamNeo removes that particular operating burden by turning an uploaded file into a YouTube live stream. It does not change how a Streamlabs source handles a playlist, and it is YouTube-only, so make the choice based on whether your need is local scene control or a persistent broadcast from a prepared file.
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 play the next video?
No. In OBS documentation, Media Source Loop repeats the selected file after playback completes. To play several videos in sequence, use a playlist-capable source and verify that it contains the intended items.
Why does the first playlist item start again?
Check whether playlist looping is enabled, whether the list order and entries are correct, and whether shuffle is changing the sequence. Also note whether the source was hidden or made active before it restarted; activation behaviour can be separate from playlist progression.
Are Streamlabs Desktop and OBS controls identical?
This article uses OBS documentation to explain the distinction between a single-file Media Source and VLC Video Source playlists. It does not establish that every Streamlabs Desktop version has the same sources, labels or settings, so verify your installed version and ask Streamlabs support when the controls differ.
Is Cloudbot Media Share the same as a local playlist?
No. Cloudbot Media Share is a viewer-request feature, while a local media source or playlist is configured in the scene. Browser Source settings are also separate and apply to web content, not local video sequencing.