CAB and WIM: The Windows Archive Formats You Actually Meet
What CAB and WIM files are, why Windows uses them internally, and how to peek inside either one without extra software.
ilove7z Team · Oct 3, 2026 · 4 min read
Beyond ZIP and 7z, Windows ships with two archive formats of its own. You meet them whenever you poke around installers, system updates or deployment media - and they behave a little differently from everyday archives.
CAB: the cabinet format
CAB (cabinet) is Microsoft’s compressed container, used since the Windows 95 era. Its whole job is compact, reliable packaging of system files:
- Windows Update payloads and hotfixes ship as
.cab - Installer frameworks extract driver packages and runtime libraries from cabinet files
- The format supports folder-level compression and built-in integrity checks
CAB uses its own compression schemes (including Quantum and LZX historically), so generic ZIP tools often cannot read it - which is exactly why these files look like dead ends when you double-click one.
WIM: the imaging format
WIM (Windows Imaging Format) is the container behind Windows deployment. A install.wim on installation
media holds one or more complete Windows editions, and the format’s design serves that purpose:
- Deduplication: identical files between images are stored once
- Multiple images in one file: Home, Pro and Enterprise editions live side by side, indexed
- Alternate streams and metadata preserved for a faithful system image
WIM is a full system-image format, not a casual archiver - that is also why a single install.wim can easily
exceed 4 GB.
How they differ from ZIP
Neither format is meant for everyday file exchange. CAB exists for compact, verifiable delivery of system files; WIM exists for capturing and reproducing entire Windows installations. Both are read targets for most people - you extract from them, you do not create them.
Opening them without extra tools
You can look inside either format straight from the browser:
- Extract CAB archives - useful when a driver or hotfix you need is buried inside an update package.
- Extract WIM images - to pull files or editions out of deployment media.
Both run locally in your browser with WebAssembly: the file is never uploaded, and you get the complete file tree with selective download. No admin rights, no installation, no Windows version requirements.