The short answer
Take payment on your own site or through a service like ExtensionPay, then have the extension ask a server whether the user has paid before opening the paid feature. That's how to add a Chrome extension paywall. Keep the check and the paid work on the server. Anything decided only inside the browser can be switched off by a curious user.
- The browser can't keep secrets. Your code ships to every user.
- Check licences against a server, and cache the answer briefly.
- In our data, ExtensionPay (about 920 listings), Gumroad (about 725) and Lemon Squeezy (about 520) are the most common payment hosts.
- Put the paywall where value appears, not on first open.
In this guide14 sections
- 01Step 1: pick how you'll take money
- 02Step 2: check the licence on a server
- 03Step 3: place the Chrome extension paywall where value shows up
- 04Step 4: say it on the listing
- 05Trials that convert
- 06Offline grace
- 07Cancels and refunds
- 08Real listings, real routes
- 09What to put behind the paywall
- 10Testing your paywall before launch
- 11Explaining the price
- 12Common mistakes
- 13Questions people ask
- 14Extensions in this guide
A Chrome extension paywall built only in the browser is a velvet rope with no bouncer. It looks official. Anyone can step over it.
This guide is about the developer side: adding a paywall to your own extension. If you came here looking for a way around someone else's, this isn't that. Paywalls are one option in our guide to monetizing a Chrome extension.
Step 1: pick how you'll take money
The Chrome Web Store doesn't process payments (TechRadar's report on the deprecation), so you bring a provider. Here's what extensions in our data point at in their links or code:
| Payment host | Extensions |
|---|---|
| extensionpay.com | About 920 |
| gumroad.com | About 725 |
| lemonsqueezy.com | About 520 |
| stripe.com | About 200 |
| polar.sh | About 160 |
| paypal.com | 56 |
Most bigger extensions don't show up here at all, because they take payment on their own website and check accounts on their own servers. So treat this table as "what small builders reach for", not market share.
ExtensionPay is built for this exact case. Its homepage lists a 5% transaction fee and no monthly fee, and it runs on Stripe (extensionpay.com).
Step 2: check the licence on a server
The flow looks like this (the full account setup is in our Chrome extension SaaS guide):
- User clicks Upgrade and pays on your checkout page.
- Your payment provider tells your server the user paid.
- The extension asks your server "is this user paid?" and gets a yes or no.
- The extension caches that answer for a short time, say a day.
- Paid features that cost you money run on your server, which checks again.
Step 5 is the real lock. If the paid feature is an AI call, a data lookup or sync, the server refuses unpaid users no matter what the browser says.
Step 3: place the Chrome extension paywall where value shows up
Asking for money on first open loses people who haven't seen anything yet. Better spots:
- After the third saved item.
- When they try a feature that costs you to run.
- When a team of two tries to share.
Show what they'll get, the price, and a plain way to cancel. Freemium, one-time or subscription decides what the paywall guards.
Step 4: say it on the listing
Google's policies ask that listings describe what's paid. Put it in the description: what's free, what's paid, roughly how much. Surprise charges earn one-star reviews.
Trials that convert
A trial lets people see the paid features before paying. It works best when the tool is used often enough that a week shows its value.
| Trial type | Good for | Watch out for |
|---|---|---|
| Time-limited (7 or 14 days) | Daily tools | Users who forget it ended |
| Usage-limited (first 10 uses) | Occasional tools | Hitting the limit too fast |
| Feature preview | Tools with one standout paid feature | Free tier feeling crippled |
Tell people when the trial ends, a day before it does. Surprise endings feel like a trick, even when they aren't.
Offline grace
A paywall that checks a server every time breaks on planes and bad wifi. Paying users notice, and they're the ones you least want to annoy.
- Cache the "paid" answer for a day or a few.
- Keep paid features working until the cache expires.
- Recheck quietly when the connection returns.
- Never lock someone out mid-task because one check failed.
This is a small amount of code, and it saves a lot of one-star reviews.
Cancels and refunds
A clear way out builds trust on the way in. Put both on your site, linked from the extension.
- A cancel buttonin the account page, not an email request.
- A plain refund policywith a time limit.
- A confirmation emailfor both.
- Paid features endingat the end of the paid period, not the moment they cancel.
Payment providers handle most of this for you. Check what yours does by default.
Real listings, real routes
Here's how some listings in our data take money. These show a route exists, not how many people pay.
| Extension | Users | Route |
|---|---|---|
| Chrome Capture | 300,000 | Paddle |
| Tally, a Claude token counter | 100,000 | Polar |
| PrettyMerch for Merch by Amazon | 40,000 | Gumroad |
| Gemini Bulk Delete | 40,000 | Lemon Squeezy |
Store figures from 5 Oct 2026, when this guide was written. Live numbers are in the windows marked “Live today”.
Open their listings and pricing pages side by side. You'll see how each one says what's free and what's paid, which is the part that keeps reviews kind. The screen recorders niche page is a good place to compare how capture tools do it.
What to put behind the paywall
Not every feature should be paid. A rough guide to choosing.
| Feature type | Free or paid? | Why |
|---|---|---|
| The core job, done simply | Free | Brings users in |
| Anything that costs you per use | Paid | Covers your costs |
| Volume, like more saves or exports | Paid | Heavy users value it most |
| Team sharing | Paid | Companies expect to pay |
| Basic settings and themes | Free | Small, and annoying to lock |
The best paywalls feel fair. Users understand why the paid part costs money, because it does more or costs you more.
Testing your paywall before launch
Run through these before real users see it.
- Pay with a test cardin your provider's test mode.
- Cancel, and check paid features end when they should.
- Go offlineand check the grace period works.
- Reinstall the extensionand check the paid status comes back after sign-in.
- Flip the local flagand check the server still refuses paid work.
The last test is the one that matters most. If it fails, the paywall is only a suggestion.
Explaining the price
The upgrade screen should answer three questions in a few lines: what you get, what it costs, and how to cancel. Link a fuller pricing page on your site.
Look at how others in your niche do it before writing yours. Our extension search shows which listings carry a payment signal, so you can open a few and compare their upgrade screens.
Common mistakes
- Paid checks only in the browser.
- No offline grace: a user on a plane loses features they paid for.
- Hiding the price until after install.
- No cancel button.
We're biased, but if you want to see how others do it, Ext Watch lets you filter extensions by payment host on the extensions page, then open their listings and pricing pages yourself.
Find your isPaid flag today and ask what happens if someone flips it.
Extensions in this guide
The extensions named in this guide, most-used first, with today’s users and ratings.
| # | Extension | Users | Rating | Open |
|---|---|---|---|---|
| 1 | PrettyMerch for Merch by AmazonMerch Technologies LLC | 40K | ★ 4.4667 | |
| 2 | Gemini Bulk DeleteHamza | 40K | ★ 3.9364 |
See every Screen recorders extension or browse all Workflow & Planning extensions
Questions people ask
Can I use Stripe directly in a Chrome extension?
Yes, through your own server and checkout page. The extension shouldn't hold your secret keys.
Is ExtensionPay safe to use?
It's open source and uses Stripe for payments. Read its docs and decide if a 5% fee is worth not running a server.
Can users bypass my paywall?
If the check lives only in the browser, yes. Keep paid work on your server.
Should I offer a free trial?
A short trial of the paid features works well for tools people use daily. Make the end date clear and don't charge without warning.
How do I handle refunds for an extension?
Through your payment provider. Write a plain refund policy on your site and link it from the upgrade screen.
1,055 extensions tracked in Screen recorders. See them all.
Compare paid extensions in your niche before you set a price.Store data, updated today



