How Do I Open or Use a Downloaded CRX File?

Updated

A downloaded CRX file is a packaged Chrome extension, and Chrome won't install it by double-clicking the way it installs extensions from the Chrome Web Store. Your practical options are to unpack the CRX and load it as an unpacked extension in Developer Mode, or to feed the CRX (or its ZIP equivalent) to an automation tool like Selenium. If you only need to read the extension's code, unpacking it is enough.

What the CRX format actually is

CRX is the container format Google uses to package Chrome extensions. A CRX file is essentially a ZIP archive with a header that carries the extension's metadata and a signature. That signature is why Chrome treats store-installed extensions differently from files you download yourself: the browser checks that the package came from a trusted source before installing it.

CRX Downloader describes itself as a service for downloading Chrome extensions as ZIP or CRX files, specifically so you can use them with testing tools like Selenium or inspect their contents. The site also links to its own "How to open CRX file?" section, which is worth reading alongside the steps below.

Option 1: Unpack the CRX and load it unpacked

This is the most reliable way to get a downloaded extension running in your own Chrome.

  1. Get the file as a ZIP if you can. CRX Downloader offers both formats. A ZIP saves you the unpacking step below.
  2. If you only have the CRX, extract it. Rename the file so it ends in .zip, then extract it with any archive tool. The result is a folder containing manifest.json and the extension's other files.
  3. Open Chrome's extension page. Go to chrome://extensions.
  4. Turn on Developer mode. The toggle sits in the top-right corner of that page.
  5. Click "Load unpacked" and select the folder you extracted.
  6. Verify. The extension appears in the list with its own ID, and its icon shows up in the toolbar if it has one.

Expected result: the extension runs locally, but Chrome will show it as an unpacked extension and may warn you each time the browser starts.

Common snags

  • The extracted folder must contain manifest.json at its top level. If extraction produced a nested folder, point "Load unpacked" at the inner one.
  • Renaming to .zip sometimes fails if the archive tool refuses a file whose internal structure it doesn't recognize. Try a different tool before assuming the download is broken.
  • Unpacked extensions don't auto-update. You'll need to re-download and re-load to get a newer version.

Option 2: Use the CRX or ZIP with automation tools

This is the use case CRX Downloader names explicitly: testing tools such as Selenium. Automation frameworks generally want the extension as a file or folder they can pass at browser launch, not something installed through the Chrome UI.

The general pattern is:

  • Input: the downloaded CRX or the unpacked folder.
  • Action: pass it to the browser driver as an extension to load at startup (for Chrome-based drivers, this is typically an "add extension" or "load extension" argument pointing at the file or directory).
  • Expected result: the automated browser session starts with the extension already active, with no manual clicking.

Because the exact flag or option differs by driver and language binding, check your framework's documentation for the current syntax rather than copying an old snippet.

Why Chrome blocks direct CRX installation

Chrome restricts installation of extensions that don't come from the Chrome Web Store. Dragging a CRX onto the extensions page, or opening it directly, will usually be refused or silently ignored. This is a security measure, not a bug in your download.

The practical consequences:

  • For personal use, unpacking and loading in Developer Mode is the path that works.
  • For automation, loading the file through the driver sidesteps the store requirement entirely.
  • For simply reading the code, unpacking is all you need — no browser involved.

Which option fits your situation

Your goal Best approach
Run the extension in your own Chrome Unpack and load in Developer Mode
Use it in Selenium or similar tooling Pass the CRX/ZIP to the driver at launch
Inspect the extension's code or assets Unpack and open the folder
Install it normally, like a store extension Not possible from a downloaded CRX

If you're unsure which you need, start by unpacking the file — that single step serves inspection, local use, and most automation setups.