Coming soon: Updates to Extension Management

We’re live! Check out the announcement post here: Introducing a new Extension Management Experience


On February 27 March 7, we are rolling out a new Extension management experience on the Twitch Developer Dashboard (now referred to as the Developer Console). This new experience brings a few improvements to setup and maintain Extensions in the console, all of which are a result of your feedback shared via these forums, Twitter, or events like TwitchCon Developer Day. Thank you for your support!

Upcoming improvements

Lower latency: Get back to your development with low wait times on page loads.

Version cloning: Clone any previous version of your Extensions with one click, allowing you to rapidly create development branches that you can test simultaneously before selecting a release candidate.

Add whitelist users by Twitch username: When testing your Extension, you can search for whitelist users by Twitch username, making it easy to collaborate with others as you take your Extension to market.

Easy secret management: Find Twitch API and Extension credentials in one place, so it is easy to get every critical variable you need to continue development.

UX improvements: Our refreshed design organizes information closer to how Extensions operate on Twitch and how information is reflected in the Extensions Directory. We’ve also provided in-context guidance so you know what to do next during any extension state.

Get ready for the new experience

While we do not anticipate any data loss or change in your Extensions’ performance, please take the following precautions as soon as you can.

  1. Backup Extension assets: Please have backup copies of all of your Extension assets, including images and asset files. Most likely, you will have these assets stored as part of your normal development process on your machine or on a code repository like GitHub.
  2. Complete Extension state transitions: Be sure to commit changes to the Extension manifest by saving changes on the current version(s) and its current state. For example, in rare cases changing the description of an Extension without saving changes prior to the migration period could result in the description field reflecting an older (or null) description.
  3. Let us know if you have a release planned between February 24 and March 1 March 3 and March 9: We do not want to disrupt your plans, so if you have a release coming up, please let us know via email ( so we can work closely with your team during this transition.

Launch timeline

On February 27 March 7 8:00 a.m. PST: Extensions development maintenance window begins. During this time, you will not be able to create or edit Extensions. Your Extensions on will still function for streamers and viewers. We anticipate the downtime to be no longer than four hours.

For the latest updates during the launch, including announcements and notification of the maintenance window’s conclusion, you can follow along via @TwitchDev on Twitter.

If you have any questions or need support, visit our website and connect with our team or the community. Thanks for working with Extensions and happy building!