The short answer
Sign in to the developer dashboard with a Google account, accept the agreement, and pay a one-time registration fee. That's how you get a Chrome extension developer account. Google requires 2-Step Verification on developer accounts and suggests a separate email just for publishing.
- Register through the Chrome Web Store developer dashboard.
- A one-time registration fee applies; the dashboard shows the amount.
- 2-Step Verification is required on all developer accounts.
- Google suggests a dedicated email for publishing.
In this guide17 sections
- 01What a Chrome extension developer account needs
- 02The setup, step by step
- 03Gotcha 1: the email
- 04Gotcha 2: emails that never arrive
- 05Gotcha 3: 2-Step Verification
- 06Gotcha 4: personal versus business
- 07After the account exists
- 08Group publishing for teams
- 09Trader details and contact info
- 10What to prepare before your first item
- 11Keep the account secure
- 12How crowded the store is
- 13Account mistakes that cost the most
- 14If you lose access
- 15Planning for a future sale or team
- 16One small step
- 17Questions people ask
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.
Group publishing for teams
If more than one person will manage your extensions, don't share a single login. Google supports group publishers, which lets a team share access to items. The register docs and dashboard explain the current setup.
| Setup | Good for | Risk |
|---|---|---|
| Personal account | Solo hobby projects | Hard to hand over later |
| Dedicated publishing account | Solo founders | One person holds the keys |
| Group publisher | Teams and companies | Needs care with who's added |
Even solo founders benefit from thinking about this early. A company that grows, raises money or sells a product will want the listing under a business, not one person.
Trader details and contact info
Depending on where you are and whether you charge, the store may ask for trader details, such as a business name, address and contact information, shown to users. Rules differ by region, so check the dashboard's account section.
Have these ready before you start, so the first submission isn't held up by paperwork:
- A public contact email you're happy to show.
- A business address, if you're registering as a trader.
- A support page or site, linked from the listing.
What to prepare before your first item
The account is quick. The first item takes longer. Collect these first.
- A zip of your extensionthat loads cleanly as unpacked.
- An iconat 128 pixels, plus the smaller sizes.
- Screenshotsof the tool working.
- A short summarythat names one job.
- A privacy policy URL, if you handle any user data.
- A justificationfor each permission.
With these ready, the listing form takes under an hour. Our guide to review timing covers what happens after you click submit.
Keep the account secure
The account that owns your extension is a target. If someone takes it over, they can push an update to every user.
- Use a security key or app for 2-Step Verification.
- Keep recovery codes somewhere safe and offline.
- Don't reuse the password anywhere else.
- Review who has access each quarter if you use a group.
Extension takeovers have happened, and users rarely know until something odd ships. Our guide to ownership changes shows how sudden changes look from outside.
How crowded the store is
You'll join a big field. The store's roughly 270,000 extensions come from about 185,000 publishers. About 8 in 10 publishers have a single extension. You can browse the biggest group of tools on the Developer Tools category page.
Account mistakes that cost the most
A few setup choices cause trouble years later. Here's what to avoid.
| Mistake | What happens later | Better choice |
|---|---|---|
| Personal Gmail as publisher | Hard to hand over or sell | A dedicated publishing account |
| No 2-Step Verification backup | Lockout if you lose your phone | Save recovery codes offline |
| A freelancer's account | They hold your listing | Create it yourself, then invite |
| Spam-filtered inbox | Missed review notices | Test the inbox first |
Each fix takes minutes on day one and saves a painful week later.
If you lose access
Getting locked out of the publisher account is stressful. A few steps help.
- Try account recoverywith your recovery codes or backup method.
- Contact developer supportthrough the store's help pages.
- Don't create a new listingfor the same extension, which can look like spam.
- Tell usersthrough your website if updates will be delayed.
Prevention is far easier. Store recovery codes somewhere safe today.
Planning for a future sale or team
Even if you're solo now, set things up as if someone else might join or buy. Use a dedicated email, keep a list of every account the product needs, and note who owns each one. Our guide to selling a Chrome extension shows why buyers ask for exactly this.
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.
Can more than one person manage the same extensions?
Yes. Google supports group publishers, so a team can share access to items without sharing one login. Check the dashboard for the current setup.
How many developers publish on the Chrome Web Store?
The store's roughly 270,000 extensions come from about 185,000 publishers. About 8 in 10 publishers have a single extension.
31,198 extensions tracked in Developer Tools. See them all.
Start from a niche with proven demand instead of a blank page.Store data, updated today



