You will now be ready to start turning your idea for a browser extension into reality. Before you start that journey, it's worth being aware of a few things that will help to make it a smooth one.

Your development environment

You don't need any special development or build environment tools to create browser extensions: It's entirely possible to create great browser extensions with no more than a text editor. However, you may have been developing for the web and have a set of tools and an environment you want to reuse. If you do, you need to be aware of a couple of things.

If you use minification or obfuscation tools to deliver your final code, you’ll need to provide your source code to the AMO review process. Also, the tools you use—those for minification,  obfuscation, and build processes—will need to be open source (or offer unlimited free use) and be available to run on the reviewer’s computer (Windows, Mac, or Linux). Unfortunately, our reviewers can't work with commercial or web-based tools.

Learn more about build tools

Third-party libraries

Third-party libraries are a great way to add complex features or functionality to your browser extensions quickly. When you submit an extension to the AMO review process, the process will also consider any third-party libraries used. To streamline the review, make sure you always download third-party libraries from their official website or repository, and if the library is minified provide a link to the source code. Please note that third-party libraries cannot be modified in any way.

Learn more about submitting source code

The Firefox Add-on Distribution Agreement

Browser extensions need to be signed to install into the release or beta versions of Firefox. Signing takes place in addons.mozilla.org (AMO) and is subject to the terms and conditions of the Firefox Add-on Distribution Agreement. The goal of the agreement is to ensure Firefox users get access to well supported, quality add-ons that enhance the Firefox experience.

Read the agreement

Learn more about signing

The review process

When a browser extension is submitted for signing, it's subject to automated review. It may also be subject to a manual review, when the automated review determines that a manual review is needed. Your browser extension won't be signed until it’s passed the automated review and may have its signing revoked if it fails to pass the manual review. The review process follows a strict set of guidelines, so it’s easy to check and avoid any likely review problems.

Check out the review policy and guidelines

If you choose to list your browser extension on AMO, your extension could be featured on the AMO website, in the Firefox browser’s add-on manager, or elsewhere on a Mozilla website. We've compiled a list of guidelines about how extensions are selected for featuring, by following these guidelines you give your extension the best chance of being featured.

Learn more about getting your add-ons featured

Continue your learning experience

Now you know what lies ahead, it's time to dive into more details about browser extension development. In the sections that follow, you’ll discover:

  • More about the fundamental concepts behind browser extensions, starting with details on how to use the JavaScript APIs.
  • A guide to the user interface components available to your browser extensions.
  • A collection of how-to guides on achieving key tasks in your extensions or making use of the JavaScript APIs.
  • Information on how to port other browser extensions to Firefox.
  • Details about the Firefox specific workflows you can use to develop browser extensions.
  • A full reference guide to the JavaScript APIs.
  • A full reference guide to the Manifest keys.

Document Tags and Contributors

Contributors to this page: rebloor
Last updated by: rebloor,