How to Price a Chrome Extension: Models, Checkout and Licensing

Price a Chrome extension by what each extra user costs you to serve. If the extension runs entirely in the browser, a one-time price or a free tier with a paid upgrade works well; if every click calls an AI model or a paid API, charge a subscription or sell credits. Since the Chrome Web Store stopped processing payments on 1 Feb 2021, you also need your own checkout and your own way of checking who has paid.

Facts about Google, Lemon Squeezy, Paddle and Stripe come from their own pages, checked on 6 Nov 2026. The advice in between is ours.

TL;DR#

• The store will not take money for you. Google's notice says that from Feb 1, 2021, "your existing items and in-app purchases can no longer charge money with Chrome Web Store payments" (Chrome for Developers).
• Marginal cost picks the model. Client-side tools suit one-time or freemium pricing. Extensions that call AI models or paid APIs need recurring revenue or credits.
• Licensing is your job. Developers using the old licensing API were told to "implement another way of tracking user licenses" (same source).
• Merchants of record cost more and handle tax. Lemon Squeezy and Paddle both list 5% + 50¢ per transaction (Lemon Squeezy fees, Paddle). Stripe charges less per payment, but you remain the seller (Stripe).
• There is no reliable "average" extension price. Price from value and cost, then test with real buyers.

Disclosure: ZeroRaised publishes this guide and is a launch site for bootstrapped products. Facts come from the linked sources as checked on 6 Nov 2026; ZeroRaised has no commercial relationship with the companies named.

Chrome extension pricing is the choice of how and how much to charge for a browser extension, including the payment model (one-time, subscription, freemium or credits), the checkout provider and the way the extension verifies that a user has paid.

What happened to Chrome Web Store payments?#

For years, developers could charge for an extension directly in the Chrome Web Store. That ended in stages. Google's deprecation page lists the milestones:

• March 27, 2020: publishing of paid items temporarily disabled.
• September 21, 2020: "You can no longer create new paid extensions or in-app items." The change became permanent.
• December 1, 2020: free trials disabled, and the "Try Now" button removed.
• Feb 1, 2021: existing items and in-app purchases can no longer charge money with Chrome Web Store payments. Subscriptions "won't auto-renew".
• At some future time: the licensing API will no longer report license status.

Google's explanation was that "developers now have many payment-handling options available to them." The practical result is that every paid Chrome extension today follows the same pattern: a free listing in the store, a checkout on your own site or inside the extension, and a license check you build or rent (Chrome for Developers).

So the store listing is a distribution channel, not a till. Getting the listing approved and found is a separate job, covered in our guide on how to launch a Chrome extension.

Start with marginal cost, not competitor prices#

The most useful question before choosing a model is: what does one more active user cost you each month?

Extensions fall roughly into three groups.

1. Fully client-side. The code runs in the browser. Think of tab managers, page tweaks, keyboard shortcuts or local formatting tools. Once built, an extra user costs you close to nothing, apart from support.
2. Light backend. The extension syncs settings, stores data or sends occasional requests to your server. Each user costs a little, and the cost grows slowly.
3. Metered backend. Every action calls an AI model, a paid data API or heavy compute. Each use has a real, variable cost, and your heaviest users may cost many times more than your lightest.

The pricing model should match the cost shape. If revenue is one-off but costs repeat every time someone clicks, a popular extension can lose money faster as it grows. If costs are near zero but you charge monthly, some buyers will see a subscription as rent on a tool that never changes.

The four pricing models compared#

One-time purchase#

A single payment unlocks the paid version. This suits a client-side extension that solves a clear, stable problem. It is easy to explain and it removes the "another subscription" objection.

The weakness is that revenue depends entirely on new buyers. If you plan to maintain the extension for years, consider pricing major versions separately or offering paid upgrades, and say so on the sales page so early buyers know what they are getting. Avoid it for an extension that calls a paid API on every use: a heavy user who pays once can end up costing more than they paid.

Subscription#

Monthly or yearly billing fits two cases. The first is any extension with ongoing costs per user, such as sync, storage or API calls. The second is a tool that keeps improving in ways users notice, so the monthly fee pays for continuing work.

Offer a yearly plan next to the monthly one. It gives buyers who are sure a reason to commit and gives you cash up front. Our guide on how to price a SaaS product goes deeper on tiers and annual discounts, and most of it applies to subscription extensions.

Freemium#

The extension is free to install and use, with limits, and a paid tier removes them. Because the Chrome Web Store already gives you free distribution, freemium is a natural fit: people install with no friction, and the paid tier is pitched to the ones who come back.

Freemium works when two things are true: the free tier costs you almost nothing to run, and there is an obvious line heavier users cross. Good lines include number of uses per day, number of saved items, sync across devices, or advanced features that only power users want. A free tier that calls an expensive API without a cap is a cost centre, not a funnel.

If you are weighing a free tier against a time-limited trial, we compare both in freemium vs free trial for solo founders. Note that Chrome Web Store free trials were disabled on December 1, 2020, so any trial now has to run through your own licensing.

Credits or usage-based pricing#

Users buy a pack of credits, and each action spends some. This is the cleanest fit for AI-backed extensions, where cost scales with use. Light users pay little, heavy users pay more, and your margin per action stays roughly fixed.

