Publishing to the Chrome Web Store in 2026: Fees, Review Times, Limits and Rejections
What it takes to publish a Chrome extension as of November 2026: the $5 fee, 2-Step Verification, new publishing limits, privacy disclosures and common rejection codes.
Building an extension is the fun part. Getting it through the Chrome Web Store is where many first-time developers lose a week. Usually that’s not because the extension is bad. It’s because of a missing privacy disclosure, a permission they didn’t need, or a description that reads like keyword spam.
This is a practical submission checklist, updated with the store changes Google announced during 2026. Policies change often, so every rule below links to the official page. Treat the details as accurate as of November 2026.
Before you start: the account
Register and pay the one-time fee
You need a Chrome Web Store developer account, created from the developer dashboard. Registration costs a one-time $5 fee. There’s no annual renewal.
A few account decisions are hard to undo:
- Use a dedicated email. Google recommends a separate account for publishing, and you can’t change the account’s email later. To move to a new address, you’d have to create a new account and transfer your items.
- Check that your country is supported. Registration is only available in listed countries and regions.
- Turn on 2-Step Verification. It’s required before you can publish or update an item.
Know your publishing limit
In August 2026 Google changed how many extensions one account can publish. New accounts now get a default of two extension slots. The limit grows based on the quality and usage of your published extensions, and you can request an increase from the dashboard (announcement). Existing publishers kept at least as many slots as they had published at the time.
In practice, don’t burn your two slots on throwaway experiments. Test privately first (see below).
Prepare the package
- Manifest V3 only. The store no longer accepts MV2 items, and on August 31, 2026, all remaining MV2 extensions were removed from it.
- Zip the contents, not the folder.
manifest.jsonmust sit at the root of the zip. - No remotely hosted code. All JavaScript must be in the package. Loading a script from your server and executing it is a violation (rejection code Blue Argon). Fetching data such as JSON or config is fine. Fetching code is not.
- No obfuscation. Minification is allowed. Obfuscated code that hides what it does is not (code Red Titanium). If you use a bundler, keep the output readable.
- Request the minimum permissions. Every permission must be needed for the extension’s purpose. Unused or overly broad permissions are among the most common rejections (code Purple Potassium). Prefer
activeTaband optional permissions over<all_urls>. Our permissions guide explains the trade-offs.
Since August 2026, the dashboard also runs automated installation tests as soon as you upload a package to a draft, so broken manifests are caught before you submit.
Write the listing
The listing isn’t decoration. Reviewers check it against the code.
- Single purpose. Every extension must have one narrow, easy-to-understand purpose. “Productivity toolkit with 14 features” invites trouble. “Saves the open tabs in a window as a named session” doesn’t.
- Description that matches behavior. If the code does something the description doesn’t mention, that can count as deceptive behavior (codes Red Nickel, Red Potassium, Red Silicon).
- No keyword stuffing. A description padded with competitor names or long keyword lists breaks the spam and placement policies (code Yellow Argon).
- Complete metadata. Missing icons, screenshots or description, or a blank or broken listing, fail the quality check (code Yellow Zinc).
- Screenshots should show the real extension. Mock-ups of features that don’t exist are a fast way to a rejection.
Fill in the privacy section honestly
The Privacy practices tab is where many rejections come from. You must:
- Justify each permission in a sentence. Be specific: “
tabsis used to read tab titles so users can search their open tabs” beats “required for functionality”. - Declare the data you collect by category (personally identifiable information, web history, user activity, website content and so on). If your extension sends any user data to a server, including analytics, it’s collected.
- Certify the Limited Use rules. You can’t sell user data, use it for advertising unrelated to the extension, or use it to determine creditworthiness.
- Link a privacy policy if you handle user data. It has to be a real page that describes your extension’s practices, not a generic template.
Google tightened two of these rules in a July 2026 policy update, enforced from August 1, 2026 (policy update):
- Any user data you collect must be strictly necessary for the extension’s single, disclosed purpose. Collecting data “because it might be useful” is now explicitly prohibited.
- All data collection must be prominently disclosed to users, even when closely related to the purpose, and you must tell users if your data handling changes after they installed.
The same update added a policy against extensions designed to circumvent safety guardrails or usage restrictions of AI services, and expanded the gambling rules to cover prediction markets. If you’re building an AI-related extension, read those sections carefully.
Test before you go public
You have three visibility options when you submit:
- Public: listed and searchable.
- Unlisted: only people with the link can install it. Useful for beta testers. It still goes through review.
- Private: limited to trusted testers or a Google Workspace domain.
For your very first submission, we recommend a careful private or unlisted release to a few testers, then switching to public once the reviews and crash reports look clean.
Review: how long it takes
Google’s review process page says most extensions are reviewed within a few days, but it can take up to a few weeks. Review times stretched in mid-2026 after a surge in submissions, and Google said in August that it had brought them back to normal levels. Things that tend to slow review down:
- broad host permissions (
<all_urls>), especially combined withwebRequest,debuggerorscripting; - a lot of code changed in a single update;
- being a new developer account with no history.
Updates go through review too. Keeping releases small and permissions stable makes each one faster.
If you’re rejected
The rejection email includes a violation reference ID, the color-and-element codes mentioned above. Look it up on the troubleshooting page. The common ones:
| Code | Meaning | Usual fix |
|---|---|---|
| Purple Potassium | Excessive permissions | Remove unused permissions, narrow host patterns, use activeTab |
| Purple Lithium / Nickel / Copper / Magnesium | User data privacy issues | Fix privacy disclosures, add or repair the privacy policy, handle data securely |
| Yellow Zinc | Missing or poor metadata | Complete the description, icons and screenshots |
| Yellow Argon | Keyword spam | Rewrite the description in plain language |
| Blue Argon | Remotely hosted code (MV3) | Bundle all code. Fetch data, not scripts |
| Red Titanium | Obfuscated code | Ship readable or merely minified code |
| Red Nickel / Potassium / Silicon | Deceptive behavior or misleading listing | Make the listing match the code exactly |
| Grey Titanium | Undisclosed affiliate links or codes | Disclose and get consent for affiliate monetization |
Fix the issue, resubmit and say what you changed in the submission notes. If you believe the reviewer was wrong, use the Appeal button on the item in the dashboard. Google says appeal replies can take up to three days.
For a policy problem in an already-published item, Google usually sends a warning with a deadline, typically between 7 and 30 days depending on the violation, before taking the extension down. Read every email from the store. An ignored warning is the most avoidable takedown there is.
After publishing
- Selling or transferring your extension? Think hard about the buyer. Some of the most damaging 2026 extension incidents happened after ownership transfers, when the new owner pushed malicious updates to existing users. Your users trusted you.
- Respond to reviews. The store’s rating now weighs recent reviews more heavily, so fixing a bug and replying quickly matters more than a big launch.
- Keep your privacy disclosures current. If you add analytics or a server feature, update the privacy tab and tell users. That’s now a requirement, not a courtesy.
- Consider Edge and Firefox. Microsoft Edge Add-ons and Firefox Add-ons have their own (free) developer programs, and a clean MV3 extension usually needs only small changes for each.
The store is stricter than it was a few years ago, and that’s mostly good news for honest developers. If your extension does one thing, asks for little, and says exactly what it does with data, review is usually uneventful.