Submit or Manage Extensions

Signing and distributing your add-on

Add-ons need to be signed before they can be installed into release and beta versions of Firefox. This signing process takes place through addons.mozilla.org (AMO), whether you choose to distribute your add-on through AMO or to do it yourself.

Here we look at the signing requirements and the related reviews, before discussing how to choose between distributing on AMO or distributing an add-on yourself. We also look at the channels available on AMO and answer questions about code ownership and disputes.

Signing your add-ons

Extensions and themes need to be signed by Mozilla before they can be installed in release and beta versions of Firefox. Dictionaries don't need to be signed.

Unsigned extensions can be installed in the Developer Edition, Nightly, and ESR versions of Firefox, after toggling the xpinstall.signatures.required preference in about:config. To use this feature your extension must have an add-on ID.

Mozilla signs add-ons through addons.mozilla.org. You can use one of the following methods to sign your extension, but please be aware that not all signing methods support all distribution options.

Signing method Supported distribution channel(s)
Web upload via the AMO Developer Hub Public listing on AMO or self-distribution (unlisted).
Upload using web-ext sign Version 8 and higher: Initial submission and updates for extensions listed on AMO or self-distributed (unlisted).

Version 7 and lower: Initial submissions for self-distributed (unlisted) extensions. Updates for extensions listed on AMO or self-distributed (unlisted).
The AMO Add-on Create API (V5) and Version Create API (V5) Initial submission and updates for extensions listed on AMO or self-distributed (unlisted).
The AMO Signing API (V4) Initial submissions for self-distributed (unlisted) extensions. Updates to extensions publicly listed on AMO or self-distributed (unlisted).

All submissions, regardless of how they are signed, are subject to Mozilla's Add-on Policies and the Firefox Add-on Distribution Agreement.

Distributing your add-on

You can choose to distribute your add-on publicly on addons.mozilla.org (AMO) or distribute it yourself. Here are some things to consider when you are deciding which method is most appropriate for your needs.

Public listing on addons.mozilla.org (AMO)

AMO is a very popular distribution platform, with millions of monthly visitors and installations. It's integrated into the Firefox Add-ons Manager, allowing for easy installation of add-ons published on AMO. You can boost your extension’s SEO and attract more users by creating an appealing listing.

When an add-on is listed on AMO, updates to installed copies are handled automatically by Firefox each time a new version is listed on AMO.

For more information on how to submit an add-on for distribution on AMO or self-distribution, see Submitting an add-on.

Self-distribution

Self-distributed add-ons are sometimes referred to as “unlisted” extensions because they cannot be publicly viewed or installed from AMO. You may want to self-distribute your extension if it is a beta version or if it is intended to be used by a limited audience. All add-ons, including self-distributed ones, are subject to be manually reviewed at any time after submission to check for compliance with the Add-on Policies.

If you choose this method, be sure to read the article on self-distribution to learn how users can install self-distributed add-ons and how to push automatic updates to your users.

Post-submission review

Regardless of distribution method, all add-ons undergo automated validation before they are signed. It can take up to 24 hours for your submission to be signed and published, or longer if your submission is selected for manual review.

All add-ons are subject to a manual code review at any time after submission. The review criteria applied to add-ons are found in the Add-on Policies. Reviews may result in the rejection of current or previous versions of your add-on, or in your add-on being blocked.

See What does review rejection mean to users? and Add-ons Blocking Process for more information.

More information about addons.mozilla.org (AMO)

Ownership

Add-ons on AMO can have multiple users with permission to update and manage the listing. The authors of an add-on can transfer ownership and add developers to an add-on's listing through the Developer Hub. No interaction with Mozilla representatives is necessary for a transfer of ownership.

To transfer ownership

  • Make sure the new owner has an account on addons.mozilla.org. New accounts can be created using the "Register or Log in" button, after which the owner must confirm their email address.
  • Sign into your account on the Add-on Developer Hub, and click "Edit Listing" for the extension you want to transfer.
  • On the left-hand side of the screen, you will see a blue box labeled "Edit Information". Click "Manage Authors & License" — from the resulting page you can add and remove authors.
  • Once you have added the new author's email address, set that person as the extension owner and make sure the "Listed" box has a checkmark. Now you can remove yourself by clicking the "x" next to your email address.
  • When you're done, click "Save Changes". The new owner will be able to manage updates, listing information, etc., when logged in.

Code disputes

Many add-ons allow their source code to be viewed. This does not mean that the source code is open source or available for use in another add-on. The original author of an add-on retains copyright of their work unless otherwise noted in the add-on's license.

If we're notified of a copyright or license infringement, we will take steps to address the situation per the DMCA, which may include taking down the add-on listing. Details about this process and how to report trademark or licensing issues can be found here.

If you are unsure of the current copyright status of an add-on's source code, you must contact the author and get explicit permission before using the source code.