Every guide to this topic is published by a company selling you a payment SDK. None of them tell you that 57.1% of tracked extensions earn nothing, that only 6.3% ever clear $1,000 a month, or that the reason is a decision Google made in 2020.
A Chrome extension is the cheapest software product you can ship and the hardest one to charge for. Both halves of that sentence are measurable, and the second half has a specific cause almost nobody writing about extension monetization mentions.
Across 112 revenue-verified browser extensions we track, 57.1% earn nothing at all and only 6.3% clear $1,000 a month. For comparison, 10.3% of all 8,600+ tracked startups clear that same threshold. Chrome is the only major plugin ecosystem we have measured that performs worse than software generally at reaching a first real revenue milestone, and WordPress matched the baseline almost exactly.
Decide how you will charge before you publish, because Google deprecated Chrome Web Store Payments in 2020 and there is no store billing to fall back on. Then pick a problem tied to someone’s work rather than their convenience, keep the extension to one job, put the account in a companion web app, and expect search rather than the Web Store to bring the users. Picking the right problem is the part no SDK solves, which is what BigIdeasDB is for.
Search this topic and the results are almost entirely owned by companies selling a payment SDK or a monetization network. The technical advice is often fine. What none of them publish is a revenue distribution, because the distribution is the argument against the category.
We can publish it, using the same evidence base behind the state of indie SaaS revenue and revenue benchmarks by category.
| Measure | Chrome extensions | All tracked products |
|---|---|---|
| Earning $0 per month | 57.1% | 56.5% |
| Clearing $1,000 per month | 6.3% | 10.3% |
| Average monthly revenue | $295 | — |
| Highest in the set | $9,742 | — |
| Consumer-facing | 56 | — |
| Business-facing | 13 | — |
The zero rate is unremarkable. The $1,000 rate is the finding. Extensions reach that threshold at roughly 60% of the rate of software generally, which means the gap is not founder quality or market size. It is something about the category itself. Our wider work on startup failure statistics and how fast SaaS startups actually grow sets the baseline this is measured against.
Chrome Web Store Payments was a Google service that let extension developers charge through the store for a 5% transaction fee. In September 2020, Google announced it was permanently shutting down the Web Store Payments API, and the Chromium team followed with an urgent deprecation notice telling developers to switch their payment settings to free or third-party. Nothing replaced it.
That single decision explains most of the distribution above. Every extension developer since has had to build checkout, licensing, entitlement and subscription management themselves, before earning a dollar, for a product that often took a weekend to write. The friction lands precisely at the point where a hobby project would have become a business.
Compare that with Shopify, which bills merchants on their existing invoice and takes 0% of a developer’s first million. The platforms made opposite choices and the revenue distributions look accordingly different. The same structural point runs through pricing strategy and how recurring revenue is valued.
We have now run the same analysis on all three major extension ecosystems. The comparison is the most useful thing we can give you if you have not committed yet.
| Measure | Shopify apps | WordPress plugins | Chrome extensions |
|---|---|---|---|
| Platform billing rail | Yes, 0% to $1M | None | Removed in 2020 |
| Median profit multiple | 3.90x | 2.80x | 4.40x |
| Median profit margin | 85.4% | 88.9% | 73.3% |
| Median asking price | $250,000 | $120,000 | $249,000 |
| Share clearing $1,000/mo | — | 10.0% | 6.3% |
| Primary audience | Merchants (B2B) | Agencies (B2B) | Consumers (B2C) |
Read the Chrome column carefully, because it is counterintuitive. Extensions carry the highest median exit multiple of the three and the lowest rate of reaching revenue at all. Both are true because they measure different populations: the nine listings are survivors, and the 112 revenue records include everyone who tried. A profitable example from the middle of the distribution describes itself as “a profitable, bootstrapped micro-SaaS that provides 450+ fully responsive, ready-to-use UI components” — revenue-verified product listing, at roughly $1,560 a month.
The practical reading is that Chrome is a high-variance lottery with a cheap ticket, while Shopify is a lower-variance business with a higher entry cost. See profit multiples by category for how those two shapes are usually priced.
Fifty-six of the extensions in our revenue set are classified consumer-facing against thirteen business-facing. More than four to one.
That inverts the standard advice, which is to sell to businesses because businesses have budgets. It also explains the pricing ceiling: consumers have been trained for fifteen years that browser add-ons are free, and the extension sits alongside a dozen free ones in the same store. That is the same crowding problem mapped in the micro SaaS competition map and oversaturated side hustles. Our analysis of who micro SaaS actually sells to found the same segment penalty at corpus scale.
The most honest picture of this market comes from the celebration posts. Read them in order and the economics become unmistakable.
“I just got my first paying customer. I know it’s ‘just’ $9, but I can’t stop smiling... The money isn’t what made me happy. It’s the fact that someone I don’t know looked at my product and thought, ‘Yeah, this is worth paying for.’” — r/chrome_extensions
“My Chrome extension has hit 20 lifetime license sales!” — r/chrome_extensions
“I know it’s not a big amount but being in India and being able to have someone pay from other side of the world feels surreal.” — r/chrome_extensions
“I started building this extension in April 2024 to solve myself a problem... After 1.8 years, I have finally hit 100+ paying customers.” — r/chrome_extensions
“I started building this extension in 2024. I had a rough time figuring out various monetization plan and finally settled with a subscription plan and a BYOK plan. Recently, our subscription plan has hit $100 MRR.” — r/chrome_extensions
“After 2+ years, my Chrome Extension finally hit 10,000+ users!” — r/chrome_extensions
“Launched my chrome extension 4 months ago, reached ~1500$ in total revenue.” — r/chrome_extensions
And the one that shows the gap between users and revenue most starkly: “After 5 months of developing this project and over a hundred continuous improvements, [my extension] has reached 1,000 users.” — r/chrome_extensions
These are the successful posts, the ones the community upvoted into the hundreds. A market where $100 in monthly recurring revenue after two years is a celebrated milestone is a market you should enter with accurate expectations. Compare against getting to the first $1K MRR and solo developer revenue examples.
The other side of the variance. Extension-related acquisition listings carry a 4.40x median profit multiple, a 73.3% median margin, $104,000 median trailing revenue and a $249,000 median asking price.
Individual listings show the range. An AI prompting extension with “over 200k users to maximize LLM outputs without technical expertise” — acquire.com listing, reports $104,000 revenue against $100,000 profit at 5.0x. A “WhatsApp Marketing Automation Chrome Extension — $132K ARR, 54% Growth” — acquire.com listing, sits at 1.9x. Same ecosystem, wildly different pricing, driven by how replaceable the buyer judges each one.
Nine listings is a small sample and we are not going to pretend otherwise. Treat 4.40x as evidence that a successful extension is a real asset, not as a category benchmark. See SaaS valuation multiples.
The top of our revenue-verified set clusters into four groups: social account management, AI writing and rewriting, marketplace seller automation, and academic assistance. The single highest earner describes itself as “established Chrome extensions for Facebook friend and group management” — revenue-verified product listing.
One reseller tool describes itself as helping “Depop sellers grow faster by automating tasks like bumping listings, relisting” — revenue-verified product listing, and another helps “Vinted sellers generate descriptive titles and descriptions for their listings” — revenue-verified product listing.
The pattern worth extracting is that the earners attach to something the user is already doing for money or for a grade. A Depop seller automating relisting, a Vinted seller generating descriptions, a freelancer scraping job feeds: each has a reason to pay that a general convenience tool does not. A privacy extension in the same set states its job in one line: “helps hide sensitive information while screen sharing” — revenue-verified product listing. Our guides to finding a profitable niche and single-feature micro SaaS ideas follow the same logic.
A meaningful share of the highest-earning extensions in our revenue-verified set are academic dishonesty or detection-evasion tools: exam assistance, quiz answering, and AI-detector bypass products. Several sit in the top ten by revenue.
We report this because it changes how you should read the revenue data, not as a recommendation. If a visible portion of the top of the market is built on products that a platform could remove overnight and that no acquirer wants on their books, then the legitimate market is smaller than the raw distribution suggests, and the survivor multiple is measuring a narrower population than it appears to. Build in a category you would be happy to put your name on at exit. See what counts as a moat in the AI era.
This is the single highest-leverage decision in the whole article, and it is irreversible in practice. A free extension with ten thousand installs cannot easily be converted to a paid one, because those users installed it on the understanding that it was free and will leave one-star reviews explaining that.
The developer who reached $100 MRR described exactly this cost: “I had a rough time figuring out various monetization plan and finally settled with a subscription plan and a BYOK plan.” — r/chrome_extensions. That figuring-out happened after launch, which is why it took two years.
The right model if you intend to sell the business, because recurring revenue is what buyers pay a multiple on. It is also the hardest sell to a consumer audience that resents subscriptions on principle, which is why the developers who run one usually pair it with something else. See SaaS pricing strategies.
Lifetime converts against consumer resistance in a way subscriptions do not, and the public milestone posts show it accumulating faster. One developer’s framing of what they built explains why people bought: “a distraction-free alternative to Grammarly. To improve your articulation, vocabulary, and tone wherever you write.” — r/chrome_extensions. Clear substitution for a known product, one clear job. The same developer posted “My Chrome extension has hit 30 lifetime license sales!” — r/chrome_extensions while the subscription line was still around $100 a month.
The trade is the one we documented in the WordPress plugin market: lifetime revenue is a flow that stops while the support obligation accumulates. Use it to fund the early months, not to build the business on.
The model AI extensions should default to. The user supplies their own provider API key and you charge for the interface. Your variable cost goes to zero, which matters enormously when a free user of an AI extension otherwise costs you money on every request.
One developer explicitly ran a “distraction-free alternative to Grammarly... With BYOK support” — r/chrome_extensions, alongside a paid subscription. That pairing is the pattern: BYOK for the technical users who prefer it, subscription for everyone else.
The most durable structure, and the one that turns an extension into a sellable business. The extension becomes a client. The account, entitlement, data and billing live in a normal web app you control.
This is visible in the acquisition data: the listings with the strongest multiples describe themselves as a platform with an extension attached rather than as an extension. One is a “Workflow/process management app & Chrome extension for Standard Operating Procedures” — acquire.com listing at 4.4x. Our guide to building a SaaS covers the shape.
Donations do not work. That finding is consistent across every ecosystem we have looked at, and matches what WordPress plugin developers report, and one extension developer captured the scale precisely: “I still got a random 3 dollar donation from someone who uses my extension daily.” — r/chrome_extensions
Ad and data-monetization networks exist for extensions and will find you. Weigh them carefully: they change what your extension does on a user’s machine, and that is exactly the category of change that gets extensions removed and destroys resale value.
The best statement of the method came from a developer with a genuinely successful extension:
“My advice for creating a successful Chrome extension is simple: Find something that bothers you. If the current solutions are not good enough (or non-existent), create the solution that you and likely many others could use.” — r/chrome_extensions
The same developer described how the idea arrived: “I built this extension when I found a problem I couldn’t solve, published it, and was glad to find out a lot of other people had the exact same issue.” — r/chrome_extensions
That works, and it scales badly, because it depends on you personally having the problem. A second developer showed the market-gap version of the same instinct: “Screen Studio and similar products are thriving right now, but because they are restricted to mac only I figured creating a smooth screen recorder that is right inside the browser is bound to have some market.” — r/chrome_extensions
The systematic version is to search a corpus of other people’s documented complaints instead, which is what our validation method describes.
Extensions are unusually well suited to complaint-driven discovery, because the complaints are about specific websites people already use every day. The relevant shapes are: a workflow on a popular site that takes too many clicks, missing bulk operations, missing export, and data trapped in a UI. More of them in daily frustrations that need an app and problem-solving app ideas.
Our own tracked example of the pattern is an extension built because “Chrome doesn’t have a single button to toggle all your extensions on or off” — r/chrome_extensions, which reached 10,000+ users. Start at the pain points database, the complaint browser and Chrome extension ideas ranked by demand.
The clearest operating rule in the entire ecosystem, and it is stated by a developer who learned it the hard way: “Extensions with 100k or 1M users are usually stupid simple. They solve one problem and stay in their lane. When you start adding too much ‘cool stuff,’ you lose the magic.” — r/chrome_extensions
This is also why small MVPs win in this category more than in any other.
The full account is worth reading, because it is the rare case of a developer publishing a negative result:
“I pushed a huge update to my Extension... new UI, new features, small improvements, a ‘buy me a coffee’ button, everything. Three days later: user count went DOWN instead of up.” — r/chrome_extensions
The rollback was not the only surprise. They added: “The crazy part? I still got a random 3 dollar donation from someone who uses my extension daily.” — r/chrome_extensions
The uninstall feedback they quoted was “too complicated now”, “has bugs”, “harder to use” — r/chrome_extensions, and the fix was a rollback: “I ended up rolling everything back to the old simple version and immediately the numbers stabilized again.” — r/chrome_extensions
Since the store will not do it, you have three realistic options, and the choice mostly depends on whether you already have a backend.
| Approach | What it handles | Best for | Main cost |
|---|---|---|---|
| Extension payment layer, e.g. ExtensionPay | Checkout and subscription state without your own server | Solo developers with no backend | A fee, and a dependency on a small vendor |
| Your own backend plus Stripe | Everything, on your terms | Anyone who already runs a web app | You build and maintain entitlement logic |
| Bring your own key | Removes variable cost, not billing | AI extensions with technical users | Narrower audience, still needs a paid tier |
These exist because of the 2020 deprecation and they solve a genuine problem: taking money inside an extension without running servers. The trade is a dependency on a small vendor for the part of your business that collects revenue.
That risk is not theoretical in adjacent ecosystems. Shopify app developers had exactly this happen when a widely used billing vendor wound down with 60 days notice, as we covered in the Shopify app analysis. Keep an export of your customer and entitlement data.
More work up front and strictly better if you intend to sell. A buyer acquiring an extension wants the revenue system included and transferable, and an account system you control is the asset. See what transfers when you sell.
Observed pricing in our data runs from around $9 for a one-off unlock to about $40 for a lifetime tier, with subscription tiers typically in the single-digit to low-double-digit dollars per month. One developer described their launch offer as “$39.99 for only first 15 users lifetime access with lifetime updates” — r/chrome_extensions.
That developer’s full sixteen-day result is a useful benchmark for a launch: “2500+ visitors, 100+ users signups, 50+ videos are exported, 7 total paid users, $313 in total revenue, 46 install on my chrome extension.” — r/chrome_extensions
Those numbers are low because the audience is consumer. The way out is not to charge consumers more, it is to pick a problem whose owner is not a consumer.
The clearest evidence in our whole extension dataset is one developer running four paid extensions and reporting “~$4.3K MRR (up 3.5x in 6 mo) · 72 subs · ~91% margin · ~$82K/yr profit · fully automated” — revenue-verified product listing.
Seventy-two subscribers. Roughly $60 each per month. That is a better business than an extension with 50,000 free users, and it is the inverse of how this market usually talks about success. Install count is vanity; this is the number. The same lesson appears in what micro SaaS actually charges and how to price a micro SaaS.
The Chrome Web Store gives you a listing and a trickle. Everything else you build yourself, and the developers who succeed are unusually specific about what worked.
The most striking data point in our revenue set comes from an extension owner who wrote: “Google Chrome extension. 100% traffic comes from SEO. I currently spend about 20 minutes per week on customer support.” — revenue-verified product listing. That product earns around $1,368 a month.
Twenty minutes of support a week and all traffic from search is close to the ideal shape for this category: simple product, searchable problem, no human in the loop. Another developer was candid about the alternative: “The traffic has been mostly organic, I get new sales quite often, and honestly I’m not 100% sure where they are coming from... I keep forcing myself to do more marketing, but as 99% of devs, I am struggling.” — r/chrome_extensions
The single most replicable tactic we found, described plainly:
“Searched for ‘screen studio alternatives reddit’ in google, picked the top 10 results and commented on those threads to check out [my product]. Honestly this is such a low hanging fruit and is driving some consistent traffic, so I recommend you do this with your own competitors and genre.” — r/chrome_extensions
Do it with disclosure. The same developer in the Shopify ecosystem found that undisclosed promotion got them banned quickly, and the honest version worked better anyway.
Still worth doing, with modest expectations: “Post on producthunt. No big preparing or anything, just a nice video and some nice product screenshots with gradient background. It received 120 upvotes and got my first few customers.” — r/chrome_extensions
The same developer kept relisting deliberately: “List and relist on HN, indiehackers, peerlist, tinylaunch and so on. I try to do it as much as possible without being too spammy.” — r/chrome_extensions
First few customers, not a business. Useful as a starting push. See startup directories and getting customers for a new product.
A structurally smart move for any extension that produces an output: “Free users export with watermarks, so if they share a video, they also do a little bit of advertising for me. They can also share now via a quick share link without downloading the video, which directly leads to my landing page.” — r/chrome_extensions
This converts the free tier from a cost into a channel, which is the only way a free tier pays for itself in a market with no billing rail. The same developer’s landing page advice is worth stealing too: “Have a nice landing page... It’s simple, it’s clear, I think that’s why people like it.” — r/chrome_extensions
Extension developer communities are full of extension developers. A heavily upvoted post made the point bluntly:
“Most People post their chrome extension in this sub hoping to get users. But this is the last place you should be looking for users. The only thing you will achieve is to get 10 more copy cats to your extension. There are no real extensions users here, only other chrome extension builders.” — r/chrome_extensions
The counter-practice that does work is treating it as a journal rather than a billboard: “Post on reddit. I don’t do this too much, because I don’t want to be too spammy, but like once a month I try to create a journey post like this one here... Even if I don’t get paid users, some activity and conversation around the product is always beneficial.” — r/chrome_extensions
Use those communities for feedback and technical help. Find customers where your users’ problem lives instead, which is the argument in getting your first 100 users.
A developer in this market put the shift better than most marketers have: “Right now I am trying to look into some long-term user acquisition with SEO, and possibly GEO. Getting cited in LLMs are probably going to be an even bigger market then SEO is right now.” — r/chrome_extensions
They are right, and for extensions specifically it matters more than for most products, because “is there an extension that does X” is an archetypal assistant question. If the answer does not name you, the Web Store listing never gets opened. The practical work is publishing the page that answers the question directly, with specifics a model can quote. Same discipline as optimising for AI Overviews.
Reviews and install count drive Web Store ranking, and both compound slowly. Developers report their extension being featured by Chrome as a meaningful traffic event, with one noting it alongside “3 five star review on my chrome extension” — r/chrome_extensions in their first sixteen days.
The same launch report noted the payoff of the store surfacing it: “My extension got featured by chrome” — r/chrome_extensions.
Ask for reviews after you solve a problem, exactly as Shopify app developers do. The mechanic transfers cleanly between ecosystems.
Extensions have the best support-to-revenue ratio of the three ecosystems when the product is simple, and the worst when it is not. The twenty-minutes-a-week example above is achievable precisely because the product does one thing.
Every feature you add moves you toward the other end, and the most requested features data is a better guide to what to build than your own backlog. That is the same trade as the churn drivers we see across categories.
Chrome gives you an uninstall feedback channel and almost nobody reads it. The feature-creep post above only diagnosed the problem because the developer checked it.
The lesson that developer drew is the one to keep: “Now I’m shipping a new version that’s basically 95% the old one with tiny fixes. Still testing, still learning, still messing up.” — r/chrome_extensions
Track weekly active users rather than installs, read every uninstall reason, and treat a falling active count after a release as a rollback signal rather than a marketing problem. See SaaS metrics benchmarks.
Google has already removed the billing system once. It has also migrated the whole ecosystem to Manifest V3, deprecating capabilities extensions depended on. Assume further changes.
The mitigation is the companion web app. If the account, data and billing live outside the extension, a browser policy change costs you a client rather than a business.
Extension developers with real install bases receive unsolicited purchase offers, and this is a known hazard rather than an opportunity. An installed base with broad permissions is valuable to people who want to inject something into it.
If you sell, sell through a reputable marketplace or broker with a proper transfer process, and understand what your users are being handed. Our guide to selling a SaaS and due diligence checklist apply.
The listings with the best multiples in our extension data share three traits: recurring revenue rather than one-off unlocks, an account system that transfers, and a problem the buyer believes will still exist. The ones at 1.0x and 1.9x are the opposite. Read buying versus building and the state of SaaS acquisitions for how buyers frame that difference.
Not every developer wants that outcome, and that is a legitimate choice: “For now, I want to go solo and take 100% ownership.” — r/chrome_extensions. Just decide it deliberately rather than by default.
Build toward the first shape from month one. See finding acquisition targets for the buyer’s view.
| Multiple killer | What the buyer sees | Fix |
|---|---|---|
| One-off and lifetime revenue | No forward stream | Subscription tier from launch |
| Extension-only architecture | Nothing to transfer but a listing | Companion web app owns the account |
| Grey-area category | Uninsurable, removable overnight | Build something you would sign |
| Trivially replicable feature | Ten copycats in the store | Depth, data, or an integration barrier |
If you want the cheapest possible test of whether anyone wants your idea, build the extension. It is days of work, the store gives you a free listing, and you will learn quickly, which is the argument in launching a micro SaaS in a weekend and validating a side hustle idea.
If you want a business with a renewal stream and a real exit, build the Shopify app. If you want maximum control and no platform above you, take the WordPress route and accept the lower multiple. See also how to decide what business to start.
The build is cheap here. The expensive mistake is building the wrong extension, which is why BigIdeasDB is the tool we would use for this step and the one we built.
We hold 1M+ documented complaints plus revenue-verified products, live acquisition listings and a payment index of 30,000+ companies. Four questions, answerable before you write code:
Pair it with ChatGPT or Claude for code, Google Trends for direction, and Notion for notes. None of them hold a complaint corpus. Start at the discovery tool or the idea browser, or read how the validation tool works and how to find problems worth solving.
Every figure was queried live on September 12, 2026.
| Source | Used for | Evidence type | Limitation |
|---|---|---|---|
| Revenue-verified products (8,600+) | Revenue distribution, audience split, top earners | Connected payment data | Extension subset is n=112, matched on self-description. Self-selects toward founders who publish revenue, so the true zero rate is likely higher. |
| Acquisition listings (650+ live) | Exit multiples, margins, asking prices | Seller-reported financials | Extension subset is only n=9. These are asking prices, not closes. The 4.40x median is a survivor statistic and should not be read as a category benchmark. |
| Stripe payment index (30,000+) | Cross-checking ecosystem composition | Public directory plus classification | Only 11 extension matches. Most extension developers bill through a payment layer rather than appearing as a company, so coverage is poor. Reported as context only. |
| Idea validation swipes (78,000+ cards) | Founder interest in extension problems | User behaviour | 38 extension cards, few with meaningful impressions. Supporting colour only. |
| Live community (r/chrome_extensions) | Milestones, tactics, negative results | Self-reported developer accounts | Unverified individual claims, quoted as lived experience rather than measurement. Celebration posts are a biased sample by construction: they are the successes. Usernames stripped. |
| Published platform history | Chrome Web Store Payments deprecation | Vendor and press record | The 2020 shutdown and the prior 5% fee are well documented. Causal attribution of the revenue gap to it is our interpretation, not a measured effect. |
The honest caveat. The two headline numbers come from different populations and point in opposite directions: 6.3% reaching $1,000 a month is measured across 112 products, while the 4.40x median multiple is measured across nine survivors. Both are true. Neither generalises to the other. The comparison we trust most is the cross-ecosystem one, because all three were measured the same way on the same day.
What this cannot tell you. Whether your extension will work. A category median says nothing about a specific product, and the cheapest way to find out is still to build the thing and put it in front of people, then measure it the way the pain points database and the micro SaaS guide describe.
Search 1M+ documented complaints, revenue-verified products and live acquisition listings before you build the extension.
Start with real complaints →You build the billing yourself, because Google deprecated Chrome Web Store Payments in September 2020 and never replaced it. The practical options are a payment layer built for extensions, your own backend with a payment processor, a companion web app that holds the account, or a bring-your-own-key model. There is no platform billing rail and no store-managed subscription.
Very little, for most. Across 112 revenue-verified extensions we track, 57.1% earn nothing at all and only 6.3% clear $1,000 per month, against 10.3% across all 8,600+ tracked startups. Average monthly revenue is about $295 and the top earner in the set is around $9,742 per month.
Because the platform removed the billing rail. Chrome Web Store Payments let developers charge through the store for a 5% transaction fee until Google shut it down in 2020. Every developer since has had to build checkout, licensing and subscription management themselves, for an audience that expects browser add-ons to be free.
The few that reach an exit sell well. Across extension-related acquisition listings the median profit multiple is 4.40x on a 73.3% median margin, with a $104,000 median trailing revenue and a $249,000 median asking price. The sample is only nine listings, so read it as evidence that survivors are valuable rather than as a category median. Compare with profit multiples by SaaS category.
It is a good first product and a risky only product. The build cost is the lowest of any distribution platform and the survivors carry strong multiples. But 57.1% earn nothing, the audience is 4 to 1 consumer over business, and you own all the billing infrastructure yourself. Treat it as a cheap way to test a problem, then move the account into a web app. See micro SaaS examples for what the next step looks like.
Offer both and expect lifetime to dominate early. Developers report lifetime license sales accumulating far faster than subscriptions, with one reaching 30 lifetime sales while the subscription line was still around $100 a month. Lifetime converts better against consumer resistance; subscriptions are what make the business sellable later.
Bring your own key means the user supplies their own AI provider API key and you charge for the interface rather than the tokens. It removes your variable cost entirely, which matters because AI extensions otherwise pay per use for customers who may not pay you at all. Developers running it report it working alongside a subscription tier rather than replacing it.
Fewer than the install-count culture suggests, if you price properly. One developer in our data runs four paid extensions at roughly $4,300 per month from 72 subscribers, about $60 each. Meanwhile plenty of extensions with 10,000+ users earn nothing, because they never built a payment path. See what micro SaaS actually charges.
Longer than the launch posts suggest. Public developer milestones include a first paying customer at $9, 100 paying customers reached after about 1.8 years, $100 in monthly recurring revenue after starting in 2024, and 10,000 users after more than two years. Plan in years, not months.
Mostly search and word of mouth rather than the Chrome Web Store itself. Developers report organic traffic from Google, from commenting on competitor comparison threads, from Product Hunt launches, and from watermarked free exports that advertise the product. One notes that 100% of their traffic comes from SEO.
Not to find users. A widely upvoted post in that community argues the subreddit contains extension builders rather than extension users, and that launching there mainly attracts copycats. It is a good place for feedback and a poor place for customers.
In our revenue-verified set the top earners cluster in social media account management, AI writing and rewriting, marketplace seller automation, and academic assistance. That last category is large enough to be worth naming honestly: several of the highest earners are exam and detection-evasion tools, which carry obvious platform and reputational risk.
Overwhelmingly consumer. In our revenue-verified set, 56 extensions are classified B2C against 13 B2B, a ratio of more than 4 to 1. That is the inverse of the standard indie advice to sell to businesses, and it is a large part of why revenue per user is so low. See who micro SaaS actually sells to.
Usually not. One developer described shipping a large update with new UI and features and watching user count fall, with uninstall feedback citing complexity and bugs, then recovering by rolling back. Their conclusion was that extensions with very large user bases are typically simple and solve one problem.
Shopify, on every measure that matters commercially. Shopify apps bill through the platform, sell to businesses, and carry a 3.90x median profit multiple. Chrome extensions have no billing rail, sell to consumers, and only 6.3% reach $1,000 a month. Chrome wins on speed to launch and nothing else. Read the Shopify app analysis.
Yes, and unsolicited offers are common enough to be a known risk in the ecosystem, because an installed base is valuable to whoever wants to inject something into it. Sell through a reputable channel, transfer properly, and be aware that buyers of extension user bases do not always have benign intentions.
Building the extension before building any way to charge for it. Because there is no store billing, a free extension with 10,000 users and no payment path cannot be retrofitted easily: the users installed it on the understanding it was free. Decide the monetization model before you publish.
Chrome extensions are the cheapest way to put a software product in front of people and the hardest way to get paid for it. Both facts trace to the same source: the platform gives you free distribution and no billing, so the barrier moved from building to charging.
One developer summarised the emotional arithmetic of the category better than any metric: “It took me 8 months to build this application and now after seeing the responses, feedback I feel so happy that I’ve finally built something that people actually need.” — r/chrome_extensions
That makes the extension an excellent first move and a poor final destination. Use it to prove a problem is real at almost no cost, then put the account in a web app, price against a buyer who is not a consumer, and decide deliberately whether the business belongs on a platform that will bill for you.
If you are choosing a platform rather than a product, start at the seven-ecosystem comparison. Otherwise start with the complaint data, check the niche against what has actually sold, and read Chrome extension ideas ranked by demand plus micro SaaS ideas backed by complaints if you are still choosing.
BigIdeasDB Research. (2026). How to Monetize a Chrome Extension in 2026: Real Data. BigIdeasDB. Retrieved from https://bigideasdb.com/how-to-monetize-a-chrome-extension