If a video stops replaying in Streamlabs Desktop, first identify how you added it: a YouTube page in a Browser Source and a video file in a Media Source use different playback controls. There is no single documented cause for every “YouTube video stops looping” report, so the point at which playback stops matters as much as the source setting.
If it plays once and ends, check the loop mechanism for that source. If it stops or starts over when you change scenes, inspect visibility and activation behaviour instead; those controls can change what happens to a source when it is hidden or shown again.
Start by identifying the source
Look in the Sources list for the item that contains the video. A Browser Source loads a URL, such as a YouTube watch page or an embedded player. A Media Source plays a file stored on your computer. Streamlabs Media Share is a separate widget source, not another name for either of those playback paths.
This distinction is easy to miss when the result on screen looks the same: a video is visible in a scene. But the setting that repeats a local file does not control a web page, and a YouTube player’s controls do not set a local file’s loop behaviour. Find the source name, open its properties, and note whether the content is a URL, a file path, or a Media Share widget.
| Source in Streamlabs Desktop | What it plays | First place to check |
|---|---|---|
| Browser Source | A webpage or player loaded from a URL | The page’s playback behaviour, then Browser Source visibility settings |
| Media Source | A video file on your computer | The source’s Loop option and activation behaviour |
| Media Share | A widget that can display shared media, including public YouTube links | The widget’s own setup and behaviour; do not assume it has the local-file Loop option |
Streamlabs describes Media Share as a widget that you add as a Media Share source and configure to accept public YouTube links in its Media Sharing setup guide. That identifies a distinct source path; it does not establish that Media Share has a repeat option. If that is what you use, troubleshoot it as a widget rather than applying instructions for a Browser Source or local file.
If you are building a continuous music channel from a computer, the distinction between the broadcast tool and the content source also matters. The lofi radio setup guide discusses a local streaming arrangement, while this article focuses on the point where playback stops inside a scene. Do not infer that one source type is more reliable than another: the documentation describes different controls, not a reliability comparison.
If it is a Browser Source, check the player first
A Browser Source displays a URL. If that URL opens a YouTube player, replay depends first on playback behaviour available to that page or player context. That is separate from Streamlabs Desktop’s loop control for a local Media Source. Do not look for the local-file checkbox and expect it to repeat a YouTube page.
Check what the page actually does at the end of the video. If the video plays once and then remains ended, the scene may be working normally while the player has not been set to repeat. Where the player presents a repeat control, test it while previewing the scene. However, the official materials reviewed for this issue do not provide universal, current instructions for enabling repeat across every YouTube player, embed, or Browser Source context. A control available on one page may not appear or behave identically in another.
YouTube’s Help pages are the appropriate place to check current player guidance. The evidence here does not establish that YouTube player repeat controls loop every kind of source, and a repeat setting in a page should not be treated as a guarantee about a widget or a local file. Keep your test narrow: use the same URL and source you intend to broadcast, and observe whether it reaches the end, repeats, or stops only after another event.
If your Browser Source uses a YouTube watch page rather than an embed, avoid changing several things at once. First test its own player controls. Then, if the source stops around a scene change, move to the visibility checks below. A single end-of-video test cannot tell you whether the page lacks repeat behaviour or whether Streamlabs has hidden or reloaded the source.
Review Browser Source visibility and refresh settings
Streamlabs documents two Browser Source properties relevant to scene transitions: “Shutdown source when not visible” and “Refresh browser when scene becomes active”. In its Browser Source documentation, Streamlabs explains that shutting down a source while it is not visible stops the page or video; refreshing when the scene becomes active reloads the page when the source appears again.
These behaviours can make playback appear to stop or restart when you switch scenes. With shutdown enabled, a hidden source may no longer continue playing in the background. With refresh enabled, showing it again can reload the page, which is different from resuming exactly where it left off. The documentation describes those behaviours; it does not say that either setting is the cause in every report or that all versions behave identically in every setup.
Open the Browser Source properties and record the current state of both options. If you expect playback to carry on while another scene is live, test with shutdown disabled. If the page should not reload on return, test with refresh disabled. Change one setting at a time, then reproduce the same scene change. This is a diagnostic test, not a claim that disabling both is always the right configuration: keeping a hidden page active may not suit every scene or resource budget.
You can also distinguish the two effects by watching the preview and noting where playback resumes. If it freezes or stops while the source is hidden, shutdown is worth investigating. If it begins again from the start after the source becomes visible, a reload is a plausible explanation to test. Those are inferences from the documented controls, not proof of what happened in your specific session.
Make sure the source is genuinely hidden during the test. A source can remain visible in another active scene, depending on how your scenes are composed. Switching scenes alone does not prove that a particular Browser Source became invisible. Check the scene arrangement and visibility indicator rather than assuming that every scene change shuts the page down.
For a local file, check Media Source Loop
A local video added as a Media Source has its own properties. Open them and confirm that Loop is enabled. The OBS Project’s Media Sources documentation describes Loop as replaying a file after playback completes. That is the relevant control when the content is a file on your computer, not when the source is a YouTube page.
Keep Loop separate from “Restart playback when source becomes active”. The OBS Project documentation treats activation behaviour as a distinct setting: it controls what happens when the source becomes active, rather than making a file replay continuously by itself. If Loop is off, the file can finish even if activation settings are configured. If restarting on activation is on, making the source active again can begin playback from the start rather than continuing at the previous position.
A useful first test is to play the file in an otherwise stable scene and wait for it to reach its end. If it does not begin again, confirm Loop before changing activation settings. Then test hiding and showing the source, or changing scenes, separately. Note whether it repeats at the end, restarts on activation, or stops only after it is no longer active. This helps you avoid treating two different settings as interchangeable.
The OBS Project documentation is useful for explaining the Media Source controls, but it should not be stretched into a claim about every Streamlabs Desktop version or every file. If your properties use different wording, check the current help for the version you are running. Do not assume a VLC playlist control applies to a single Media Source: a playlist and a single local file are different arrangements.
For a channel built around a sequence of hymns or ambient tracks, the content arrangement may matter as well as the source setting. A playlist that reaches its end is not the same issue as one file that should replay; the continuous hymn playlist guide covers the broader playlist problem. Here, establish whether the individual file itself loops before changing how the stream is assembled.
Treat Media Share as a separate case
If the source is Media Share, pause before applying either Browser Source or Media Source instructions. Streamlabs’ setup article identifies Media Share as a widget and explains its use with public YouTube links. It does not establish that the widget provides the same Loop option as a local Media Source, nor does it establish that a YouTube player repeat control will govern every item submitted to the widget.
Check the widget’s configuration and the item being played, then observe whether playback ends on its own or changes when the widget is hidden or its scene is switched. If the source behaviour is not clear in the current documentation, do not assume an undocumented checkbox exists. Test the widget in a controlled scene and consult Streamlabs’ current support material for its specific behaviour.
This distinction is particularly useful if a creator has changed methods over time. A video that used to come from a local file may now be arriving through Media Share or a Browser Source, even though the scene name and layout stayed the same. The source list and properties tell you which control family is relevant; a scene label such as “music” or “live video” does not.
Reproduce the trigger before changing more settings
Run a short diagnostic in the same scene arrangement you use on air. Start playback and watch for three separate events: the end of one pass, a visibility change, and a page refresh or source activation. Record which event comes first. If it ends after one pass with no scene change, investigate the player or Loop setting for the identified source. If it stops only when hidden, investigate visibility behaviour. If it starts at the beginning when shown again, investigate refresh or activation behaviour.
Use one change per test. For example, leave the Browser Source player and URL untouched while testing the shutdown option. Restore the original state if the result does not explain the symptom, then test refresh separately. For a local file, leave scene transitions alone while checking Loop at the end of a pass. Changing several settings together may make playback appear fixed, but it will not tell you which change mattered or whether it will behave as expected overnight.
Also test whether the relevant source remains in the scene that is currently live. A source that is present only in a scene you have left may be hidden, while a source duplicated in another scene may remain visible. The documented shutdown and refresh settings are tied to visibility and activation, so scene construction is part of the test rather than background detail.
Streamlabs’ general YouTube live-streaming guide covers broader setup, but it does not document this loop symptom as a universal bug. The official sources establish what specific controls do; they do not establish a single confirmed cause across Streamlabs Desktop versions and source types. Record the source type, trigger, and setting state if you need to ask support for help.
If scene transitions are only one part of a larger always-on setup, consider whether the computer and broadcast process should remain responsible for keeping the stream going. The computer-shutdown comparison addresses that separate operating question. It will not diagnose a Browser Source or file loop setting, so resolve the playback symptom on its own before changing the wider streaming arrangement.
What to do for a long-running channel
Before leaving a channel unattended, test the exact source in the exact scene sequence you plan to use. Let a local file reach its end, or test the Browser Source player’s repeat behaviour, then switch away and back to the scene. A successful test of the end-of-file loop does not verify behaviour on a scene change, and a successful scene switch does not prove the video will repeat after a pass.
Keep a small note of what you tested: source type, relevant Loop or visibility settings, and the event that caused the stop or restart. If the symptom returns after an update or a source change, that note helps you repeat the diagnosis rather than starting with a guess. Do not treat one successful preview as proof of uninterrupted operation; it establishes only what happened in that test.
For a channel where the specific burden is leaving a computer running to carry a file-based broadcast, StreamNeo addresses that separate operational task: you upload the video and use your YouTube stream key, rather than keeping your own computer switched on for the broadcast. It does not change what a Browser Source, Media Source, or Media Share widget does inside Streamlabs Desktop, so it is not a fix for a particular loop setting.
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
Why does my YouTube video play once and then stop?
First identify whether it is a Browser Source, Media Share widget, or local Media Source. For a Browser Source, check the player’s available repeat behaviour; for a local file, confirm the Media Source Loop option. The documentation does not establish one cause for all source types.
Why does the video stop when I change scenes?
Check whether the Browser Source becomes hidden and whether “Shutdown source when not visible” is enabled. Also inspect “Refresh browser when scene becomes active”, since Streamlabs documents that it reloads the page when shown again. Confirm the source’s actual visibility in your scene arrangement before concluding that a transition caused the change.
Does Media Source Loop repeat a YouTube page?
No: the Media Source Loop option is for a local file, as described by the OBS Project. A YouTube page in a Browser Source uses the page or player’s behaviour instead. Keep the source type in view when choosing which setting to test.
Is there one confirmed Streamlabs Desktop bug behind this?
The official documentation reviewed here does not confirm a universal bug or a single cause for videos stopping across source types. It documents the effects of particular settings, which makes the source type and trigger the useful evidence to collect. Check current official support material for your version if those tests do not explain the behaviour.