OBS does not create Super Chat alerts itself; you add an alert overlay from a third-party service as a Browser Source. Before setting it up, confirm that YouTube has enabled Supers for your channel and that the particular stream can receive them.
For a YouTube looping stream, the overlay belongs in the same OBS scene as the video, positioned above it and sized to your output canvas. The alert still depends on YouTube eligibility and the overlay service delivering the event, so test the whole composition rather than assuming a visible widget guarantees a notification.
Check YouTube Supers eligibility first
A Browser Source cannot make an ineligible channel or stream accept Super Chats. First open YouTube Studio and confirm that Supers are available and enabled for your channel. YouTube’s Super Chat and Super Stickers eligibility guidance explains that availability depends on factors including location, applicable policies and the video’s settings. Check the current guidance for your channel and territory, as feature availability can change.
Eligibility also needs to hold for the specific live stream. YouTube lists restrictions for certain types of video, including age-restricted, unlisted and private videos, videos made for kids, and YouTube Giving fundraisers. Supers are also unavailable when live chat or comments are turned off. Read the exclusions on YouTube’s official page rather than relying on the fact that a previous stream accepted a Super Chat.
For an always-on channel, check the settings that apply to the broadcast before you build the overlay. Confirm its visibility, audience setting and live-chat availability in YouTube Studio. A widget can be present in OBS while YouTube does not offer viewers the option to send a Super Chat; these are separate parts of the setup.
This distinction matters when troubleshooting. If the alert does not appear, first establish whether a Super Chat could have been sent on that stream. Then investigate the third-party alert configuration and its delivery. A correctly pasted URL cannot remove a YouTube restriction, and an enabled YouTube feature cannot fix a hidden or paused overlay.
Choose a third-party alert overlay
OBS Studio does not supply stream alerts. The OBS Project’s stream-alerts FAQ describes adding alerts from third-party providers using a Browser Source. In practice, the provider hosts a web overlay, and OBS displays that page inside a scene. The looping video remains its own source; the alert page is another layer in the same scene.
StreamElements documents a YouTube workflow that fits this approach: connect your YouTube account, choose or create an overlay, configure its AlertBox, and add the resulting overlay URL to OBS. Its overlay documentation describes the overlay approach. Other services may have different menus or YouTube support; the sources here do not establish their current Super Chat-specific steps, so check a provider’s own documentation before choosing it.
There are two routes to keep distinct. The standard route is to use the provider’s overlay URL in an ordinary OBS Browser Source. The other is the StreamElements SE.Live add-on workflow, which has its own integration steps. StreamElements’ SE.Live tutorial for YouTube, dated May 8, 2025, specifies OBS v31.x or newer for that guide. That requirement belongs to its SE.Live add-on workflow; it is not a general requirement for every Browser Source in standard OBS.
Choose based on what you need to change and maintain. If you only need an alert page layered over a loop, a normal Browser Source keeps the job focused: the provider manages the widget, while OBS handles the scene. If you already want the add-on’s integration and your OBS version is compatible with the cited guide, follow the add-on instructions instead. Do not install an add-on simply because you assume ordinary Browser Sources require it.
Plan to use one provider’s instructions consistently. Mixing a URL from one service with settings from another creates avoidable ambiguity: you may not know which dashboard controls the event filter, test alert or pause state. If you are planning a wider setup, first consider how the recorded video reaches OBS; this guide on where to paste a YouTube live stream key in OBS for a recorded video covers that separate part of the workflow.
Connect YouTube and select an overlay theme
In StreamElements, sign in and connect the YouTube account associated with the channel. Follow the provider’s authorisation prompts and review which account is connected before editing. If you manage more than one channel, this simple check prevents configuring an overlay under a different account from the one that is live.
Create a YouTube overlay or select an existing one. The overlay is the page that will be rendered by OBS; its theme controls how events appear. Choose a visual treatment that remains legible over the looping footage. For a devotional stream, for example, a small alert with a clear message may preserve the view of the artwork better than a large animation that covers the centre of the image. For a local news loop, keep important captions and the presenter’s face unobstructed.
Do not confuse a theme preview with a live event. A provider may let you preview or test an alert in its dashboard, but that only helps check the design and rendering path. It does not demonstrate that YouTube will accept a Super Chat on a particular stream or that a future event will be delivered under every condition. Treat the preview as a composition check, not proof of eligibility.
Before moving on, locate the overlay’s AlertBox settings. Keep the provider’s own documentation open while following the current interface; labels can change. StreamElements’ getting-started documentation for overlays is a primary reference for its overlay setup. The goal is to produce one overlay URL whose AlertBox is configured for the event you actually want to show.
Limit AlertBox alerts to Super Chat
If the channel also receives memberships, subscriptions or other events, decide whether those should appear in this scene. For a Super Chat-only display, open the AlertBox settings and leave SuperChat enabled while switching off the other event types. StreamElements documents this YouTube-specific AlertBox path in its SE.Live guidance; follow the current dashboard labels for the standard overlay route as well.
This filter is useful on a continuous channel because the scene may remain on screen for long periods. A membership alert or other event may be welcome in a general chat scene, but it can interrupt a quiet ambience loop or cover a shop promotion unexpectedly. Filtering is a presentation choice; it does not change which events YouTube considers eligible, nor does it enable Supers on the channel.
After saving the filter, inspect the alert’s size, duration and placement in the provider’s preview if those controls are available. Avoid assuming that a default theme will suit every canvas. A large graphic may obscure a menu price or a song title, while an alert that is too small may be hard to read on a phone. Make adjustments in the provider’s settings, then return to OBS to check the actual scene.
If you do want other alerts, leave only the event types that serve the channel and test their appearance separately. Keep the Super Chat requirement clear: the desired event must be enabled in the provider’s widget, and YouTube must permit that event on the stream. These are independent checks, not interchangeable switches.
Copy the overlay URL
Once the overlay and event filter are ready, copy its URL from the provider’s overlay controls. Treat it as the address for the rendered widget, not as your YouTube stream key. Paste the URL into the Browser Source’s URL field in OBS. If the provider offers a dedicated copy control, use it rather than reconstructing the address by hand; a missing character can leave the source blank.
Keep the URL private in the same practical way you would treat a control link: do not post it publicly or put it in a visible chat. If you have reason to believe it has been exposed, check the provider’s instructions for changing or regenerating it. The URL is not a promise that alerts will arrive; it identifies the overlay page OBS is being asked to display.
The overlay provider and OBS each have a role. The provider’s page contains the alert widget and receives its event information according to that service’s integration. OBS embeds the page in your scene. If the provider is disconnected from the correct YouTube account, the Browser Source can render while the event does not reach the widget. If the URL is wrong, the provider may be configured correctly but OBS will not display the intended page.
Add a Browser Source in OBS
Open the OBS scene that carries your looping video. Add a new source and choose Browser Source, then give it a clear name such as “Super Chat overlay” so it is easy to identify later. Paste the overlay URL into the source settings. Use the provider’s documented instructions if a setting or control is not clear; do not assume the SE.Live add-on is required for this standard Browser Source method.
The source needs to be visible and above the video in the scene’s source stack. If it sits below an opaque video source, it may load correctly but remain hidden. If you use scene groups or several overlays, check which scene is active when you stream and whether the alert source is included there. A source added to a different scene will not automatically appear in the loop scene.
Keep the loop configuration separate from the alert configuration. This article does not prescribe how to make a video repeat indefinitely; the alert step is simply to add the overlay to the scene used by the broadcast. If the broadcast is already running through a different method, check that its actual output includes the OBS scene you are editing. A looping video and an alert widget can coexist, but the setup alone does not establish that a particular repeat workflow has been tested.
For background on the broadcast side, see how to keep a YouTube live stream running after an SSH disconnect. That is a separate reliability question from whether an alert widget is visible in OBS. Similarly, a 24/7 pre-recorded-video service comparison can help you think through how the underlying video is delivered, but it does not replace YouTube eligibility checks or the provider’s alert setup.
Size the alert for the stream canvas
Set the Browser Source dimensions to match the stream canvas you actually output. StreamElements’ example uses 1920×1080, but that is an example rather than a universal setting. If your canvas is a different size, use its dimensions instead. Matching the source to the canvas gives the overlay room to render at the expected proportions and makes it easier to position relative to the video.
In OBS, place the alert where it will not cover content viewers need to read or see. Check the result against the full frame, not just a cropped preview of the Browser Source. For an Indian restaurant menu loop, keep prices and contact details clear; for a study or lofi station, avoid an oversized panel that dominates otherwise calm footage. Consider how the composition appears on a smaller screen as well as a desktop monitor.
A useful check is to preview the provider’s test alert, then inspect the scene at the intended output size. Confirm that the alert is visible, that text is readable, and that the animation does not spill beyond the frame. If the test is too large or too small, adjust the widget styling or the source dimensions and position, then preview again. Do not change the video’s loop settings to solve a Browser Source sizing issue.
The source being visible in the OBS preview is only one part of the path. Before going live, check that the Browser Source is enabled, sits above the video layer, uses the correct URL, and is not hidden by another source. If the provider has a pause or mute control, verify its state. StreamElements’ troubleshooting guidance calls out checking the URL and whether alerts are paused or muted; this is a sensible first pass when the page appears but an event does not.
A live Super Chat is not a suitable first test if you have not checked the channel’s eligibility and the consequences of sending one. Use the provider’s preview or test feature to check rendering, and check the YouTube eligibility page independently. If you need to verify a real event path, follow the provider’s current official instructions and YouTube’s current rules rather than treating a visual preview as a real transaction.
If the stream itself is created from an uploaded recording and you want your computer switched off, StreamNeo turns that file into a YouTube live stream, so the overlay question does not have to depend on keeping your own OBS computer running. The alert still needs a correctly configured third-party provider, and YouTube’s Supers rules still apply.
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 Super Chat alerts by itself?
No. OBS displays a third-party alert overlay through a Browser Source; the overlay provider and YouTube determine whether an event reaches that widget. The OBS Project explains this in its stream-alerts FAQ.
Do I need SE.Live or OBS v31.x for a Browser Source alert?
No. The v31.x-or-newer requirement belongs to StreamElements’ SE.Live add-on tutorial, not to every ordinary OBS Browser Source. If you choose that specific add-on workflow, check its current instructions and compatibility requirements.
Why can the overlay show but no Super Chat alert arrive?
The channel or stream may not be eligible for Supers, the provider may be connected to the wrong YouTube account, or SuperChat may be disabled in the AlertBox. Also check the overlay URL and whether the alert widget is paused or muted; a visible page does not prove that event delivery is working.
Does adding the alert enable monetisation or guarantee delivery?
No. Adding a Browser Source only places the third-party widget in your OBS scene. It does not enable Supers, change YouTube’s rules, or guarantee that an alert will be delivered.