Launch guideBrowser and IDE extensions
How to launch a Firefox add-on
Firefox add-ons go through addons.mozilla.org (AMO), where you choose between a public listing and self-distribution. Listed add-ons get automated validation and then a manual review before they appear; self-distributed ones are signed after validation for you to host. Firefox users skew toward privacy and control, so a clear, honest permissions story does more for installs than polish.
Updated · platform facts checked against the official docs linked below
At a glance
Where people find Firefox add-ons
- addons.mozilla.org: The main store: search, categories and the Recommended badge.
- Recommended Extensions program: A curated, badged list. You can self-nominate by email.
- Privacy and open-source communities: Firefox users often find add-ons through privacy forums and GitHub.
- Your Chrome audience: If you already have a Chrome version, announce the Firefox port to people who asked for it.
Assets to prepare
| Asset | Spec or guidance |
|---|---|
| Summary | Up to 250 characters, as short as possible.[2] |
| Screenshots | 1280×800 recommended (or a 1.6:1 ratio), each showing one feature.[2] |
| Icon | 32×32 and 64×64 PNG/JPEG, or SVG for clean scaling.[2] |
| Source code archive | Required if your package contains minified, obfuscated or machine-generated code.[1] |
| Privacy policy | Needed if you collect or transmit user data; declared in the submission form. |
Store and listing rules
What the platform itself says, with a link to the page we checked.
- Listed add-ons pass automated validation and then manual review before publication; self-distributed versions are signed automatically after validation.[1]
- Submit source code when your add-on includes code that's hard to read, such as minified or obfuscated code.[1]
- Self-distributed add-ons need
browser_specific_settingswith an update URL in manifest.json.[1] - Recommended status is chosen by Mozilla staff for functionality, safety, user experience and global relevance.[3]
A 4-week launch timeline
Week 1 · four weeks out
- Test the extension in Firefox specifically; APIs differ from Chrome in places.
- Decide listed vs self-distributed.
- Prepare a source archive and build instructions if you minify.
Week 2 · three weeks out
- Write the 250-character summary and a scannable description.
- Make 1280×800 screenshots.
- Submit to AMO.
Week 3 · two weeks out
- Build or update the landing page with a Firefox install button.
- Tell people who asked for a Firefox version.
- Prepare a privacy-focused explanation of permissions.
Week 4 · launch week
- Respond to any reviewer questions quickly.
- Plan a post for privacy-minded communities.
- Set up a way to collect bug reports from Firefox users.
Launch-day checklist
- Confirm the listing is public and the install works on a clean profile.
- Announce to your existing users and the people who requested it.
- Post in relevant communities with a clear list of what data the add-on touches.
- Add the listing to your landing page and LaunchRanked product page.
After launch: SEO steps
Launch boards reset; search pages don't. These steps keep people finding you after launch week.
- Add a "for Firefox" section or page to your site; people search browser-specific terms.
- Link the AMO listing from your site and docs.
- Nominate the add-on for Recommended once it's stable and maintained.
- Keep release notes public; reviewers and users both read them.
Common mistakes
- Submitting minified code without a source archive, which stalls review.
- Assuming Chrome APIs behave the same in Firefox.
- A vague permissions explanation for a privacy-minded audience.
Templates for this launch
- Directory listing descriptionWrite directory and launch-site listings once: a 60-character tagline, a 160-character short description and a long version, with a filled example.
- Release notesRelease notes for a notable launch or version: what's new, why it matters, how to use it, upgrade steps and known issues, with a filled example.
- Changelog entryA changelog entry template grouped by Added, Changed, Fixed and Removed, written for users rather than commit logs, with a filled example.
FAQ
Do I have to list my add-on on AMO?
No. You can self-distribute; Mozilla signs it after automated validation. Listing on AMO adds manual review but gets you store discovery.
When does AMO ask for source code?
When your package includes code that's hard to read, such as minified, obfuscated or machine-generated code. Provide the source and build steps.
What size should Firefox add-on screenshots be?
Mozilla recommends 1280×800, or another size at a 1.6:1 ratio.
How do I get the Recommended badge?
Mozilla staff choose extensions for the program. You can nominate yours, including self-nomination, by emailing the address on the Extension Workshop page.
Sources
- Firefox Extension Workshop: Submitting an add-on
- Firefox Extension Workshop: Create an appealing listing
- Firefox Extension Workshop: Recommended Extensions program
Checked . Platforms change their rules; open the source before you rely on a number.
Related launch guides
- How to launch a Chrome extensionChrome extension launch guide: Web Store image sizes, 132-character summary, review times, single-purpose rule, Edge Add-ons, and SEO beyond the store.
- How to launch an open-source projectLaunch an open-source project: README and repo setup, GitHub topics and social preview, Show HN rules, awesome lists, and docs that rank on Google.
- How to launch a VS Code extensionVS Code extension launch guide: vsce publishing, icon and README rules, 30-keyword limit, pre-releases, Open VSX for other editors, and SEO.
- How to launch a JetBrains pluginJetBrains Marketplace launch guide: upload and approval, name and description rules, 1200×760 screenshots, tags, and how IDE users actually find plugins.