53 Million Installs Without a Future: Who Will Capture Users of Disappearing MV2 Extensions?
On August 31, 2026, Chrome Web Store will remove every remaining Manifest V2 extension. For developers maintaining older products, this is a migration deadline. For everyone else, it is a rare window: users of thousands of extensions are starting to look for replacements for tools they used to rely on. Chrome’s official timeline
My name is Anjey. I have been building browser extensions for more than ten years. Today, I am working on a service that helps extension creators monetize their products through subscriptions and better understand their audiences through analytics.
I looked at the remaining MV2 extensions in Chrome Web Store not as technical legacy, but as a map of demand: which jobs people already solve in the browser, which products are losing support, and where an independent alternative can be prepared in advance.
MV2 Is Not Going Away Someday — Demand for Replacements Already Exists
August 31 is when the remaining MV2 listings disappear from Chrome Web Store. But it is not the first day of the problem.
Chrome has already disabled Manifest V2 for users, and MV2 extensions stop working on Chrome 139 and later. Once a listing is removed from the Store, its old version can no longer be properly found, reinstalled, or updated. Chrome explains the transition in its official timeline
That means demand for alternatives does not start after August 31. It already appears when:
- an extension stops working after a Chrome update;
- a user changes computers or browser profiles;
- an extension cannot be installed again;
- its developer does not release an MV3 version;
- a familiar product is still known, but no longer has a future.
This is not about building a clone overnight. It is about preparing for the moment when a user searches for an old tool’s name and adds one word: alternative, replacement, not working, or Manifest V3.
This Is Not a Small Market: 13,000 Products and 53.8 Million Installs
In my local Chrome Web Store dataset, collected on August 7, 2026, 13,005 MV2 listings remained after excluding themes. Chrome Web Store displayed an install count for 9,867 of them.
| Metric | Value |
|---|---|
| MV2 listings in the dataset | 13,005 |
| Listings with an available install count | 9,867 |
| Total known installs | 53.8M |
| Installs held by the top 1,000 MV2 products | 50.5M |
| Top 1,000 share of all known installs | 94.0% |
These figures do not mean that 53 million users will suddenly lose their extensions at once. Store-reported installs are rounded counts, not active users, revenue, or retention.
But they show something else: demand has already been proven. People installed these products, used them, and left reviews. And nearly all meaningful demand is concentrated not in thousands of small listings, but in the first thousand.
That is where it makes sense to look for opportunities.
Not Every Disappearing Extension Is an Attractive Target
The largest install count is not automatically a ready-made business idea.
A large extension may belong to Google, Microsoft, Adobe, or another established company. It may have a brand, distribution, enterprise customers, and an ecosystem around it. Such a product is a poor candidate for direct imitation.
But it can still reveal something valuable: the job users have become accustomed to doing in the browser.
For the top 1,000 MV2 extensions, I also looked at ratings and reviews.
| Signal | Number | What to do with it |
|---|---|---|
| Products with 100+ reviews | 656 | Read reviews and look for repeated requests |
| Rating of 3.5 or lower with 100+ reviews | 191 | Check what specifically frustrates users |
| Installs held by that low-rated group | 6.44M | This is meaningful demand, not isolated experiments |
| High-priority products for manual research | 32 | Start here: demand, reviews, and signs of a problem |
| Products worth monitoring | 223 | Watch for a working MV3 successor |
The most useful signal is not popularity alone. It is the combination of three factors:
- The extension has meaningful installs.
- It has enough reviews to reveal the real user pain.
- Its developer does not have a strong, clear, working MV3 successor.
When all three conditions are present, this is no longer an abstract niche. It is a specific user workflow with proven demand and a possible gap in the market.
How to Use an Old Extension’s Name Correctly
The name of a disappearing product is not just a brand. It is a search query with very clear intent.
A person searching for a familiar extension already understands the problem, knows the outcome they want, and is often ready to install an alternative immediately. That is much stronger than cold traffic from a broad query such as “productivity extension.”
Using those keywords is therefore logical. But it is important not to create the impression that you are the original developer.
A workable approach looks like this:
- build an independent product with its own name and clear value;
- use the former product’s name in comparison materials, documentation, articles, and migration pages when the comparison is honest;
- explain which specific job your product solves and how it differs;
- use keywords only where they are genuinely relevant to the product’s functionality.
Do not copy an icon, pretend to be an official product, use phrases such as “the new official version,” or turn the description into a list of other brands. Chrome Web Store prohibits misleading metadata, impersonation of another developer, and irrelevant keyword spam. Chrome Web Store policies
But “users search for this product because it solved a specific task” is a completely legitimate foundation for positioning.
What to Build Instead of the Disappearing Product
A weak idea is to see a popular extension and reproduce its entire menu, interface, and twenty-feature list.
A strong idea is to find the one job people installed it for and do that job better.
For example, a user may be searching for an old extension not because the brand matters, but because they need to:
- move data from a page into a CRM;
- download or convert a file;
- fill in a form from page data;
- save a conversation or webpage in a structured format;
- process PDFs;
- automate a repetitive browser action;
- work with media, tabs, links, or web data;
- connect two work tools without manual copying.
The winner is not the person who reproduces the old extension in full. The winner is the person who makes the core workflow faster, simpler, and more reliable.
A disappearing MV2 product gives you an advantage: you do not have to guess whether the problem exists. You need to understand which part of the solution users valued and which part they disliked.
A Simple Model for Choosing Candidates
I would not start with “the top 1,000 extensions.” I would start with a short list and inspect every product manually.
| Question | Why it matters |
|---|---|
| Does it have at least 10k installs? | This is a minimum signal of meaningful demand |
| Does it have 100+ reviews? | You can investigate real complaints and expectations |
| Is there a working MV3 version? | If there is, the replacement window may already be closed |
| What job sits behind the product? | Build for the job, not a copy of the interface |
| Can the value be explained in one sentence? | If not, the product is still too broad |
| Is there a path to paid features? | Automation, history, volume, integrations, teams, or limits |
For example, not: “a new alternative to a well-known extension.” Instead: “An extension that saves a LinkedIn lead to your CRM with a note and tags in one click.”
Not: “a universal PDF tool.” Instead: “An extension that extracts specific fields from incoming PDFs and sends them to a spreadsheet.”
The first description tries to capture branded demand. The second explains what a user may be willing to pay for.
The strongest version combines both approaches: you understand which old product the user is searching for, but you sell them a better outcome — not someone else’s name.
How to Make Money During the Transition
This market has three clear models.
First: an independent alternative. Take one job from a disappearing product, improve it, and release an MV3 solution.
Second: a paid version of a familiar workflow. Give the user the core result for free. Charge when scale begins: batch processing, history, sync, automation, integrations, and team collaboration.
Third: services for owners of older extensions. Not every developer will be able to migrate well or in time. They may need an audit, development help, testing, subscription migration, or a safe MV3 release.
For an independent developer, the first model is usually the most interesting: enter a niche where users already understand the problem and are actively looking for a new tool.
The Main Point
Manifest V2 is not only a technical sunset for an old platform.
It is a moment when part of existing demand loses its familiar products. In my dataset, that means 13,000 MV2 listings and 53.8 million known installs, with almost all of that demand concentrated in the top 1,000 products.
You do not need to replace everything at once. Find one product with a real audience, understand its core workflow, study its reviews, and build an independent MV3 alternative that solves the job better.
August 31 will not create a market from zero. It will simply make an existing problem more visible.
Which categories of disappearing MV2 extensions would you like to explore next: PDFs, CRM, automation, files, media, development tools, education, or data workflows? Leave a comment — I can break down a specific niche from the top 1,000 list and show where demand, complaints, and room for a new product actually exist.
Extension data is based on a local Chrome Web Store dataset collected on August 7, 2026. Store-reported install counts are not active users, revenue, growth, or retention. The list is intended for demand research, not as a prediction of which extensions will be removed or successfully replaced.