Who makes CRX?
What is a CRX file?
Who makes CRX?
How packaging works
The steps below outline the typical lifecycle from authoring to a packaged CRX ready for distribution.
- Develop the extension code and a manifest.json that declares permissions, background scripts, and UI elements.
- Test the extension locally in a Chrome profile to ensure it behaves as expected and complies with policies.
- Package the extension using Chrome's packaging tools (or via the Web Store uploader), generating a signed file (CRX) and a private key for future updates.
- Publish the extension to the Chrome Web Store or distribute it within an enterprise environment, where installation may be managed by policy.
- Users install the extension from the Store or via enterprise deployment, after which updates are delivered through Chrome.
In short, CRX files are produced through Google's packaging tooling, but the actual software inside is authored by developers; distribution is handled by Google via the Chrome Web Store, or by organizations through policy-based deployment.
Security and provenance
Because CRX files are the vehicle for browser extensions, users should only install from trusted sources like the Chrome Web Store or known enterprise distributions. Developers sign their extensions with a private key, and Chrome verifies the signature before installation, helping to prevent tampering and impersonation.
Summary
CRX is the Chrome extension package format created and maintained by Google as part of the Chrome/Chromium project. The content inside a CRX is authored by independent developers, while Google provides the packaging framework, signing, and distribution channels. Understanding this lifecycle clarifies who makes CRX and how Chrome extensions reach users.
