What changed
On August 20, Google changed the Chrome Web Store’s publication model. Each publisher now has an individualized extension limit based on factors including the quality and usage of existing extensions, with a default of two extension slots. Existing published extensions are grandfathered into at least the current count, and publishers can request a higher limit through the developer dashboard. Google also introduced pre-submission installation checks, says review times have returned toward expected baselines, is shifting extension ratings to emphasize recent reviews, and has stopped new self-nominations for the Featured badge ahead of retiring that badge later in 2026.
Why it matters
For developers and small businesses that treat browser extensions as a product portfolio or distribution channel, publication capacity is now partly governed by an opaque account-level quality and usage assessment rather than being effectively open-ended. The immediate risk is not removal of existing extensions but friction when launching additional ones. At the same time, discovery signals are changing: Featured badges are going away and recent reviews will carry more weight, making ongoing product quality and current user sentiment more important than historical reputation.
Two slots is now the default, not a universal hard cap
Google says every publisher account now has an updated individual extension limit, with two extension slots as the default. The limit can be higher based on factors such as quality and usage. Accounts with more published extensions than their newly calculated allowance are not forced to remove them; their limit will be at least their existing published count.
Portfolio expansion can now require an explicit increase
A publisher that reaches its current limit must request additional capacity through the developer dashboard. Google says most requests receive an immediate response, but it has not published a deterministic formula for how quality, usage or other factors translate into slot counts. Teams planning several launches should therefore treat store capacity as an operational dependency rather than assuming another item can always be created on demand.
Review feedback is moving earlier
The Web Store now runs installation checks when a draft package is uploaded, before formal submission. Google says these checks catch installation or validity problems earlier and that its broader review-process changes have brought review times back toward expected baselines. That can shorten failure loops, although Google does not promise a fixed review SLA.
Discovery signals are changing too
Google is ending new self-nominations for the Featured badge and plans to sunset the badge later in 2026. It is also refreshing extension ratings so recent reviews matter more. Publishers that previously relied on a Featured badge or accumulated historical ratings should expect current product quality and recent user feedback to play a larger role in marketplace perception.