Stores & marketplaces

Firefox Add-ons

Smaller store with loyal, privacy-minded users.

Visit addons.mozilla.org
Cost
Free

Free to use. No paid tier is needed to list or post.

Verdict
slow burn

Slow burn: a smaller store with loyal, privacy-minded users.

Difficulty
Easy

Mostly self-serve. Sign up and post, with light checks.

Effort
Low

About 2 to 4 hours a month.

First result
1 to 2 weeks

A rough range for one person working on it part-time.

Payoff
Compounds

keeps growing while you keep at it.

Best for

Privacy-focused extensions.

Not for

Products aimed at mass consumer audiences.

Pros

  • Loyal, privacy-minded users
  • Free

Cons

  • Small audience
  • Separate build and review

The full guide

Last verified 2026-10-30

Links checked 2026-10-30 · All links answer

01What it is and who is there

Firefox Add-ons (addons.mozilla.org) is Mozilla's store for Firefox extensions. Its users tend to care about privacy and open software, and they are loyal to tools that respect them. It is a smaller audience than Chrome, but often a good fit for privacy and developer tools.

02Cost and what you actually pay for

Publishing is free. Your cost is adapting your extension to Firefox, if needed, and passing review.

03Is it right for you?

It fits privacy-focused tools, developer tools and productivity extensions. It fits poorly for mass consumer reach, and for extensions that rely on Chrome-only features. Firefox uses the WebExtensions API, so many Chrome extensions port with small changes.

04Before you start

  • A Firefox account and a developer profile on addons.mozilla.org.
  • Your extension tested in Firefox.
  • Read Mozilla's add-on policies, including rules on data collection and source code review.
  • A privacy policy that matches what the extension does.

05Step-by-step: how to distribute here

  1. Test the extension in Firefox and fix differences.
  2. Submit it, with source code if Mozilla's rules require it for minified code.
  3. Write a listing focused on what the extension does and what data it touches.
  4. Respond to reviewer feedback.
  5. Link the Firefox listing from your site.
  6. Keep it updated with each release.

06What to post or submit

Summary:

[Product] [does job] in Firefox. No tracking; [data stays local / what it sends]. Open source: [yes/no].

07Common mistakes and do-nots

  • Do not collect data without clear disclosure.
  • Do not submit minified code without what review requires.
  • Do not let the Firefox version lag behind.

08How to measure it

  • Track daily users and installs in the developer hub.
  • Track reviews and ratings.
  • A realistic test: two to three months.

09Time budget

  • Before: 2 to 6 hours to port and submit.
  • Ongoing: 30 minutes per release.

10Pair it with

11Sources

Sources