• Skip to main content
  • Select language
  • Skip to search
MDN Web Docs
  • Technologies
    • HTML
    • CSS
    • JavaScript
    • Graphics
    • HTTP
    • APIs / DOM
    • WebExtensions
    • MathML
  • References & Guides
    • Learn web development
    • Tutorials
    • References
    • Developer Guides
    • Accessibility
    • Game development
    • ...more docs
Add-ons
  1. MDN
  2. Mozilla
  3. Add-ons
  4. Updates

Updates

In This Article
  1. Enabling updates to your extension
  2. Manifest Structure
    1. Addon objects
    2. Update objects
    3. Application objects
  3. Testing Automatic Updating

Requires Gecko 45 (Firefox 45 / Thunderbird 45 / SeaMonkey 2.42)

Firefox supports automated updates to add-ons using JSON update manifests. Add-ons hosted on AMO automatically receive updates to new versions posted there. Other add-ons must specify the location of their update manifests.

A typical update manifest looks something like:

{
  "addons": {
    "addon@example.com": {
      "updates": [
        { "version": "0.1",
          "update_link": "https://example.com/addon-0.1.xpi" },
        { "version": "0.2",
          "update_link": "http://example.com/addon-0.2.xpi",
          "update_hash": "sha256:fe93c2156f05f20621df1723b0f39c8ab28cdbeec342efa95535d3abff932096" },
        { "version": "0.3",
          "update_link": "https://example.com/addon-0.3.xpi",
          "applications": {
            "gecko": { "strict_min_version": "44" } } }
      ]
    }
  }
}

Enabling updates to your extension

If your extension is not hosted on AMO, you must specify the location of your update manifest in your extension. For extensions developed with WebExtension APIs, add the following to your manifest:

"applications": {
  "gecko": {
    "update_url": "https://example.com/updates.json"
  }
}

For XUL add-ons, add the following to the <Description about="urn:mozilla:install-manifest"> element of your install.rdf file:

  <em:updateURL>https://example.com/updates.json</em:updateURL>

Manifest Structure

The manifest is a JSON file, with a top-level object literal. This object may have the following properties:

Property Type Description
addons object An object containing one entry for each add-on to be updated. For each such entry, the name of the property must be the add-on's ID, and the value must be an object describing the add-on and its updates.

Addon objects

addons[*]

Properties of the addons object must contain object literals, each describing an add-on to update. These objects may have the following properties:

Property Type Description
updates Array Optional An array containing zero or more update description objects for the add-on.

Update objects

addons[*].updates[*]

Update description objects must be object literals. They may have the following properties:

Property Type Description
version string The version number this update entry describes. If an update URL is specified, it must use this version. If any compatibility information is specified, it will override the compatibility information of any installed version with this version number.
update_link string Optional A link to the XPI file containing this version of the add-on. This must be an HTTPS URL, or an update_hash must be provided to verify it.
update_hash string Optional A cryptographic hash of the file pointed to by update_link. This must be provided if update_link is not a secure URL. If present, this must be a string beginning with either sha256: or sha512:, followed by the hexadecimal-encoded hash of the matching type.
update_info_url string Optional A link to an HTML file containing information about the update.
multiprocess_compatible  bool Optional
(default: true)
If false, this add-on requires compatibility shims to run in a multi-process Firefox environment.
applications object Optional

An object containing application-specific compatibility information. Each property must contain an application object, as described below.

The only application currently supported is gecko, which includes Firefox, and all other applications built on the same runtime.

If this property is omitted, support for Gecko is assumed. Otherwise, if this property is defined, it must contain a gecko property, or the update entry will be ignored.

Application objects

addons[*].updates[*].applications.gecko

Application objects specify compatibility information for a specific application. They must be object literals, and may have the following properties:

Property Type Description
strict_min_version string Optional
(default: 42.0a1)
The minimum version of the application this add-on will run on.
strict_max_version string Optional
(default: *)
The maximum version of the application this add-on will run on.
advisory_max_version  string Optional
(default: *)
The maximum version of the application this add-on is likely to run on. This property is ignored in most cases.

Testing Automatic Updating

