Skip to content
Ask Claude about any Chrome extension, answered with Ext Watch data. See how →
Build and launch

Chrome Extension Development Guide for Founders: 5 Steps

A Chrome extension development guide for founders: the parts of an extension, Manifest V3, testing, publishing and charging.

By Ext Watch Research4 min read
Pip, the blue bird mascot, wearing a hard hat and fitting the last blue puzzle piece into a stepped block structure on a pale blue background

The short answer

This Chrome extension development guide covers what founders need: an extension is a manifest file plus scripts, built on Manifest V3 with a service worker for background work. You test it unpacked, upload a zip to the developer dashboard, pass review, then sell plans on your own site.

  • An extension is a manifest plus HTML, CSS and JavaScript.
  • Manifest V3 runs background code in a service worker.
  • Ask for the fewest permissions you can.
  • Upload a zip through the developer dashboard.
In this guide10 sections
  1. 01Chrome extension development guide: the parts
  2. 02Step 1: build the smallest version
  3. 03Step 2: ask for less
  4. 04Step 3: test like a user
  5. 05Step 4: package and upload
  6. 06Step 5: charge on your own site
  7. 07Before you write the first line
  8. 08Every guide in this series
  9. 09One small step
  10. 10Questions people ask

This Chrome extension development guide skips the browser-engineer theory. You need to know which pieces exist, which mistakes cost weeks, and where the money comes in.

Chrome extension development guide: the parts

PartWhat it doesFounder note
manifest.jsonNames the extension, lists files and permissionsReviewers read this first
Service workerBackground code that runs only when neededCan't keep state in memory forever
Content scriptRuns inside web pagesBreaks if the site changes its layout
Popup or side panelThe small interface users clickKeep it to one job
Options pageSettingsOften skipped; users notice

Google's docs on Manifest V3 explain that it moved background work to service workers, which run only when needed. Plan for your background code to sleep. Save anything important to storage.

Step 1: build the smallest version

Start with one feature on one site. Load it as an unpacked extension in Chrome's extensions page with developer mode on, as Google's get-started guide shows. Click around until it does that one thing reliably.

For the current numbers, check the Developer Tools category page.

Step 2: ask for less

Permissions shape how users and reviewers see you. A tool that asks to read every site looks scary next to one that asks for a single domain.

Every permission is a question you'll have to answer in review. Request only what the feature needs today.

Step 3: test like a user

  • Fresh Chrome profile, no other extensions.
  • Slow network.
  • The target site logged out, then logged in.
  • An update from the previous version, so saved data survives.

The store's policies say to test for crashes and broken features before submitting. Reviewers may reject items they can't use.

Step 4: package and upload

Zip the folder and upload it in the developer dashboard with Add new item. Google's publish docs list a 2GB maximum package size, though a good extension is a tiny fraction of that.

Then fill in the listing, the privacy tab, and distribution settings. Once it's live, Chrome Web Store SEO decides who finds it, and the publish API can automate later releases. The privacy tab asks you to declare a single purpose and how you handle user data.

Step 5: charge on your own site

Many paid extensions sell plans on their own website, then turn on paid features after sign-in. Our guide to monetizing a Chrome extension compares the options. That's also why store listings so often hide whether a tool charges.

Across the roughly 270,000 extensions in the store, a check of listing text and manifests finds paid evidence in only about 3,000, roughly 1%. We know big paid tools slip past that check, which shows how rarely listings talk about money.

Before you write the first line

  1. Confirm demand: popular tools exist for this job.
  2. Read their reviews for gaps.
  3. Check their pricing pages by hand.

We're biased, since Ext Watch shows step one and parts of step two with dates attached. Step three is always worth doing yourself.

Every guide in this series

This page is the hub for our guides on building and launching. Each one goes deeper on a single step:

One small step

Install a fresh Chrome profile tonight and load a hello-world extension from Google's get-started guide.

Small, working, and on one page: that's the whole recipe.

Questions people ask

How hard is it to build a Chrome extension?

A simple one takes a day if you know JavaScript. A product with accounts and payments takes much longer.

What language are Chrome extensions written in?

JavaScript or TypeScript, with HTML and CSS for any interface.

Do I need Manifest V3?

Yes. Google's docs describe Manifest V3 as the current platform, and new extensions should use it.

Ext Watch logoExt Watch ResearchBuilt from Ext Watch’s own store data
Developer Tools

31,127 extensions tracked in Developer Tools. See them all.

Start from a niche with proven demand instead of a blank page.Store data, updated today

Ask Claude about this dataPlans from $19/mo