A YouTube live overlay, alert or widget usually comes from a provider or editor, not from OBS itself. Configure it there, copy its private overlay URL, and add that URL as a Browser source in the OBS scene where you want it to appear.
The final checks matter as much as the setup: match the source to your canvas, place it above or below the right content, and trigger a test before broadcasting. Providers and widgets differ, so check the controls and event types available in the one you choose.
Choose a provider that fits the job
Start with the thing you want viewers to see. A static logo or label may be a graphic in your video layout; chat, a goal bar or a rotating information panel is a widget; an alert is a short visual or sound that appears in response to an event. These are related, but they are not interchangeable. A provider may support some event types or widgets and not others.
OBS Studio is the production software that combines sources in scenes and sends the finished picture to YouTube. It does not generate stream alerts by itself. As the OBS Project FAQ explains, alerts generally come from a third-party service and are brought into OBS as a source. That distinction helps you decide where to configure an alert: use the provider's editor for its design and event behaviour, then use OBS for where and when it appears in your production.
For a general setup, the Browser-source route is straightforward: the provider gives you a URL, and OBS loads what that URL displays. StreamElements documents overlays that can combine alerts, labels, goals, chat and other widgets in an editor. Streamlabs documents an Alert Box workflow, including its own software and plugin options. Neither setup means every widget will work the same way, or that all providers offer the same event choices.
| Route | What you configure | When it may suit you |
|---|---|---|
| Provider URL in an OBS Browser source | The overlay or widget in a provider editor, then its URL and placement in OBS | A flexible starting point when you want a hosted graphic in a scene without adding a provider plugin |
| StreamElements overlay | One or more widgets in its overlay editor, then the resulting overlay in OBS | Useful if you want to arrange several supported items in a single hosted layout |
| Streamlabs Alert Box | Alert appearance and event choices in Streamlabs, added through its documented software/plugin route or a Browser source | Useful if you already use Streamlabs' alert tools or want its testing controls |
Compare providers by checking whether they support the events and widgets you need, whether you can control the appearance, and how you will test and reuse the result. A plugin can be convenient if you already work in that software; a URL may be simpler if you only need a hosted overlay in OBS. Feature names and dashboard layouts change, so use the current provider documentation and dashboard rather than relying on an old tutorial.
If you are building a continuous channel, keep the overlay modest and useful. A local news loop might need a discreet station label; a study stream might need a clock or a short subject label; a bhajan channel may need only a channel name and current programme. A constant stack of animated elements can obscure the content viewers came to see. Pick the minimum set that answers a real viewer question.
Configure the item and copy its URL
Sign in to the provider you selected and open its overlay or widget editor. Choose the visual elements and event types you actually intend to use. For an alert, decide which events should trigger it, how the message should read, and whether it should play sound. For a static label or chat panel, check its text, colours and background. The exact controls depend on the provider and the particular widget.
Save or publish the changes using the provider's own controls before copying the URL. Some editors give you a URL for an entire overlay, while others let you copy a link for a particular widget or scene. Make sure you have selected the version you edited. If the provider offers multiple themes, confirm the active theme is the one you mean to broadcast; otherwise, the displayed alert can differ from the preview you were editing.
Treat the overlay URL as private. StreamElements warns that overlay URLs can contain sensitive tokens. Anyone with a link may be able to load the associated overlay, depending on the provider's access model. Do not post it in a public document, screenshot, chat or support forum. If you think the link has been exposed, use the provider's account controls or support guidance to replace or protect it.
The URL is not necessarily a downloadable graphic. In the Browser-source workflow, OBS loads the provider's hosted page, which can render the graphic or widget. Keep the link in a password manager or another private record if you need to add it to more than one scene later. Do not assume a URL copied from an editor is safe to share merely because it looks like an ordinary web address.
Add a Browser source in OBS
First select the scene that should contain the overlay. In OBS, sources belong to scenes, so adding a Browser source to one scene does not automatically put it in every other scene. The OBS tutorial for alerts describes the general sequence: select a scene, add a Browser source, paste the alert URL, then adjust the source dimensions.
In the Sources dock, choose the add button and select Browser. Give the source a name that will make sense later, such as “Alerts” or “Chat panel”. In its properties, paste the provider URL into the URL field. Set the width and height to suit the overlay and your stream canvas, then confirm the changes. The exact property labels can vary between OBS releases, but the key is to use the Browser source and the URL supplied by the provider.
For StreamElements, its support guidance gives 1920×1080 as the default Browser-source size unless the source resolution has been changed. That is a provider default, not a universal requirement. Use dimensions that match the layout you made and the canvas you produce. Its guidance also discusses 30 or 60 FPS depending on stream settings and computer capability; treat that as guidance for that provider's setup, not a rule that applies to every overlay or computer.
A provider plugin is an alternative workflow, not a requirement for using alerts. Streamlabs documents adding its Alert Box through its OBS plugin, while the Browser source approach works without that plugin. Choose one route for a given alert and test it; avoid adding the same alert through both a plugin and a Browser source, since that can result in duplicate display or sound.
Size and position the source in the scene
After adding the source, look at the OBS preview. If the source is bigger or smaller than intended, adjust its width and height in the Browser-source properties or transform controls. A full-canvas overlay may need to occupy the complete canvas even if most of its page is transparent. A chat panel or alert region may instead use a smaller area. What matters is the actual rendered layout, not just the dimensions printed in the provider editor.
Drag the source in the preview to place it. Keep text and alerts away from the edges where they might be cut off, and check that they do not cover important faces, subtitles, lyrics or information. For example, if a local news loop has a lower-third caption, a chat panel in the same corner may obscure the story details. Move one element or change the layout before going live rather than hoping viewers will tolerate the overlap.
Source order controls what covers what. The OBS sources guide explains that sources higher in the list render above sources lower in the list. Place a graphic above the camera or background if it should cover them; move it below an element if that element must remain in front. If a camera disappears after you add an overlay, inspect the source order before changing the camera itself.
For a layout with several elements, rename sources clearly and group related items where useful. Keep alerts distinct from always-visible labels so you can hide or adjust them independently. If you copy a scene or use several scenes, check each one rather than assuming source visibility or placement carries across exactly as you intend. A reused source may share settings, while a separately created one can drift in size or position.
Set visibility and interaction behaviour
Decide whether the item should be visible all the time or only in particular scenes. A channel label may belong in every programme scene, while an alert box might be enabled only where you want event notifications. Use the eye control in the Sources list to show or hide a source as you build and review scenes. Before switching scenes during a live programme, check that the source is present in the intended scene and absent where it would distract.
For alerts, the provider's event settings determine which events can trigger the graphic, and the provider may expose separate choices for style, message, duration or sound. Check the active theme and event-specific controls if the alert looks different from the preview. The test button in a provider dashboard or supported software can help verify the particular event. Do not assume that changing a graphic in OBS changes the provider's alert rules; those are configured in different places.
Some Browser sources can be interacted with in OBS using the source's interaction controls, but that is not the same as viewers interacting with a widget on YouTube. Interaction options are provider- and widget-specific. If a widget needs clicks or input, consult its provider documentation and test the behaviour in the production software; do not promise viewers that an on-screen item is interactive unless the full path supports it.
If an alert should appear across several scenes, decide how you will avoid duplicates. StreamElements documents using one alert box across scenes and removing or hiding duplicate alert sources to prevent repeated audio. The practical principle is to use a deliberate arrangement: one intended alert source where possible, and a visibility plan for scene changes. Test a transition between scenes as well as the alert itself.
Test alerts and troubleshoot before broadcast
Run a test from the provider dashboard or its streaming software, if available. Streamlabs documents both dashboard and in-software test functions. Check the animation, sound, text, size and position in the OBS preview. If an event selector is available, test the event type you expect to use, not just a generic sample that may have different text or styling. A preview proves that the graphic can render; it does not prove that every live event integration is configured correctly.
Then check the result in the complete scene. Confirm the overlay is not hidden behind another source, cut off at the edge or obscuring an important element. Listen for the alert sound in the mix and consider whether it is appropriate for the channel. For a music or devotional stream, an unexpected alert sound can interrupt the programme; you may prefer a visual-only alert or a restrained sound, depending on the purpose of the channel.
| Symptom | What to check first | Practical next step |
|---|---|---|
| Nothing appears | The selected scene, source visibility and URL in Browser properties | Confirm the URL, then trigger the provider's test function |
| Overlay is clipped or misplaced | Browser dimensions and source position | Adjust the source size and placement against the canvas |
| Camera or video is hidden | Source order in the Sources list | Move the overlay above or below the content as intended |
| Wrong alert design or event | Active theme and event-specific provider settings | Save the right settings and test again |
| Two alerts or sounds play | Duplicate sources or plugin and Browser-source overlap | Keep one intended path and test scene changes |
| Link works in editor but not OBS | Whether the correct overlay URL was copied and saved | Re-copy the private URL and check the provider's current instructions |
A blank source is not always a reason to rebuild the scene. Check the selected scene, URL and visibility first, then use the provider's test function. If it remains blank, confirm that the provider has saved or published the overlay and that you copied the correct link. Provider dashboards change, so follow their current troubleshooting steps before relying on an old menu path.
For a channel that loops prerecorded material, separate the visual production problem from the video-loop problem. An overlay source belongs to the OBS scene; it does not repair a gap or black frame in a playlist. If your picture is otherwise set up in OBS, this guide to looping a playlist of videos in OBS on Windows covers a different part of the production. For a long-running channel, also review common black-screen fixes between videos rather than treating an overlay as the cause of every picture issue.
Keep a short pre-broadcast check for the production as a whole: confirm the intended scene is selected, inspect the overlay placement, test an alert, and listen for its sound. If you stream from a phone or mobile connection, a Browser source in a desktop production setup is a different workflow; the continuous-stream mobile data guide may help you think through that separate connection constraint. Do not add an overlay during a live broadcast without checking the transition and result in the programme output.
If the format itself is changing between programmes, keep the widgets appropriate to each audience. A playlist channel may display current-track information, while an overnight study stream may use a quiet clock or label. For a schedule built around different music periods, the article on planning Indian music genres by time of day can help with programming decisions; the overlay is a separate scene element that should be tested alongside those changes.
When you want the uploaded programme to continue without keeping your computer running, StreamNeo addresses that specific operational burden: upload the file, provide your YouTube stream key, and the broadcast runs with your computer off, with monitoring and automatic restarts if it drops. It is YouTube-only; it does not create alerts or replace the provider-to-OBS Browser-source workflow described here.
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
Does OBS create alerts by itself?
No. OBS Studio does not directly provide stream alerts. Configure alerts with a provider, then bring them into OBS through a Browser source or a provider's documented software or plugin route.
Do I need a plugin to add an alert?
No. A Browser source can load a provider's overlay URL, and the OBS Project documents that workflow. A provider plugin may suit you if you already use that software, but choose one route and test it to avoid duplicates.
Why is my overlay blank or in the wrong place?
Check that you are in the correct scene, that the source is visible and that its Browser properties contain the current URL. Then check its dimensions, position and source order, and use the provider's test function to confirm that the overlay itself renders.
Can I share my overlay URL with someone helping me?
Treat it as private unless the provider explicitly offers a safe sharing method. Some overlay URLs contain sensitive tokens, so use the provider's access or collaboration controls rather than posting the URL publicly.