I Just Published My First Chrome Extension. Now What?
We analyzed 185,000+ Chrome extensions to show what happens after launch: review timing, realistic install benchmarks, ratings, and early growth tactics.
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 analyzed 185,000+ public Chrome Web Store extensions to give you a realistic picture of what to expect and what to do about it.
The median Chrome extension has just 18 users. If you break 100, you've already outperformed 70% of the store.
Half of all extensions currently have zero ratings. Your first review is harder to earn than you think.
The Chrome Web Store won't market your extension for you. Organic discovery tends to favor listings with stronger engagement and quality signals, so you need to bring your own audience early on.
The review process won’t kill you (but it might test your patience)
After you hit publish, your extension enters Google’s review queue. According to Google’s official documentation, review times vary. Google notes that in early 2021 most submissions completed review in under 24 hours, and over 90% completed within three days.
That said, certain things can slow you down. Google explicitly calls out signals like new developers, new extensions, dangerous permission requests, and significant code changes as factors that trigger closer review. Requesting broad permissions like `<all_urls>`, including hard-to-review code, or shipping something that touches sensitive browsing contexts can all extend review times.
Common reasons for rejection include requesting permissions your extension doesn’t actually need, missing or weak store listing metadata like descriptions and screenshots, broken functionality, and privacy-policy issues when handling user data. Most of these are avoidable if you read the Chrome Web Store Program Policies before submitting.
Here’s the good news: rejection isn’t the end of the world. You’ll usually get an email explaining what went wrong, and you can fix and resubmit. Think of the first submission as a trial run. If it sails through on the first try, great. If not, you’re in excellent company.
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. And one of them is you.
Don’t panic. We looked at user counts across 185,000+ active extensions in the Chrome Web Store, and here’s the reality.
The median Chrome extension has 18 users. Not 18,000. Eighteen. Reaching 100 users puts you ahead of 70.3% of every extension in the store.
| Percentile | Users |
|---|---|
| 25th | 4 |
| 50th (median) | 18 |
| 75th | 164 |
87.9% of extensions currently have fewer than 1,000 users. So if your first month looks quiet, that’s not failure. It’s the default state of the Chrome Web Store. The distribution is brutally skewed: a tiny number of blockbuster extensions (ad blockers, password managers, big dev tools, language translators) account for a huge share of total installs.
The takeaway? Getting to 100 users is a genuinely meaningful milestone. Treat it as your first real target, not as a disappointment.
Don’t expect ratings (most extensions have zero)
If slow user growth is the first gut punch, the silence in your reviews tab is the second. You might go weeks or months without a single rating.
That’s because 50.5% of all active Chrome extensions currently have zero ratings, based on our analysis of 185,459 public extensions. The median number of ratings across the store in our dataset is exactly zero.
Among extensions that do have at least one rating, the picture is surprisingly rosy: the median rating is a perfect 5.0 stars, and the average is 4.56. This reflects a strong positivity bias. Users who bother to rate tend to rate highly, and many developers actively nudge their happiest users toward leaving reviews.
Okay so what does this mean for you?
1. Getting your first rating is the hard part. Once you have one, you’re already ahead of a huge share of the store.
2. Don’t obsess over your star count early on either. With very few ratings, a single disgruntled review can tank your average. That’s noise, not signal.
3. And when it comes time to ask for reviews, do it politely, at the right moment. A subtle prompt after a user finishes a task they came to your extension for works far better and annoys far less than a popup on first install.
The Chrome Web Store won’t market your extension for you
One of the biggest misconceptions new developers have is that publishing to the Chrome Web Store is like listing on an app store with built-in traffic. It isn’t. Discovery on the Chrome Web Store is limited, and new extensions start with very little built-in momentum.
Google’s official discovery documentation explains that store ranking uses a heuristic that considers user ratings and usage statistics, including downloads relative to uninstalls over time. It also considers qualitative factors like design, clarity of purpose, onboarding, and ease of use. Traction helps, but so does a polished product and a strong listing.
A few discovery channels exist, including search, category browsing, the homepage, featured collections, and Editors’ Picks. But for a new extension with zero users and zero ratings, visibility is usually limited until you start generating real usage signals.
Google also offers two badges that can boost credibility. The Featured Badge is manually assigned by the Chrome team to extensions that meet high UX and technical standards. Google also allows developers to nominate eligible public extensions for consideration through One Stop Support. The Established Publisher Badge is automatically granted to verified publishers with a positive compliance track record. Google says badge holders may receive higher rankings in search and filtering, so this is more than cosmetic trust signaling.
Here’s the thing: you are your own marketing department in the early days. The store is a distribution endpoint, not a demand engine. But your listing still matters enormously, because when traffic does arrive, your listing determines how well that traffic converts.
What actually moves the needle after launch
Knowing that the Chrome Web 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.
Write a clear, benefit-driven description. Lead with what the extension does for the user, not how it works under the hood.
Use all available screenshot slots and show the extension in action, not just an icon sitting on a toolbar.
Pick the most accurate and specific category that fits your use case. If your extension handles user data, publish a clear privacy policy. Even if it doesn’t, a short privacy page can still reduce confusion and build trust.
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, possibly more valuable than a five-star review. Fix it fast, ship an update, and let them know. Those early users become your advocates.
Track your metrics
You can’t improve what you don’t measure. The Chrome Web Store developer dashboard gives you basic stats, but it’s limited. Tools that track installs, ratings, and trends over time across the extension ecosystem can help you benchmark your progress and spot opportunities in your category.
The long game beats the launch day
The most important thing to internalize: extension growth is a slow burn, not a rocket launch.
Almost every successful extension you can think of today went through the same silent early period. The ones that made it kept shipping. They fixed bugs, added features users asked for, posted updates, and showed up in communities. The ones that didn’t? They published once and moved on.
Here’s a rough, non-guaranteed heuristic for what "normal" can look like for a first extension if you’re actively sharing it and improving it:
| Timeframe | What to expect |
|---|---|
| Week 1 | Review approval in many cases. Single-digit users. Probably no ratings. |
| Month 1 | Low double-digit users if you’ve shared it in a few relevant places. Maybe one rating if you’re lucky. |
| Month 3 | If you’ve kept iterating and promoting, the first 100 users becomes a reasonable milestone to aim for. |
| Month 6+ | Compounding can begin: repeat usage, word of mouth, better conversion, and more organic discovery. |
These aren’t guarantees. They’re directional expectations based on store-wide benchmarks and common launch patterns. Your mileage will vary based on your extension’s niche, quality, and how much effort you put into promotion.
The developers who succeed treat their first extension like a learning experience, not a product launch. Build something you’d use yourself, listen to the handful of people who show up, and keep improving. The numbers will follow.
FAQ
How long does the Chrome Web Store review take?
Google says review times vary. In its official documentation, Google notes that in early 2021 most submissions completed review in under 24 hours, and over 90% completed within three days. New developer accounts, broad permissions, and sensitive functionality can all make review take longer. Plan for some variance on your first submission.
How many users should I expect in my first month?
Realistically, modest numbers unless you actively promote. The median Chrome extension in our dataset has only 18 users total, so even getting into the low double digits early can put you on a reasonable trajectory compared to the broader store.
Do I need a privacy policy for my Chrome extension?
Yes if your extension handles user data. Google’s policy requires an accurate, up-to-date privacy policy for products that handle user data, and that policy must be linked in the designated Chrome Web Store field. Even if your extension collects nothing, a brief privacy page can still help reassure users.
Why was my extension rejected?
The most common reasons are excessive permissions, missing metadata like descriptions and screenshots, broken functionality, and privacy or disclosure issues. Google typically sends a notification explaining the specific issue. Fix it and resubmit. Rejection is usually a revision loop, not a dead end.
Is there a fee to publish a Chrome extension?
Yes. Google charges a one-time registration fee to create a Chrome Web Store developer account. After that, you can publish extensions, with a default limit of 20 published extensions per developer account unless Google approves a limit increase.