Chrome Extension Tools

Chrome Extension Downloader

Paste a Chrome Web Store link or a 32-character extension ID and get a direct CRX download request for that extension. Nothing is installed, and no files are uploaded.

For examplehttps://chromewebstore.google.com/detail/react-developer-tools/fmkadmapgofadopljbjfkapdkoienihior justfmkadmapgofadopljbjfkapdkoienihi.

Waiting for a link or ID.

This downloads a .crx file. It does not install anything, and no web page can install a Chrome extension for you. See what a CRX file is for what to do next.

How to use

  1. Copy the Chrome Web Store link of the extension you want, or open the extension in the Web Store and copy the address bar URL.
  2. Paste it into the field above. If you paste the raw ID on its own, that works too.
  3. The extension ID appears immediately, along with the exact download URL that will be requested.
  4. Select "Download CRX file" to send the request to Google. If your browser blocks the download, use "Copy download URL" and paste it into a new tab.

How it works

The tool reads your input as plain text. If it is a URL, it is parsed with the browser's URL parser and the path segments are checked for a 32-character extension ID. If it is not a URL, the whole input is checked against the extension ID format directly.

A Chrome extension ID is exactly 32 characters long and uses only the letters a to p. That alphabet is not a typo: the extension system maps a 128-bit number into base-16 letters, and only a–p fall in that range. Anything else is rejected before a request is built.

The download request targets the same endpoint Google's own Chrome Enterprise documentation lists for extension downloads: clients2.google.com/service/update2/crx, with a response=redirect parameter and a crx2,crx3 accept format. A Chrome version is reported in prodversion, which testing showed is required — without it the endpoint returns "204 No Content" even for extensions that can otherwise be downloaded.

The button triggers a browser navigation to that URL rather than a fetch() call. This is deliberate: the endpoint returns no Access-Control-Allow-Origin header, so a cross-origin fetch from this page is blocked and the response cannot be read. A plain navigation works, because the browser downloads the result based on its application/x-chrome-extension content type. No server proxy is involved, and nothing about your input is sent anywhere except to Google's own endpoint, in the form of the extension ID you supplied.

Important limitations

  • Not every Chrome Web Store extension can be downloaded this way. Google returns no content for some listings, including extensions still built on Manifest V2, and returns a 404 for IDs that do not exist.
  • This tool requests a download. It cannot install an extension. Chrome only installs extensions from its own UI or from a policy, and no web page can install an extension on your behalf.
  • Your browser cannot tell us whether the download succeeded. Because the request is a cross-origin navigation with no CORS headers, the response is not readable from this page. The status shown is "download requested", never "downloaded".
  • Google can change the endpoint, its parameters, or its access rules at any time. If downloads stop working, check the guide linked below before assuming the extension is gone.
  • Only IDs and Web Store links are accepted. The tool does not scrape the store page, and it does not fetch or display extension names, ratings or any other listing metadata.

Privacy and security

This tool does not upload anything, because it has no server-side code. The only network request it can make is the download request to Google's own extension endpoint, and that request contains the extension ID you supplied. This site cannot read the response, so it cannot see whether a download succeeded.

Frequently asked questions

Is this an official Google or Chrome tool?

No. Chrome Extension Tools is an independent project. It is not affiliated with, sponsored by, or endorsed by Google, and nothing here is "Google-approved" or "Chrome-certified". The download request is sent to Google's own public endpoint because that is where Chrome fetches extension packages from.

Why did nothing download?

Three things are common. Your browser or an extension may be blocking downloads from that domain. The extension may not be available through this endpoint at all — Google returns no content for some listings, particularly Manifest V2 extensions. Or the ID may not exist. Copy the download URL into a new tab: a CRX downloads silently, while an error shows an error page, which tells you which case you are in.

Can this install an extension for me?

No, and it is not trying to. Chrome does not allow a web page to install an extension. The tool gives you the CRX file so you can inspect it, convert it, or load it yourself through Chrome's own "Load unpacked" or developer mode flow.

Why is prodversion needed?

Testing against real public extension IDs showed that omitting prodversion makes the endpoint return 204 No Content even for extensions that download fine when it is present. The tool therefore reports a current Chrome build version. You do not need to change it.

Does the download request reveal me to Google?

The request goes to Google's own servers and necessarily includes the extension ID you asked for, plus your normal IP address and user agent, exactly as if you had clicked download in Chrome. This site adds nothing to that request and sees no part of the response.

What is a CRX file?

A CRX is the container format Chrome uses to install an extension: a small binary header followed by an ordinary ZIP archive. Understanding the difference explains why a downloaded CRX cannot simply be unzipped, and why the CRX to ZIP converter exists.

Related tools