Dev.to WebDev 🛠 Dev 👁 0 📖 4 min read

What Percentage of Users Leave a Review? Under 1 in 200

Originally published on ExtensionBooster. What percentage of users leave a review on a Chrome extension? Across 678 Chrome Web Store listings, the median was 0.46 ratings per 100 users, so fewer than 1 user in 200 ever

Originally published on ExtensionBooster.

What percentage of users leave a review on a Chrome extension? Across 678 Chrome Web Store listings, the median was 0.46 ratings per 100 users, so fewer than 1 user in 200 ever rates. Here is how that number shifts with size, a small script to benchmark your own listing, and what the top quarter does differently.

The numbers by user count

The data was collected on October 14, 2026, from each listing's public user count and rating count. The middle half of all listings sat between 0.14% and 1.29%.

The bigger the extension, the lower the rate:

Users Listings Median rate Top quarter starts at Median ratings
Under 1,000 157 0.79% 3.08% 2
1,000 to 9,999 146 0.69% 1.27% 20
10,000 to 99,999 191 0.37% 1.13% 113
100,000 to 999,999 120 0.32% 0.77% 646
1,000,000+ 64 0.22% 0.63% 6,221

A few more data points worth knowing:

  • For the 521 listings with 1,000+ users, the median was 0.43%. The top quarter started at 1.10% and the top tenth at 2.54%.
  • Very small listings often have nothing: 48 of the 87 listings under 100 users had zero ratings.
  • Well-known extensions vary wildly. Todoist for Chrome sat around 10.29%, Grammarly around 0.11%, and React Developer Tools around 0.03%.

So if you hit 1% with over 1,000 users, you are already in the top quarter.

Why the rate falls as you grow

None of these are bugs in your extension. They are structural:

  1. Installs are not active users. The user count includes people who installed months ago and never open the extension. They will not rate it.
  2. Many big installs are hand-me-downs. An employer, a course or a friend told them to install it, so they never browse the listing.
  3. Chrome has no default rating button. Rating means finding the listing, signing in and clicking through. Each step loses people.
  4. Unhappy users have a reason to write. Happy ones rarely bother unless asked.

Benchmark your own listing

This snippet compares your rate with the median and top quarter for your tier, and tells you how many ratings you need to reach the top quarter:

const TIERS = [
  { max: 1_000, median: 0.79, topQuarter: 3.08 },
  { max: 10_000, median: 0.69, topQuarter: 1.27 },
  { max: 100_000, median: 0.37, topQuarter: 1.13 },
  { max: 1_000_000, median: 0.32, topQuarter: 0.77 },
  { max: Infinity, median: 0.22, topQuarter: 0.63 },
];

function reviewRate(users, ratings) {
  const tier = TIERS.find((t) => users < t.max);
  const rate = (ratings / users) * 100;
  return {
    rate: `${rate.toFixed(2)}%`,
    vsMedian: rate >= tier.median ? "above median" : "below median",
    ratingsForTopQuarter: Math.ceil((users * tier.topQuarter) / 100),
  };
}

console.log(reviewRate(4200, 18));
// { rate: '0.43%', vsMedian: 'below median', ratingsForTopQuarter: 54 }

An extension with 4,200 users and 18 ratings is below the 0.69% median for its tier and needs 54 ratings to join the top quarter.

How the top quarter gets there

  • Ask after a win, not on install. Trigger the prompt after a moment that proves value, such as a 10th saved item or a first finished export. Web Highlights asked after a user's 12th highlighted site and reported that about 3.7% of its users left a review.
  • Link straight to the reviews page. Every extra click costs raters.
  • Ask everyone the same way. Showing the review prompt only to happy users and sending unhappy ones elsewhere is review gating. It can backfire and can break store policy. Offer a feedback link for problems and the same review request to everyone after a real win.
  • Reply, then follow up after fixes. Replies show the listing is maintained, and some users raise their rating once the bug is gone. Update your reply when the fix ships.
  • Guard against bad releases. A broken update can bring a burst of one-star reviews, so keep a rollback ready and a written incident plan.

One caution when reading your own number: a high rate is not always good news. A wave of complaints also raises it, so watch the star average next to it.

What the data can't tell you

  • The sample is not random. It came from 60 store searches plus listings linked from well-known extensions, so small, low-traction extensions are under-represented and the true store-wide rate is probably lower.
  • Large listings show rounded user counts, so their ratios are approximate.
  • Ratings are a count, not written reviews.
  • Categories differ: developer tools and ad blockers tend to have lower rates.
  • Listings rated 4.5+ stars had a median of 0.68 ratings per 100 users versus 0.33 under 4.0 stars. That is a correlation, not proof that more ratings cause higher stars.

Key takeaways

  • Median review rate: 0.46 ratings per 100 users, fewer than 1 in 200.
  • The rate drops with size, from 0.79% under 1,000 users to 0.22% above a million.
  • Above 1,000 users, 1.10% puts you in the top quarter.
  • Ask once, after a clear win, with a direct link, and ask everyone the same way.
  • Track the star average alongside the rate so complaint bursts don't look like success.

The full write-up, with methodology and the FAQ, is in the Chrome extension review rate benchmarks from 678 listings. For more data-backed guides on ratings and reviews, see ExtensionBooster's resources for extension and app developers.

What is your extension's ratings-per-100-users right now, and which prompt timing moved it the most for you?

📰 Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.