Skip to content

Sell your Chrome extension

Indiemaker · Updated 17 November 2026

In short

You sell a Chrome extension by transferring its Chrome Web Store item to the buyer's developer account, along with the code, any backend and the billing. Buyers check weekly users, permissions, review history and policy standing. For extensions with profit, Indiemaker's guide is 2.7 to 3.2 times trailing annual profit.

An extension's whole distribution lives inside one store listing. The users, the reviews, the search position and the automatic updates are all attached to a single item ID in the Chrome Web Store, and that item sits in a developer account. So when you sell a Chrome extension, the item is the asset, and everything else in the deal is arranged around moving it.

What a buyer of an extension looks at

  • Weekly users and their trend. From the developer dashboard, not the rounded figure on the public listing. Buyers also look at installs against uninstalls.
  • Permissions. What the extension can read and change, and whether each permission is needed for what it does. Broad permissions on a simple tool worry a legitimate buyer and attract the wrong kind.
  • Policy standing. Any warnings, rejected updates or takedowns, and whether the item is currently published without open issues.
  • Technical currency. Which manifest version it is on, and when the last update was accepted by the store.
  • How it earns. Paid plans through your own billing, a licence key, affiliate links. Many extensions have users and no income, which changes how they are priced.
  • Where installs come from. Store search, a website, a single mention somewhere. An extension dependent on one ranking in one store carries platform risk twice over.

What to have ready before listing

  1. Dashboard exports: weekly users, installs, uninstalls and store listing impressions for twelve months.
  2. Revenue from your payment provider for the same period, and your costs.
  3. The source repository, with a build that reproduces exactly the package currently in the store.
  4. A plain-language list of every permission and why it is needed.
  5. The privacy policy, and a statement of what data the extension collects and where it goes.
  6. Store correspondence: review outcomes, warnings, appeals.
  7. A list of everything connected to the item: website and domain, support inbox, backend hosting, analytics, the payment account, any other browser stores where it is published.

Number three is worth testing yourself. If the buyer cannot rebuild the live version from the repository, they cannot safely ship an update. The wider checklist is in what you need before you list.

How the item moves: the Chrome Web Store developer account

This is taken from Google's Chrome Web Store developer documentation, checked on 17 November 2026.

  • An item is transferred to a different developer by submitting a form to Chrome Web Store support. The documentation's page on registering a developer account links to that form.
  • The buyer needs their own Chrome Web Store developer account. Registering one involves a one-time registration fee.
  • A developer account's email address cannot be changed after the account is created. So the route is to move the item to the buyer's account, not to rename yours.
  • Separately, you can share access to items by adding members to the publisher that owns them. That grants access. It is not a change of owner.

We could not confirm on Google's pages how long a transfer takes, what conditions an item has to meet, or exactly what you are asked to confirm, because those details sit on the support form itself. Open the form from the documentation, read its conditions with the buyer, and do not put a completion date in the agreement until you have.

Do not hand over the login to your Google account as a shortcut. It gives the buyer everything else in that account, leaves you named as the developer of an item you no longer control, and is not the route Google documents.

Why this handover needs care

A transferred extension keeps its users, and those users receive whatever the new owner ships next, automatically. That makes an extension unusually sensitive to who buys it. A buyer who intends to add tracking or advertising to an installed base can do real harm to people who trusted you. You are entitled to ask a buyer what they plan to do with it, and to prefer the offer from the one who gives a straight answer.

The rest of the handover is ordinary but easy to forget:

  • Billing. Payment accounts are tied to you. If subscribers pay through your account, ask the provider what its route is for moving them, and start early.
  • Backend and keys. Servers, API keys and OAuth client registrations used by the extension have to move or be reissued, in an order that does not break the live version.
  • Other stores. If the extension is also published for other browsers, each store has its own process. List them all in the transfer schedule.

How pricing is approached

For extensions that make a profit, Indiemaker's guide for SaaS, tools, APIs, browser extensions and mobile apps is 2.7 to 3.2 times trailing annual profit. It is a guide to listing prices, not a valuation.

Take an extension with $15,000 of subscription revenue over the last twelve months and $3,000 of costs for hosting, payment fees and a support tool. Profit is $12,000, and the guide range gives $32,400 to $38,400.

An extension with users and no revenue has no profit to multiply, so no range applies. It is priced on what the users could become, cautiously, and how to value a business with users but no revenue sets out how buyers do it.

How to sell a Chrome extension on Indiemaker

Listings are priced from $1,000 to $500,000. Every published listing has been checked against our listing standards. Connect Stripe, RevenueCat, Paddle, Lemon Squeezy or Polar and your revenue can be shown as Revenue Verified. Figures you type in are owner-declared.

Buyers can open a limited number of listings a month for free, then message you and make an offer from the opened listing. Payment and handover run through Escrow.com, with the buyer's money held until the transfer is done, which matters when the transfer depends on a third party's support queue. You pay a success fee out of the sale and the buyer pays Indiemaker nothing. See /pricing.

When the repository rebuilds the live version and your exports are ready, list your extension.

Sources

Related: platform-risk, transferability, how-to-value-a-business-with-users-but-no-revenue, sell/saas

List it when the numbers are ready.

One form, the same fields every buyer reads, from $1,000 to $500,000.