How to Publish a Browser Extension (Chrome, Firefox, Edge)
How to publish a browser extension to the Chrome Web Store, Firefox Add-ons, and Microsoft Edge Add-ons: fees, review times, assets, rejections, and automation.

To publish a browser extension to most users, you publish it three times: on the Chrome Web Store, on Firefox Add-ons, and on Microsoft Edge Add-ons. Each store has its own account, listing, review, and rules. The code can be the same. The release process can't.
This post compares the three stores side by side and shows the order that saves the most time. For the click-by-click steps, each store has its own guide in the TurboStarter docs:
- Chrome Web Store Developer Dashboard: publish your extension
- Publish a Firefox extension on addons.mozilla.org
- Microsoft Edge Add-ons: publish your extension in Partner Center
Short answer
Build one Manifest V3 extension, then register a developer account on each store: Chrome ($5 one-time), Firefox (free), and Edge (free). Upload a .zip with manifest.json at the root, fill in the listing, privacy answers, and screenshots, and submit for review. Chrome usually reviews in a few days, Firefox signs within 24 hours in most cases, and Edge certifies within seven business days. The first upload on every store is manual. After that, you can release updates from CI.
The three stores at a glance
| Chrome Web Store | Firefox Add-ons (AMO) | Microsoft Edge Add-ons | |
|---|---|---|---|
| Reaches | Chrome, Brave, Opera, Vivaldi, and other Chromium browsers | Firefox desktop and Android | Microsoft Edge |
| Dashboard | Developer Dashboard | Developer Hub | Partner Center |
| Registration fee | $5, one time | None | None |
| Review time | A few days, up to a few weeks | Up to 24 hours, longer for manual review | Up to 7 business days |
| Screenshots | 1280×800 (or 640×400), up to 5 | 1280×800 recommended | 1280×800 or 640×480, up to 6 |
| Store-specific requirement | Privacy practices tab, single purpose | Add-on ID, data collection permissions, source code for bundled builds | Per-language description and logo, no "Chrome" branding |
| Same package as Chrome? | — | No, separate Firefox build | Yes, usually unchanged |
| Full guide | Chrome guide | Firefox guide | Edge guide |
Chrome is the one that matters most for reach, and it has the only fee. Firefox asks the most of your build. Edge is the cheapest win: it usually takes your Chrome package as is.
Before you submit anywhere
Every store rejects extensions for the same few reasons, so fix these once before the first upload:
- Request only the permissions you use. Broad host access like
<all_urls>slows review on every store. Scope permissions to features, as in TurboStarter's permissions guide. - Bundle all code. Manifest V3 doesn't allow remotely hosted code, and Firefox and Edge apply the same rule.
- Write a privacy policy that matches the code. Every store asks what data you collect. If your answers, your policy, and the network traffic don't agree, review fails.
- Describe one clear purpose. The listing, the single purpose field, and the actual behavior must agree.
- Give reviewers a way in. If the extension needs a login, add a test account and steps. A SaaS extension that signs in through your web app can't be tested otherwise.
- Take real screenshots. Show the popup, side panel, or in-page UI at 1280×800. That size works on all three stores.
TurboStarter's pre-publishing checklist covers the rest, from the production API URL to store assets.
Step 1: Publish to the Chrome Web Store
Start with Chrome. It has the most users, the longest review, and the fee, so you want it in the queue first.
- Register at the Chrome Web Store Developer Dashboard, pay the $5 fee, and turn on 2-Step Verification.
- Click Add new item and upload your
.zip. - Fill in Store listing, Privacy practices, Distribution, and Test instructions.
- Click Submit for review.
The Privacy practices tab is where most Chrome rejections start: every permission needs a justification, and the data use answers must match your policy. New publishers can also have only two published extensions until they ask for more.
Full walkthrough: Chrome Web Store Developer Dashboard guide. For a tour of the dashboard itself, see Chrome Web Store developer dashboard: setup guide.
Step 2: Publish to Microsoft Edge Add-ons
Edge comes second because it reuses almost everything from Chrome: the package, the screenshots, and most of the privacy answers.
- Register in Partner Center with a personal Microsoft or GitHub account. There's no fee.
- Click Create new extension and upload the same
.zipyou sent to Chrome. - Fill in availability, properties, privacy, and a store listing for each language.
- Add notes for certification and click Publish.
Remove "Chrome" from the name, description, and screenshots first. It's the most common Edge-only rejection. Certification takes up to seven business days, so start it early.
Full walkthrough: Microsoft Edge Add-ons guide.
Step 3: Publish to Firefox Add-ons
Firefox takes the most build work, but its review is the fastest.
- Sign in to the Add-ons Developer Hub with a free Mozilla account.
- Add an add-on ID (
browser_specific_settings.gecko.id) and, for new add-ons,data_collection_permissionsto the manifest. - Test the build from
about:debugging, and check its permissions inabout:addons. - Upload the Firefox
.zip, and a source zip if your build is bundled or minified. - Fill in the listing and submit.
Release versions of Firefox install only signed add-ons, so even a private build has to go through AMO. Choose On your own to have it signed without a public listing.
Full walkthrough: Firefox Add-ons guide.
What about Safari and Opera?
Opera installs extensions from the Chrome Web Store, so most Opera users are covered by your Chrome listing. Opera also runs its own add-ons store if you want a separate listing.
Safari is a different process. You package the extension inside a macOS or iOS app with Xcode, distribute it through the App Store, and need a paid Apple Developer Program membership. It's worth it if your users are mostly on Safari, but plan it as a separate project.
Automate releases after the first upload
On all three stores, the first submission has to be manual. The stores assign the extension ID during that upload, and some listing fields can only be filled in through the dashboard. After that, each store has an API for new versions:
| Store | API | Credentials |
|---|---|---|
| Chrome | Chrome Web Store API | OAuth client ID, client secret, refresh token |
| Firefox | AMO add-on API | JWT issuer and secret |
| Edge | Edge Add-ons API | Client ID and API key |
wxt submit calls all three from one command. A typical release then looks like this: bump the version, build, upload to every store, and send each to review.
Automation only uploads and submits. If an update adds a permission or changes what data you collect, update the privacy answers in each dashboard by hand before the review, or it will fail.
How TurboStarter fits in
TurboStarter Core is a SaaS starter kit with a web app, a mobile app, and a browser extension that share one backend and one sign-in. The extension is built with WXT, so the same code produces a Chrome and Edge package and a Firefox package.
For publishing, the kit includes:
- Store-ready builds for Chrome, Firefox, and Edge.
- A
publish-extension.ymlGitHub Actions workflow that uploads new versions to all three stores withwxt submit. - Step-by-step Chrome, Firefox, and Edge guides, a pre-publishing checklist, and an updates guide.
- Extension auth that signs users in through your web app, plus scoped permissions to keep reviews short.
If you're comparing options, see the WXT + Vite extension stack or the Chrome, Firefox, and Edge extension starter kit.
FAQ
$5 in total for the three main stores. The Chrome Web Store charges a one-time $5 registration fee. Firefox Add-ons and Microsoft Edge Add-ons are free. Safari is the exception: it needs a paid Apple Developer Program membership.
Plan for about a week across all three stores. Chrome usually reviews in a few days but can take a few weeks. Firefox signs most add-ons within 24 hours. Edge certification takes up to seven business days.
The same code, yes. Chrome and Edge can usually share one package. Firefox needs its own build with an add-on ID and data collection permissions. A framework like WXT builds all of them from one codebase.
Chrome. It has the most users and the longest review, so it should be in the queue first. Then Edge, which reuses your Chrome package, and Firefox, which needs a separate build.
On every store, the main reasons are permissions you don't use or don't justify, privacy answers that don't match the code, remote code, a listing that doesn't match what the extension does, and reviewers who can't log in to test it.
Yes, after the first manual upload on each store. Chrome, Firefox, and Edge all have APIs for new versions, and wxt submit calls them in one command from CI.
Takeaway
Publishing a browser extension means three reviews, not one. Fix permissions, privacy answers, and screenshots once. Submit to Chrome first, Edge second with the same package, and Firefox third with its own build. After the first approval on each store, release updates from CI. The store guides for Chrome, Firefox, and Edge have every step.
How to build multi-tenant SaaS - complete guide
How to build multi-tenant SaaS: pick shared DB + org_id, wire auth, RBAC, billing, and isolation. Decision table, steps, and when a starter wins.
Introducing Edge Kit: TanStack Start SaaS starter for Cloudflare
Edge Kit is a TanStack Start SaaS starter kit for Cloudflare Workers, with auth, Stripe billing, D1, R2, Queues, email, and AI deployed as one Worker.



