I Just Published My First Chrome Extension. Now What?

You clicked "Publish". The zip file uploaded. The Chrome Web Store developer dashboard now shows your creation with a little "Pending review" badge. Congratulations, you’re officially a browser extension developer. But what actually happens next?

At exstats.com we crawl the Chrome Web Store daily. Every store-wide figure below comes from our snapshot of 254,621 live Chrome listings taken on September 5, 2026. That lets you measure a normal launch against the whole catalog, not against the handful of extensions you’ve heard of.

The median live Chrome extension has 14 users. Get to 100 and you’re ahead of 75% of the store.

54.1% of live extensions have no ratings at all. Your first review is harder to earn than you think.

Growth is measured in years, not weeks. Listings published in the last two months have a median of 4 users. Listings still up after two years have a median of 105.

The review process won’t kill you (but it might test your patience)

After you hit publish, your extension enters Google’s review queue. Google’s review process documentation puts it plainly: for most extensions review is completed within a few days, but it can take up to a few weeks. If yours is still pending after three weeks, Google asks you to contact developer support rather than wait it out.

Certain things reliably slow you down. Google calls out new developers, new extensions, dangerous permission requests, and significant code changes as signals that trigger closer review. As a first-time developer shipping a first extension, you start with two of those four. Requesting broad host permissions such as `*://*/*` or `<all_urls>` adds a third, because review has to verify that each permission is genuinely necessary. Obfuscated code is not merely slow to review, it is disallowed.

Common reasons for rejection include requesting permissions your extension doesn’t actually need, thin store listing metadata, broken functionality, and privacy-policy gaps when you handle user data. Most are avoidable if you read the Chrome Web Store Program Policies before submitting.

Rejection isn’t the end of the world. You’ll get an email explaining what went wrong, and you can fix and resubmit. Treat the first submission as a trial run.

Correction, September 5, 2026. This section previously said that most submissions clear review in under 24 hours and that over 90% finish within three days, attributing it to Google’s documentation and a measurement from early 2021. That language is no longer on the cited page, and a five-year-old figure should not have been carried as current guidance. The section now follows Google’s current text, which is both vaguer and slower.

Your user count will be humbling. That’s normal.

This is the part no one prepares you for. You check your dashboard a week after launch and see 4 users. Maybe 11. One of them is you.

Don’t panic. Across all 254,621 live Chrome listings, the median extension has 14 users. Not 14,000. Fourteen. Three quarters of the store sits under 100 users, which means the 100-user mark you are quietly embarrassed about is in fact the 75th percentile.

Fewer than one extension in ten has reached 1,000 users. The distribution is brutally skewed: a small set of blockbusters (ad blockers, password managers, big dev tools, translators) holds most of the installs, and the long tail is very long.

One caveat on precision. Chrome publishes user counts in rounded buckets, so treat any individual number as an order of magnitude rather than an exact headcount. Medians and percentile splits survive that rounding fine, which is why we report those instead of averages.

The takeaway: 100 users is a genuinely meaningful milestone. Make it your first target, not your disappointment.

Don’t expect ratings (most extensions have none)

If slow user growth is the first gut punch, the silence in your reviews tab is the second. You can go months without a single rating.

54.1% of live Chrome extensions have zero ratings. Among the 116,808 that do have at least one, the median extension has collected exactly 2 ratings in its entire life. So the bar is lower than it feels: two reviews puts you at the midpoint of the rated half of the store.

Among rated extensions the scores skew high. The median rating is a perfect 5.0, the mean is 4.60, and 66.1% sit at exactly 5.0. That is positivity bias, not quality: people who bother to rate a small extension are usually people who like it, and plenty of developers nudge their happiest users toward the review form.

Three things follow from that.

1. Getting the first rating is the hard part. Once you have one, you’re out of the silent half of the store.

2. Don’t read much into your star average early on. With two or three ratings, one annoyed user moves your score by a full star. That’s noise.

3. When you do ask for reviews, ask politely and at the right moment. A quiet prompt after someone finishes the task they installed you for works better, and irritates far less, than a popup on first install.

How long growth actually takes

Advice about extension launches is usually written in weeks. The data is written in years.

We grouped every live Chrome listing by how long it has been on the store. The median user count climbs slowly at first and then compounds: 4 users in the first two months, 11 by the end of the first year, 105 for listings still up after two years. Ratings follow the same curve in reverse, with the share of listings that have no ratings falling from 74.4% to 34.6% over the same span.

Read that curve with one correction in mind. These are listings that are still on the store today, so the older groups only contain the extensions that survived. Plenty of two-year-old extensions never reached 105 users; they were abandoned or removed and are not in the count. The curve shows what staying power looks like, not what your extension is guaranteed to do.

Even with that caveat pointing in the optimistic direction, the shape is the useful part. Nothing in this data supports the idea of a launch week that decides your fate. Your first two months put you in a group whose median is 4 users. That is the normal starting point, not a verdict.

The Chrome Web Store won’t market your extension for you

