On 20 August 2026 the Chrome Web Store started enforcing a publishing limit on developer accounts. I had twenty published extensions. I asked for an increase. What came back was a limit of 18 of 18 — and two of my extensions were no longer listed. Nobody told me which, and nobody told me why.
I posted about it in r/chrome_extensions mostly to find out whether I had done something wrong. I had not. Other developers replied with limits of 4, of 10, of 11 — every one of them sitting exactly at their own published count.
What Google actually documents
The Chrome Web Store publishing documentation says new publishers are limited to a maximum of two published extensions, that a request for an increase receives an immediate decision based on a number of criteria, and that a request can be denied — for insufficient user engagement, or for not meeting tenure and activity requirements. Themes are excluded from the cap.
Two things are worth saying precisely, because I have seen both stated wrongly since.
The documentation carries no effective date. 20 August is when I was notified, not a date Google published. If you are writing this up, do not attribute my date to them.
“Immediate decision” is doing a lot of work. My request returned a number instantly. It just returned a number lower than where I already was. A support agent escalated it. As of writing there is no decision.
A hypothesis, clearly labelled as one
Across every reply I got, the granted limit matched the developer’s current published count. Four extensions, limit four. Eleven extensions, limit eleven. Twenty extensions, limit… eighteen.
That pattern is consistent with the cap being derived from your existing catalogue rather than assessed on merit. I want to be careful here: this is a hypothesis built from a handful of self-reported numbers on a forum thread, not a finding. It fits the data I have. It is not evidence of intent, and I have no visibility into the criteria Google actually applies. If your own numbers contradict it, I would rather hear that than keep a tidy theory.
One piece of advice in that thread I want to explicitly not repeat: someone suggested paying the developer fee on a second account to double the allowance. Someone else pointed out that operating multiple accounts to work around a limit is the kind of thing that gets both suspended. I do not know which reading is right, and the downside is asymmetric enough that I am not going to find out.
The part that actually stings
It is not the cap. A store deciding how many things one account may list is entirely its business, and I would not have shipped twenty if I had known the number mattered.
It is that two extensions came down and I found out by reading a dashboard. No email, no line item, no name. If a platform can silently unpublish work, then the store listing is not a place where work lives — it is a place where work is displayed, at the platform’s discretion, until it is not.
I have three more games finished and ready. Under an 18-of-18 limit, shipping any of them means taking one down.
So I stopped waiting for the slot
Seven of those games now run in a browser tab at play.dhseadev.online, on hosting I control, with no queue and no cap. The port was less work than the appeal has been: extension games need a chrome.storage API, a launcher, and a service worker, and it turns out only the first of those is real once the URL does the launching.
The engineering side of that is written up in the arcade post, and the hosting side in what Cloudflare Pages taught me. The individual games are still on the projects pages, and the ones that remain published are still in the store.
I am not leaving the Chrome Web Store. I have stopped treating it as the only front door.
Questions I have been asked since
How many extensions can a Chrome Web Store developer publish?
Google’s documentation states new publishers are capped at two published extensions. Established accounts are given a higher limit and can request an increase, which receives an immediate automated decision. Themes do not count toward the cap.
Can a request for a higher limit be denied?
Yes. Google names insufficient user engagement and unmet tenure or activity requirements as reasons. In my case the request returned a limit below my existing published count.
Does Google notify you when an extension is unpublished under the cap?
I received no notification. Two extensions were no longer listed and I discovered it by checking the dashboard. Treat the dashboard as the source of truth rather than your inbox.
Is the limit based on how many extensions you already have?
Unconfirmed. Every developer who reported a number to me had a limit equal to their published count, which is suggestive but is not documented anywhere and is not something Google has stated.
What should you do if you are near the cap?
Have somewhere else to put the work. A static host serves an extension-derived game with no review queue, no cap, and no unpublish button that someone else controls.
Leave a Reply