A StreamElements overlay is a browser source built from widget files

The setup

StreamElements is a browser-based overlay and alert platform that a creator layers into OBS or another broadcast application as a source, rather than a standalone broadcast tool. As retrieved on 16 September 2026, the company's own site describes its core products as 'Alerts and Overlays' and 'SE.Live,' which it calls 'the ultimate plugin for OBS Studio.' The distinction is not cosmetic: StreamElements does not replace OBS, it supplies content that OBS displays.

What the documents show

The SE.Live product page states that the tool uses 'native logins for all platforms,' meaning a creator's Twitch or YouTube account connects directly rather than through a manually copied stream key, and that it aggregates a 'multiplatform activity feed' tracking follows, subscriptions, tips and memberships across connected platforms in one place. Separately, the company's public widget repository documents the technical shape of a widget: every widget lives in its own folder containing a widget.html, widget.js, widget.css and widget.json file. That is a genuinely different kind of document from the marketing page. It shows a widget is, mechanically, a small web page with a defined structure that a browser source can render, not a sealed black box.

The craft

In a working setup, a VTuber typically adds a StreamElements overlay as a Browser Source inside OBS, pointed at a URL StreamElements generates once the platform account is connected. The alert widget then displays over the avatar capture without the performer manually triggering anything: a new subscription or tip fires the alert because the widget's own code listens for that account event, per the repository's file structure. Because the widget is a standard web page under the hood, a creator or designer can edit its HTML, CSS or JavaScript directly, which is why a marketplace of custom widget designs exists alongside StreamElements' own default templates.

Keeping the creator in control

Connecting a platform account to a third-party overlay service means that service can read the account events it needs to trigger alerts, which is the trade a creator makes for automation. The documents reviewed here describe the connection mechanism and the widget format; they do not describe StreamElements' data retention practices, so a creator weighing that trade should treat this entry as a description of how the feature works, not a privacy assessment. That gap is editorial to flag, not something the marketing or repository pages address themselves.

• Which platform accounts does the overlay actually need connected, and can any be disconnected after setup?
• Is the widget in use a StreamElements default or a modified widget.html a creator should review before trusting it?
• What happens to the overlay if the underlying platform account connection is revoked mid-stream?

An overlay that looks seamless on stream is, underneath, an ordinary web page StreamElements taught OBS to display. Naming that plainly is more useful to a creator than treating the alert box as unexaminable magic.