Automatically update extensions in Microsoft Edge


This article doesn't apply to extensions that you publish using the Partner Center dashboard. You can use the dashboard to release updated versions to your users and to the Microsoft Edge Add-ons website. For more information, see Update a Microsoft Edge extension.

When you set your extension to automatically update on users' machines, your extension shares the following benefits with Microsoft Edge:

  • Incorporate bug and security fixes.
  • Add new features or performance enhancements.
  • Improve the user interface.

Previously, non-store based extensions were supported. Also, previously, you updated the native binaries and the extension at the same time. Now, the Microsoft Edge Add-ons website hosts your extensions and you can update your extension using the same mechanism as Microsoft Edge. You don't control the update mechanism.


Be careful when you update extensions that have a dependency on native binaries.


Every few hours, Microsoft Edge checks whether each installed extension or app has an update URL. To specify an update URL for your extension, use the update_url field in the manifest. The update_url field in the manifest points to a location that can complete an update check. For each update_url, this URL sends requests for updated manifest XML files. If the update manifest XML file lists a newer extension or app version, Microsoft Edge downloads and installs the newer version. The same process works for manual updates, where the new .crx file must be signed with the same private key as the currently installed version.


In order to maintain user privacy, Microsoft Edge doesn't send any Cookie headers with auto-update manifest requests, and ignores any Set-Cookie headers in the responses to those requests.

Update URL

If you host your own extension or app, you must add the update_url field to your manifest.json file. The following code snippet shows an example of the update_url field:

  "name": "My extension",
  "update_url": "",

Update manifest

The updated manifest returned by the server should be an XML document; for example:

<?xml version='1.0' encoding='UTF-8'?>
<gupdate xmlns='' protocol='2.0'>
  <app appid='aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa'>
    <updatecheck codebase='' version='2.0' />

The updated manifest XML file defines the following attributes:

Attribute Details
appid The extension ID is generated based on a hash of the public key. To find the ID of an extension, open Microsoft Edge and see edge://extensions.
codebase A URL to the .crx file.
version This attribute value is used by Microsoft Edge to determine whether it should download the .crx file specified by codebase. It should match the value of version in the manifest.json file of the .crx file.

The update manifest XML file can contain information about multiple extensions, by including multiple <app> elements.


Microsoft Edge automatically checks for updates of extensions every few hours. To update extensions immediately, go to edge://extensions, turn on the Developer mode toggle, and then click the Update button.

Advanced usage: request parameters

The basic mechanism to update using parameters is simple. To automatically update your extension:

  1. Upload your static XML file on your web server, such as Apache.
  2. Update the XML file as you release new versions of your extensions.

Take advantage of the fact that some parameters added to the update manifest request indicate the extension ID and version. You can use the same update URL for all your extensions, instead of a static XML file. To use the same update URL for all your extensions, point to a URL that runs dynamic server-side code that tests the parameters.

The following example demonstrates the format of the request parameters of update URL:


In this example, {extension_data} is a URL-encoded string that uses the following format.


For example, the following two extensions both point to the same update URL

  • Extension 1
    • ID: aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
    • update URL:
    • Version: 1.1
  • Extension 2
    • ID: bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
    • update URL:
    • Version: 0.4

The following examples are requests to update each extension.

You can also list multiple extensions in a single request for each unique update URL. The following example merges the previous requests into a single request:

If you send a single request and the number of installed extensions that use the same update URL is too long, the update check issues more GET requests. A GET request URL is too long if it's approximately 2000 characters.


In the future, instead of issuing multiple GET requests, a single POST request might be issued, with the request parameters in the POST body.

Advanced usage: minimum browser version

As new APIs are released for the Microsoft Edge extensions system, you might want to release an updated version of your extension or app that only works with newer versions of Microsoft Edge. When Microsoft Edge is automatically updated, it can take a few days before most of your users update to that new release.

To ensure that a specific update applies only to Microsoft Edge versions that are current or newer than a specific version, add the prodversionmin attribute in your update manifest.

For example, in the following code, the prodversionmin attribute value of specifies that your app is automatically updated to version 2.0 only when the user is running Microsoft Edge or newer:

<?xml version='1.0' encoding='UTF-8'?>
<gupdate xmlns='' protocol='2.0'>
  <app appid='aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa'>
    <updatecheck codebase='' version='2.0' prodversionmin='' />


Portions of this page are modifications based on work created and shared by Google and used according to terms described in the Creative Commons Attribution 4.0 International License. The original page is found here.

Creative Commons License This work is licensed under a Creative Commons Attribution 4.0 International License.