Submit or Manage Extensions

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.

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):

  • If you have a Mozilla Account, in the page header, click Log in and log in with your Mozilla Account. This connects your account with AMO.
  • If you don't have a Mozilla Account, in the page header, click Register.

Go to Add-ons Developer Hub and click Submit Your First Add-on or Submit a New Add-on. You reach the following page:

The submit an add-on page showing the submission options: list the add-on on AMO or your site.

Choose:

  • On this site, if you want your add-on listed on AMO.
    Click Continue and follow the Listing on AMO guide.
  • On your own, if you plan to distribute the add-on yourself and don't want it listed on AMO.
    Click Continue and follow the Self-distribution guide.

Listing on AMO

  1. The Upload Version page displays.

    The submit an add-on page showing the option to select a file containing your add-on.

  2. Click Select a file, select and upload your add-on.

  3. The validator checks the add-on for issues and the page updates.

    The submit an add-on page showing that add-on validation is complete.

  4. If your add-on passes all the checks, you receive this message:

    A message saying that your add-on was validated with no errors or warnings.

    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:

    A message saying that your add-on failed validation with errors.

    The message informs you of what failed. You cannot continue. Address these issues and return to step 1.

  5. Select the add-on's compatible platform(s).

  6. Click Continue.

  7. Indicate whether you need to provide your source code.

    The submit an add-on page asking whether your extension requires a source code submission, showing the option to browse and upload a source code package when you select yes.

    If you select Yes, a section displays describing what you need to submit. Click Browse and locate and upload your source code package. See Source code submission for more information.

  8. Click Continue.

  9. The Describe Add-on page displays.

    The submit an add-on page with the options to add details about your add-on that display in its AMO listing.

    Provide the following:

    • Name: your add-on's name.
    • Add-on URL: the URL for your add-on on AMO. A URL is automatically assigned based on your add-on's name. To change this, click Edit. The URL must be unique. You are warned if another add-on is using your chosen URL, and you must enter a different one.
    • Summary: a useful and descriptive short summary of your add-on.
    • Description: a longer description that provides users with details of the extension's features and functionality.
    • This add-on is experimental: your add-on is experimental or otherwise not ready for general use. The add-on will be listed but with reduced visibility. You can remove this flag when your add-on is ready for general use.
    • This add-on requires payment, non-free services or software, or additional hardware: indicate if your add-on requires users to make an additional purchase for it to work fully.
    • Select up to 2 Firefox categories for this add-on: select categories that describe your add-on.
    • Select up to 2 Firefox for Android categories for this add-on: select categories that describe your add-on.
    • Support email and Support website: an email address and website where users can get in touch when they have questions, issues, or compliments.
    • License: select the appropriate license for your add-on. Click Details to learn more about each license.
    • This add-on has a privacy policy: if any data is being transmitted from the user’s device, a privacy policy explaining what is being sent and how it’s used is required. Check this box and provide the privacy policy.
    • Notes for Reviewers: information to assist the AMO reviewer, such as log in details for a dummy account, source code information, or similar.

  10. Click Submit Version

  11. The Version Submitted page displays. You also receive an email confirmation.

    The submit an add-on page confirming that the add-on has been submitted and providing buttons for things you can do next, including managing the listing, editing the submission, adding a new submission, or going to a list of your submissions.

Your add-on is published and available on AMO for users to discover and install. Note, however, that your add-on may be subject to further review. If it is, you 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 add-on and not a new one.

Learn how to make your add-on listing appealing with these tips.

Self-distribution

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.

  1. The Upload Version page displays.

    Submit an add-on page

  2. Click Select a file, select and upload your add-on.

  3. The validator checks the add-on for issues and the page updates.

    The submit an add-on page showing that add-on validation is complete.

  4. If your add-on passes all the checks, you receive this message:

    A message saying that your add-on was validated with no errors or warnings.

    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:

    A message saying that your add-on failed validation with errors.

    The message informs you of what failed. You cannot continue. Address these issues and return to step 1.

  5. Select the add-on's compatible platform(s).

  6. Click Continue.

  7. Indicate whether you need to provide your source code.

    The submit an add-on page asking whether your extension requires a source code submission, showing the option to browse and upload a source code package when you select yes.

    If you select Yes, a section displays describing what you need to submit. Click Browse and locate and upload your source code package. See Source code submission for more information.

  8. Click Continue.

  9. The Version Signature Pending page displays.

    The submit an add-on page displaying a message indicating that the version signature is pending and providing a link to a list of your submissions.

  10. Click Go to My Submissions.

  11. You receive an email when your extension has been signed.

  12. Follow the link in the email or open your extension from My Add-ons and, under the latest version details, click View All.

    The option to view all versions highlighted in the latest version box of an add-on submission page.

  13. Select the version you uploaded and, on the version page, click the file link to download the signed copy of your add-on.

    The download link for a signed copy of an add-on highlighted in an add-on submission version page.

You can now distribute your add-on. Note, however, that your add-on may be subject to further review. If it is, you receive notification of the outcome of the review later.

Get help

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.