VSIX Viewer and Extractor Online

Inspect an extension's identity, entry points and packaged files without installing it.

VS Code and Visual Studio VSIX packages

These are two different extension ecosystems. VS Code extensions contain extension/package.json and usually JavaScript: inspect publisher, version, engine constraints, main/browser entry points, activation events, contributions and capabilities. Visual Studio VSIX packages contain OPC/VSIX metadata and may include managed assemblies. Supported assemblies are decompiled to C# through ILSpy.

vscode-example.vsix/
  EXTENSION-SUMMARY.txt
  extension.json
  files/extension.vsixmanifest
  files/extension/package.json
  files/extension/dist/extension.js

visual-studio-example.vsix/
  files/[Content_Types].xml
  files/extension.vsixmanifest
  files/Example.dll
  recovered/Example.dll/source.cs

VSIX schema 2.x is supported. Legacy schema 1.x and unsupported layouts retain available files with explicit notes. Missing recovery tools or unsupported assemblies leave original files available. C# recovery is distinct from extraction of already packaged scripts.

Browse and download extension files

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

Bundled JavaScript and source maps are preserved as supplied. Original TypeScript, names and comments are not reconstructed, and formatting minified code is not original-source recovery. See source-map recovery work for that separate feature. Native, Hermes, V8 and custom bytecode do not pass through a generic JavaScript decoder.

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, 25,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.