Where we list / Listing guides
How to submit your extension to Firefox Add-ons
You sign in to the Add-ons Developer Hub with a free Mozilla account, upload your extension as a zip or xpi, choose to list it on addons.mozilla.org, and fill in the listing. Mozilla's docs mention no submission fee. Automated signing and publishing can take up to 24 hours, and any add-on can still be manually reviewed later.
Checked on Firefox Add-ons's own pages on 2026-11-12.
| Cost | No submission fee is mentioned in Mozilla's documentation. |
|---|---|
| Who can submit | Anyone with a Mozilla account who accepts the Add-on Policies and Developer Agreement. |
| Review | Automated validation and signing first, which can take up to 24 hours. Mozilla can manually review any add-on at any time after submission; no timeframe is given for manual review. |
| Fits | Firefox extensions (including ports of Chrome extensions built on WebExtensions) and Firefox themes. Privacy, productivity, developer and reading tools do well. |
| Time needed | 1 to 3 hours to package the add-on, prepare source code if needed, and write the listing. |
Before you start
- A Mozilla account to sign in to the Add-ons Developer Hub.
- Your add-on packaged as .zip, .xpi or .crx, no larger than 200 MB.
- A separate source code package with build instructions if your code is minified, bundled or transpiled.
- Icons at 32 x 32 and 64 x 64 px (PNG or JPEG) and screenshots at 1280 x 800 px or another 1.6:1 size.
- A summary of 250 characters or less and a description that explains what the add-on does and any paid parts.
- Privacy policy text if the add-on sends any data off the user's device.
- Test login details for Notes for Reviewers if features sit behind an account.
How to list on Firefox Add-ons, step by step
Read the policies first
Go through the Add-on Policies and Developer Agreement before you package anything. Most rejections come from data handling, remote code and missing source, which are easier to fix before you upload.
Start a new submission
Sign in to the Developer Hub and start a new add-on. Choose 'On this site' to be listed on addons.mozilla.org, or 'On your own' if you only want a signed file to distribute yourself.
Upload and validate
Upload the file and let the validator run. Errors stop you; warnings do not, but fix security and privacy warnings because they can fail a later review.
Pick platforms and answer the source question
Choose Firefox for desktop, Firefox for Android or both. Say whether you need to provide source code, and upload it with clear build steps if you do.
Complete the listing
Add the name, add-on URL, summary, description, up to two categories per platform, support email and website, license and privacy policy. Use Notes for Reviewers for test accounts or build details.
Submit the version
Click Submit Version. You get a confirmation email, and the add-on is signed and published, usually within 24 hours unless it is picked for manual review.
Add screenshots and keep it updated
Edit the listing to add screenshots and polish the text. When you upload a new version, Firefox updates installed copies automatically.
What the Firefox Add-ons form asks for
| Field | Limit | Tip |
|---|---|---|
| Name | – | If your add-on is a fork, make the name clearly different from the original. |
| Add-on URL | – | This slug must be unique on the site, so pick a short, readable one. |
| Summary | 250 characters | Mozilla advises keeping it as short as possible; one sentence on the main benefit works. |
| Description | – | Explain features and any unexpected changes, such as new tab or search changes, without writing an essay. |
| This add-on is experimental | – | Tick it for early builds; the listing gets reduced visibility. |
| Requires payment, non-free services or software, or additional hardware | – | Tick it if any feature needs payment; undisclosed paid features break policy. |
| Categories (Firefox / Firefox for Android) | Up to 2 each | Supporting Android gives you a second set of categories to appear in. |
| Support email / Support website | – | Use an inbox you check, since users and reviewers will write there. |
| License | – | Choose the license that matches your repository so users know what they can do with the code. |
| Privacy policy | – | Required if data leaves the user's device; describe exactly what is sent and why. |
| Notes for Reviewers | – | Add test credentials and build commands so a reviewer can reproduce your package. |
Why submissions get rejected
- Minified or transpiled code submitted without the original source and build instructions.
- Obfuscated code or code that hides its purpose.
- Loading or running remote code, or weakening page security headers such as Content Security Policy.
- Requesting permissions the add-on does not need.
- Sending data that is not needed for the main function, or collecting personal data without clear opt-in consent.
- Unexpected features, such as changing the new tab page or search engine, that are not disclosed and opt-in.
- An add-on whose only purpose is to promote or open an outside website or app.
- Paid features not disclosed in the listing.
- Low-quality, stretched, blank or duplicate themes.
Tips that make a difference
- Use only build tools Mozilla supports and give exact commands, because reviewers must be able to rebuild your package from source.
- Fix every validator warning that mentions security or privacy before you submit, even though warnings do not block upload.
- Make your consent screen part of the add-on UI; consent prompts that are easy to miss are a stated rejection reason.
- If your add-on needs an account, give reviewers a test login, since add-ons must be testable.
- Choose 'On your own' if you only need a signed file for a closed group; you still get automatic updates by adding an update_url.
Example: what JustLaunched prepared
These are the texts Pushify prepared for JustLaunched, a real brand, before listing it on sites like Firefox Add-ons. See the full sample report ›
| Name | JustLaunched |
|---|---|
| Tagline | Launch board for founders and early adopters |
| Short description | JustLaunched is a free launch board where founders introduce new products and early adopters try them first, ask questions and share feedback. |
| Tags | product launch, launch platform, startup discovery, indie makers, early adopters, beta testers, launch deals, product hunt alternative, saas, startups |
Questions people ask
Is it free to publish a Firefox extension?
Mozilla's submission docs mention no fee. You need a free Mozilla account to use the Developer Hub.
How long does it take for a Firefox add-on to go live?
Automated signing and publishing can take up to 24 hours. It takes longer if your add-on is selected for manual review, and Mozilla gives no timeframe for that.
What is the difference between listed and self-distributed add-ons?
Listed add-ons appear on addons.mozilla.org and get automatic updates through it. Self-distributed add-ons are signed by Mozilla but you host and share the file yourself.
Do I have to upload my source code?
Only if your package contains code that is hard to read, such as minified, bundled or transpiled files. Then you must provide the original source and build steps, or the add-on can be rejected or blocked.
What is the maximum add-on file size?
The upload limit is 200 MB. Larger files fail validation.
Sources
The Firefox Add-ons pages this guide was checked against.