OBS does not create YouTube Live alerts itself. To show alerts in an OBS broadcast, configure them with an alert provider, then add that provider’s overlay to your scene as a Browser Source.
The OBS steps are separate from whether a provider currently supports the YouTube events you want to display. Check the provider’s current YouTube documentation and test the events before relying on them in a live broadcast; the documented OBS workflow does not require an alerts plugin.
What OBS Does and Does Not Provide for Alerts
OBS Studio is where you assemble scenes and sources and send your programme to YouTube. It can display an alert overlay supplied by another service, but it does not itself generate notifications for new subscribers, donations, memberships or other channel events. The alert provider is responsible for connecting to the relevant account, deciding which events to show, and producing the overlay.
In the usual setup, the provider gives you a web address for an overlay. OBS loads that page in a Browser Source, much as a browser displays a web page. You place and size the source in an OBS scene alongside your video, artwork, text, or other elements. The provider’s controls determine the alert’s content and appearance; OBS controls where it appears in your broadcast.
The OBS alert FAQ explains that alerts come from third-party services and that an OBS plugin is not needed for the normal setup. The OBS alert tutorial walks through using a provider URL in a Browser Source. That distinction is useful when troubleshooting: if the browser source is visible but a YouTube event does not trigger an alert, the issue may be the provider connection or its event support, rather than a missing OBS feature.
Choose an Alert Provider and Check YouTube Support
Choose a provider based on the events you need, the customisation you want, and its current instructions for connecting a YouTube channel. OBS names Streamlabs, StreamElements, NerdOrDie and OWN3D Pro as examples of services that can supply alert overlays. Their inclusion in OBS documentation is not confirmation that each currently supports every YouTube event, or that its available events and account requirements have stayed the same.
Before choosing, look up the provider’s own current YouTube documentation. Check that it supports the specific events you plan to display, such as the kinds of channel notifications you care about, and that its connection method applies to your account. A provider might support some events but not others, or change its setup process. Do not infer current compatibility from an old video tutorial or from the fact that the provider offers alerts for another platform.
| What to check | Why it matters | What to confirm |
|---|---|---|
| YouTube event support | The alert overlay can only show events the provider receives and supports. | The provider currently documents the specific YouTube events you need. |
| Account connection | Events depend on the correct channel being connected and authorised. | Which channel and permissions the provider asks you to connect. |
| Alert design | Images, sounds and text affect how the notification fits your stream. | Whether you can customise the alert to suit your channel and viewers. |
| Overlay arrangement | You may want alerts alongside other on-screen widgets. | Whether the provider documents combining the elements you plan to show. |
| Current terms | Features and commercial terms can change. | Current provider documentation and terms, rather than an old comparison. |
OBS notes that StreamElements can combine widgets such as alerts and chat in an overlay. That is a documented example, not a reason to assume other providers cannot combine widgets or that the feature is right for your channel. Check each provider directly. Also check its current pricing and terms before committing; this guide does not compare plans or establish current provider prices.
For a channel that mainly plays a continuous playlist, decide whether alerts add useful information or interrupt the viewing experience. A devotional channel may want to acknowledge a membership without covering the main image, while a study stream may prefer no sound at all. The same question applies to the rest of your presentation: if you are planning a radio-style broadcast, the guide to streaming radio audio with a visualiser covers a different visual treatment that can sit alongside an alert overlay.
Connect the Account with the Provider
Once you have checked the provider’s YouTube support, follow the provider’s own connection steps. The exact wording and screens can change, so treat its current instructions as authoritative. Typically, the provider asks you to sign in, select or authorise the YouTube channel, and grant the permissions it needs to detect events or manage widgets. Read the authorisation prompt and make sure you are connecting the channel you intend to stream from.
After connecting, configure the alerts on the provider’s site. The options commonly include which event types appear and the alert’s image and sound. Keep the first configuration simple: enable only the events you intend to use, choose a readable design, and avoid a sound that overwhelms the programme audio. If the provider offers a test alert, use it to check the visual and audio presentation before adding the overlay to OBS.
The provider may label its address an “Overlay URL”, “Widget URL” or “Alert URL”. Copy the URL for the alert or widget layout you configured, rather than a general dashboard or preview page. Treat this address as private if the provider’s instructions say it can expose or control your overlay; do not post it publicly. If you later change widgets or create another layout, check whether the provider expects you to copy a new URL.
YouTube’s own help pages describe YouTube Live and its channel features, but provider integrations are maintained by the providers. For example, consult YouTube Help on live streaming for YouTube’s current guidance, then use the alert provider’s own documentation for its connection and event support. Neither an OBS walkthrough nor a YouTube Help page should be treated as proof that a particular third-party alert event works today.
Add the Alert Overlay as an OBS Browser Source
Open OBS and select the scene that will contain the alert. In the Sources panel, select the plus button and add a Browser source. Give it a recognisable name, such as “YouTube alerts”, so it is easy to identify later if you add more than one browser-based element.
Paste the provider’s overlay URL into the Browser Source URL field. Set the source width and height to suit the layout the provider tells you to use. These are the page’s dimensions inside OBS, not a promise that an alert will occupy the whole area. If the provider specifies a canvas size, begin with that. Otherwise, use dimensions that fit the scene and check the result in the preview.
Confirm the source and return to the scene. If the provider page is configured correctly, the source should load in the preview, although a quiet overlay may look blank until a test event appears. Use the provider’s test feature or a documented test procedure to see an alert. If you see an error or an unexpected page, check that you copied the overlay URL rather than a dashboard address, and revisit the provider’s instructions.
OBS documents Browser Source properties including viewport dimensions, a custom frame rate and refresh options. Start with the defaults unless the provider’s instructions or a specific troubleshooting need calls for a change. Changing several properties at once makes it harder to tell which change helped. The OBS Browser Source guide describes these settings and confirms the source is part of OBS’s normal functionality. Browser Source is available through official OBS packages on Windows, macOS and Linux.
If you are already building a complex scene, add the alert source to the scene where it should appear rather than assuming it will automatically follow every scene. OBS sources belong to scenes; decide whether alerts should appear in all programme scenes, only in a starting scene, or only during certain segments. You can add the source to each required scene or organise scenes in a way that suits your production, then test the transitions.
Place and Test Overlay Elements in a Scene
Use the OBS preview to position the Browser Source. Select it and drag it into place, or use Edit Transform when you need to enter or adjust its dimensions more deliberately. Leave enough room around the alert so it does not obscure a face, the main devotional artwork, a song title, a news ticker or any other information viewers need to see. A small test on a laptop preview may look different on a television or phone, so check the composition at the output size you intend to use.
OBS draws sources in order: sources higher in the list appear over sources below them. If an alert seems to be missing, it may be behind an image or another browser source. Move it higher in the Sources list and check the preview again. Conversely, if the alert covers something important, change its position or source order. The OBS Sources guide explains layering and how image and text sources can be added and transformed.
Static artwork and labels are separate from the provider’s alerts. Add an Image source for a logo or background, or a Text source for a channel label, then size and position it in the scene. Keep static elements and alert widgets as separate sources where practical: you can adjust or remove one without rebuilding the other. Avoid adding a large frame or logo over the alert area before you have checked how the alert itself is rendered.
Test the layout with more than one alert if the provider offers different styles or event types. A long name or message can take more space than a short one; a graphic may have a different shape from the sample shown in a provider dashboard. Check that the element fits within the video frame, that text remains legible, and that sound does not clash with speech or music. If you intend a quiet stream, confirm that the alert sound is disabled or appropriately restrained in the provider’s configuration.
For a pre-recorded broadcast, an alert overlay and a playlist are separate parts of the production. OBS can compose sources in a scene, while the playback method determines what video or audio is running underneath. If your starting point is a playlist broadcast rather than a conventional camera scene, the guide to streaming a pre-recorded playlist to YouTube with Larix Broadcaster may help clarify that separate workflow; it does not replace testing the alert provider’s YouTube support.
Check Alerts Before Going Live
A source appearing in OBS is not the same as a working alert. Verify the whole path before you rely on it: the intended YouTube channel is connected to the provider, the provider supports the event you want, its test alert appears in the overlay, and the Browser Source is visible in the correct OBS scene. If the provider offers event-specific tests, check the events you plan to enable rather than assuming one successful sample proves every alert type works.
Check both picture and sound. Confirm the alert can be read at the size shown in the scene, does not cover essential content, and plays at a level that fits the programme. If viewers will see the channel on a phone, examine the layout at a smaller display size too. A graphic that looks tidy on a large monitor may become cluttered when the video is reduced.
If an alert does not appear, work from the provider towards OBS. Confirm the account connection and event settings on the provider’s site, then run its test again. Check that the Browser Source contains the current overlay URL and is enabled in the active scene. Look at its source order, dimensions and position; if needed, refresh the source using OBS’s available controls or the provider’s documented advice. Do not install a plugin as a first response: OBS’s documented workflow uses Browser Source without one.
If the test appears in the provider’s preview but not OBS, focus on the URL and Browser Source. If it appears in OBS when tested but a real YouTube event does not trigger it, focus on current provider support, account authorisation and event configuration. This division helps avoid changing scene settings to solve an account integration problem. For a stream that runs continuously, include the alert in your pre-live checks and revisit it after changes to the provider connection or overlay layout. The advice in how to fix a 24/7 YouTube stream that stops concerns a different failure mode, but it is a useful reminder to distinguish a presentation issue from a broadcast interruption.
An OBS alert overlay is only one part of a live setup. It does not establish that your channel, content or event handling meets YouTube’s current policies. Check YouTube’s current official guidance for your use case, and check the provider’s own documentation for changes to its integration. Keep a note of which channel you authorised and which overlay URL belongs to the scene, so a later edit does not leave you testing the wrong connection.
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 provide alerts directly?
No. OBS can display an alert overlay, but a third-party provider supplies the alert and connects it to supported events. Configure and verify the events with that provider, then add its overlay URL to OBS as a Browser Source.
Do I need an OBS plugin to add alerts?
No plugin is needed for the standard workflow documented by OBS. Add the provider’s overlay URL as a Browser Source, then arrange that source in your scene. Follow provider or OBS guidance if you have a separate, specific requirement.
Does every alert provider support YouTube events?
Do not assume so, or assume that support covers every event you want. Check the provider’s current YouTube documentation for the exact events and account-connection requirements, then test them before relying on the alerts in a broadcast.
Why does my alert appear in the provider preview but not in OBS?
Check that the Browser Source has the correct overlay URL, is enabled in the active scene, and is not hidden behind another source. Confirm its dimensions and position in the OBS preview, then refresh or test it according to the provider’s current instructions.