Create an account on then submit your add-on for signing and distribution.

Package your extension, manually or using the web-ext tool.

If you have any problems, contact us on the dev-addons mailing list or Add-ons channel on Matrix.

Install your extension in Firefox by using about:debugging or the web-ext tool (similar to Chrome’s command-line tools).

If you're using features or APIs that aren't supported in Firefox, you might not be able to port your extension. Mozilla provides a service that can help to automate this step:.

Review your use of manifest.json features and Chrome extension APIs against the Chrome incompatibilities reference.

The process of porting an extension from Chrome or Opera is, therefore, relatively straightforward: In those cases, the API documentation page states that support is provided only in the browser namespace.

The only APIs that aren't supported in the chrome namespace are those that are intentionally incompatible with Chrome. Almost all of the WebExtension APIs provide support for callback functions under the chrome namespace, the same as Chrome. Extensions written for these browsers will, in most cases, run in Firefox with just a few changes. The WebExtension APIs is therefore, to a large extent, code-compatible with the extension API supported by Google Chrome and Opera. The browser extension APIs are designed to promote cross-browser compatibility among extensions. Removing your extension from distribution.Will I ever be able to sell through AMO?.Use plain language in any privacy policy or license agreement.Select the right platforms and versions.The add-on description can be longer, but not too long.Focus on key features in your screenshots.Make sure your summary is just long enough.

Fireshot addon