PPlatformAppStores

Twitch Extensions Directory

General SaaS

Twitch Interactive, Inc. (Twitch) · General SaaS app marketplaces

Best for: Developers building interactive viewer or broadcaster experiences that need to run natively inside Twitch streams, channel panels, or supported mobile viewing surfaces.

Overview

Twitch Extensions are webpages embedded inside Twitch that communicate with Twitch and add interactive functionality for viewers and broadcasters. Extensions can appear as panel, overlay, or component experiences, and mobile-capable extensions can run in the Twitch iOS and Android apps. Broadcasters can browse featured and categorized extensions, review developer-provided information and legal links, install or add extensions, configure them, and activate them in available slots. Twitch supplies the Extension Helper JavaScript API, identity and chat-related capabilities, configuration and feature-flag surfaces, Bits support, and access to Twitch APIs. Most extensions are built by third-party developers, while Twitch provides the hosting, review, and platform framework.

How to build & ship

  1. 1Create an extension in the Twitch Developer Console and choose its extension type.
  2. 2Build the web experience and include the Twitch Extension Helper as the first script in front-end HTML.
  3. 3Configure asset hosting, paths, HTTPS or local testing, and any Extension Backend Service or Twitch API integration.
  4. 4Package the extension files as a ZIP, upload a version, and move it through Local Test or Hosted Test.
  5. 5Submit a live, functioning version for Twitch review; after approval, publish it and make it discoverable and installable through Twitch.

Key APIs & SDKs

Twitch Extension Helper JavaScript API
Twitch API / Helix
Extension Backend Service (EBS)
Twitch Developer Console / Extensions Manager
Extension iframe and postMessage communication

Integration types

Embedded app
Extension

Authentication & security

  • Primary auth: Twitch Extension Helper authorization callback, which supplies a JWT for Extension Backend Service calls and a helixToken for front-end Twitch API requests.
  • Also supports: Twitch API OAuth access tokens where the selected Twitch API operation and scope require them.
  • Security review: Required
  • Public approval requires Twitch review covering functional loading and configuration, technical implementation and asset/source transparency, mobile behavior where applicable, content and commerce compliance, and moderation and privacy-related requirements.
  • Twitch requires a live review channel and an activated extension that loads successfully, plus sufficient testing and configuration information and required files, fetched URLs, and human-readable submitted code. It reviews functional, technical, mobile, content, commerce, and applicable moderation requirements. Approved extensions can be released; unapproved extensions may remain in testing or allowlisted states, and Twitch may remove non-compliant extensions.
  • Not publicly specified
Auth docs Store policies

Monetization

Free
Usage-based
Revenue share
Onboarding
Not publicly specified
Commission
Not publicly specified
Merchant of Record
Not publicly specified

Pros & cons for builders

Pros

  • Native panel, overlay, component, and supported mobile surfaces for interactive experiences.
  • Extension Helper capabilities cover identity, context, configuration, chat and actions, feature flags, and Bits.
  • Official monetization support includes Bits and subscription-status-based features.

Cons

  • Public release is gated by Twitch review and detailed technical and content policies.
  • Extensions operate within Twitch’s iframe and runtime constraints and available slot limits.
  • Revenue-share percentages, commissions, onboarding fees, merchant-of-record treatment, and directory-specific API limits are not publicly specified.

Frequently asked questions

How do I get my app approved on Twitch Extensions Directory?

Twitch requires a live review channel and an activated extension that loads successfully, plus sufficient testing and configuration information and required files, fetched URLs, and human-readable submitted code. It reviews functional, technical, mobile, content, commerce, and applicable moderation requirements. Approved extensions can be released; unapproved extensions may remain in testing or allowlisted states, and Twitch may remove non-compliant extensions.

What authentication does Twitch Extensions Directory use?

Twitch Extensions Directory apps primarily authenticate with Twitch Extension Helper authorization callback, which supplies a JWT for Extension Backend Service calls and a helixToken for front-end Twitch API requests., also supporting Twitch API OAuth access tokens where the selected Twitch API operation and scope require them..

How is Twitch Extensions Directory monetized?

Twitch Extensions Directory supports Free, Usage-based, Revenue share. Typical commission: Not publicly specified. Onboarding fee: Not publicly specified.

Is a security review required to list on Twitch Extensions Directory?

Yes, Twitch Extensions Directory requires a formal security or listing review before apps go live. Public approval requires Twitch review covering functional loading and configuration, technical implementation and asset/source transparency, mobile behavior where applicable, content and commerce compliance, and moderation and privacy-related requirements.