Chrome extension ideas: how to find and validate one with Chrome Web Store data

Good Chrome extension ideas rarely come from a list of "50 extension ideas". They come from evidence: a workflow people repeat every day, a popular extension its users are unhappy with, or a category that lost its tools when the platform changed. The Chrome Web Store shows most of that evidence in public, on every listing: how many people use an extension, how they rate it, how often it ships, and what its unhappiest users say.

This guide shows how to turn those public numbers into a shortlist of Chrome extension ideas, how to read them without fooling yourself, and how to validate an idea in a couple of weeks before you write the first line of code. It includes real listing data we collected on October 12, 2026, a scoring sheet, and the store policies that rule some ideas out from the start.

Key takeaways

• The best Chrome extension ideas sit where demand is proven and satisfaction is not: many users, a mediocre rating, slow updates, or the same complaint repeated in reviews.
• Every listing shows five signals: users, average rating, rating count, version and last update date. User counts are weekly users and are rounded for large extensions, so use them for orders of magnitude, not precise growth.
• 1- and 2-star reviews are your free research report. Read them in the browser; the store's robots.txt disallows crawling review pages.
• Manifest V2 extensions were removed from the Chrome Web Store by August 31, 2026, according to Google's timeline. Tools that never migrated left real gaps.
• Policies narrow the field: an extension must have "a single purpose that is narrow and easy to understand," and one developer may not publish several extensions with duplicate functionality.

Where good Chrome extension ideas come from#

Most extensions that keep their users start from one of four places:

1. A repeated workflow. Something you or your team do many times a day inside the browser: copying data between two web apps, cleaning up a page before printing, checking the same dashboard. If it annoys you daily, it annoys others.
2. A popular extension with unhappy users. A category leader with millions of users and a stream of complaints about one missing feature, a pricing change or a permission it should not need.
3. An abandoned tool. An extension that people still use but that has not shipped an update in years. Its users are waiting for an alternative, and its reviews tell you what they want.
4. A platform change. When Chrome removes an API or adds a new one, whole categories reset. The end of Manifest V2 is the clearest recent example.

The first source needs only your own experience. The other three need data, and that is where the store listing helps.

The five signals on every Chrome Web Store listing#

Every public listing at chromewebstore.google.com/detail/<id> shows the same small set of numbers. Each answers a different question about a niche:

Two caveats matter before you compare anything. The user count is weekly users, not installs, and it moves in large steps once an extension is big. Our guide to the Chrome Web Store stats API explains how precise each public number is, and the post on why Chrome extension weekly users drop covers what moves the user count. Neither caveat stops you from comparing extensions in a niche, because the questions here are about orders of magnitude.

A worked example: screenshot and tab manager extensions#

Here is what the public listings of seven well-known extensions in two crowded categories showed on October 12, 2026:

What a builder can read from this, without any private data:

• Both categories have proven demand. Several products have a million users or more. Nobody needs to be convinced that full-page screenshots or saving tabs is useful.
• The screenshot leader is very strong. A 4.9 average over 84.4K ratings with a release two weeks earlier leaves little room for "the same thing, but better". A new screenshot tool needs a sharply different angle, not a clone.
• One large listing has not shipped since July 2024. Two million users and a 4.4 rating on a listing with no update in more than two years is worth a closer look. Read its recent reviews before drawing conclusions: a simple extension may simply not need updates, and the reviews tell you whether users feel left behind.
• Tab managers are crowded but split. Ratings from 4.2 to 4.7 and very different sizes suggest users have not settled on one winner. Reviews in this category will tell you which job each one fails at, such as sync, search or large numbers of tabs.

Rating counts relative to users also hint at how engaged a user base is. Session Buddy has about 25 ratings per thousand users, GoFullPage about 8 and Lightshot about 3.5. Treat this as a hint only, since both numbers are rounded and older extensions collect ratings for longer.

Mine 1- and 2-star reviews for real problems#

Numbers tell you where to look. Reviews tell you what to build. Patrick Bushe puts it well in his Chrome extension playbook: "Read the 1- and 2-star reviews on the top competitors." His reason: "Negative reviews tell you exactly which features are missing, which permissions users hate, and which workflows break."

Read them yourself, in the browser. The Chrome Web Store's robots.txt disallows automated access to review pages, so a crawler is the wrong tool here. Twenty minutes per competitor is enough. Sort each complaint into a theme and count it:

Also note the dates. A complaint repeated across two years is a durable gap. A burst of complaints in one week is usually a bad release that the developer will fix. Our guide to reading review and rating trends covers how to tell the two apart.

Bushe adds a warning that matters for idea selection: "Chrome users don't switch extensions for UX, they switch for missing features or trust." A prettier version of an existing tool is a weak idea. A version that does the one thing users keep asking for, with fewer permissions, is a strong one.

Gaps left by the end of Manifest V2#

