An overlay is added to a scene as a source: in OBS Studio, a still graphic is usually an Image source, while a web-based alert or chat widget is a Browser source. If you have a packaged Streamlabs setup, install or import it through Streamlabs Desktop or transfer its scene collection instead; those routes are not the same workflow.
Start by checking what you were given and which software and operating system you use. The exact menus can differ by app and version, but the practical sequence is consistent: add the right kind of source or collection, put it in the intended scene, arrange its layer and position, then test what viewers will see.
Choose the overlay format
An overlay is any visual element placed over a scene’s underlying video or other content. A border around a camera, a logo in a corner, an alert animation, and a chat box may all be called overlays, but their files and setup steps can be different. Identify the format before opening settings.
| What you have | Usual route in OBS Studio | What to check |
|---|---|---|
| A still image file, such as a logo or frame | Add an Image source | Transparency, dimensions and which scene needs it |
| A widget or alert URL from a provider | Add a Browser source | Correct URL, source width and height, and provider access |
A Streamlabs .overlay file |
Import it in Streamlabs Desktop | Imported scenes and elements may need adjustment |
| A Streamlabs scene collection | Import the collection into the software you intend to use | Scene contents, source paths and compatibility |
The first two choices use sources inside OBS. An image file is a local asset; a Browser source displays a web page supplied by a URL and may show changing content. An imported collection is a set of scene and source arrangements, not just one image. A provider-hosted page may depend on that provider being available and the widget being configured, so do not assume it will load merely because you once copied its URL.
If you only need a logo or a simple frame, a still image is usually the least complicated choice. If alerts or chat must change during the broadcast, a browser widget is more appropriate. If you have already built scenes in Streamlabs, importing them may save repeated setup, although you should inspect the result rather than assume every element transfers exactly.
For an always-on channel, keep the design legible at the size it will occupy on screen. A devotional image with a small channel mark may need little more than a transparent logo; a local news loop may need a clear label that does not cover the headline. If the channel is based on a looping playlist, consider how persistent graphics sit against the content, as in this guide to a 24/7 Tamil songs playlist stream.
Add a static image as a scene source
In OBS Studio, open the scene that should contain the graphic. In the Sources dock, select the plus button, choose Image, then create a source or select an existing one. OBS describes Image sources as a way to add an image or slideshow to a scene; the source-based method lets you use the same graphic in whichever scenes need it. See the OBS guide to sources for the current descriptions and controls.
Choose the file and confirm the source properties. If the graphic is intended to sit around footage rather than replace it, use an image with transparency where needed. A solid rectangle may be correct for a full-screen title card, but it will hide everything underneath it. The source name is for your own organisation, so use something recognisable such as Corner logo rather than leaving several entries called Image.
Check the source order in the Sources dock. The source higher in the list is drawn above sources below it, so put the image above the camera, video, or background it should cover. If it appears behind everything, moving the source higher is a more direct fix than changing the image file.
Select the image in the preview to show its bounding box. Drag it to position it, and use the handles to resize it. For precise dimensions or placement, open the source’s Edit Transform controls; if only part of the source should appear, use the available crop controls. Menu labels can vary with OBS versions, so consult the current interface rather than relying on a screenshot from another release.
Preview the whole scene after adjusting it. Check that the image does not cover subtitles, a face, a song title, a news ticker or another piece of information viewers need. If the same logo belongs on several scenes, add it to each one or use an arrangement supported by your software; do not assume that adding it to one scene automatically adds it everywhere.
A still graphic is useful when the image should not change during the stream. It also avoids relying on a widget page to load. For more involved production questions, the OBS settings guide for a 24/7 playlist stream can help you think about the scene alongside the channel’s ongoing video and audio setup.
Add a browser overlay or widget
For an alert, chat box, or other provider-hosted overlay, first configure the widget with its provider and find the URL it gives you. The label may be Overlay URL, Widget URL or Alert URL, depending on the service. Make sure you have selected the right widget and copied its current URL; a dashboard’s general page address is not necessarily the address OBS needs.
In OBS, select the target scene, choose the plus button in the Sources dock, and add a Browser source. Paste the widget URL into its URL field, then set the source width and height to suit the design. A browser overlay needs a canvas on which to render, so a wrong size can clip content or leave unused space. The OBS Project’s Stream Layout Tutorial: Alerts and Chat Box shows this browser-source route and explains that plugins are not required for alerts.
Place the Browser source above the underlying footage if it should be visible on top. Position and size it in the preview as you would other sources. If the widget includes animation, alerts or chat, test the actual output rather than judging only from its configuration screen. Some widgets may appear blank until an event arrives or until the provider’s page has loaded.
Treat an account-linked widget URL with care. If a provider says the URL is private or can control a widget, do not publish it in a screenshot or public post. The URL is a setting you paste into OBS, not a public-facing link to share with viewers.
A browser widget brings a dependency that a local image does not: it must be served and rendered when you need it. That may be worthwhile for changing alerts, but for a permanent logo a static image avoids an unnecessary external page. You can also run a clean scene without the widget if the provider page fails, rather than letting a blank box or an error message dominate the programme.
This distinction matters for channels that run unattended. If a 24/7 playlist needs to show episode names, decide whether those names are baked into the video or supplied by a changing widget; they are different production choices. The practical considerations in showing podcast episode titles during a 24/7 stream are relevant when deciding whether a changing on-screen label belongs in the scene.
Import a Streamlabs overlay or scene collection
If your overlay is a Streamlabs package rather than a single image or URL, use its import path. Streamlabs Desktop has routes for installing an overlay from its library and for importing an existing .overlay file. In Streamlabs Desktop, the guide documents Settings → Scene Collections → Import Overlay File for an existing file. After import, review the created scenes and elements; the package may not be laid out exactly as you want for your channel.
Streamlabs also describes installing a library overlay by choosing an overlay and its components, with the resulting overlay appearing in a scene collection. Alternatively, you can build scenes manually and add image elements through the Sources controls. These options are useful when you want a packaged design, but they do not turn every overlay into a generic file that works identically in every broadcasting application. Follow the current instructions on the Streamlabs overlay guide for the route matching your file and software.
To use a Streamlabs setup with OBS Studio, Streamlabs documents a scene-collection transfer route. Import the collection into the application you plan to broadcast from, then inspect its scenes, sources and assets. A collection can save you rebuilding the arrangement, but a missing image or a source that needs reconfiguration can still require attention. Confirm that the intended scene is selected and that all expected elements appear.
Streamlabs also documents a plugin route for browsing and installing overlays from within OBS. Its published plugin guidance says the plugin requires OBS Studio 28.0.0 or later and is currently available on Windows; it directs Mac users to Streamlabs Desktop for Mac. Those compatibility details can change, so verify the current Streamlabs plugin guide before installing it. The plugin is a convenience route, not a requirement for adding a browser-source alert in OBS.
Streamlabs describes some overlays as free and some premium animated overlays or features as requiring Streamlabs Ultra. That is a vendor description, not a reason you must use a paid design. If a simple image or browser widget meets the need, OBS’s built-in sources may be enough. If you want a ready-made collection, check what the specific package includes and whether your intended route supports it.
Position, resize and layer sources
Once an overlay is present, treat it as one element in a visual stack. In OBS, sources higher in the list render in front of lower sources. Put the overlay above the content it should decorate, but below any element that should remain in front of it. If a camera frame must surround a camera image, for example, arrange the frame above the camera source; if captions must remain readable, ensure the overlay does not sit across them.
Use the preview to place a selected source. Drag the source to move it and use its bounding-box handles to resize it. For exact positioning, use Edit Transform rather than trying to judge a pixel-perfect position by eye. Cropping is useful when a source has excess margins or when only a portion should show, but it changes what is visible, not the underlying artwork.
Check proportions when resizing an image. Stretching a logo may make it appear distorted, while a browser widget with a fixed design area may be clipped if the source dimensions do not match what the provider expects. When the overlay includes text, inspect it at the actual output size: a label that looks clear while editing may become difficult to read when scaled down.
Do not assume that a single placement suits every scene. A lower-third may work over a static music visual but obstruct a face or lyrics in another scene. If your channel switches between playlists or visual formats, preview each one. The advice for building a 24/7 Telugu old songs channel with VLC is a useful reminder that the material underneath an overlay affects how a scene should be arranged.
Test alerts and chat widgets in the scene
A browser source being present in the list does not prove that it is ready. Check that the URL is correct, the widget is configured with the account or event settings it needs, and its dimensions match the design. Then use the provider’s test alert or equivalent preview control, if available, and watch the scene output in OBS. Do not assume that a real alert will appear merely because the widget’s settings page shows a preview.
For chat, test a message or use the provider’s preview feature if one is offered. Look for clipping, text that is too small, an opaque background that obscures the programme, or content that sits outside the source box. Also check how the widget behaves when there is no activity: an empty chat box may leave a blank panel on screen when you would rather show only the underlying content.
Test the complete scene, not just the widget. Confirm the alert appears above the footage, that it does not cover an important title or caption, and that other sources remain visible afterwards. If the same source is used in multiple scenes, verify each scene separately. A test done in one scene does not establish that another scene has the same source or layer order.
For an always-on broadcast, include this check in the final preparation rather than waiting for the first live event. A channel that plays pre-recorded content still has a live scene and can still benefit from a logo, title, alert or chat overlay, but each extra element introduces another thing to verify. If the main task is keeping the underlying programme continuous, the guide to streaming pre-recorded videos to YouTube addresses that separate part of the setup.
Check software and operating-system differences
The steps above use OBS Studio’s source-based approach, but exact menu wording and placement can differ by software, version and operating system. OBS on one system may not match a tutorial recorded on another. Look for the relevant source type and current application documentation, and avoid assuming a missing menu means the feature is unavailable.
Streamlabs Desktop has its own scene and overlay workflow, including the .overlay import route. A Streamlabs plugin inside OBS is a separate path, with its own compatibility requirements. If you use the plugin, check the vendor’s current compatibility notes first; if it is not available for your system, use Streamlabs Desktop or a supported scene-collection transfer route instead. Do not install a plugin simply because a guide for a different operating system shows it.
Before changing software, consider what you actually have: a still file can be added as an image source in OBS without a Streamlabs plugin, and a provider-hosted alert can be added as a browser source. The plugin is relevant when you want its direct overlay-installation workflow, not as a universal requirement. If the menus on your screen differ, consult the current official instructions for the particular version you have installed.
Finally, keep the scene setup proportionate to the channel. A static logo on a music loop may need no widget at all; a local news channel may need a changing headline graphic, while a study stream may benefit from a quiet timer. The right format depends on what must change during the broadcast and what you are willing to test and maintain. A 24/7 stream also raises operational questions beyond graphics; for example, an OBS-on-cloud setup has different trade-offs from leaving a personal computer running, as covered in the OBS Ubuntu VPS setup guide.
If your overlay is ready but keeping the broadcast running from your own computer is the problem, StreamNeo can remove the need to leave that computer on for the continuous YouTube broadcast; it does not choose or configure the overlay for you.
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
Can I add an overlay in OBS without a plugin?
Yes. OBS has Image and Browser sources for local graphics and web-based overlays, alerts or chat. A Streamlabs plugin is only one separate way to install Streamlabs overlays, not a prerequisite for browser-source widgets.
How do I add an alert overlay to OBS Studio?
Configure the alert with its provider, copy the supplied overlay or alert URL, add a Browser source to the intended scene and paste the URL into its properties. Set suitable dimensions, layer it above the content and test the alert in the scene before going live.
How do I import a Streamlabs .overlay file?
Use Streamlabs Desktop’s documented import route under Settings and Scene Collections, then choose the overlay file. Review the resulting scenes and sources after import; the exact labels may vary as the software changes.
Why is my overlay hidden or clipped?
Check the source order first: an overlay below the footage may be hidden behind it. If it is clipped, adjust the source dimensions or transform and check whether a browser widget’s configured size matches its design; then preview the full scene again.