Chrome Web Store | Faster Reviews and Publisher Limits
Chrome Web Store announced changes to its extension review and publication systems on August 20, 2026. Developers now receive automated installation feedback before submitting a draft, review times have returned to expected levels, publisher accounts have individualized extension limits, and the store is changing how ratings and quality badges influence discovery.
Chrome Web Store gives extension developers earlier feedback
A growing number of extension submissions had increased review times and made release schedules less predictable. The latest changes are intended to reduce that delay while identifying installation and package problems before an extension enters the complete review process.
Pre-submission installation tests now begin when a developer uploads an extension package to a draft. These automated checks confirm whether the extension can be installed on supported Chrome platforms and flag installation or validity problems early enough for the publisher to upload a corrected package before requesting review.
Review improvements aim to shorten extension release cycles
Chrome Web Store has also optimized its review processes and prioritization framework, bringing review times back toward their expected baseline. A faster initial validation step can prevent developers from waiting through a full review only to discover that the submitted package contains a basic installation problem.
This can be particularly useful when an extension supports web design, browser testing, accessibility, content management, or frontend development workflows. Publishers can identify packaging problems sooner and reduce the risk of delaying an important compatibility update or production fix.
Publisher accounts now receive individual extension limits
New Chrome Web Store publishers have a default limit of two published extensions. The actual limit is assigned individually and may consider factors such as the quality, usage, tenure, activity, and sustained engagement of the publisher's existing extensions.
Extensions that were already published remain available, and the updated limit will not be lower than the number of extensions published by the account when the change took effect. Publishers that reach their limit can request an increase through the Developer Dashboard, with an immediate decision provided in most cases. The publication limit does not apply to Chrome themes.
Recent reviews will have more influence on extension ratings
Extension ratings will place greater emphasis on recent reviews, giving current user experiences more influence over the score displayed in the store. This may help an actively maintained extension recover from older problems, but it also makes the quality of recent versions and support responses more important.
Developers should continue testing updates carefully and monitoring feedback after publication. A release that introduces compatibility, usability, or performance problems may now affect the visible rating more directly than older reviews that no longer represent the extension's current condition.
The Featured badge program will close later in 2026
Chrome Web Store plans to discontinue its Featured badge program later in the year. Google considers the badge less useful as a separate quality signal after strengthening baseline security and performance requirements across the extension ecosystem.
Self-nominations closed when the update was announced, and pending nominations were also closed. The refreshed rating system is expected to become the store's stronger public quality signal, placing more emphasis on the extension's current user experience instead of a promotional designation.
IMPORTANT: The default limit for a new publisher is two published extensions, but limits are assigned per account and can change according to the publisher's history and existing items. Check the Developer Dashboard before planning multiple releases or creating separate extensions for closely related features.{alertWarning}
Daisuki's Take: What This Means for Web Designers
Earlier installation checks can make Chrome extension development more predictable for teams building design, accessibility, debugging, and content-production tools. Catching package failures before review reduces avoidable delays without replacing the need for complete browser and workflow testing.
The new publication limits may also encourage developers to maintain a smaller and more coherent product catalog. For web tool creators, combining closely related functions into a well-supported extension may be more sustainable than publishing several narrowly differentiated items.
We would treat recent ratings as ongoing product feedback rather than a promotional score. Clear release notes, responsive support, compatibility testing, and careful permission choices will remain essential as the store moves away from the Featured badge and gives current user experiences more visibility.
Sources and Recommended Links
- Chrome Web Store updates: Faster reviews, new publication limits, badge updates, and more | Chrome for Developers Official Blog
- Publish in the Chrome Web Store | Chrome Extensions Official Documentation