Platform changes create the most obvious openings. Google's Manifest V2 deprecation timeline shows the end of a long transition: Manifest V2 extensions were disabled for all users with Chrome 138, stopped working entirely from Chrome 139, and by August 31, 2026, "all remaining Manifest V2 extensions have been removed from the Chrome Web Store."

Some of those extensions were abandoned rather than migrated. Their users either found replacements or are still looking. To find these gaps:

• Check the tools you and your colleagues used to rely on. If a listing now returns the generic store page instead of the extension, it is gone. A removed listing answers with a normal page, not a 404, as our post on what happens when an extension is removed from the Chrome Web Store explains.
• Search forums and issue trackers for "alternative to" plus the old name. Users of a dead extension ask for replacements in public.
• Look at what still works in Firefox. Some Manifest V2 add-ons remain on addons.mozilla.org. Their user counts, which the AMO API exposes publicly as our guide to Firefox add-on stats shows, tell you how much demand the Chrome version left behind.

Validate Chrome extension ideas before you build#

An idea that passes the data check still needs validation. This checklist takes a week or two and costs almost nothing:

1. Write the single purpose in one sentence. The Chrome Web Store quality guidelines say "an extension must have a single purpose that is narrow and easy to understand." If your sentence needs "and", you may have two extensions.
2. Name the incumbents and your difference. List the top three to five extensions for the job with their numbers from the table above. Write down the one thing yours does that they do not, ideally a theme from their reviews.
3. Check the policies that could block you. Beyond single purpose, the spam and abuse policy does not allow a developer or related accounts "to submit multiple extensions that provide duplicate experiences or functionality". Plan one strong extension, not a family of near-copies.
4. List the permissions you will need. Broad host access triggers strong install warnings and is a common reason for complaints. If your idea only works with access to every site, make sure the value justifies it.
5. Test demand with words before code. Describe the extension on a simple page, share it where the users from those reviews spend time, and count sign-ups for early access. Reply to public "alternative to" threads only where it is genuinely helpful.
6. Decide how it will make money, or why it does not need to. A paid extension in a category full of free 4.7-rated tools needs a strong reason.

Score your shortlist#

When you have three to five candidates, score each from 1 to 5 on the same criteria and compare totals:

The scores are not science. They force you to write down why you believe an idea is good, which makes it easier to drop a weak one early.

Watch the niche for two weeks before you commit#

A single snapshot can mislead you. A leader you think is abandoned may ship tomorrow, and a rating can move after one bad release. Before you commit months of work, record the niche daily for a couple of weeks: users, rating, rating count and version for each competitor. If you want to collect this yourself, the Chrome Web Store stats API guide shows a respectful daily collector, and you can pipe its changes into a chat with Telegram bot notifications.

If you would rather not run a scraper, Extenify does this as a competitor extension monitoring dashboard. Add the extensions in your niche from the Chrome Web Store, Edge Add-ons and Firefox Add-ons, and it records users, ratings, reviews and versions every day and alerts you when a competitor ships, slips or disappears. Every account starts with a 7-day free trial with no card required, and the pricing page lists the plans. Once you launch, the same dashboard tracks your own extension next to them, as our guide to tracking one extension across Chrome, Edge and Firefox describes.

Frequently asked questions#

How do I find good ideas for a Chrome extension?#

Start from a repeated task in your own browser, then check the store for existing extensions that do it. Look for categories with many users and mediocre ratings, extensions that have not been updated in a long time, and complaints that repeat in 1- and 2-star reviews. Platform changes, such as the removal of Manifest V2 extensions in 2026, also leave gaps.

How many users should a niche have before I build an extension for it?#

There is no official threshold. As a rule of thumb, if the leading extensions in a category together have tens of thousands of weekly users or more, demand is proven. Smaller niches can still work for a paid tool with a clear business audience, but you will need to validate willingness to pay directly.

Can I see how many users a Chrome extension has?#

Yes. Each listing shows its weekly users. Small extensions show an exact number, while large ones show a rounded figure, so the public count is good for comparing extensions but not for measuring small changes in a big one.

How can I tell if a Chrome extension is abandoned?#

Check the "Updated" date on the listing, then read the most recent reviews. An old date combined with recent complaints about broken features is a strong sign. An old date with recent positive reviews usually means the extension simply works and does not need updates.

Is it allowed to build an extension similar to an existing one?#

Building a competing extension is normal, but copying another developer's code, name or branding is not, and the original developer can report a copycat listing. The store's spam policy also prevents one developer from publishing several extensions with duplicate functionality, so focus on one extension with a clear difference.

Summary#

The Chrome Web Store already tells you most of what you need to choose an extension idea. Use users to confirm demand, ratings and 1- and 2-star reviews to find dissatisfaction, update dates to spot neglect, and platform changes like the end of Manifest V2 to find gaps. Check every idea against the single purpose and duplicate functionality policies, score your shortlist honestly, test demand with a simple page, and watch the niche daily for a couple of weeks before you commit to building.

Image credits#

• Cover photo: Sticky notes and pen on a laptop keyboard by Rashed Hossain on the WordPress Photo Directory, CC0.