New developers often assume the Chrome Web Store works like a mobile app store with built-in traffic. It doesn’t. Discovery is thin, and a new listing starts with essentially no momentum.

Google’s discovery documentation says ranking "is performed by a heuristic that takes into account ratings from users as well as usage statistics, such as the number of downloads vs. uninstalls over time." Read that closely and you’ll notice the circularity: the inputs to visibility are ratings and usage, which are the two things a brand-new extension has none of.

Google offers two badges that carry weight here. The Established Publisher badge showcases developers who have verified their identity and demonstrated compliance with the developer program policies. The Featured badge is awarded by Google, and the documentation notes it is trialing an option that lets developers nominate their own extensions for it through One Stop Support. Google says badge holders "may receive higher rankings in search and filtering," so this is more than a trust ornament.

In our snapshot, 11.0% of live Chrome listings carry a featured marker, and their median user count is 520 against 11 for everything else. Resist the obvious conclusion. Extensions get featured partly for already being polished and used, so that gap describes what the top of the distribution looks like rather than a lever you can pull in week one. It is a target, not a tactic.

The practical point: you are your own marketing department early on. The store is a distribution endpoint, not a demand engine. Your listing still matters enormously, because it decides how well the traffic you bring converts.

What actually moves the needle after launch

Knowing that the store won’t hand you users, here’s where to spend your energy.

Optimize your store listing

Your listing is your landing page. Treat it like one, because most of the catalog doesn’t.

The median live Chrome listing carries just 2 media assets, and only 28.2% use four or more. Screenshots are free and most of your competitors have skipped them. Use every slot and show the extension doing its job, not an icon parked on a toolbar.

Write a benefit-driven description. Lead with what the extension does for the reader, not how it works inside. Pick the most specific category that genuinely fits.

On privacy: 33.7% of live Chrome listings have no privacy policy URL at all. If yours handles user data, that field is not optional (see the FAQ below). If it handles nothing, a two-paragraph page saying so still removes a reason for someone to close the tab.

Share it where your users already are

Reddit communities like r/chrome_extensions, niche subreddits for your use case, Hacker News, Product Hunt, Dev.to, relevant Discord servers and Slack groups: that’s where early adopters are. Write a genuine post about what you built and why. Developers especially appreciate a good "I built this" story. Be honest about what’s rough. People respect that more than polished marketing copy.

Iterate based on real feedback

Your first version isn’t your best version. Pay attention to the few users you do get. If someone emails you a bug report, that’s gold, and probably worth more than a five-star rating. Fix it fast, ship the update, and tell them. Those early users become your advocates.

Track your metrics

You can’t improve what you don’t measure. The developer dashboard gives you basic stats for your own extension and nothing about anyone else’s. Benchmarking against your category is where the useful signal lives: whether your growth is slow in absolute terms or slow relative to comparable extensions is a completely different diagnosis. We mapped which categories still have room in our category opportunity map.

The long game beats the launch day

The most important thing to internalize: extension growth is a slow burn, not a rocket launch. The cohort curve above is the whole argument. Nothing about a first-week user count predicts where a listing sits after two years.

Almost every successful extension you can name went through the same silent early period. The ones that made it kept shipping: bug fixes, requested features, updates, showing up in communities. The ones that didn’t published once and moved on.

Two pieces of context worth having. The store you’re entering is much larger than it was a year ago, and that growth is concentrated in productivity and AI tooling, which we broke down in the Q2 2026 cross-store report. And a bigger catalog has not meant a bigger audience: the store’s aggregate user count has not moved with its listing count, so competition for attention is genuinely tighter than it was.

These benchmarks describe the store, not your extension. Your niche, your product quality, and how much effort you put into promotion will move you off the median in either direction.

The developers who succeed treat their first extension as a learning exercise rather than a product launch. Build something you’d use yourself, listen to the handful of people who show up, and keep improving. The numbers follow later than you want them to.

Methodology

Every store-wide figure in this article comes from our own daily crawl of the Chrome Web Store via exstats.com. The snapshot is September 5, 2026, covering 254,621 Chrome listings that were publicly listed on that date; store-deleted listings are excluded throughout. Chrome publishes user counts in rounded buckets, so we report medians and percentile splits rather than sums or averages of user counts. Rating averages are calculated only over the 116,808 listings with at least one rating. The listing-age cohorts are built from each listing’s store creation date and partition the live set exactly, with no listing missing a date. Because the cohorts contain only listings that are live today, older cohorts exclude extensions that were removed, which biases their medians upward. All Chrome Web Store policy and process facts are sourced inline to Google’s developer documentation.

Correction, September 5, 2026. This article originally reported store-wide figures from an April 2026 snapshot of 185,459 listings, written in the present tense with no snapshot date. Those numbers have moved: the median user count was reported as 18 and is now 14, the share of extensions with no ratings was 50.5% and is now 54.1%, and the percentile table has been recalculated. The article also stated that developer accounts have a default limit of 20 published extensions. That was wrong. Google’s documentation says a new publisher is limited to a maximum of two published extensions, with an option to request an increase. The FAQ has been corrected.