I've been publishing Chrome extensions for about a year. Six months ago I started adding freemium monetization to my extensions using ExtensionPay. Here are the actual numbers and what I've learned.
I'm sharing this because almost no one publishes real conversion data for Chrome extension monetization. The advice is almost always theoretical. Here's what I've observed across 5 monetized extensions.
The Portfolio
Five extensions with ExtensionPay freemium:
| Extension | Category | Price | Free Limit | Installs |
|---|---|---|---|---|
| Procshot | Productivity | $4.99/mo | 2 guides/month | ~900 |
| Japanese Font Finder | Dev Tools | $2.99/mo | 30 inspections/day | ~1,200 |
| PaletteGrab | Dev Tools | $3.99 one-time | 10 colors in tray | ~600 |
| AdLegalCheck | Productivity | $9.99/mo | 3 scans/month | ~150 |
| ToritekiCheck | Productivity | $4.99/mo | 3 analyses/month | ~80 |
Installs are approximate active users from CWS Insights. Monthly active users are lower.
Conversion Rates
Across all five extensions, my overall free-to-paid conversion rate is 0.8%.
That sounds low. For SaaS, 2-5% free-to-paid is considered decent. For Chrome extensions, I've come to believe 0.5-2% is realistic.
Why so low?
Zero friction to install and use the free tier. There's no sign-up, no credit card, no friction at all. The baseline installed count includes a lot of casual installs that never became engaged users.
The upgrade decision happens at an inconvenient moment. Users hit the free limit while they're trying to do something. The friction of the upgrade prompt competes with the task they were trying to complete.
Trust gap. Chrome extension payments are unusual. ExtensionPay shows a payment page that says "extensionpay.com" — which many users don't recognize. Some users who would pay for a web app won't pay for an extension.
The Limit Design Matters More Than the Price
My highest-converting extension is Japanese Font Finder at about 1.4% conversion. The free limit is 30 inspections per day, which sounds generous but is calibrated to the power user's usage pattern.
A designer who uses JFF seriously will hit 30 inspections in a work session. The limit creates just enough friction for real users without frustrating casual users.
My lowest-converting extension (by rate) is PaletteGrab at 0.3%. The free limit is 10 colors in the color tray. This turns out to be fine for most use cases — you can pick and copy colors without saving them. The upgrade prompt appears too rarely.
What I've learned: The free limit should be just below the threshold for your power user's typical session. Too generous = no upgrade pressure. Too tight = users abandon before getting value.
The Upgrade Prompt Matters
My initial upgrade prompts were modal alerts: "You've reached your limit. Upgrade to Pro?"
Conversion from prompt to upgrade: 2%.
I rewrote them to show what the user would get: "You've made 2 guides this month. Pro users get unlimited guides + PDF export + annotation tools." Then two buttons: "Upgrade to Pro ($4.99/month)" and "Maybe later."
Conversion from prompt to upgrade: 8%.
The difference is showing value rather than showing a wall. Users need to remember why they'd pay before they decide to.
ExtensionPay Observations
ExtensionPay is the only practical solution for Chrome extension payments that I've found. It handles the Stripe integration, the payment UI, and the license verification API.
A few things I've noticed:
The payment flow is not optimized for conversion. The user leaves the extension, opens a new tab, sees "extensionpay.com", enters their email, then pays. Each step is a drop-off point. I estimate 30-40% of users who click "Upgrade" complete the payment.
Monthly vs. one-time matters by category. Productivity tools (recurring use) convert better to monthly subscriptions. Utility tools (occasional use) convert better to one-time payments. PaletteGrab switched from $2.99/month to $3.99 one-time and conversion improved 60%.
Free users complain; paid users don't. My CWS reviews are overwhelmingly from free users frustrated by limits. Paid users tend to leave positive reviews or no review at all. This is expected but worth knowing.
The Revenue Reality
My current monthly recurring revenue across all five extensions is approximately $180/month. That's well below what I'd need to make this a business, but it's meaningful signal.
The trajectory matters more: three months ago it was $60/month. Six months ago it was $0.
The install base is growing (mostly through CWS organic search), and conversion rates have improved as I've refined the upgrade prompts and limit designs. At current growth rates, I expect to cross $400/month within 6 months.
What I'd Do Differently
Ship freemium from day one. Extensions I launched without monetization have free users who feel entitled to free forever. Adding a paywall retroactively generates negative reviews. New extensions now launch with the freemium model from the first public version.
One-time pricing for tools, subscription for productivity. The recurring revenue math is better for subscriptions, but one-time pricing converts better for tools users reach for occasionally. Match the pricing model to the usage pattern.
The free limit should be lower for higher-priced plans. My $9.99/month AdLegalCheck has a free limit of 3 scans/month. That's appropriate for a $10 product. My $2.99/month JFF has a limit of 30/day — much more generous, appropriate for a $3 product. The limit signals the value relative to the price.
I track my Chrome extension revenue and growth at dev-tools-hub.xyz.
Top comments (0)