Setting up a Chrome extension developer account takes about ten minutes. The choices you make in those ten minutes can follow you for years, mostly the email address.
It's step one of the Chrome extension development guide.
What a Chrome extension developer account needs
| Requirement | Why it matters |
|---|---|
| A Google account | It becomes your publisher login |
| 2-Step Verification | Required for all developer accounts by store policy |
| A payment method | For the one-time registration fee |
| A supported country | Registration is limited to listed countries and regions |
| An email you check often | Policy and review notices go there |
The setup, step by step
- Open the Chrome Web Store developer dashboard while signed in.
- Read and accept the developer agreement and policies.
- Pay the one-time registration fee.
- Fill in your publisher details and contact email.
Google's register page says that once you've paid and agreed, you won't see the registration screen again. That's the whole process. The rest happens when you add your first item.
Our Developer Tools category page keeps the same counts, each with the day we saw it.
Gotcha 1: the email
Google's own advice is to use a new email account just for publishing. You'll get important alerts there, and you may want to delete a personal account someday without losing your extensions.
Pick the email you'd hand to a buyer if you ever sold the extension. A shared business inbox ages better than a personal address.
Gotcha 2: emails that never arrive
The store's policies say to make sure your publisher account can receive email from outside parties without it being flagged. A review notice sitting in spam can cost you days.
Gotcha 3: 2-Step Verification
It's required, so set it up first. Use an authenticator app or security key you won't lose. Getting locked out of the account that owns your extension is a bad week.
Gotcha 4: personal versus business
Founders often register with a personal account, then form a company later. Think about who should own the listing from day one, especially if you might raise money or sell the product.
After the account exists
You upload a zip, fill in the listing, the privacy tab and distribution, then submit for review. Our development guide walks through those steps, and how long review takes sets your launch date.
We're biased, since Ext Watch helps you research niches before you build. None of that matters until this account is in order, so do it early.
One small step
Write down who should own your extension in two years: you, a company, or a future buyer.
Then choose the email that fits that answer.
Questions people ask
How much does a Chrome developer account cost?
There's a one-time registration fee, paid once. Check the amount on the dashboard's sign-up screen, since we only quote what Google's page shows.
Can I publish a Chrome extension for free?
Not to the public store. Registration needs the fee. You can load extensions unpacked on your own machine for free.
Can I change the developer email later?
Plan as if you can't easily. That's why Google suggests a dedicated email from the start.
Where these numbers come from
- developer.chrome.comRegister your developer account
- developer.chrome.comChrome Web Store program policies
- developer.chrome.comPublish in the Chrome Web Store
Part of our guide: Chrome Extension Development Guide for Founders: 5 Steps. More in Build and launch.
1,182 new extensions in the last 30 days in Developer Tools. See them all.
Start from a niche with proven demand instead of a blank page. Updated 3 Oct 2026 from our Chrome Web Store crawl
