A Twitch Extension runs on Twitch's servers, not the streamer's PC

The setup

Twitch Extensions are a developer feature documented on Twitch's own developer site, letting a broadcaster add an interactive web application to their channel that viewers see alongside the video. As retrieved on 16 September 2026, Twitch's Extensions documentation defines an Extension as 'a webpage that sits inside Twitch and communicates with Twitch to provide extra functionality,' distinguishing it clearly from a stream overlay built in OBS: an Extension runs inside Twitch's own player for every viewer, not inside the broadcaster's local software.

What the documents show

The documentation names three Extension types: a Panel Extension displays in a box under the video, an Overlay Extension displays as a transparent layer on top of the whole video, and a Component Extension takes up part of the video and can be hidden by viewers. It states an Extension runs in 'a specially sandboxed iframe' communicating with Twitch through postMessage and a JavaScript library called the Extension Helper, and that a logged-in viewer is identified only by an opaque identifier starting with 'U-', not by their Twitch username, unless the user separately grants further access. A second document, the Guidelines and Policies page, covers the review side: submitted Extensions must be tested live on a review channel, submitted JavaScript must be human-readable or have minified libraries sourced separately, and Twitch states it 'reserves the right to remove any Extension, for any reason, at any time.'

The craft

For an avatar-focused channel, an Overlay or Component Extension is a way to put something interactive on top of a performance without touching the broadcaster's own OBS scene at all, since the code runs on Twitch's servers and in each viewer's browser rather than the streamer's PC. The documented content security policy restricts an Extension to loading only its own files, Twitch's own APIs, and specifically allow-listed domains, which is why an interactive overlay the documentation cites as an example can show live data without being able to load arbitrary third-party scripts.

Keeping the creator in control

The opaque-identifier design documented here is a meaningful safety detail: an Extension cannot see who a viewer is on Twitch unless that viewer is separately authenticated and consents, which limits what a poorly built or malicious Extension could learn about an audience. The review requirements in the policies page put a check on Extensions before they reach a channel, though Twitch's stated right to remove an Extension at any time means a creator relying on one for a core interactive feature should treat it as replaceable, not a permanent part of the setup.

• Which Extension type actually fits the interaction being built: panel, overlay, or component?
• Does the Extension request more than the opaque viewer identifier, and if so, is that disclosed to viewers?
• What happens to the channel's layout if Twitch removes or the developer discontinues the Extension?

An Extension is Twitch's own sandboxed platform feature, reviewed and hosted by Twitch rather than a broadcaster's local software. That distinction, laid out in Twitch's own documentation, is the reason an Extension behaves so differently from an OBS overlay even when the two look similar on screen.