Streamlabs overlays are in the Overlay Library, while alert and widget settings are managed separately in the Streamlabs dashboard. You can add a library design to Streamlabs Desktop, use Streamlabs’ documented routes for OBS, or add individual widget URLs as browser sources in other software.
The practical distinction is that an overlay is a design or set of scene components, while a widget theme is a profile of widget settings. Choosing an overlay does not automatically customise every widget to match it. Find the design and components you need, then check and save the relevant widget settings in the theme you intend to use.
Find an overlay in the Streamlabs library
Open the Streamlabs Overlay Library and browse its featured designs or search for a visual idea, game, or use case. Filters can narrow results by keyword, colour, type, widget type, and style. Collections group designs around subjects such as games, holidays, languages, streaming categories, or a shared look, which can be quicker than trying many unrelated search terms.
Start with the actual shape of your stream. A devotional channel may need a clear frame for a still image, a restrained title treatment, and room for a song or programme label. A local news loop might need a compact lower third and space for a ticker. A study stream may be better with no animated border at all. Make a short list of the components you will use rather than choosing a bundle because it looks complete in its preview.
As you compare designs, check four things: whether the colours work with your video, which components are included, whether the design is available to your account, and whether it suits the software you use. Streamlabs says many designs are free and that its full library is available with Ultra; access can vary by item and account, so verify the selected design in the library before building around it. See Streamlabs’ overlay installation and import instructions for the current documented workflow.
An overlay is a starting point, not a promise that every software package will show the same result. Components and setup paths depend on whether you use Streamlabs Desktop, OBS with the Streamlabs plugin, OBS via an imported scene collection, or another application. If you are also deciding how to keep a YouTube channel running when your own computer is off, separate that broadcast decision from the visual design decision; the always-on streaming options review discusses the different operating model.
Choose and apply an overlay theme
When you find a design, select it and use the library’s installation flow. Streamlabs documents selecting the overlay, choosing “Select and Install”, and then selecting the components to include. Treat component selection as a useful editing step: you can leave out panels or alerts that you will not use, rather than placing every available item into the scene and removing clutter later.
After installation, check the scene collection in Streamlabs Desktop. The new design should appear there according to Streamlabs’ guide. Confirm that the intended scene is active and that the included components are present. If you have been given an .overlay file rather than choosing a library design, Streamlabs documents importing it in Streamlabs Desktop under Settings, then Scene Collections, using Import Overlay File.
Do not assume the word “theme” means the same thing in every part of the workflow. The library design determines the overlay components you install; a widget theme holds settings for alerts and other widgets. The two can be used together, but selecting a design does not necessarily change widget appearance, text, animation, or behaviour. That separation is useful if you want one scene design with a different alert treatment, but it means you need to verify both parts.
If you are making a long-running channel, keep the screen useful for the person watching rather than treating every gap as space to fill. A small logo and a legible now-playing label may be enough for a music stream. You can compare overlay decisions with broader live production quality considerations, especially readability and visual restraint. For an audio-led stream, also consider whether visual elements remain understandable when a listener glances at the screen rather than watching continuously.
Add a Streamlabs overlay to OBS
There are two documented ways to bring a Streamlabs overlay into OBS: install and use the Streamlabs OBS plugin, or transfer a Streamlabs scene collection into OBS without the plugin. The right route depends on how you want to manage scenes and widgets. Do not expect a Streamlabs Desktop installation, the OBS plugin, and a separate OBS import to behave identically; follow the instructions for the route and software version you actually have.
With the plugin route, follow Streamlabs’ current installation instructions for the plugin and use its overlay settings to select the design. With the no-plugin route, Streamlabs documents transferring a scene collection by importing it into OBS. The support guide establishes that route, but does not replace the current transfer instructions for each application version. Use the official overlay guide for the appropriate detailed steps rather than assuming that a menu or import behaves as it did in another release.
After setup, inspect the scene in OBS itself. Check that the sources appear, are visible, and are layered in a sensible order. A frame can sit above the video when it should be behind it; a lower third can cover captions; a browser-based element can load differently from a native source. If you imported scenes, confirm the intended scene collection is selected. If you used the plugin, confirm the plugin is installed and that the chosen overlay is the one you meant to apply.
Keep the first check simple: open the scene, look at it at the output size you plan to broadcast, and verify that the live picture remains the focus. Then test transitions and any animated items. More detailed broadcast configuration is a separate topic; for example, OBS keyframe settings concern stream encoding rather than overlay appearance. Avoid changing unrelated stream settings while you are diagnosing a missing border or widget, so that you know which change fixed the display.
Find and customise alerts and other widgets
Widget appearance and behaviour live in the Streamlabs dashboard’s All Widgets area. Choose the widget you want to edit, adjust the available settings, and save. For alerts, that can include how an alert appears and behaves; other widgets have their own controls. The options are specific to the widget, so inspect its own settings rather than expecting one global design control to change everything.
A widget theme is a saved profile of alert and widget settings. If you have different looks for different programmes or scenes, separate themes can help you keep those choices distinct. In the theme area, select Use for the theme you want active. In Streamlabs Desktop, themes can be associated with scene collections, so check both the active theme and the theme assigned to the collection when a widget does not look as expected.
Once saved, add the widget using the route that fits your software. Streamlabs Desktop can use saved widgets as sources. In other streaming software, including OBS, you can use a widget’s URL as a browser source. The precise controls for adding a source belong to the application, and browser-source settings or availability may differ between programs. Streamlabs’ guide to widget themes and using them explains the theme and URL approach.
Alerts deserve a test before you rely on them. Streamlabs documents test controls in the dashboard, Streamlabs Desktop, and its OBS plugin. Send a test for the particular alert variation you intend to use, then check the actual scene for position, legibility, animation, and sound. A dashboard preview alone may not reveal that the source is hidden behind another layer or positioned outside your broadcast canvas. Streamlabs’ alert setup guide covers its testing controls.
For an always-on channel, alerts may not be central to the viewing experience, but the same preview discipline applies to a clock, chat panel, title, or other widget. If the source can update or animate, watch it long enough to see more than its initial loading state. Keep a plain fallback scene available if a widget’s content is distracting or fails to load, rather than allowing a broken element to dominate the broadcast.
Use a widget from a different theme
You do not have to make the entire set of widgets use one theme. Streamlabs documents copying a widget URL from a theme and adding that URL as a browser source. That lets you use a widget from an inactive theme while keeping another theme active for the rest of your setup. For example, you could use an Alert Box URL from one theme and a Chat Box URL from another as separate browser sources.
The trade-off is that you are managing each source individually. Give sources clear names so that you can tell which theme and widget they represent. If you replace a URL or switch the active theme later, retest the affected source; do not assume it has inherited the active theme’s settings. Keep track of which version you have placed in each scene, especially if you have separate collections for a regular programme and a special event.
This route can also help when your streaming program is not integrated with Streamlabs. Add the widget URL in that program as a browser source, using its own instructions. That does not mean every application handles browser sources or Streamlabs widgets in precisely the same way. Check that the URL loads in the target scene and that your program’s source settings fit the intended display before relying on it live.
If you mix themes, do so deliberately. A different alert style may stand out from the rest of the screen, which can be useful for a clear notification or may look inconsistent. Preview the combined scene at its normal viewing size, not only in a large editor window. Use the same colour and typography decisions where possible, but prioritise readable text and unobstructed video over a perfect visual match.
Check sources and preview the result
A successful installation is not the same as a successful broadcast preview. Inspect the final scene in the software that will send it to YouTube. Verify the overlay background is transparent where expected, sources are layered correctly, text is within the visible canvas, and any image or animation loads. Then test the widget itself: fire an alert, check a chat or label if used, and watch a transition from one scene to another.
Previewing at the intended output size matters because decorative details that look clear on a desktop monitor can become difficult to read on a phone. A local news ticker should not be so small that viewers cannot follow it, and a devotional title should not disappear against a bright image. For a looping video channel, assess the overlay against several representative frames, not just the opening frame. If the underlying footage changes in brightness, the same colour treatment can become hard to see later.
Check audio separately from appearance. Some alerts have sound, and a test can confirm whether the sound is present and at a suitable level in your scene. Do not infer that an alert sound is audible to viewers simply because it plays on your computer; verify the actual output monitoring path you use. Keep a written note of the source and theme choices if more than one person maintains the channel.
The work of an overlay is to help someone understand the stream, not to signal that the scene has been customised. A clean picture may serve a lofi or study channel better than several animated widgets. The guide to streaming relaxing music without the file ending deals with continuity of the underlying programme; overlays are a separate layer and should not obscure the content that makes viewers stay.
Troubleshoot missing or unchanged elements
If a whole overlay is missing, first confirm the expected route. A library installation should be checked in the relevant Streamlabs Desktop scene collection; an imported .overlay file is handled through the scene collection import control; an OBS setup may depend on the plugin or on importing scenes. A widget URL, by contrast, must be added as a browser source in the target software. These paths are related but not interchangeable.
If the overlay is present but a component is absent, check whether you selected that component in the installation flow and whether its source is hidden or covered by another source. Inspect the scene collection and the particular scene, not just the library preview. If a browser widget is blank, verify that the URL belongs to the intended widget and theme and that the browser source is in the scene you are viewing.
If a widget looks unchanged after you edited it, check that you saved the settings and that the source is using the intended theme. In Streamlabs Desktop, verify the active theme and the theme associated with the current scene collection. For a widget copied from an inactive theme, the browser source URL may intentionally refer to that other profile. Editing a different theme will not necessarily change the source you already added.
When the displayed result differs from a dashboard preview, test in the actual broadcast application. Confirm the source is visible, refresh or reload it only using the target application's available controls, and test again. If you are using a plugin, check Streamlabs’ current plugin and overlay instructions; if you are importing scenes, check the current transfer guidance. Labels can shift between versions, so avoid following a menu path from a different application or an older tutorial without confirming it applies.
Finally, isolate the fault. Temporarily hide unrelated sources, test one widget, and restore the rest after confirming the result. That is usually clearer than changing the overlay, theme, browser source, and scene collection at once. Keep a plain scene available for the broadcast while you troubleshoot, particularly if your channel is meant to run unattended for long periods. A preview can show that the composition is usable, but it cannot promise uninterrupted operation or resolve a platform or account issue.
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
Where do I find Streamlabs overlays?
Use the Streamlabs Overlay Library to browse featured designs or search and filter by things such as colour, type, widget type, and style. Check the selected item’s components and access requirements in your account before installing it.
How do I add a Streamlabs overlay to OBS?
Streamlabs documents a route using its OBS plugin and a separate route that transfers a scene collection into OBS without the plugin. Follow the current instructions for the route you choose, then inspect the scene in OBS; do not assume it behaves exactly like Streamlabs Desktop.
Where do I customise Streamlabs alerts and widgets?
Open All Widgets in the Streamlabs dashboard, select the widget, adjust its settings, and save. Then use the saved widget as a Streamlabs Desktop source or add its URL as a browser source in other software, according to the workflow you are using.
Can I use a widget from a different theme?
Yes. Streamlabs documents copying that widget’s URL from its theme and adding it as a browser source, even when the theme is not active. Test the source in your target scene, since changing the active theme does not mean every separately added widget will change with it.