Microsoft Edge Extension Guide

How to Get a CRX from Microsoft Edge Add-ons

To download an Edge extension CRX, copy its Microsoft Edge Add-ons listing URL, paste it into CRXFile, and choose Download CRX after parsing. You don't need to install the extension first.

Published October 11, 2026 · 5 min read

Copy the Microsoft Edge Add-ons URL

Open the extension's detail page in Microsoft Edge Add-ons. Check the name and publisher, then copy the address bar URL. A search results page or publisher homepage won't identify the package you want.

We used the public uBlock Origin listing for this walkthrough. Its open source project links to the same Edge listing. Copy the last URL segment to get its 32-character Edge extension ID.

Store URLhttps://microsoftedge.microsoft.com/addons/detail/ublock-origin/odfafepnkmbhccpbejgmiehpchacaeakEdge extension IDodfafepnkmbhccpbejgmiehpchacaeak

You can paste that ID alone, but select Microsoft Edge Add-ons in the tool first. If you also work with Chrome listings, our extension ID guide explains how to separate an ID from a readable name or version number.

Download the Edge extension CRX with CRXFile

Open the CRX downloader and paste the full Edge Add-ons URL into the input field.
Click Parse extension. Check that the result says Microsoft Edge Add-ons and that its ID matches the listing.
Compare the name and developer with the store page. For our example, the result showed uBlock Origin and Raymond Hill (gorhill).
Click Download CRX, then check that your saved file ends in .crx. Choose Download source .zip if you want extractable files.

Keep the store URL alongside the file. A filename is easy to rename, so it's a poor record of where a package came from. CRXFile needs no account and downloads the package available from the official endpoint at the time of your request. It doesn't offer a historical version library.

Choose CRX or ZIP for your task

Download CRX when you need to retain the Edge extension package as received. A CRX includes package headers around its ZIP payload. Saving it is useful for a permitted backup or later package comparison, though the saved file won't update itself when the publisher releases a new version.

For an Edge extension ZIP download, choose Download source .zip. CRXFile removes the CRX header and returns the files inside the package. Extract the ZIP and start with manifest.json, then follow the scripts it names. These are the distributed files, which may contain compressed JavaScript or build output. They aren't necessarily the developer's original project files.

What our real Edge download returned

We checked this workflow on October 11, 2026, using Chrome 154.0.8037.94 on macOS for the tool interface and separate requests to CRXFile's live download routes to inspect the files. Both downloads returned HTTP 200.

Check	Observed result
CRX package	CRX3, 4,600,286 bytes
ZIP source	4,598,964 bytes, matching the CRX's ZIP payload

CRXFile displayed Latest without a release number. We opened the ZIP's manifest.json to check the actual package and found these fields. Each value answers a different question.

The extension's label"name": "uBlock Origin"The downloaded release number"version": "2026.916.75.0"The manifest format used by this package"manifest_version": 2

These values describe our October 11 test. You may receive a different release after an update. Our checks cover file structure only. We didn't audit the extension's security or verify its signature.

Edge Add-ons and Chrome Web Store use different sources

CRXFile selects the download source from the listing URL. An Edge Add-ons URL selects Microsoft's endpoint, while a Chrome Web Store URL selects Google's. You can open the downloader in either browser. Microsoft documents both endpoints in its extension update URL FAQ. Don't assume that matching extension names mean the listings have the same ID, version, or package contents.

If your extension comes from Google's store, follow the Chrome Web Store CRX download guide and use that listing's URL, even when you normally browse in Edge.

What to check when an Edge CRX download fails

Start with the input. Open the official listing again and copy its detail URL. For an ID-only request, remove spaces and URL punctuation, and confirm the store selector says Microsoft Edge Add-ons. Then compare the parsed ID with the listing. A result card by itself doesn't prove that a package is downloadable.

A 204 No Content response means the update endpoint returned no package for that request. It doesn't explain why. A 403 or 404 response, a timeout, or a removed listing also needs checking against the original store page. Retry a temporary failure later. CRXFile can't bypass private access or restore a withdrawn package, and it doesn't fetch Firefox XPI files.

Can you install the downloaded CRX in Edge?

For ordinary installation, use the official listing. Local CRX installation can depend on your platform, browser version, and organization's policies. Downloading the file doesn't remove those restrictions.

For authorized development testing, Microsoft's sideloading guide describes Developer mode and Load unpacked in edge://extensions. Extract a ZIP first and select the directory containing manifest.json. Browser support for the package's manifest version still matters. Check the download FAQ for more package limits, and keep the publisher's license with any files you retain or share.

Sources

Microsoft's extension FAQ identifies the store update endpoints. Its local testing guide documents Load unpacked. The uBlock Origin project links to our example listing and includes its license. The download results above come from our live CRXFile checks.