What is an MSI file and how do you unpack it without installing?
An MSI extractor reads the Windows Installer Compound File Binary (CFB/OLE2) container directly in your browser up to 512 MB, extracts SummaryInformation metadata, decodes obfuscated table names, lists files inside embedded CAB streams, and saves raw CABs or streams without installing software.
Unlike a ZIP archive, an .msi is an OLE2 Compound File holding a relational database and embedded Microsoft Cabinet (MSCF) streams. Generic unzip utilities fail because there is no ZIP central directory. EasyExtract walks the CFB header, FAT, mini-FAT (for streams under 4 KB), and directory entries directly in JavaScript, decoding Microsoft's 0x3800-0x4840 stream-name encoding back into readable names such as File, Directory, and _StringData.
| Extraction Method | Works Without Installing | Reads SummaryInfo & Streams | CAB Decompression | Operating Systems |
|---|---|---|---|---|
| EasyExtract MSI Extractor | Yes (browser RAM, up to 512 MB) | Yes (decodes 0x3800-0x4840 names + lists CFFILE index) | Saves raw .cab and .bin streams | Windows, macOS, Linux, Chromebook |
msiexec /a (Windows CLI) | Yes (administrative unpack) | No table viewer | Full tree extraction to TARGETDIR | Windows only |
| 7-Zip (Desktop) | Requires 7-Zip install | Shows raw encoded stream names | Decompresses MSZIP and LZX CABs | Windows, Linux CLI |
| EasyExtract EXE Extractor | Yes (PE headers & ZIP SFX) | Identifies MSI wrapper; inspects PE signatures | Unpacks ZIP SFX; points MSIs here | All browsers |
For a breakdown of installer database tables and payloads, read what is inside an MSI file or how to open and extract MSI files on Mac.
How to extract an MSI file online
- Open the package. Drop the .msi, .msp, .msm, or .mst file onto the box above, or click to browse. The Compound File Binary structure is parsed locally in browser memory.
- Read the package details. Review Product name, Manufacturer, Package code, Platform and language, Schema version, build tool, and timestamps parsed from SummaryInformation.
- Inspect the files inside. Switch to Files inside to list every file in any embedded MSCF CAB stream (up to 400 rows previewed, full list in the TXT report).
- Save the CAB or individual streams. Download the embedded .cab stream to extract compressed payloads with 7-Zip or Windows Explorer, or save any decoded database stream as .bin.
What the extractor reads from the package
- Product and publisher details: Product name, Manufacturer, Title, Comments, and Keywords from the package
SummaryInformationstream. - Package code: The GUID that uniquely identifies a specific MSI build for deployment and SCCM verification.
- Target platform and language: For example
Intel;1033for 32-bit English orx64;1033for 64-bit English. - Build details: The authoring tool (
Created with), schema version, security flags, and Created / Last saved timestamps. - Embedded CAB inventory: Every stream starting with the
MSCFcabinet signature is parsed for folder count andCFFILEentries (filename, byte size, modification date), and saved as a downloadable.cab. - All database streams: Sorted largest-first with decoded table names and individual
.binexport buttons.
Supported packages and size limits
Primary support covers .msi packages, plus .msp patches, .msm merge modules, and .mst transforms that share the OLE2 Compound File Binary format.
Both 512-byte and 4096-byte CFB sector layouts parse locally. Files up to 512 MB open directly in browser memory; larger packages stop with an explicit memory-guard message pointing to desktop 7-Zip.
Why the package is never uploaded
The Compound File Binary parser runs completely in local JavaScript inside your browser tab, so zero package bytes cross the network.
Enterprise MSI installers frequently embed internal server hostnames, licence keys, and custom configuration inside property streams. Inspecting packages locally keeps proprietary deployment artifacts off third-party cloud servers.
What this tool does not do
Three technical boundaries apply:
- It does not decompress MSZIP or LZX CAB payloads: Browsers lack native MSZIP/LZX decoders, so EasyExtract lists the files inside each embedded CAB and lets you save the raw
.cabto unpack with 7-Zip or Windows Explorer. - It does not decode relational MSI rows into SQL tables: Database streams are decoded by name and downloadable as
.bin, but_StringDatarelational lookups are not joined into spreadsheets. - It does not install, modify, or execute code: Reading is strictly static and read-only.
On Windows, unpack the full directory tree natively without installing software by running msiexec /a package.msi /qb TARGETDIR=C:\out in Command Prompt.
Who inspects MSI packages
- Deployment and Intune/SCCM administrators: Checking the Package code GUID, Product name, and platform architecture before pushing software to endpoints.
- macOS and Linux engineers: Reading Windows MSI metadata and extracting embedded CAB payloads without booting Windows or Wine.
- Security reviewers: Inspecting publisher details and file inventories before executing an unfamiliar installer.
- Release and packaging engineers: Verifying that a freshly built installer contains expected streams and CAB file counts.
MSI packages compared with EXE and ZIP containers
An MSI is a relational Windows Installer database container, whereas an .exe is a Portable Executable binary that runs arbitrary installer logic. Many downloads wrap an MSI inside an EXE bootstrapper.
For .exe installers, use the EXE file opener and extractor to inspect PE signatures, strings, and ZIP SFX payloads. To pull only application icons from executables, use the EXE icon extractor. For plain archives, open the ZIP extractor or browse all archive and executable tools.
MSI format internals and extraction edge cases
A Windows Installer (.msi) file is a Compound File Binary Format (CFBF) container —
the same format used by .msg files. Inside, database tables are stored as CFBF streams with
names encoded using a proprietary scheme. The binary payload is in the
_Streams table or in a Cabinet (CAB) archive referenced by the
Media table.
Three edge cases: (a) a compressed MSI stores its CAB file as a stream in the
_Streams table — the extractor reads that CAB stream and lists the installation
files it contains; (b) transform files (.mst) patch the MSI's table data at install time
but are separate files — the extractor reads the base MSI, not any applied transforms;
(c) merge modules (.msm) share the MSI format but lack a Product GUID and cannot be
installed directly — they are intended to be merged into MSI packages at build time; the
extractor reads and lists their contents identically to a regular MSI. For a complete breakdown of what is inside an MSI file, including the Property, File and Registry tables, see the guide.
Frequently asked questions
Can I extract an MSI file online?
Yes. Drop an .msi file above to read SummaryInformation details, list every file inside embedded CAB streams, and download raw .cab or .bin streams in-browser. To decompress MSZIP/LZX CAB contents, open the saved .cab with 7-Zip or Windows Explorer.
How do I extract files from an MSI without installing it?
Drop the file here to inspect metadata and save its CAB stream on any OS, or run an administrative unpack on Windows Command Prompt: msiexec /a package.msi /qb TARGETDIR=C:\out.
Why can't I just unzip an MSI?
An MSI uses the OLE2 Compound File Binary format rather than a ZIP central directory, so standard unzip tools cannot read its streams.
Is my MSI uploaded to a server?
No. The CFB parser runs in JavaScript inside your browser tab with zero server uploads.
What is the package code?
A GUID in SummaryInformation identifying a specific MSI build so deployment systems can distinguish builds even when version numbers match.
Why does my package show no embedded CAB?
Uncompressed MSI installers store payload files alongside the .msi or inside external .cab files in the original download folder.
What are the obfuscated stream names?
Windows Installer encodes table stream names into Unicode range 0x3800-0x4840. EasyExtract decodes them back to readable names such as File and _StringData.
Does it work on macOS, Linux, or Chromebook?
Yes. Parsing executes inside your browser, letting you inspect Windows MSI files on any operating system.