To interact with a browser source in Streamlabs Desktop, select Interact to open a separate window for operating the page loaded in that source. Use Properties instead when you need to change source settings, such as audio monitoring; it is not the control window for the page.
That difference matters when you are working with a video, a widget, or a browser-based drawing overlay. The exact controls available depend on the page in the source, so treat the pop-out as a way to operate that loaded content, not as a universal control panel for every website.
What Interact does
A Browser Source displays a web page or widget as part of a Streamlabs Desktop scene. Interact opens a separate pop-out window that lets you use controls on the loaded page. Streamlabs demonstrates it with a video: you can stop or play it, seek through it, or enter fullscreen from the pop-out. The command is useful precisely because the page is being displayed inside a scene rather than in an ordinary browser window.
Think of Interact as an operating view, not an editing view. It does not edit the Browser Source's configuration. If you want to click a button on a loaded page, test a widget control, or use a drawing overlay, open Interact and work in that separate window. If you want to change source-level options, open Properties instead.
The distinction is easy to miss because both commands relate to the same source. A practical way to remember it is: Interact is for controls belonging to the content; Properties is for settings belonging to the source. Streamlabs' guide to controlling a video in a browser source uses that separation for video controls and audio monitoring.
A pop-out does not promise that every site will behave the same way. A page may have no controls to operate, a widget may offer only its own limited actions, and some elements may not respond as expected. If a control is not available or does not work, check that the correct source is loaded and use the relevant widget or page guidance rather than assuming Interact changes the source itself.
Add or select a Browser Source
If you have not added the page yet, create a Browser Source from the Sources panel. If it is already part of the scene, select that source. Make sure you have the intended one when a scene contains multiple browser sources, such as an alert box, chat box, or other overlay.
For a Streamlabs widget, obtain its widget URL from the Streamlabs dashboard, then add a Browser Source and paste that URL into its source settings. Set the width and height to suit the widget and the scene. Those are widget-specific setup steps, not a rule that every website needs the same dimensions or settings. Streamlabs describes this URL-based process in its widget setup instructions.
Use a size that makes sense for how the content will appear in your scene. An alert widget may need room for its visual elements, while a compact control or information panel may use less space. If the page is cut off or looks oddly scaled, inspect its source dimensions and how the source is fitted in the scene before changing unrelated settings. The right dimensions depend on the content and intended layout.
You can also select a Browser Source already in the scene when you need to interact with it. Do not add another source simply because you want to open the pop-out. First identify the existing source by its name or preview; operating the wrong source can make a correct widget appear unresponsive when the actual issue is that another page was selected.
Open the Interact window
Find the selected Browser Source's controls in the Sources panel or the Mixer, then choose Interact. Streamlabs' interface may present source commands through a menu; use the command associated with the browser source you intend to operate. A separate pop-out window should open with the loaded page.
If the command is not obvious, right-click the source and look for Interact in its menu. Streamlabs documents this route for its Annotate and Draw. overlay. Depending on the selected content, the menu and available page controls may differ, but the purpose remains the same: opening a separate window for working with the loaded page.
Once the pop-out appears, arrange it where you can see it alongside the main editor. It is a working window rather than a new scene element. Clicking or drawing in the main editor can select or move sources, which is not the same as operating the page. Use the pop-out when the intended action belongs to the page or overlay.
If no window appears, confirm that the selected source is a Browser Source and that you chose its Interact command rather than Properties or another source action. Also check whether the pop-out opened behind the main application. These are straightforward checks before treating a missing window as a problem with the widget itself.
Operate the page or widget
Use the pop-out's controls to operate whatever page is loaded. For a video page, Streamlabs' example includes play, stop, seeking, and fullscreen controls. These actions affect the content displayed by that page; they are not edits to the source's dimensions, URL, or other configuration.
Widget URLs are a useful example because the page can be both visible in the scene and interactive in its own pop-out. The available actions still come from the particular widget. An alert, a chat box, and a drawing overlay are not interchangeable, so do not expect the same buttons or behaviour from each. If the widget does not expose a control you need, consult its instructions or dashboard rather than assuming a different source setting will create that control.
Streamlabs' Annotate and Draw. overlay shows why the location of the action matters. Its drawing tools are controlled from the Interact pop-out. Drawing in the main editing window can move sources instead, because that window is for composing the scene. Streamlabs explains this workflow in its drawing overlay guidance.
For that overlay, the source also needs to sit above the content you intend to mark in the Sources list. If the drawing is visible in the pop-out but not over the intended scene element, check layer order. Moving the overlay above the target source can resolve a stacking issue, but it does not change what controls are available in Interact.
Close or move the pop-out when you have finished operating the page, then return to the scene preview to check the result. If an action appears not to take effect, verify both which source you selected and whether the control was used in the pop-out. Keep the diagnosis narrow: a page control, scene layer, and source setting are separate things to check.
Use Properties for source settings
Choose Properties when the task is to configure the Browser Source, rather than operate its loaded page. The options there relate to the source itself. Streamlabs' video example specifically directs users to Properties for audio monitoring, while using Interact for controls on the loaded video.
This is the practical boundary: opening Properties does not provide the pop-out page controls, and opening Interact does not change the source configuration. If you are trying to adjust source audio monitoring, look in Properties. If you are trying to click a page control, use Interact. Keeping those jobs separate makes troubleshooting more precise and avoids changing settings that are unrelated to the problem.
Widget setup may involve changing its URL or its width and height in the source configuration. Those are configuration tasks, so look in the source settings rather than trying to do them through the Interact window. Conversely, once the widget URL is loaded and visible, use Interact for controls the widget itself provides. A widget's own dashboard may also offer settings outside Streamlabs Desktop; follow the instructions for that widget when a change is not available in the source properties.
Do not change several settings at once just because a page is behaving unexpectedly. First decide whether the issue concerns the page's controls, the Browser Source configuration, or where the source sits in the scene. Then change the relevant item and inspect the preview again. This makes it easier to see whether the change helped and to undo it if it did not.
Check the scene and audio
After operating a source, check the scene preview as well as the pop-out. Confirm that the content is visible where you expect it, that an overlay is above the items it should cover, and that nothing was moved while you were working in the editor. For a drawing overlay, the source order is especially important: Streamlabs says Annotate and Draw. must be above the content it is meant to mark.
Then check the audio path if the browser source is expected to produce sound. Use Properties for the source's audio monitoring setting, and listen to the result in the way you plan to use it. Monitoring and what reaches the stream are related but not interchangeable assumptions; verify the actual scene and audio behaviour rather than inferring it from a page playing in the pop-out.
If a widget looks wrong, check its layer position first, then consider Streamlabs' troubleshooting suggestions: try browser hardware acceleration on or off, restart Streamlabs Desktop, or remove and re-add the widget source to refresh it. These are options to test, not guaranteed fixes or proof of a specific cause. Streamlabs lists them in its widget troubleshooting guidance.
For a live channel, make this check before relying on a scene for an extended run. A page that looks correct in a pop-out may still be hidden behind another source or have an audio setting that does not match your intended mix. If the broader job is keeping a repeated video broadcast running while your computer is off, this is a separate operational question from Browser Source interaction; our guide to choosing cloud streaming or an Indian VPS explains that trade-off.
When to use a browser source in a longer-running channel
A Browser Source is useful when a scene needs a web-based element such as a widget or an interactive overlay. It lets you place that content alongside other scene sources, and Interact gives you a way to operate the page without confusing its controls with the editor. It is not a substitute for checking whether the page is suitable for the scene or whether its controls behave as needed.
For a channel that runs continuously, distinguish the production tool from the content workflow. Streamlabs Desktop can compose and run a scene on the computer where it is open, but Interact itself does not keep a broadcast alive after that computer or application stops. If the stream must continue through an overnight period, plan for the whole broadcast path, not just the widget interaction. Our guide to making an FFmpeg stream reconnect after an internet outage covers a different part of that reliability problem.
A simple scene test is often more useful than changing everything at once: load the intended page, open Interact, try its actual control, close or move the pop-out, and inspect the scene and audio. If the content will be part of a repeating video channel rather than an interactive overlay, make sure that distinction is reflected in how you build and operate the broadcast. The guide to looping nature videos on YouTube Live addresses that separate content pattern.
StreamNeo is relevant only when the pain is keeping an uploaded video broadcasting without leaving your own computer on: you upload the file, connect your YouTube stream key, and the cloud-run broadcast can be monitored and restarted if it drops. That does not replace Streamlabs' Interact workflow for operating a Browser Source, and it is limited to YouTube.
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
How do I interact with a browser source in Streamlabs Desktop?
Select the Browser Source and choose Interact from its controls or source menu. A separate pop-out opens so you can operate the loaded page, using only the controls that page provides.
What is the difference between Interact and Properties?
Interact opens a pop-out for operating content already loaded in the Browser Source. Properties is for configuring the source, including settings such as audio monitoring; it does not operate the page.
Why is my browser widget hidden behind other scene content?
Check the source order in the Sources list. An overlay that should appear on top must be layered above the content it is meant to cover; for Streamlabs' Annotate and Draw. overlay, the source needs to be above the marked content.
What should I try if a widget looks wrong or stops responding?
First confirm that you selected the intended source and used Interact for page controls. Then check layer position and consider Streamlabs' troubleshooting options, such as toggling browser hardware acceleration, restarting the application, or removing and re-adding the widget source; none is a guaranteed fix.