An alert box adds on-screen notifications to your YouTube live video when a provider receives supported events, such as a new public subscriber or a contribution. To set one up, choose an alert provider, connect your YouTube channel, configure the events and appearance, add the widget to your streaming scene, then test it before broadcasting.
The alert box is not supplied by YouTube itself: it is a third-party overlay rendered by your streaming software. Streamlabs Desktop has a native Alert Box source; in OBS Studio and compatible software, you can usually add the provider’s widget URL as a Browser Source.
What an alert box does
An alert box is a visual widget layered over your stream. Depending on the provider and the events it supports, it can show text, an image or animation, and play a sound when the provider receives an event. The source is part of the scene in your streaming software, like a camera or logo, rather than a control in YouTube Studio.
That distinction matters when you troubleshoot. YouTube and a provider have separate roles: YouTube supplies platform event data under its rules, while the provider configures and renders its widget. You then place that widget in the scene you send to YouTube. A missing alert could therefore involve the event, the provider’s configuration, or the source in your scene.
An alert box is also different from a YouTube notification sent to viewers. For encoder-based streams, YouTube says it sends notifications to eligible subscribers after a stream is public and YouTube detects that it is live. A viewer’s account and device settings also affect whether they receive those notifications. See YouTube’s explanation of live-stream notifications.
If you are running a long prerecorded loop, decide whether alerts belong in the presentation at all. A quiet devotional or study stream may benefit from subtle visual notices; a news loop may need a fixed safe area so an alert never covers a headline. Plan the overlay alongside the rotation and scene decisions for multiple 24/7 streams, rather than treating it as decoration added at the end.
Choose an alert provider
First choose a provider that supports YouTube events you care about and offers an integration your streaming program can use. The provider’s settings and interface are where you choose alerts and their appearance. They are not YouTube settings, and the same provider may present different event options for different platforms.
If you already use Streamlabs Desktop, its native source is a direct route. If you use OBS Studio without a Streamlabs plugin, a provider widget URL can be added as a Browser Source. Other compatible software may call the equivalent feature a web source or browser overlay; check that program’s documentation before relying on a menu name. OBS describes how third-party alert overlays are embedded with a Browser Source in its official FAQ.
| Workflow | How the widget reaches the scene | A sensible fit |
|---|---|---|
| Streamlabs Desktop native source | Add Alert Box from Sources | You already produce the stream in Streamlabs Desktop and want its built-in integration |
| OBS Studio Browser Source | Copy the provider’s widget URL into a Browser Source | You use OBS and want a URL-based overlay |
| OBS with a provider plugin | Add the source through the plugin’s integration, if available | You have installed and want to use that provider’s OBS integration |
| Other compatible software | Use its browser or web source, if supported | The programme accepts a widget URL; confirm its instructions first |
These are workflow differences, not a reliability ranking. The available documentation establishes how the integrations are added, but does not establish that one route is universally more reliable or feature-rich. Prefer the programme you already know, and make the test in the actual scene you intend to broadcast.
Connect your channel through the provider’s own account or platform controls, then check which channel is linked before you copy a widget URL. Streamlabs’ YouTube alert setup guide describes channel linking, alert settings, and the available setup routes; its interface labels can change, so use the current guide if the steps on screen differ.
Configure YouTube alert events
In the provider’s dashboard or widget settings, select the YouTube event types you want the overlay to display. Depending on provider support, these can include subscriber, member, or contribution alerts. Read the labels carefully: do not assume every event is available, that one event category works the same across providers, or that selecting it changes YouTube’s own settings.
Then set the visible and audible details. A typical configuration may let you choose an image or animation, sound, message text, duration, and variations for different event conditions. Save the changes before returning to the streaming software. If you use a variation for a particular event, make sure the default alert still has a sensible appearance and message when that variation does not apply.
Keep the alert readable at the size it will appear in the finished video. A long name or message can occupy more space than a short test label, and an animation can draw attention away from captions or the main content. For a bhajan or lofi stream, for example, a short sound and a compact notice may fit better than an elaborate animation over the centre of the frame. The right choice depends on what your viewers need to see and hear.
It is worth separating event configuration from expectations about delivery. A provider can be configured to display a subscriber alert without being able to show every account. YouTube says subscriptions are private by default; a private subscription does not appear in the channel’s Subscribers List. Review YouTube’s subscription privacy guidance and the provider’s current documentation before interpreting a quiet alert feed as proof that nobody subscribed.
For the same reason, do not advertise an overlay as a complete record of channel activity. It is a presentation widget whose behaviour depends on the provider and the events it can receive. If you track growth, use YouTube’s own channel analytics as the source for channel-level reporting, and treat the alert as a moment in the live presentation. The subscriber-growth troubleshooting guide is useful context when a change in alerts and a change in measured channel growth seem to point in different directions.
Add the alert box in Streamlabs Desktop
In Streamlabs Desktop, open the scene where the alert should appear and add an Alert Box from the Sources area. Streamlabs documents the native source in its alert setup instructions. Use the source that belongs to the intended scene, then place it above the background and other elements it should overlay. If it sits below an opaque image or video source, the alert may be active but hidden.
After adding it, inspect the source’s available settings and confirm that it is associated with the correct provider account or widget configuration. The source in the scene is the display path; the provider’s dashboard remains where you normally choose event types and customize their appearance. If you change the widget settings, save them there and retest the source rather than assuming the scene has inherited unsaved edits.
A practical scene check is to look at the alert area at the same canvas size and with the same overlays used in your live scene. Keep it clear of a face, logo, lyrics, lower thirds, or the key information in a news loop. If the stream switches between scenes, add the source only to scenes where alerts should be visible, or use the software’s available scene-sharing method if you intentionally want a consistent overlay. Verify the result on each relevant scene.
If Streamlabs Desktop is not your current production software, there is no need to change programmes just for alerts. A separate workflow may suit your existing setup better. For example, a channel built around a specific OBS scene and replay workflow can keep its existing scene structure and add the alert as another source.
Add its URL as an OBS Browser Source
For OBS Studio without the Streamlabs plugin, copy the widget URL provided by your alert service. In the target scene, add a Browser Source, enter the URL in its properties, and set a width and height that match the canvas area you intend the widget to occupy. OBS’s explanation of Browser Sources and third-party overlays confirms the general method; the provider controls the widget itself.
Treat the widget URL like a credential if the provider presents it as private or warns against sharing it. Do not paste it into a public chat or a screenshot. If you regenerate or replace a URL in the provider dashboard, update the Browser Source too; an old URL can leave the source looking blank even when the provider’s settings are correct.
Check that the Browser Source is enabled and visible in the scene, and that its dimensions are large enough for the provider’s widget. A source can load successfully but render outside the part of the canvas you are viewing, or be covered by another source. If your software has a refresh or shutdown-when-hidden option, understand its effect before changing it: it may affect when the widget reloads, but it does not change whether YouTube exposes an event to the provider.
Some providers also document a plugin-based route for OBS. That is an alternative integration, not a requirement for all OBS users. Choose either the provider’s documented plugin workflow or the Browser Source route that fits your setup, then avoid maintaining duplicate alert sources unless you deliberately want duplicate overlays.
Adjust the overlay in your scene
Position the widget after it is present in the scene, not just in the provider preview. A dashboard preview can show the intended alert, while the live canvas reveals whether it overlaps another element or is too small to read. Select the source and move or resize it within the canvas, then inspect the scene at the output resolution you plan to use.
Think about both visual and audio interruptions. A sound that is distinct on a quiet study stream may be distracting over continuous music; a large animation may temporarily obscure lyrics or a presenter. You can choose a softer sound or a compact image and text combination, or disable audio if the event should be visual only and the provider supports that choice. Check the message length and text contrast against the scene behind it.
For a channel that changes language or content across a playlist, the same placement may not suit every segment. Hindi and English captions, for instance, may use different areas of the frame. Consider whether the alert should move, whether the content layout should reserve a common clear area, or whether it should appear only in scenes where it does not compete with important text.
If your stream runs unattended, an overlay is still a scene element that needs a deliberate test. StreamNeo can remove the need to leave your own computer running for a file-based 24/7 YouTube broadcast, but it does not make YouTube or a third-party alert provider supply every event. Keep the overlay’s event configuration and display path separate from the way the underlying stream is kept on air.
Test alerts before going live
Use the provider’s test function after saving settings, and trigger a test in the scene you will actually use. Streamlabs says its testing controls let creators check how saved changes look before going live. A test can confirm that the widget renders and give you a chance to judge placement, timing, text, animation, and sound. It is not proof that YouTube will expose or promptly deliver every real event.
Check the stream as a viewer would see it, not only the editing canvas. If possible, open the programme’s preview or make a private or unlisted test using the controls appropriate to your channel. Look for clipped edges, unreadable text, a sound that is too loud, or an alert that appears behind another source. The guide to testing a live stream without going public covers the distinction between a controlled test and a public broadcast.
If no test appears, work through the display path in order. Confirm that you tested the correct alert type, saved the provider settings, copied the correct widget URL or added the intended native source, and placed that source in the active scene. Check that it is visible, not obscured, and large enough to render. Then try the provider’s test control again and consult its current troubleshooting notes if the widget itself still does not load.
If the provider’s test works but a real YouTube event does not appear, do not assume the scene is broken. The test checks the widget’s rendering path, while real event delivery depends on what the provider receives and how the event is exposed. A subscriber may have private subscriptions, and provider guidance may describe delays or limits for particular alert types. Check the provider’s current YouTube-specific guidance and YouTube’s own documentation rather than promising that every event must appear.
Keep a small note of what you tested: scene, event type, visible result, and whether you heard the sound. This is useful when you edit a source or change scenes later, because you can retest the parts that changed instead of relying on a test performed before the layout was updated.
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 YouTube provide the alert box?
No. An alert box is a third-party overlay that your streaming software renders in the live scene. YouTube’s own viewer notifications are a separate system, with their own eligibility and account or device conditions.
How do I add alerts in OBS Studio?
Copy the alert provider’s widget URL and add it to a Browser Source in the intended OBS scene, following the provider’s instructions. Check the source’s visibility, dimensions, and stacking order, then trigger a provider test before going live.
Why are subscriber alerts not showing?
Check that the provider is connected to the right channel, the event is enabled and saved, and the widget source is present and visible in the active scene. A test alert and a real subscriber event are different checks: subscription privacy and provider event delivery can affect whether a real event appears.
Does testing prove that every live event will appear?
No. A provider test helps you check that the widget renders and how it looks or sounds in the scene. It does not establish that YouTube will expose every event or that a provider will deliver each one promptly.