The trade-off is predictability. Some users dislike watching a balance. A common middle path is a subscription that includes a monthly allowance, plus optional top-ups for heavy months. Whatever you choose, show the remaining balance clearly inside the extension so nobody hits zero by surprise.

How to choose a checkout: Lemon Squeezy, Paddle or Stripe#

With the store out of the payment loop, you need a provider that can take money and, ideally, issue or verify licenses. The main decision is whether you want a merchant of record (the provider legally sells to the customer and handles sales tax and VAT) or a payment processor (you are the seller and handle tax yourself). We explain the difference in detail in merchant of record vs payment processor.

Sources: Lemon Squeezy fees, Paddle pricing, Stripe pricing.

Lemon Squeezy's fee page gives a worked example: on a $20.00 product with 20% VAT, a $24.00 total and an international payment, the platform fee is $2.06, leaving $17.94 (Lemon Squeezy fees). Run the same kind of sum for your own price. On small one-time prices, the fixed 50¢ takes a much larger share than it does on a yearly plan, which is one more reason to offer annual billing.

Our view for solo developers:

• Choose a merchant of record if you sell to customers in many countries and do not want to register for sales tax and VAT yourself. Extensions are sold globally from day one, so this is usually the default.
• Choose Stripe if you already handle tax, sell mainly in one country, or need custom billing logic and are comfortable owning compliance.

Whichever you pick, check what it offers for license keys or customer status lookups. That decides how much licensing code you write yourself.

Build the license check before you set the price#

Google's notice is blunt: if you used the store's licensing API, "you'll need to implement another way of tracking user licenses" (Chrome for Developers). New extensions have to do this from the start.

The usual options:

1. License keys. Checkout issues a key, the user pastes it into the extension, and the extension verifies it with your server or the provider's API. Simple, and it works across browsers.
2. Accounts. The user signs in inside the extension, and your backend knows their plan. Better for subscriptions and credits, because status can change month to month.
3. Server-side enforcement. For metered extensions, check entitlement on the server before doing the expensive work. Client-side checks can be bypassed; server checks protect the thing that costs you money.

For a fully client-side extension, accept that a determined user can bypass a local check. Price and design for honest users, and make paying easier than cracking.

How to set the actual number#

We will not quote an average Chrome extension price, because we could not find a primary source we trust for one, and copying a competitor's number tells you nothing about your costs or your buyers. Instead:

1. Write down the job the extension does and what that job is worth to the user in time or money. A tool that saves a recruiter an hour a day can charge more than one that tidies tabs.
2. Work out your cost per active user each month, including API calls, hosting, checkout fees and the support time you expect.
3. Set a floor. Your price should cover that cost with a margin even for heavier users. For credit models, set the price per credit above your worst-case cost per action.
4. Talk to real users. Ask a handful of people who use the free version what they would pay for the paid tier, and offer them the chance to buy. A payment tells you more than an opinion.
5. Launch, then adjust. You control pricing on your own checkout, so you can raise prices for new customers as the extension improves. Consider keeping early buyers on their original price as a thank-you.

Frequently asked questions#

Can you still charge for a Chrome extension in the Chrome Web Store?#

Not through the store itself. Google's deprecation notice says new paid items stopped permanently on 21 September 2020, and from 1 February 2021 existing items and in-app purchases could no longer charge money with Chrome Web Store payments. You can still list the extension for free in the store and take payment through your own checkout.

Should a Chrome extension be a one-time purchase or a subscription?#

Decide by marginal cost. If the extension runs in the browser and costs you almost nothing per user, a one-time price is honest and easy to sell. If it calls an AI model, a paid API or your own servers on every use, a subscription or credits keep revenue in line with the cost of serving each user.

What is the best payment provider for a Chrome extension?#

For most solo developers, a merchant of record such as Lemon Squeezy or Paddle is the simplest choice, because it handles sales tax and VAT. Both list 5% + 50¢ per transaction, and Lemon Squeezy adds 1.5% for international payments and 0.5% for subscriptions. Stripe has lower processing fees but you are the seller and handle tax yourself, unless you use its Managed Payments product.

How do I check whether a user has paid inside my extension?#

Issue a license key or tie the purchase to an account at checkout, then have the extension verify it against your backend or your provider's license API. Google's deprecation notice says developers who used the Chrome Web Store licensing API must implement another way of tracking user licenses.

Is freemium a good model for a Chrome extension?#

It often fits, because the Chrome Web Store is a free distribution channel and a free tier lets people try the extension without friction. It works best when the free tier is cheap to run and the paid tier unlocks something heavier users clearly need, such as more usage, sync or advanced features.

Where ZeroRaised fits#

ZeroRaised is a launch directory for products built without institutional VC or accelerator equity, including browser extensions. Once your pricing and checkout are live, you can submit your extension for free. For more guides on pricing, launching and funding without investors, join the ZeroRaised newsletter.

Sources#

• Chrome for Developers: Chrome Web Store payments deprecation, last checked 6 Nov 2026
• Lemon Squeezy pricing, last checked 6 Nov 2026
• Lemon Squeezy fees, last checked 6 Nov 2026
• Paddle pricing, last checked 6 Nov 2026
• Stripe pricing, last checked 6 Nov 2026