A scene change can hide or activate a source, and some OBS source settings stop, unload or restart playback when that happens. For a local Media Source, turn off Restart playback when source becomes active and leave Close file when inactive off; use the equivalent continue-while-hidden behaviour for VLC, and avoid browser-source shutdown or refresh if you want its page state retained.
Those settings control OBS, not every player embedded in a website or the whole YouTube broadcast. A third-party player may still pause or reload, so test the actual project and content through the scene changes you plan to use before relying on it overnight.
Why playback can pause at a scene change
A scene in OBS is an arrangement of sources: for example, a background video, a logo, a text label and a browser overlay. When you move between scenes, a source may become hidden in one arrangement and visible in another. OBS source properties determine what happens to playback while the source is not visible and when it becomes active again.
That distinction matters in a 24/7 stream. If the same video appears in several scenes as separate sources, a transition might activate a newly configured source rather than preserve the playback position of the one you were watching. Even when a source remains in the project, a setting that unloads or restarts it can make the picture stop briefly or begin again when the next scene appears.
There are two different questions to investigate. First, did OBS keep the source alive and playing while hidden? Second, did the media or website player itself continue? OBS settings can address the first question for supported source types, but they cannot guarantee that an embedded third-party player behaves seamlessly or that YouTube ingest, the network or a long-running computer remains uninterrupted.
Start with the source type. A file added as a Media Source, a playlist handled by a VLC Video Source, and a webpage displayed by a Browser Source have different controls. The OBS media source settings for a VOD livestream are a useful point of reference for the local-file case, but check the properties in your own project: source behaviour is configured per source.
Keep a local Media Source active when hidden
For a video stored on the computer, select its Media Source in the Sources list, open its properties and check the playback options. If the file should carry on while the scene changes, leave Close file when inactive unchecked. OBS describes this setting as closing the file when the source is not visible; when the source is displayed again, that can mean a delay before it appears.
Also turn off Restart playback when source becomes active if returning to the source should not start the file from the beginning. OBS documents this option as on by default. With it on, making the source active again can trigger a restart, which is usually the wrong behaviour for a continuous background video that is meant to keep its current position.
The settings solve different problems. Keeping the file open avoids unloading it while hidden; disabling restart avoids deliberately starting it over on activation. One does not substitute for the other. If you want the video to restart each time you bring it back, you may choose differently, but that is a design choice rather than a continuity setting.
Do not confuse Loop with either of these options. Loop controls whether the file starts again after reaching its end. Enable it when the media is intended to repeat, and leave it off if it should finish rather than cycle. Looping a file does not by itself prevent a scene change from unloading or restarting the source.
A practical arrangement is to have one background Media Source and change only the foreground elements: a title card, a schedule panel or a temporary notice. OBS’s guide to sources and source ordering explains how items are arranged and layered. Keep the playback source in the scene or scenes where it needs to remain available, and place changing graphics above it rather than creating duplicate background videos with different playback positions.
Check restart and close-file options deliberately
Before adjusting a source, note its current properties and decide what it ought to do when hidden. A children’s story loop that must continue beneath a brief information panel has a different goal from an intro clip that should replay whenever a scene is selected. The settings should match that intent, rather than being switched on or off by habit.
Use this quick check for a local file:
| Media Source option | For playback to carry on while hidden | What it controls |
|---|---|---|
| Restart playback when source becomes active | Off | Whether playback starts again when the source becomes active |
| Close file when inactive | Off | Whether OBS closes or unloads the file while the source is not visible |
| Loop | Only if the file should repeat | Whether playback starts over after the file reaches its end |
These controls are a useful first diagnosis when the clip restarts at a transition or reappears late. If the image continues but sound disappears, investigate audio routing and track choices separately; the three options above describe media playback behaviour, not every part of the audio path. Likewise, a frozen picture can have causes outside scene visibility, including a problematic file or machine load. Avoid changing several unrelated settings at once, so a test tells you which adjustment mattered.
For more context on how a local file behaves in a live setup, see the OBS settings for a YouTube VOD livestream. If your project uses a single repeated file as its whole channel, also consider the trade-offs of looping pre-recorded videos around the clock; scene continuity and the broader choice of how to run a channel are related, but they are not the same technical problem.
Keep a VLC source playing while hidden
If the media is supplied through an OBS VLC Video Source, open that source’s properties and look for Visibility Behaviour. OBS documents choices that determine whether playback continues, pauses or stops when the source is not visible. Choose the continue-playing behaviour when the source should remain in motion in the background during a scene change.
This is distinct from a local Media Source. Do not assume that a setting with a similar purpose exists under the same name or defaults for both source types. Select the actual VLC source in the Sources list and confirm its own visibility behaviour. If you use a playlist, test a transition while one item is playing and again around an item change; a successful scene transition does not establish how every playlist or media file will behave over a long run.
VLC is a requirement, not an optional extra, for this OBS source type. If you do not need VLC-specific playlist handling, a local Media Source may be simpler for a single file. If the material is on a webpage, the relevant controls are in Browser Source instead. Choose based on where the content comes from and what needs to keep playing while hidden, rather than selecting VLC on the assumption it is built into every OBS installation.
Check VLC installation and architecture
If the VLC source is missing, fails to initialise or does not behave as expected, first verify that VLC is installed. OBS notes an architecture requirement: 64-bit OBS needs 64-bit VLC. Installing a different architecture can prevent OBS from using the VLC components it expects, even if a VLC player appears to be present on the computer.
Check which OBS build you are running and install the matching VLC architecture from VLC’s own distribution. Then reopen OBS if needed, select the source and review its visibility behaviour. This is a prerequisite check, not a guarantee that a particular file or playlist will play correctly; the media format and the rest of the setup still matter.
If installing VLC is inconvenient or the source only needs to show one local file, compare whether a Media Source is adequate before rebuilding the scene. If the source must use a webpage player, switching to VLC does not automatically solve the webpage’s playback behaviour. Keep the source type aligned with the actual content and retest after any change.
Avoid Browser Source shutdown and refresh settings
A Browser Source displays a webpage inside OBS. Open its properties and, if the page’s player should retain its state across scene switches, leave Shutdown source when not visible unchecked and Refresh browser source when scene becomes active unchecked. The first option shuts down the source while hidden; the second refreshes it when it becomes active. Either action can discard page state or prompt the embedded player to reload.
These are OBS page-lifecycle settings, not controls over the player’s own rules. A website may pause video while hidden, require interaction, lose a session or change its behaviour for reasons OBS cannot override. Leaving shutdown and refresh off is a way to avoid OBS deliberately unloading or refreshing the page at each transition; it is not proof that every site will keep playing without a gap.
For a children’s channel, a browser player may also depend on the site’s own content, account, or playback controls. Check that the webpage is appropriate for your intended stream and that you have the necessary rights to use the material. Do not treat a persistent browser source as a substitute for understanding what is being rebroadcast, or as a promise that YouTube will accept or maintain the stream.
The OBS Browser Source guide describes the source’s shutdown and refresh options. If you are still choosing the wider workflow for a channel, this is different from scheduling YouTube live streams with streaming software: scheduling concerns when a broadcast is set to begin, while these controls concern what OBS does to a hidden source during a scene transition.
Test scene changes before going live
Test the exact project, not just a blank scene with a sample clip. Save a copy of the production scene collection, start playback and switch among the scenes that will actually be used: for example, the main animation, an overlay with a bedtime message and a screen with a channel schedule. Watch whether the video continues from the same point, starts over, disappears temporarily or returns only after loading.
Test each source type separately if the project mixes them. A Media Source’s settings do not determine what happens to a Browser Source on the same canvas, and VLC’s visibility behaviour belongs to the VLC source. Change one relevant property at a time and repeat the same transition. Keep notes of what you changed so you can restore the intended configuration if an experiment makes the result worse.
Check sound as well as the picture. A source can remain visible while audio behaviour changes because of how the scene is built or how audio is routed. Listen at the start and end of a transition, and verify that temporary overlays do not unexpectedly cover the programme or expose the desktop. For a live channel, a test should include the ordinary scene changes and the less frequent ones you might make during maintenance.
Finally, distinguish an OBS test from an end-to-end broadcast check. A local preview can show that a source remains active in OBS, but it cannot establish that a website’s player will always behave the same way, that a network connection will hold or that YouTube ingest will stay healthy. For broadcast settings such as upload capacity, use a separate checklist like bitrate guidance for a YouTube radio livestream, and verify the current guidance from the relevant official sources.
If the practical problem is that a home computer must stay awake for an always-on channel, there is also a different operational choice: StreamNeo can take an uploaded video and run it as a YouTube live stream without leaving your computer switched on. That addresses the computer-running burden, not OBS scene configuration or the behaviour of a third-party embedded player.
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
Will these settings guarantee that a kids’ stream never pauses?
No. They control how OBS handles the source when it becomes hidden or active, but they do not guarantee uninterrupted playback by an embedded website, the computer, network connection or YouTube. Test the complete setup and check the current official guidance for the services involved.
Should I enable Loop on a Media Source?
Enable Loop only when the file should repeat after it reaches the end. It does not keep a source loaded during a scene change and does not prevent a restart triggered by the activation setting. For continuity, check Close file when inactive and Restart playback when source becomes active separately.
Does a VLC Video Source work without VLC installed?
No. VLC must be installed for this source type, and OBS documents that 64-bit OBS requires 64-bit VLC. If that dependency does not suit your setup, consider whether a local Media Source or Browser Source better fits where the content comes from.
What should I change for an embedded webpage player?
In the Browser Source properties, leave Shutdown source when not visible and Refresh browser source when scene becomes active off when you want OBS to retain the page rather than unload or refresh it on a transition. The website’s own player may still pause or reload, so confirm its actual behaviour in the project you intend to use.