Why Are Expired Chrome Extensions Considered Proven Demand?

An expired Chrome extension counts as "proven demand" because it already had real users who installed it — the market validated the idea before the extension died. Chrome Goldmine's database of 9,656 expired extensions leans on exactly this logic: each listing shows historical user counts, the category, why it died, rebuild difficulty, current competitors, and an estimated monthly revenue range. So instead of guessing whether anyone wants a tab manager or a coupon clipper, you start from a number that says people already did.

The core idea: installs are evidence

A brand-new extension idea is a hypothesis. An expired extension with 48,200 historical users is closer to a tested result. Those users chose to install it, which means the underlying job-to-be-done was real. The extension dying doesn't erase that demand — it just removes the supply.

That gap between "people wanted this" and "nobody is serving them now" is the opportunity the site is built around.

What each listing tells you

Chrome Goldmine structures every entry so you can judge feasibility without doing the market research yourself. From the sample rows, the fields are:

The "died because" field matters most. It separates two very different situations:

• MV3 — the extension broke when Chrome moved to Manifest V3. The demand is intact; the code just needs updating.
• Abandoned — the developer walked away. The demand is intact; the product just needs someone to maintain it.

Both are supply problems, not demand problems.

Why the death reason changes the play

If an extension died from an MV3 migration, the rebuild is largely technical: port the code, restore functionality, and you're competing against a known baseline. If it was abandoned, the work is more about re-engaging users and keeping the thing alive.

The sample shows both patterns across categories — MV3 deaths in Productivity, Shopping, and Writing, and abandoned ones in Accessibility, Customization, and New Tab. Difficulty ranges from Low (Dark Sites, Reading Mode) to High (Grammar Lite), which maps roughly to how much engineering the rebuild needs.

How to read the revenue estimates

The estimated monthly figures ($300–$900 at the low end, up to $1,000–$3,000 for Grammar Lite) are ranges, not guarantees. They're useful as a relative signal: a High-difficulty extension with a wide range is a bigger bet than a Low-difficulty one with a narrow range.

Use them to compare opportunities against each other, not as a forecast you can bank on.

What you actually get and what it costs

The full database is 9,656 extensions. Twenty rows are visible as a free sample without signup; the remaining 9,636 unlock at checkout. The listing price is $29, discounted to $23.20 for the first 100 buyers, with a 30-day money-back guarantee and lifetime quarterly updates. Delivery is an instant Notion workspace plus CSV. The site states there's no subscription.

Where this approach fits — and where it doesn't

This model works best if you can ship a Chrome extension and want a starting point with evidence behind it. It's less useful if you'd rather build something original, or if you can't act on a technical rebuild.

The honest caveat: historical users are a signal, not a promise. An extension that once had 91,400 users may have lost them for reasons beyond MV3 — a better competitor, a changed market, or a feature that no longer matters. The listing gives you the competitor picture and the death reason so you can check that before committing. Treat the user count as the start of your diligence, not the end of it.