TL;DR

• Chrome extensions that make money in 2026 cluster around five patterns: subscription SaaS sidekicks, one-time license keys, freemium with usage caps, donation-plus-pro, and B2B seat licenses.
• Revenue bands for indie-built extensions range from a few hundred dollars a month to mid-six-figure ARR, with the bulk of profitable ones sitting between $2K and $20K MRR.
• The biggest predictor of revenue isn't install count — it's how tightly the extension wraps a workflow the user already pays for elsewhere.

Chrome extensions that make real money in 2026

Chrome extensions that make money in 2026 fall into a small number of repeatable patterns, and most of them are reachable by a single developer working evenings. The myth that browser extensions are a hobbyist category — toys, dark-mode toggles, novelty cursors — hasn't matched reality for a few years now. The Chrome Web Store today hosts a steady tier of indie-built extensions clearing $5K to $30K MRR, and a smaller tier of bootstrapped teams running well past $1M ARR off a single listing.

What changed isn't the platform. It's the willingness of users to pay for narrow tools that save them ten minutes a day inside the browser they already live in.

How much do Chrome extensions actually make?

There's no single answer, but a rough distribution shows up consistently in Indie Hackers threads, public Twitter revenue dashboards, and the few Chrome Web Store listings that publicly link to ProfitWell or Stripe data.

A reasonable mental model for an indie-built extension that has found product-market fit:

The bottom band is $200 to $1,500 MRR. This is where most paid extensions actually land. Small but consistent, often a side project for a developer with a day job. The extension solves one specific annoyance for a few hundred people who care enough to pay $3 to $7 a month.

The middle band is $2,000 to $20,000 MRR. This is where extensions stop being a side project and start being a business. The product usually wraps a paid SaaS workflow — Notion, Linear, Salesforce, LinkedIn Sales Navigator — and charges $9 to $29 a month for power-user features the host platform won't ship itself.

The top band is $30,000+ MRR, running up to mid-seven-figure ARR for the largest. These are usually teams of two to five people, often with a freemium funnel that converts on usage caps rather than feature gating. Ad blockers with Pro tiers, screenshot tools with team collaboration, AI helpers with token-based limits.

Above all of that sit a handful of category leaders — Grammarly, Honey, LastPass — which long ago graduated from "Chrome extension business" to "company that also has a Chrome extension."

What kinds of extensions make money?

Across the profitable listings we've seen, seven categories show up over and over:

AI helpers. Sidebar copilots wrapping GPT-class models for writing, summarizing, or rewriting. Usually sold as $10 to $20 a month with a free tier limited by daily message count.

Productivity layers on top of paid SaaS. Extensions that add a missing feature to Gmail, Notion, Linear, or Salesforce. The host tool's gap is the product.

SEO and marketing tools. Keyword research, SERP scrapers, on-page analyzers. B2B users will pay $30 to $99 a month if it saves a paid tool subscription.

Developer DX tools. GraphQL inspectors, cookie editors, accessibility auditors, JSON viewers with paid features. The audience is small but converts well.

Content scrapers and exporters. Pulling structured data out of LinkedIn, Twitter, Amazon, or Shopify. The legal grey area is real, but the revenue is consistent.

Ecommerce assistants. Price trackers, coupon finders, drop-shipping research tools. Revenue comes from subscriptions, affiliate fees, or both.

Security and privacy. Password managers, ad blockers, tracker blockers. Donation-plus-pro is common here. The free tier is the marketing funnel.

12 real Chrome extensions and what they earn

Composite/observed examples — exact figures rounded for privacy, drawn from public statements on Twitter, Indie Hackers threads, and Chrome Web Store listings. Treat the bands as directional, not audited.

1. Superpowers for ChatGPT-style extension. Adds folders, prompt libraries, and export to a popular LLM chat UI. Subscription, $7/mo or $59/yr. Reported in the $15K–25K MRR range based on a founder thread on Twitter in late 2025. Growth came from a viral TikTok demo, not paid acquisition.

2. Loom-style screen recorder with team workspaces. Free for solo use, $12/seat for teams. Sits in the $8K–15K MRR band. The free tier is the funnel; team upgrade is the conversion event.

3. Bitwarden-style password manager (open-source plus pro). Donation-funded core with a $10/yr premium tier for advanced 2FA. Public funding statements put it well above $100K ARR, though most of that flows to infrastructure, not founders.

4. uBlock Origin-style ad blocker. Donations only, no paid tier. Not strictly "making money" in the SaaS sense, but the maintainer's public Patreon and GitHub Sponsors reportedly sustains roughly $4K–6K MRR. Worth mentioning because the donation-plus-no-pro model is viable for a certain kind of project.

5. Honey-style price tracker. Affiliate revenue model, no subscription. The category leader was acquired for nine figures; smaller indie clones in adjacent niches (specific marketplaces, B2B procurement) reportedly run $3K–8K MRR on affiliate alone.

6. Grammarly-style writing assistant for a narrow niche (academic writing, German-language editing, or technical documentation). $15/mo subscription. Indie versions targeting a specific vertical have publicly mentioned $5K–12K MRR ranges in indie hackers threads.

7. LinkedIn power-user extension. Bulk connection messaging, profile scraping, CRM sync. $39 to $79 per month. The legal exposure is real, but founders we've seen post about this category cite $10K–30K MRR with a small team.

8. Twitter/X analytics and scheduling extension. Sidebar with thread scheduling, analytics, and a writing assistant. $19/mo. Founder publicly shared on Indie Hackers hitting mid-five-figure MRR after eighteen months.

