For an OBS overlay that should stay loaded while your nonstop YouTube stream changes scenes, leave Refresh browser source when scene becomes active and Shutdown source when not visible off. The first reloads the page when its scene becomes active; the second unloads it while it is hidden or outside the active scene.
Neither setting is a periodic refresh timer, and neither can promise that an overlay’s state or alerts will survive every reload or period out of view. If you need a page reload, use OBS’s manual refresh action deliberately, then test how your particular overlay behaves.
Choose what must persist
Start with what the overlay needs to remember, not with a checkbox. A logo or a static “Now playing” label may have little meaningful state to lose. An alert widget, chat box, countdown, poll, or page with a current session may hold information in the browser page’s memory. Reloading that page can reset that in-memory state; what returns afterwards depends on the page or overlay service.
Think through a normal stream day. You may switch from a devotional loop to a holding scene during a break, move to a news panel, or briefly show a sponsor card. If the overlay scene is inactive during those switches, decide whether it must remain loaded and whether anything should refresh when you return. Those are separate questions, controlled by separate options.
It helps to describe the requirement in observable terms. For example: “When I return to the music scene, the alert widget should still be connected, and a test alert should appear.” That is more useful than “the overlay should keep working”, because you can check the result after a scene switch. For a long-running channel, build the test into preparation rather than waiting for an overnight broadcast to expose a problem.
If the stream itself runs from a computer that stays on, scene and source behaviour remain part of your operating routine. If you are weighing that against a cloud-run video loop, the practical differences are covered in OBS versus cloud streaming for a 24/7 YouTube podcast channel. Whichever approach you use, the overlay page still needs its own behaviour tested.
Understand refresh on activation
OBS describes Refresh browser source when scene becomes active as refreshing the page when its scene is switched to. The event is scene activation: when you switch into a scene containing that source, OBS reloads the browser page. The option is off by default, according to the OBS Browser Source documentation.
That is not the same as refreshing every few minutes, every hour, or on a schedule. The setting does not specify a recurring interval. If your overlay gets data updates while its scene is active, those updates are a function of the loaded page or overlay service, not a timer supplied by this checkbox. OBS’s Sources Guide describes Browser Source as a way to add a web page to a scene, including uses such as alerts and chat.
Turning activation refresh on can be useful when you deliberately want a fresh page load each time you enter a scene. For example, a simple information page that should always start from its initial view may suit that choice. The trade-off is that a fresh load starts the page again. A page may reconnect, reinitialise, discard temporary state, or need time to display content; exact behaviour depends on its implementation.
For an overlay intended to retain a live session or its current state across scene switches, leave the option off unless testing shows that reload-on-return is required. A provider-specific warning illustrates why: Kulhad’s overlay guidance, last updated September 2026, advises that its alert overlay can forget what it has already shown after a reload and may miss alerts received while its scene is away. That warning concerns that provider’s overlay, not every browser source.
Understand shutdown when hidden
Shutdown source when not visible controls whether OBS unloads the browser page while the source is hidden or is not in the active scene. OBS lists it as off by default. With it off, the page can remain loaded while you switch to another scene; with it on, the page is unloaded when it is no longer visible. The Browser Source settings explain the control’s behaviour.
This option answers a different question from refresh on activation. Shutdown determines what happens while the source is out of view. Refresh on activation determines whether the page reloads when you enter its scene. An unloaded page must be available again when needed, but do not assume that loading it again restores a previous in-memory session or its event history.
There is a trade-off. Keeping a page loaded may preserve its current session, but it also means the page remains active in OBS while you are showing another scene. Enabling shutdown unloads an inactive source, which may suit an overlay that does not need to maintain state while hidden. The cited OBS documentation does not quantify resource savings for this setting, so do not treat it as a measured performance improvement for your setup.
For a widget that should continue to receive or retain information while its scene is away, leave shutdown off and test it. For a decorative page with no continuity requirement, unloading may be acceptable. In either case, a hidden page’s behaviour depends on the overlay itself: OBS’s setting defines whether the source is unloaded, not whether a particular service queues events or reconnects without loss.
Set controls for a persistent overlay
For the common nonstop-channel case—a browser overlay that should stay loaded as you move among scenes—begin with both checkboxes off. This leaves the page loaded while inactive and avoids an automatic reload merely because you return to its scene. It is a sensible starting configuration, not a guarantee that the overlay will preserve every event or session.
| Setting or action | What it does | Starting choice for a persistent overlay | Main trade-off |
|---|---|---|---|
| Refresh browser source when scene becomes active | Reloads the page when its scene becomes active | Off | Turning it on gives you a fresh load on return, but may reset page state |
| Shutdown source when not visible | Unloads the page when the source is hidden or inactive | Off | Turning it on unloads the page while away; hidden-page continuity may be lost |
| Refresh cache of current page | Immediately refreshes the current page when you choose the action | Use manually when needed | A deliberate reload may help recover stale content, but can reset in-memory state |
If the overlay looks stale, OBS provides Refresh cache of current page as a manual action. It refreshes the page immediately; it is not an automatic interval. Use it as a recovery or update step when you have a reason to reload, and expect the page to start over. The precise amount of state that returns is determined by the overlay page, not by the button.
Write down the chosen settings alongside the scene name or keep a simple OBS setup note. That helps if someone else takes over the channel or you rebuild a scene after a change. When troubleshooting, change one control at a time and record what happened: whether the source unloaded, whether it reloaded on return, and whether a test alert appeared. If your project also uses a video playlist, the guide to making an FFmpeg playlist skip videos that fail to open addresses a separate failure mode; a resilient playlist does not determine browser-overlay state.
Consider page state and missed events
A Browser Source is a web page rendered in an OBS scene. OBS’s browser implementation is based on the Chrome Embedded Framework, as noted in the obs-browser project documentation. The checkbox controls page loading in OBS; the loaded page or overlay service controls how it updates, stores state, connects to a service, or handles an event received while not visible.
That distinction matters for alerts. Suppose an alert source is on a scene you leave while the stream shows a different scene. If the page remains loaded, it might continue its connection, pause some work, or behave another way. If you enable shutdown, it is unloaded. If you enable refresh on activation, it reloads when you return. None of those facts alone tells you whether an alert arriving in the meantime will be queued, displayed later, or missed.
A reload may reset state held only in the page’s memory. It may also establish a new connection and fetch some information again, depending on the overlay. Do not infer that a reload will replay alerts, or that keeping a page loaded guarantees that every hidden event will be shown. For a provider-specific example, Kulhad’s September 2026 instructions warn that its overlay may forget prior alerts and miss those received while its scene was away. Check the current instructions from your own overlay provider and run a test.
If you want a static graphic, you can avoid browser-page state entirely by using an image source where suitable. If you need a live widget, retain the browser source and test what matters: a scene switch, a hidden interval, and a controlled reload. For a continuous playlist running on a Windows machine, the guide to running a 24/7 YouTube livestream on a Windows VPS discusses the broader running arrangement; it does not replace testing the overlay in OBS.
Test scene switching before going live
Use a controlled test rather than waiting for the first real alert during a long broadcast. Make a copy of the relevant scene collection or note the current settings before you experiment. Have a second scene that does not show the overlay, and use the overlay provider’s preview or test-event function if available. Avoid using a real audience-facing event as your only test.
First, start the source with both controls off. Confirm that the overlay appears and that its normal updates work. Switch to the other scene, wait long enough to match a realistic break, then return. Check whether the page appears, whether its connection indicator changes, and whether a test event is displayed. A short test cannot prove overnight behaviour, but it can expose a reload or visibility issue before you rely on it.
Then test shutdown separately if you are considering enabling it. Turn that control on, repeat the scene change, and note whether the page has to load again when it becomes visible. Finally, test activation refresh separately if you have a reason to use it. Observe that the page reloads on scene entry, and check whether its initial state and test event behave as expected. Restore your intended settings afterwards and verify them before the stream starts.
Keep the checks concrete. Did the overlay reconnect? Did its visible state reset? Did a test alert received while another scene was active appear later? Did manual refresh recover stale content, and what state was lost? Record results for the exact overlay URL and OBS configuration, because another page or version may behave differently. Do not treat a successful scene switch as proof that every future event will be delivered.
If you run a loop on a dedicated machine or cloud setup, make the same scene test part of your handover checklist. A live video loop and a browser overlay are distinct sources with different failure modes. A video can keep playing while an overlay has become stale, and an overlay can reconnect while the underlying stream has stopped. For an always-on channel, check both the picture and the page rather than relying on one indicator.
If the recurring burden is keeping the video broadcast running while your own computer is off, StreamNeo can remove that specific task: you upload a video, add your YouTube stream key, and the channel’s broadcast runs without leaving OBS open on your desk. It does not change how an OBS browser overlay handles hidden scenes or reloads, so test those controls separately.
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 refresh browser source when scene becomes active?
Leave it off when you want the page to stay loaded across scene switches, unless testing or the overlay provider’s guidance gives you a reason to reload on return. Enabling it reloads the page on scene activation, which may reset in-memory state. It is not a periodic refresh setting.
Does shutdown source when not visible refresh the overlay?
No. It unloads the page when the source is hidden or outside the active scene. That is different from reloading a page on scene activation, and it does not specify a recurring refresh schedule.
Will alerts received while the overlay scene is away appear when I return?
There is no universal answer: the overlay service determines whether it queues, replays, or misses events while its page is hidden or unloaded. Test with your provider’s test event and check its current instructions. Do not assume that a reload restores alerts or past page state.
How do I refresh a stale browser overlay deliberately?
Use OBS’s Refresh cache of current page action when you decide a reload is appropriate. It immediately refreshes the page rather than running on a timer. Because reloading can reset in-memory state, check the overlay again afterwards.