MSI Extractor Online

Inspect files inside an MSI package without installing it. Extract supported embedded cabinets and browse the application payload.

Drop your MSI package here
Choose file

⚠ 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.

Extract MSI files without installing

  1. Upload your .msi package. No Windows installation or administrator access is needed on your computer.
  2. Browse files recovered from embedded cabinets, alongside the package's database streams.
  3. Inspect supported application code or download the extracted result as a ZIP.

Application files and MSI database streams

An MSI is a Windows Installer database. Its application files may be compressed in embedded CAB archives, supplied in external cabinets or stored separately. This extractor opens supported embedded cabinets to recover the files inside them. Raw database streams are listed separately and are not themselves the installed application.

Recovered .NET DLLs and EXEs can produce readable C# source. Other supported nested formats may expose JavaScript, Java, Lua or Python code. Native binaries remain available for inspection; extraction does not turn every DLL into original source.

External CAB files and original filenames

If your MSI needs an external cabinet, put the MSI and the supplied CAB files in a ZIP named application.installer.zip and upload that bundle. Each cabinet is opened independently. Missing companion files are not downloaded. To inspect one cabinet on its own, use the CAB file extractor.

Cabinet members may keep file IDs instead of their installed names. The extractor does not reconstruct the MSI Directory table's installation paths, apply transforms or execute custom actions. It is not an MSI editor or a complete database-table viewer.

MSI extraction questions

Can I extract an MSI without running the installer?

Yes. The package is read on the server and supported embedded cabinets are extracted. No installation, registry change or MSI custom action is performed.

Can I decompile an MSI to source code?

Supported assemblies and other code inside the package can be decompiled after extraction. Converting the MSI database back into WiX XML or an original installer project is a different task and is not provided here.

Why do I see file IDs instead of filenames?

Some cabinets store MSI file identifiers. Mapping those identifiers to the names and folders used during installation requires the MSI tables. This tool preserves the extracted member names rather than rebuilding the installed directory tree.

Why does my MSI show no application files?

The payload may live in external CAB files or loose files that were not uploaded, or the package may use an unsupported layout. Database streams alone do not mean that application files were recovered.

Extraction limits and partial results

Each upload shares a five-minute extraction and source-recovery budget, with up to 1 GiB of expanded data, 256 MiB per file, 25,000 entries and four nested layers. Worker limits can stop processing sooner. You can browse completed files while processing continues; a ZIP download becomes available when the job finishes.

If a format, version or file cannot be processed, the result explains the limitation and keeps files already recovered. Extraction does not recreate a complete buildable application or the original native source code.