10+ AI SaaS templates for web & mobile
home

How to Publish a Browser Extension (Chrome, Firefox, Edge)

·9 min read

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:

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 StoreFirefox Add-ons (AMO)Microsoft Edge Add-ons
ReachesChrome, Brave, Opera, Vivaldi, and other Chromium browsersFirefox desktop and AndroidMicrosoft Edge
DashboardDeveloper DashboardDeveloper HubPartner Center
Registration fee$5, one timeNoneNone
Review timeA few days, up to a few weeksUp to 24 hours, longer for manual reviewUp to 7 business days
Screenshots1280×800 (or 640×400), up to 51280×800 recommended1280×800 or 640×480, up to 6
Store-specific requirementPrivacy practices tab, single purposeAdd-on ID, data collection permissions, source code for bundled buildsPer-language description and logo, no "Chrome" branding
Same package as Chrome?—No, separate Firefox buildYes, usually unchanged
Full guideChrome guideFirefox guideEdge 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:

  1. 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.
  2. Bundle all code. Manifest V3 doesn't allow remotely hosted code, and Firefox and Edge apply the same rule.
  3. 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.
  4. Describe one clear purpose. The listing, the single purpose field, and the actual behavior must agree.
  5. 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.
  6. 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.

  1. Register at the Chrome Web Store Developer Dashboard, pay the $5 fee, and turn on 2-Step Verification.
  2. Click Add new item and upload your .zip.
  3. Fill in Store listing, Privacy practices, Distribution, and Test instructions.
  4. 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.

  1. Register in Partner Center with a personal Microsoft or GitHub account. There's no fee.
  2. Click Create new extension and upload the same .zip you sent to Chrome.
  3. Fill in availability, properties, privacy, and a store listing for each language.
  4. 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.

  1. Sign in to the Add-ons Developer Hub with a free Mozilla account.
  2. Add an add-on ID (browser_specific_settings.gecko.id) and, for new add-ons, data_collection_permissions to the manifest.
  3. Test the build from about:debugging, and check its permissions in about:addons.
  4. Upload the Firefox .zip, and a source zip if your build is bundled or minified.
  5. 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:

StoreAPICredentials
ChromeChrome Web Store APIOAuth client ID, client secret, refresh token
FirefoxAMO add-on APIJWT issuer and secret
EdgeEdge Add-ons APIClient 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.yml GitHub Actions workflow that uploads new versions to all three stores with wxt 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

Sounds good?Now let's make it real. In minutes.
Try TurboStarter

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.

world map
Community

Connect with like-minded people

Join our community to get feedback, support, and grow together with 1,000+ builders on board, let's ship it!

Join us

Ship your startup everywhere. In minutes.

Don't burn tokens on setup and start building features on day one.

Get TurboStarter