Sell a Chrome Extension

Extensions sell on installs and weekly active users, and the transfer is easier than most software because Google supports moving an item between publisher accounts.

The catch is policy. An extension that collects data it doesn't declare, or that sits on a review flag, can be delisted after the sale. Buyers check the dashboard before they pay.

What buyers pay

Roughly $0.20 to $2 per weekly active user, more with revenue

Free extensions are priced on active users and how easily they can be monetised. Paid extensions with subscriptions are priced like SaaS, with the same multiples.

Ratings matter. A 4.6 with a thousand reviews sells for more than a 3.9 with the same installs, because the buyer inherits the listing's reputation.

Ranges reflect small-deal marketplaces in 2026 and move with the market. Your buyer decides the price; these numbers tell you where the conversation starts.

Before you list

1. A screenshot of the developer dashboard: installs, weekly users, ratings, and the review status.
2. The manifest permissions and a one-paragraph justification for each, because the buyer will be asked at review.
3. Source repository, build steps and the signing key policy.
4. Revenue export if paid, with the payment provider named.
5. Support channels and how many messages a week they bring.

What moves at closing

The buyer pays Tool Index once you've both signed. Then, in this order:

1. Web Store item transfer to the buyer's publisher account through the developer dashboard.
2. Repository and build pipeline.
3. Backend, domains and any licensing server.
4. Payment provider migration.
5. Support inbox, social accounts, and the privacy policy URL the listing points to.

You mark the deal delivered with a note of what moved. The buyer confirms inside the inspection window and the money is released to you, minus 1 percent (minimum $19, maximum $199) and the card processor's fee. If they open a dispute, a person reviews the delivery evidence before anything moves.

What kills deals

• Permissions the listing does not justify.
• Undeclared data collection or affiliate injection.
• A publisher account that is not the seller's own.
• Installs that came from paid campaigns that stopped.

Questions

Can a Chrome extension really be transferred?

Yes. The developer dashboard supports moving an item to another publisher account. Both sides keep the store listing, reviews and install base.

Firefox and Edge versions?

List them as separate assets with their own store accounts. Each store has its own transfer process and the buyer may not want all of them.

What if the extension is delisted after the sale?

That is exactly what the inspection window is for. Agree a window long enough for the transfer to complete and the listing to stay live, and only confirm delivery once it has.