How to Build a Chrome Extension and Monetize It: 10 Steps
How to build a Chrome extension step by step: pick a proven idea, code a Manifest V3 MVP, publish it, then charge via Stripe, ExtensionPay or TurboStarter.

Article content
How do you build a Chrome extension that makes money? You write a manifest.json file, add a popup, content script or background service worker, test it with "Load unpacked" in Chrome, and upload a ZIP to the Chrome Web Store. To monetize it, you sell a paid plan through your own checkout, because Google no longer processes payments for extensions. The hard part isn't the code. It's picking a problem people already pay to solve.
This guide walks through all ten steps in order, from idea to first paying customer. Each step links to a deeper tutorial when you need one. For the full technical reference, see our complete guide to building Chrome extensions. For every way to earn money from an extension, see the Chrome extension monetization guide.
The 10 steps at a glance
| Step | What you do | Typical time | Go deeper |
|---|---|---|---|
| 1. Pick a proven problem | Start from an extension people already used | 1–2 days | Chrome extension ideas |
| 2. Validate demand | Get signups or pre-orders before coding | 2–5 days | Validate an idea |
| 3. Choose your stack | Plain JavaScript, WXT or a starter kit | 1 hour | Code structure |
| 4. Write the manifest | Declare name, version, permissions and UI | 30 minutes | Manifest V3 guide |
| 5. Build the core feature | Popup, content script, service worker, storage | 1–3 weekends | Content scripts |
| 6. Test locally | Load unpacked and fix errors | 1 day | Error handling |
| 7. Publish | Developer account, privacy policy, listing, review | A few days | Chrome Web Store ASO |
| 8. Pick a pricing model | Freemium, subscription or one-time | 1 hour | Pricing strategy |
| 9. Add payments | ExtensionPay, Stripe or a starter kit | Hours to days | Stripe payment guide |
| 10. Measure and grow | Track conversion, raise prices, listen to reviews | Ongoing | Revenue benchmarks |
Times are rough estimates for a solo builder with a small MVP, not guarantees.
Part 1: Build the extension
Step 1: Pick a problem people already paid attention to
Most first extensions fail because nobody needed them, not because the code was bad. The safest starting point is an extension that already had users and then disappeared: shut down, removed from the Chrome Web Store or broken by Manifest V3. Its users still have the problem and often search for an "[old name] alternative".
Our list of 10 real Chrome extension ideas from dead extensions shows this pattern with Pocket, The Great Suspender and others, each with a rebuild plan. If you want something small for a first project, start with our easy Chrome extension ideas. For a structured way to compare candidates, use the decision framework for which expired extension to rebuild.
Be honest with yourself about one thing: you can't take over an old extension's installs, reviews or ratings. They stay with the removed listing. What carries over is the proof that people wanted the tool. You start at zero installs, not zero demand.
Step 2: Validate demand before you write code
Spend a few days checking that people will pay before you spend weekends building. Read the old extension's last reviews and Reddit threads, put up a one-page site describing the replacement, and ask for an email or a pre-order. Our guide to validating an extension idea gives a step-by-step checklist, and finding ideas on Reddit shows where those complaints live.
To collect those first emails, a simple form connected to MailerLite is enough. You don't need a full product yet.
Step 3: Choose your stack
A Chrome extension is just HTML, CSS and JavaScript plus a manifest file. You can build one with no framework at all. The question is how much you want to write yourself once you add accounts and payments.
| Option | Best for | What you still build yourself |
|---|---|---|
| Plain HTML, CSS and JavaScript | Learning, or a tiny free tool | Everything: build setup, accounts, payments, backend |
| WXT (open-source framework) | Most new extensions, with React, Vue or Svelte | Accounts, payments and any backend |
| TurboStarter (paid starter kit) | Paid extensions that need logins and billing | Your core feature and your listing |
TurboStarter is a paid starter kit whose Core Kit includes a browser-extension boilerplate built on WXT, next to a web app and a mobile app that share one backend. According to its own documentation, the extension stays thin: sign-in and checkout run on the web app, and the extension reads the same session and billing status to unlock paid features. Billing providers listed on its pricing page include Stripe, Lemon Squeezy, Polar and Dodo Payments. It's sold as a one-time lifetime licence rather than a subscription (checked November 21, 2026; prices change, so check the current offer).
If you plan to charge from day one, that saves you the part of an extension that takes longest and breaks most often: accounts, checkout and checking who has paid. If you're building a free tool or just learning, start with WXT or plain JavaScript instead. Our Chrome extension code structure guide shows a clean WXT folder layout either way.
Prefer to describe the extension and let AI write it? Our vibe coding guide for Chrome extensions covers prompting tools like Cursor to produce Manifest V3 code.
Step 4: Write the manifest
Every extension starts with a manifest.json file in its root folder. It tells Chrome the name, version and what the extension is allowed to do. This minimal Manifest V3 example adds a toolbar button with a popup and a background service worker, based on Google's Hello World tutorial:
{
"manifest_version": 3,
"name": "Reading Mode Lite",
"version": "1.0.0",
"description": "Turn any article into a clean, readable page.",
"action": { "default_popup": "popup.html" },
"background": { "service_worker": "service-worker.js" },
"permissions": ["activeTab", "scripting", "storage"]
}Use Manifest V3. On August 31, 2026, Google removed all remaining Manifest V2 extensions from the Chrome Web Store, so any tutorial still says "manifest_version": 2 is out of date. Our Manifest V2 replacement guide explains the differences and the full timeline.
Ask for as few permissions as possible. The activeTab permission gives temporary access to the current tab only when the user clicks your extension, which avoids the scary "read and change all your data on all websites" warning. Fewer warnings mean more installs and an easier review.
Step 5: Build the one feature people install it for
Most extensions combine four building blocks. Use only the ones your feature needs:
- Popup: the small window that opens from the toolbar icon. Good for settings and quick actions.
- Content script: code that runs inside web pages to read or change them. See our content scripts tutorial.
- Service worker: the background script that reacts to events. It shuts down when idle, so don't keep state in variables. Our service worker guide shows what to do instead.
- Storage: chrome.storage saves settings and data. Our storage API guide explains local, sync and session storage.
When these parts need to talk to each other, use message passing. Keep the first version to the single feature that most reviews of the old extension mentioned. Everything else can wait until someone pays.
Step 6: Test it locally
Open chrome://extensions, switch on Developer mode, click Load unpacked and select your project folder. Your extension now runs in your own browser. After each change, click the reload icon on its card. Check the service worker's console from the same page, and the page console for content-script errors. Our Chrome extension error handling guide covers the bugs that show up most in Manifest V3.
Part 2: Publish on the Chrome Web Store
Step 7: Register, write a privacy policy and submit
- Register a developer account. Google asks for a one-time registration fee and a developer email you'll actually read.
- Write a privacy policy. If your extension handles any user data, the Chrome Web Store program policies require you to disclose it. Our Chrome extension terms of service guide explains what to include.
- Upload a ZIP of your extension in the developer dashboard, then fill in the listing: description, screenshots, category and the purpose of each permission. Google's publishing guide lists every field.
- Wait for review. Google says most reviews finish within a few days but can take up to a few weeks. Broad permissions tend to slow it down.
Your listing is also your main sales page. Write the title and first lines around what people search for. Our Chrome Web Store ASO guide covers titles, screenshots and keywords, and Chrome extension internationalization helps you reach more countries.
Part 3: Monetize the extension
One fact shapes everything here: the Chrome Web Store doesn't handle payments any more. Google deprecated Chrome Web Store payments in 2020 and told developers to move to another payment processor and their own way of tracking licences. So you need your own checkout and your own check for who has paid.
Step 8: Pick a pricing model
| Model | How it works | Fits | Read more |
|---|---|---|---|
| Freemium | Core feature free, extras paid | Tools with a big free audience | Freemium guide |
| Subscription | Monthly or yearly plan | Features with ongoing value, like sync or AI | Pricing strategy |
| One-time Pro unlock | Pay once, keep Pro forever | Simple utilities with no server costs | Lifetime deals |
| Per-seat B2B | Price per team member | Sales, support and workflow tools | Pricing strategy |
| Affiliate or sponsorship | Earn from partners, not users | Free tools with many users | Affiliate marketing |
For most first paid extensions, freemium with a small paid tier is the simplest test: it keeps installs growing while showing whether anyone will pay. If your extension depends on a platform such as Gmail or LinkedIn, also read that platform's terms before you charge.
Step 9: Add payments and unlock paid features
There are three practical routes. Pick by how much you want to own:
- ExtensionPay: an open-source service built for extensions. You add a small library, and it handles checkout and checking who has paid through your Stripe account. On November 21, 2026, its site listed no monthly fee and a 5% fee per transaction, on top of Stripe's own fees. Fastest to set up.
- Your own Stripe setup: the most control and the lowest fees per sale, but you build a small backend for checkout, webhooks and checking who has paid. Our Stripe payment guide for Chrome extensions walks through it and compares it with ExtensionPay.
- A starter kit: TurboStarter's extension kit ships accounts, a web checkout and billing status that the extension reads, so you skip building that backend yourself. If you'd rather use a hosted platform for logins, payments and customer emails, Outseta covers those in one place.
Whatever you pick, follow one rule: never put secret payment keys inside the extension. Anyone can open an extension's files. Keep secret keys on a server, and have the extension ask that server whether the current user has paid.
Step 10: Measure, price up and grow
Watch three numbers: weekly active users, the share who upgrade, and how many paid users cancel each month. Here is illustrative math, not anyone's reported earnings: 2,000 weekly active users × 2% upgrading × $5 a month = $200 a month. Raising the price to $8, or doubling the upgrade rate with a better paywall, moves that number more than chasing installs.
See what real extensions earn at different user counts in our Chrome extension revenue benchmarks, or plug in your own numbers with the free Chrome extension revenue calculator. Later, a profitable extension can also be sold: our guide on how to sell a Chrome extension explains prices and buyers.
Five mistakes that cost first-time builders money
- Building before validating. A landing page and ten emails beat a finished extension nobody asked for.
- Asking for every permission. Broad access scares users and slows review. Start with activeTab.
- Adding payments last. Plan your paid feature and checkout before launch, or you'll train users to expect everything free.
- Keeping secrets in the extension. Payment keys and paid-status checks belong on a server.
- Copying the old extension's name or logo. Rebuild the idea with your own name, design and code.
Your next step
Step 1 is where most of the risk sits, so start there. The Chrome Goldmine database lists 9,656 expired Chrome extensions with 15 data points each, including the user count when it was removed, why it died, rebuild difficulty, a Rebuild Score, monetization potential and a conservative revenue range. Browse 20 free sample rows or follow the Start Here path from idea to launch. Every purchase comes with a [object Object].
Sources checked November 21, 2026: Google's Chrome for Developers documentation (Hello World tutorial, activeTab, registration, publishing, review process and program policies), Google's Chrome Web Store payments deprecation notice, and the official ExtensionPay, WXT and TurboStarter sites. Links to TurboStarter, MailerLite, Cursor and Outseta are affiliate links; we may earn a commission at no extra cost to you.


