Chrome Web Store | Faster Reviews and New Publishing Limits
Chrome Web Store is changing how extension developers prepare, submit, and manage their releases after a significant increase in store submissions. Published on August 20, 2026, the update introduces automated installation testing before submission, shorter review times, new publisher-specific extension limits, a refreshed rating system, and plans to retire the Featured badge later this year.
Chrome Web Store moves extension checks earlier in the publishing workflow
One of the most practical changes is pre-submission installation testing. Automated checks now begin when an extension package is uploaded to a draft, before the developer formally submits it for review. The tests confirm whether the extension can be installed across supported Chrome platforms and can flag installation or package-validity problems early.
This gives developers an opportunity to correct straightforward issues before entering the review queue. Chrome has also adjusted its review processes and prioritization framework, bringing review times back toward the levels developers normally expect after the recent growth in extension submissions had created longer waits.
Extension publishing limits now depend on each developer account
Chrome Web Store is also replacing a more uniform publishing model with extension limits calculated individually for each publisher. The new system considers factors such as the quality and usage of extensions already associated with the developer account.
The default is two extension slots, but existing publishers will not lose already published extensions because of the change. A publisher's new limit will be at least as high as the number of extensions already published when the system was introduced. Developers who need additional capacity can request a limit increase from the developer dashboard, with Chrome indicating that most requests receive an immediate response.
Ratings will focus more heavily on recent user feedback
The way Chrome Web Store represents extension quality is changing as well. Extension ratings will place more emphasis on recent reviews, giving current user sentiment greater influence instead of allowing much older feedback to shape the visible rating indefinitely.
For extension developers, this can make ongoing maintenance more important to marketplace perception. A product that improves after a difficult launch has a clearer path toward reflecting those improvements in its rating, while an extension whose quality declines may see more recent feedback become increasingly visible.
The Featured badge will be retired later this year
Chrome is also discontinuing the Featured badge program. The badge was originally intended to highlight extensions that met a higher quality bar, but stronger baseline review standards around areas such as security and performance have made Chrome consider it a less useful distinction between extensions.
Self-nominations for the badge closed on August 20, and pending self-nominations are being closed as well. The Featured badge itself will be sunset later in 2026, leaving the refreshed rating system as a more prominent quality signal for people evaluating extensions in the store.
IMPORTANT: Chrome Web Store publisher accounts now have individual extension limits, with a default of two slots. Existing published extensions remain published, and developers can request a higher limit through the developer dashboard.{alertWarning}
Daisuki's Take: What This Means for Web Designers
For designers and developers building browser extensions, the most useful improvement is receiving technical feedback before a release enters formal review. Catching installation problems while the package is still a draft can make the publishing cycle more predictable and reduce avoidable delays.
The new extension limits also make portfolio quality more important for publishers managing several products. Teams building design tools, frontend utilities, accessibility helpers, or other web extensions should keep existing releases maintained rather than treating the store as an unlimited collection of experiments.
We would also pay more attention to current user experience as ratings shift toward recent reviews. With the Featured badge disappearing, reliable updates, clear functionality, performance, security, and ongoing user feedback become even more important parts of how an extension presents itself in the Chrome Web Store.
Sources and Recommended Links
- Chrome Web Store updates: Faster reviews, new publication limits, badge updates, and more | Chrome for Developers Official Blog