9. Cookie editor / web debugging tool with paid sync. Free local tool; $4/mo for cross-device sync and team sharing. Niche but converts well — reported $2K–4K MRR with near-zero churn.

10. Shopify product research extension. Pulls competitor pricing, supplier info, and ad creative. $29/mo. Dropshipping audience is volatile but the right tools clear $20K MRR.

11. AI meeting note-taker browser extension. Records, transcribes, and summarizes Google Meet / Zoom Web calls. $15/mo individual, $25/seat team. Newer category, fastest-growing — top indie listings reportedly added $10K+ MRR in their first six months.

12. Accessibility auditor for developers. Scans a page for WCAG violations, generates a report. $12/mo individual, $99/mo team. Smaller TAM, but a founder posting on the Chrome Web Store developer community mentioned roughly $3K–5K MRR with extremely low churn — once a dev workflow includes a tool, it stays.

What separates the ones that make money from the ones that don't?

Five patterns show up repeatedly in the profitable listings, and they're noticeably absent from the unprofitable ones.

Wrapping a workflow the user already pays for. Almost every profitable indie extension we've looked at sits adjacent to a paid SaaS the user is locked into. The user isn't deciding "is this worth $10?" — they're deciding "is this worth $10 to fix a $50 tool I'm already buying?"

Daily-use frequency. Extensions that get opened once a week have terrible retention curves. Extensions that show up every time the user opens a specific website have retention curves that look like flat lines.

A clear "this is broken without you paying" moment. Freemium works, but the upgrade trigger has to be tied to something the user feels, not something abstract. Usage caps work; "unlock 3 more themes" doesn't.

Distribution outside the Chrome Web Store. Almost none of the founders we've seen at $10K+ MRR rely on Chrome Web Store search as their primary channel. It's Twitter, YouTube demos, dev communities, niche newsletters, or partner integrations.

Payment that actually works inside MV3. This is the one most underestimated by first-time builders. Chrome's Manifest V3 service worker model breaks a lot of older payment flows. Extensions that hand-rolled their auth and entitlement code in 2021 are quietly losing customers in 2026 to cache-eviction bugs and CORS errors in the background worker. The ones still growing are using purpose-built payment infrastructure.

How they actually collect payment (and why it matters)

There are four realistic options for collecting payment from a Chrome extension in 2026, and the choice has more impact on revenue than most founders realize.

Stripe direct. Maximum flexibility, maximum work. You build the checkout, the webhook handler, the entitlement store, the offline cache, the MV3-compatible background fetch. For a developer who already runs a SaaS backend, fine. For a solo extension dev shipping nights and weekends, it's a project that eats months before it earns a dollar.

Gumroad or Lemon Squeezy. Great for one-time license keys. Painful for subscriptions inside an extension — you end up writing your own license-key entry UI, your own renewal logic, and your own offline tolerance. Works if your product is genuinely a one-time purchase.

ExtensionPay. The established player. Drop-in, well-documented, used by hundreds of paid extensions. Flat 5% per transaction, no free tier. Solid choice if you want a turnkey solution and don't mind the fee.

crxpay. A newer drop-in subscription SDK and dashboard built specifically for MV3. The SDK handles entitlements, paywalls, offline-signed caching, and Stripe Connect integration so the developer keeps their own Stripe account. The first $2,500 of cumulative processed revenue is free; after that it's 2.5% per transaction — roughly half of ExtensionPay's fee. Comparable in spirit to what RevenueCat does for mobile subscriptions. If you're already on ExtensionPay and want to compare side-by-side, there's a direct migration path documented.

The reason the payment layer matters more than it looks: the failure modes are invisible. A bad payment SDK doesn't crash your extension. It quietly tells five paying users a month that their subscription "expired" because the service worker evicted the cache, and they churn before opening a support ticket. The fix is architectural — signed offline entitlements, deterministic state machines, MV3-native fetch handling — and it's almost impossible to bolt on after launch.

Full pricing for both ExtensionPay and crxpay is public; see crxpay's pricing page for the current numbers.

Getting started: from 0 to first paying user

The shortest realistic path from idea to first paying user, based on what's worked for the developers in the case studies above:

Ship a free version first. Get to a few hundred weekly active users before adding payment. The reason isn't marketing — it's that you need real users to find the upgrade trigger that actually converts. Guessing it in advance almost never works.

Pick your monetization model based on usage frequency. Daily-use tool: subscription. Weekly-use tool: one-time license. Occasional-use tool: probably not worth charging for, monetize through affiliate or freemium-with-a-team-tier instead.

Wire payment in once, not twice. The most expensive mistake we see is shipping a v1 with Gumroad license keys, then rewriting to Stripe at $2K MRR, then rewriting again to a proper SDK at $8K MRR when the entitlement cache bugs start costing real churn. Pick the architecture you'd want at $10K MRR and start there.

Free trials are a separate topic — the full guide covers trial length, payment-up-front versus payment-after, and how to handle trial expiry inside MV3 without locking users out mid-session.

For the deeper breakdown of pricing models — flat subscription vs. usage-based vs. one-time vs. hybrid — see the companion piece on Chrome extension monetization models in 2026.

---

If you're at the stage where you have a working extension and you're thinking about adding payment, the crxpay free tier covers your first $2,500 of processed revenue with no fees. That's enough runway to validate whether your audience will actually pay, before you owe us anything. Pricing details and sign-up are here — the SDK is a single npm install, and the dashboard handles the rest.