ExtPose's CRX Viewer opens the source code of any published Chrome or Edge extension right in your browser. There is nothing to install and nothing saved to your machine. Paste a store link or extension ID and start reading the files.
What you can see
The viewer fetches the extension's package, unpacks it in the browser, and shows:
- A full file tree of everything shipped inside the extension
manifest.json, including the permissions and host access it requests- Background and content scripts, popup pages, and stylesheets
- Icons, images, and localized message files
Syntax highlighting makes the JavaScript, JSON, HTML, and CSS easy to follow.
How to view an extension's code
- Copy the extension's Chrome Web Store or Edge Add-ons URL, or its 32-character ID.
- Paste it above. The store is detected automatically from a link, and the Chrome / Edge toggle lets you override it.
- Click View code. The file browser opens in a panel, and you click any file to read it.
Why read extension source code
- Check which permissions an extension uses and whether it loads remote code or sends data to outside servers.
- See what an extension actually does before installing it on a work machine or recommending it to a team.
- Learn how popular extensions structure their manifest, background workers, and content scripts.
- Compare versions over time, or work out how a competing extension is built.
What to look for
- The
permissionsandhost_permissionsin the manifest. Broad host access such as<all_urls>is worth a closer look. - Code that fetches and runs remote scripts, which can change an extension's behavior after you install it.
- Heavily obfuscated or minified code that hides what it actually does.
- Network requests to domains you do not recognize.
Viewer or download?
The viewer is read-only and runs in your browser, so it is the quickest way to glance at how an extension is built. If you need the files locally (to diff versions, run your own tooling, or load the extension unpacked), use the CRX Downloader instead.