Where we list / Listing guides
How to publish your extension on the Chrome Web Store
You register a developer account in the Chrome Developer Dashboard, pay a one-time $5 registration fee, upload your extension as a zip, and fill in the Store listing, Privacy and Distribution tabs before you submit it for review. Google says most items are reviewed within a few days, but some reviews take a few weeks. If you defer publishing, you have 30 days after approval to make the item live.
Checked on Chrome Web Store's own pages on 2026-11-12.
| Cost | One-time $5 developer registration fee (Chromium blog). Publishing items after that costs nothing. |
|---|---|
| Who can submit | Developers in a supported country or region with a Google account. New publishers can publish up to two extensions at first (themes are not limited) and can ask for more. |
| Review | Google's review team. Most items take a few days, some take up to a few weeks. Contact support if an item is pending for more than three weeks. |
| Fits | Chrome extensions and Chrome themes: productivity tools, AI helpers, developer tools, shopping and writing assistants, and companion extensions for SaaS products. |
| Time needed | 2 to 4 hours to prepare the package, images and privacy answers, then a few days to a few weeks of review. |
Before you start
- A Google account with an email you will keep for good. The developer email cannot be changed after registration, so a dedicated publishing address is safer.
- A zip file with a valid manifest. The manifest name can be up to 75 characters and the manifest description up to 132 characters; both appear on your listing.
- A 128 x 128 px store icon and at least one 1280 x 800 px screenshot (up to five).
- Optional promo art: a 440 x 280 px small promo tile and a 1400 x 560 px marquee tile, PNG or JPEG.
- A short single-purpose statement, a reason for every permission you request, and a working privacy policy URL if you handle any user data.
- Test account details and steps if reviewers need to log in to see your features.
- Your website verified in Google Search Console if you want it shown as the Official URL.
How to list on Chrome Web Store, step by step
Register as a developer
Open the Chrome Developer Dashboard, sign in, accept the developer agreement and policies, and pay the one-time fee. Turn on email alerts for staged and reviewed items on the Account page so you see every status change.
Upload your zip
Click Add new item and choose your zip. If the manifest and zip are valid, the item opens for editing. The package can be up to 2 GB.
Fill in the Store listing tab
Write the detailed description, pick one primary category and the language, then add the icon, screenshots, optional promo tiles and an optional YouTube video. Add homepage and support URLs so users can reach you.
Complete the Privacy tab
State the single purpose of the extension, justify each permission, and declare how you collect and use data. Add your privacy policy link here; a missing or broken link is a common rejection.
Set Distribution and test instructions
Choose where the item is listed, who can see it, and whether it is paid. In Test instructions, give reviewers credentials and the exact steps to reach gated features.
Submit and choose when to publish
Click Submit for Review. In the dialog you can untick automatic publishing so you control launch day. A deferred item must be published within 30 days of approval or it goes back to draft.
Watch for the result
If a policy issue is found, you get an email naming the violation. Fix it, upload a new package and resubmit. Warnings on a live item usually give you 7 to 30 days to fix it before takedown.
What the Chrome Web Store form asks for
| Field | Limit | Tip |
|---|---|---|
| Name (from manifest) | 75 characters | Lead with what the extension does, not a slogan, because users search for the task. |
| Summary (manifest description) | 132 characters | One plain sentence on the main job of the extension; edit it in the manifest and re-upload to change it. |
| Description | – | Open with a short statement of what the item does, then list features; never paste long keyword lists. |
| Category | – | Pick the one category where a user would look first. |
| Language | – | Set it correctly so people searching in that language can find you. |
| Store icon | 128 x 128 px | Keep it readable at small sizes and close to the icon inside the extension. |
| Screenshots | 1280 x 800 px, 1 to 5 | Show the extension working on a real page rather than a logo slide. |
| YouTube video | – | A short screen recording of the main flow helps users who scan quickly. |
| Small promo tile | 440 x 280 px, PNG or JPEG | Use bold, simple artwork; it cannot be localized. |
| Marquee promo tile | 1400 x 560 px, PNG or JPEG | Optional, but needed if you hope to be featured in a large slot. |
| Official URL | – | Only sites you verified in Search Console appear in this dropdown. |
| Homepage URL / Support URL | – | Point support to a page or form you actually monitor. |
| Mature content | – | Tick it if the content is not suitable for all ages; mature items are hidden from logged-out search. |
| Single purpose / Permission justification / Privacy policy | – | Make these match the code exactly; mismatches lead to rejection. |
| Test instructions | – | Give a working test login and a numbered path to every gated feature. |
Why submissions get rejected
- Remotely hosted code in a Manifest V3 extension (Blue Argon).
- The extension does not work as described, or files are missing or misnamed (Yellow Magnesium).
- Permissions requested but not used (Purple Potassium).
- Missing or misleading icon, title, screenshots or description (Yellow Zinc).
- No working privacy policy link when user data is collected (Purple Lithium), or data collected without clear disclosure and consent (Purple Nickel).
- Keyword spam in the description, such as long lists of sites (Yellow Argon).
- Obfuscated code (Red Titanium) or several unrelated purposes bundled in one item.
- An extension that only opens a website or another app (Yellow Lithium), or offers no real functionality (Yellow Potassium).
- Undisclosed affiliate links or codes (Grey Titanium).
Tips that make a difference
- Broad host permissions such as all URLs, sensitive permissions and large or minified code all trigger closer review, so ask only for what you need.
- New developers and new extensions get extra scrutiny, so plan your launch date with a few weeks of buffer.
- Use deferred publishing to line up the store release with your own announcement.
- If you spot a bug after submitting, cancel the review, upload a fixed package and resubmit instead of waiting.
- Localize the description, screenshots and video for each locale you support; the promo tiles stay the same in every language.
- Rejection emails do not change your live listing, so an update can be rejected while users keep the old version.
Example: what JustLaunched prepared
These are the texts Pushify prepared for JustLaunched, a real brand, before listing it on sites like Chrome Web Store. See the full sample report ›
| Name | JustLaunched |
|---|---|
| Tagline | Launch board for founders and early adopters |
| Short description | JustLaunched is a free launch board where founders introduce new products and early adopters try them first, ask questions and share feedback. |
| Tags | product launch, launch platform, startup discovery, indie makers, early adopters, beta testers, launch deals, product hunt alternative, saas, startups |
Questions people ask
Is it free to publish on the Chrome Web Store?
There is a one-time $5 registration fee for a developer account. After that, publishing and updating items does not cost anything.
How long does Chrome Web Store review take?
Google says most extensions are reviewed within a few days, but some take up to a few weeks. New accounts, broad permissions and big code changes can make it slower.
How many extensions can a new developer publish?
New publishers can publish up to two extensions at first. You can request a higher limit from the dashboard; themes do not count toward it.
Can I choose the exact day my extension goes live?
Yes. Untick automatic publishing when you submit, then publish manually after approval. You must do it within 30 days or the submission returns to draft.
What happens if my extension is rejected?
You get an email naming the policy that was broken. Fix the issue and submit again; reviews after a rejection can take longer than usual.
Can I change my developer email later?
No. The email set at registration cannot be changed, so choose an address you will keep.
Sources
The Chrome Web Store pages this guide was checked against.
- developer.chrome.com/docs/webstore/register
- developer.chrome.com/docs/webstore/publish
- developer.chrome.com/docs/webstore/cws-dashboard-listing
- developer.chrome.com/docs/webstore/review-process
- developer.chrome.com/docs/webstore/troubleshooting
- developer.chrome.com/docs/extensions/reference/manifest/name
- developer.chrome.com/docs/extensions/reference/manifest/description
- blog.chromium.org/2020/03/new-developer-dashboard-and.html