Building an extension is only half of the job. To let other people install it, you publish it in the Chrome Web Store. This guide collects the main steps from Google's documentation. Some of Google's pages are several years old, so check the current rules in the dashboard before you submit.
1. Register as a developer
You register a Chrome Web Store developer account and pay a one-time registration fee before you can publish. You accept the developer agreement during registration (Register your developer account). Google's pages we found do not state the fee amount, so look at the dashboard for the current figure.
Two rules to know about:
- You must turn on 2-step verification on the Google Account you use to publish or update an extension.
- A new publisher is limited to a maximum of two published extensions at first (Publish in the Chrome Web Store).
2. Prepare your extension
Make sure it uses Manifest V3 (the Chrome Web Store no longer accepts Manifest V2) and that you have tested it using Load unpacked (see how to build a Chrome extension). Then create a ZIP file of the extension's folder, as described in Prepare your extension.
3. Fill in the store listing and privacy tabs
The Store Listing and Privacy tabs must be completed before a new item can be published. An item with an empty description, or without an icon or screenshots, will be rejected. Misleading, inaccurate or non-descriptive information is also not allowed (Listing requirements).
The answers you give in the privacy fields must match your privacy policy and what the extension actually does. If they do not, the extension may be removed.
4. Choose who can see it
You can publish an extension as public, unlisted or private. All three go through the same review and policy requirements (Publish in the Chrome Web Store).
5. Submit and wait for review
Google says most extensions are reviewed within three days, and that a review can take up to a few weeks. Extensions that ask for broad host permissions or sensitive permissions, or that contain a lot of code or code that is hard to review, tend to take longer (Chrome Web Store review process).
Other points from the same guide:
- You should get an email with the result, usually within about three days. If you hear nothing in a week, check the status in the dashboard.
- If a review is pending for too long, you can contact developer support. Google's pages give two weeks in one place and three weeks in another.
- If you choose to publish manually, a staged approved item reverts to a draft after 30 days if you do not publish it (Publish in the Chrome Web Store).
A short checklist
- Developer account registered and fee paid
- 2-step verification on
- Manifest V3, tested locally
- Clear name and description, icon and screenshots
- Privacy answers match your privacy policy
- Only the permissions you really need
Need help with the listing?
We prepare and submit store listings as part of our browser extension work. You can add "Store listing help" in our estimate tool, or send us a brief. Consultation is free.