By default, Firefox checks for updates every 86400 seconds (24 hours).  If you want to test whether or not the updater is working for your extension, you should browse to about:config and change the value of extensions.update.interval from 86400 to 120, which is apparently the minimum supported value.  (If you set it to less than 120, update checks will only occur every 2 minutes.)  While you're in there, verify that extensions.update.enabled is set to its default value of true.  Relaunch Firefox after making any changes.

If your extension does not update as expected, click in Firefox' menu: Tools > Web Developer > Browser Console, filter for the name of your extension or update URL, and see if there are any errors logged.  If you see an error indicating that the downloaded file hash … did not match provided hash …, look up for the previous GET of your extension.  If it indicates that the download time was around zero milliseconds, for example  [HTTP/1.1 200 OK 0ms], Firefox may have used a cached download, which might be your prior version if you just recently uploaded a new version, and this may explain the hash mismatch.

Document Tags and Contributors

 Contributors to this page: andrewtruongmoz, jerrykrinock, rolfedh, wbamberg, kmaglione
 Last updated by: andrewtruongmoz, Jul 12, 2017, 3:47:15 PM
See also
  1. WebExtensions
  2. Getting started
    1. What are WebExtensions?
    2. Your first WebExtension
    3. Your second WebExtension
    4. Anatomy of a WebExtension
    5. Example WebExtensions
  3. How to
    1. Intercept HTTP requests
    2. Modify a web page
    3. Add a button to the toolbar
    4. Implement a settings page
  4. User interface
    1. Introduction
    2. Toolbar button
    3. Address bar button
    4. Sidebar
    5. Context menu items
    6. Options page
    7. Bundled web pages
    8. Notifications
    9. Address bar suggestions
    10. Developer tools panels
  5. Concepts
    1. Using the JavaScript APIs
    2. Content scripts
    3. Match patterns
    4. Internationalization
    5. Content Security Policy
    6. Native messaging
  6. Porting
    1. Porting a Google Chrome extension
    2. Porting a legacy Firefox add-on
    3. Embedded WebExtensions
    4. Comparison with the Add-on SDK
    5. Comparison with XUL/XPCOM extensions
    6. Chrome incompatibilities
    7. Differences between desktop and Android
  7. Firefox workflow
    1. Temporary Installation in Firefox
    2. Debugging
    3. Developing for Firefox for Android
    4. Getting started with web-ext
    5. web-ext command reference
    6. WebExtensions and the Add-on ID
    7. Publishing your WebExtension
  8. JavaScript APIs
    1. Browser support for JavaScript APIs
    2. alarms
    3. bookmarks
    4. browserAction
    5. browsingData
    6. commands
    7. contextMenus
    8. contextualIdentities
    9. cookies
    10. devtools.inspectedWindow
    11. devtools.network
    12. devtools.panels
    13. downloads
    14. events
    15. extension
    16. extensionTypes
    17. history
    18. i18n
    19. identity
    20. idle
    21. management
    22. notifications
    23. omnibox
    24. pageAction
    25. permissions
    26. privacy
    27. proxy
    28. runtime
    29. sessions
    30. sidebarAction
    31. storage
    32. tabs
    33. topSites
    34. types
    35. webNavigation
    36. webRequest
    37. windows
  9. Manifest keys
    1. applications
    2. author
    3. background
    4. browser_action
    5. chrome_settings_overrides
    6. chrome_url_overrides
    7. commands
    8. content_scripts
    9. content_security_policy
    10. default_locale
    11. description
    12. developer
    13. devtools_page
    14. homepage_url
    15. icons
    16. incognito
    17. manifest_version
    18. name
    19. omnibox
    20. optional_permissions
    21. options_ui
    22. page_action
    23. permissions
    24. protocol_handlers
    25. short_name
    26. sidebar_action
    27. version
    28. web_accessible_resources
  10. Themes
  11. Publishing add-ons
  12. Guides
    1. Signing and distribution overview
    2. Submit an add-on
    3. Creating an appealing listing
    4. Review policies
    5. Developer agreement
    6. Featured add-ons
    7. Contact addons.mozilla.org
  13. Community and support
  14. Channels
    1. Add-ons blog
    2. Add-on forums
    3. Stack Overflow
    4. Development newsgroup
    5. IRC Channel
  15. Legacy add-ons
  16. Legacy technologies
    1. Add-on SDK
    2. Legacy Firefox for Android
    3. Bootstrapped extensions
    4. Overlay extensions