# Chrome Web Store now defaults publishers to two extension slots and is retiring Featured badges Google has changed Chrome Web Store publisher limits to an account-specific model with a default of two extension slots, while ending new Featured-badge nominations and shifting ratings toward recent reviews. Chrome extension publishers now face individualized publication caps, with two slots as the default for new or low-history accounts. Existing extensions remain published, increases can be requested, and Google is also retiring the Featured badge while making recent reviews more important to ratings. - Status: Active - Published: 2026-08-24T17:55:35+12:00 - Updated: 2026-08-24T17:55:35+12:00 - Categories: Web Development, Marketing & Distribution, Browsers & Web Standards, Developer Tools, Marketplaces & Platforms - Tags: browser extensions, Chrome, Chrome Web Store, extension publishing - Canonical HTML: https://beyondthe.news/dossiers/chrome-web-store-two-extension-slots-featured-badge-retirement ## 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. ## Key details - The Chrome Web Store changed publisher extension limits on August 20, 2026. - The default publisher allowance is two extension slots, but the actual limit is individualized. - Google says quality and usage of published extensions are among the factors used to set limits. - Existing published extensions remain published, and an account’s new limit will be at least its existing published-extension count. - Publishers can request a higher limit through the developer dashboard. - Pre-submission installation tests now run when a draft package is uploaded. - New Featured-badge self-nominations closed August 20, and Google plans to retire the badge later in 2026. - Extension ratings will increasingly emphasize recent reviews. ## Builder takeaways - Check the publisher-limit value in the Chrome Web Store developer dashboard before scheduling a new extension launch or splitting one product into several listings. - If your roadmap needs more than the current allowance, request the increase early rather than making marketplace approval the last launch dependency. - Use the new pre-submission checks in CI/release procedures, but still budget for human review because passing installation checks does not equal publication approval. - Rework marketplace-growth reporting that treats the Featured badge as a durable acquisition asset; the program is being removed. - Track recent review quality and support issues more closely because the rating system will put less weight on older reviews. ## What to watch - Whether Google publishes clearer criteria for extension-slot increases or account-level limits. - How often legitimate multi-extension publishers are denied or delayed when requesting more slots. - The exact date and UI consequences of the Featured badge retirement. - Whether the revised rating model materially changes rankings or conversion for extensions with strong historical but weaker recent reviews. - Any further changes as the Chrome Web Store V1 publishing API approaches its separate October 15, 2026 retirement. ## Uncertainties - Google has not disclosed the weighting or thresholds used to calculate individualized extension limits. - Google says most limit-increase requests receive an immediate response but has not published an approval rate or service-level commitment. - The Featured badge will retire later in 2026, but the August announcement does not give an exact removal date. ## Sources - [Chrome Web Store updates: Faster reviews, new publication limits, badge updates, and more](https://developer.chrome.com/blog/cws-review-updates-2026) — Chrome for Developers · primary/vendor · 2026-08-20T00:00:00+12:00. Primary announcement for individualized publisher limits, two-slot default, pre-submission checks, recent-review weighting and Featured-badge retirement. - [Use the Chrome Web Store API](https://developer.chrome.com/docs/webstore/using-api) — Chrome for Developers · primary/vendor · 2026-08-20T00:00:00+12:00. Current publishing/API workflow context for Chrome Web Store developers.