Submitting an add-on
This article walks through the process of publishing an add-on. If you just want to get started, head to the Submit a New Add-on page on AMO.
This article walks through the process of publishing an add-on. If you just want to get started, head to the Submit a New Add-on page on AMO.
To start, familiarize yourself with the Add-on Policies and Developer Agreement.
Next, prepare your add-on for publication by adding all its files to a ZIP archive with the extension .zip
, .xpi
or .crx
. For information on how to create your ZIP, see Package your extension, and for details on what to include in the file, see Anatomy of an extension.
The maximum file size accepted is 200 MB. If your add-on is larger than 200 MB, it will fail validation.
If your add-on includes code that might be difficult to read, such as code created by minification or obfuscation, create a source code package. For more information on this requirement, see Source Code Submission.
Create your developer account on addons.mozilla.org (AMO):
Go to the Add-ons Developer Hub and click Submit Your First Add-on or Submit a New Add-on. You'll reach the following page:
Choose:
The Upload Version page displays.
Click Select a file, select and upload your add-on.
The validator checks the add-on for issues and the page updates.
If your add-on passes all the checks, you receive the following message:
You may receive a message that you only have warnings. It's advisable to address these warnings, particularly those flagged as security or privacy issues, as they may result in your add-on failing review. However, you can continue with the submission.
Otherwise, you receive a message similar to this:
The message informs you of what failed. You'll not be able to continue. Address the issues and return to step 1.
If you need to provide source code, click Browse and locate and upload your source code package.
Select the add-on's compatible platform(s).
Click Continue.
The Describe Add-on page displays.
Provide the following:
Click Submit Version
The Version Submitted page displays. You'll also receive an email confirmation.
Your add-on is published and available on AMO for users to discover and install. Note, however, that your add-on may still be subject to further review, if it is you'll receive notification of the outcome of the review later.
When you're ready to release a new version of your add-on, update it by visiting the add-on's page on addons.mozilla.org and uploading the new version. You must update it on the add-on's page, so AMO recognizes it as an update to an existing add-on and not a new one.
Learn how to make your add-on listing appealing with these tips.
If you want Firefox to handle updates to your add-on, remember to include the browser_specific_settings
key in your manifest.json
with the update_url
attribute set to point to an update manifest file.
The Upload Version page displays.
Click Select a file, select and upload your add-on.
The validator checks the add-on for issues and the page updates.
If your add-on passes all the checks, you receive the following message:
You may receive a message that you only have warnings. It's advisable to address these warnings, particularly those flagged as security or privacy issues, as they may result in your add-on failing review. However, you can continue with the submission.
Otherwise, you receive a message similar to this:
The message informs you of what failed. You'll not be able to continue. Address the issues and return to step 1.
If you need to provide source code, click Browse and locate and upload your source code package.
Select the add-on's compatible platform(s).
Click Sign Add-on.
The Version Signed page displays. You'll also receive an email confirmation.
Click Download to obtain a signed copy of your add-on.
You can now distribute your add-on. Note, however, that your add-on may still be subject to further review, if it is you'll receive notification of the outcome of the review later.
For resources that can help now you've published an add-on and details of how to get help if you encounter issues, check out Resources for publishers.
Publish
Publish
Publish