XPI Viewer and Extractor Online

Paste a store link or upload a file to inspect an extension's code and permissions without installing it.

Open from a store link

Public Chrome Web Store and Firefox Add-ons links are supported. The package is downloaded and inspected on our servers.

Have a Chrome extension? You can paste its link here or use the Chrome CRX viewer.

Or upload an extension

Drop your CRX or XPI file here

⚠ Drag-and-drop upload could not load — an ad blocker is most likely blocking it. Please disable your ad blocker and reload the page to upload a file.

Open Firefox XPI extensions

The XPI viewer reads WebExtension Manifest V2 and V3 packages. Inspect Firefox identity, background and content scripts, ordinary and optional permissions, host declarations and resources. A declared permission describes requested access; it is not a malware verdict.

example.xpi/
  EXTENSION-SUMMARY.txt
  extension.json
  files/manifest.json
  files/background.js
  files/icons/icon.svg

Legacy non-WebExtension XPI packages are explicitly labeled. Their install.rdf, chrome.manifest and bootstrap.js remain available as data; the viewer does not invent a modern manifest or permission model. Unsupported legacy metadata receives diagnostic notes.

Browse and download extension files

The result shows the extension name, provider, package version, declared permissions, host access and entry scripts above the file browser. Store imports fetch an available public version; the result identifies the version actually downloaded. If the store cannot supply a package, upload a local CRX or XPI instead.

Processing runs on our servers. Start with EXTENSION-SUMMARY.txt and extension.json, then open original files under files/. Relative paths remain navigable. Download individual members or the complete result ZIP. Recovered C# is kept under recovered/ with assembly provenance in the report.

Uploaded HTML, JavaScript and SVG follow the site's inert text or isolated image preview boundaries. Extensions, hooks, npm scripts and native hosts are never installed or executed. Dependencies and referenced URLs are not downloaded. Signature verification is not performed.

Limits and source recovery

Select a bundled script or source map for JavaScript recovery: export embedded original source text or split supported bundles into modules. Original TypeScript, names and comments require supplied source text; formatting alone is not original-source recovery. Native, Hermes, V8 and custom bytecode use separate paths.

Metadata reads are limited to 1 MiB per manifest or CRX header. ZIP64 and split ZIPs are unsupported. Extraction shares the existing five-minute parent budget, 1 GiB expanded data, 256 MiB per file, 100,000 entries and four nested layers; worker limits may stop processing earlier. Each assembly recovery gets up to 30 seconds within that budget. Complete extracted files remain available after a failure; check DECOMPILATION-NOTES.txt for details.

Related viewers: CRX, XPI, VSIX, Electron ASAR and packaged JavaScript, .NET DLL decompiler and NuGet package viewer.