What Is a CAB File and Why Would You Encounter One on Mac?
CAB (Cabinet) is a compressed archive format developed by Microsoft for software distribution since the Windows 95 era. Windows uses CAB files internally in MSI installers, Windows Update packages (.msu and .cab), driver stores, Office installation media, and Internet Explorer extension packages. Mac users encounter CAB files in several practical scenarios: downloading cross platform fonts bundled in Windows installers that are not available through other channels, accessing driver configuration files for peripherals that ship with Windows only software, extracting resources from Windows applications for compatibility analysis or cross platform development, and working with legacy enterprise software distributions in mixed OS environments. CAB files use a combination of MSZIP, LZX, and Quantum compression algorithms that are not recognized or supported by macOS Archive Utility, which means double clicking a .cab file in Finder produces no result.
How Do You Extract a CAB File on Mac with UnFox?
Drag the .cab file onto UnFox. The app reads the Cabinet archive header and displays the internal file list with individual file sizes and the total uncompressed footprint. Click "Extract Here" to unpack all contents to a folder alongside the CAB file, or use the keyboard shortcut to choose a custom destination. UnFox handles MSZIP and LZX compressed CAB files through its libarchive backend, which includes native implementations of both decompression algorithms. Extraction preserves the internal directory structure faithfully, including deeply nested folder hierarchies that some CAB files use to organize hundreds of files. You can download UnFox free from the Mac App Store and start extracting CAB files without installing Homebrew, cabextract, or any other command line dependency.
Tip
Press Cmd+Shift+E in UnFox to choose a specific destination directory for extracted files.
What Files Are Typically Inside a CAB Archive?
CAB files from Windows installers commonly contain DLL libraries, EXE executables, INF driver configuration files, SYS driver binaries, MUI localization resources, and XML manifests that describe component relationships. Font distribution CABs contain TTF or OTF font files alongside license documents and installation scripts. Windows Update packages include system files organized by architecture (x86, x64, ARM64) with accompanying catalog files for signature verification. For Mac users, the most practically useful contents are font files that can be installed directly on macOS, documentation in PDF or HTML format, configuration templates that reveal software settings, and media assets like icons, images, and sound files. DLL and EXE files extracted from CAB archives cannot run on macOS natively, but their resources (icons, images, embedded strings) can be examined with resource extraction tools.
Can You Extract CAB Files on Mac with the Terminal?
macOS does not include a native CAB extraction utility in the Terminal. The open source "cabextract" tool can be installed through Homebrew with "brew install cabextract" and provides command line CAB extraction with support for all Microsoft compression methods. The Python standard library does not include CAB support, though third party packages exist. For users who prefer a graphical interface over command line tools, UnFox provides drag and drop CAB extraction with progress tracking, file previews, and disk space validation. UnFox requires no Homebrew installation, no Terminal configuration, and no familiarity with command line arguments.
CAB Compared to Other Windows Archive Formats on Mac
CAB is one of several Windows specific archive formats that Mac users encounter when working across platforms. WIM (Windows Imaging Format) is used for Windows installation media and system deployment, and opening WIM files on Mac follows a similar extraction pattern through UnFox. SFX (self extracting) archives are another Windows distribution format that bundles an extraction engine inside an executable file, and opening SFX files on Mac follows the same drag and drop extraction approach since UnFox reads the archive payload without running the Windows executable. Both CAB and WIM appear frequently in enterprise IT environments where Mac workstations need to access Windows infrastructure resources, driver packages, or system configuration files. UnFox handles all of these Windows formats alongside the complete list of 37 archive and compression formats, providing a single tool that bridges the gap between the two operating systems for IT professionals and developers.
Extracting Fonts and Resources from Windows CAB Files
One of the most common reasons Mac users open CAB files is to extract fonts that are distributed exclusively through Windows installers. Microsoft’s core fonts for the web, specialized typography packages for enterprise use, and regional font collections for CJK character sets often ship inside CAB archives embedded within MSI or EXE installers. After extracting the CAB file with UnFox, the TTF or OTF font files can be installed on macOS by double clicking them in Finder, which opens Font Book for preview and installation. Graphic designers working on cross platform projects also extract icon resources, bitmap images, cursor files, and UI assets from Windows application CABs to maintain visual consistency between platforms or to reference Windows UI elements in documentation. Enterprise administrators extract INF driver configuration files from CAB archives to review peripheral settings, identify driver versions, and prepare deployment configurations before rolling out hardware across a mixed fleet of Mac and Windows machines. The extraction process with UnFox is completely safe for Mac systems.
Note
Extraction only reads and copies file data. No Windows binaries, scripts, or installer logic are executed.
Troubleshooting CAB Extraction Issues on Mac
CAB files occasionally present extraction challenges on Mac for a few predictable reasons. The most common issue is encountering a CAB file embedded inside an MSI installer rather than stored as a standalone archive. MSI files use the OLE Compound Document format, which wraps the CAB payload in an additional container layer. If UnFox does not recognize the file, it may be an MSI wrapper rather than a standalone CAB. Tools like msiextract (available through Homebrew) can separate the CAB streams from the MSI container, after which UnFox handles the extracted CAB files normally. Incomplete downloads from Windows Update catalogs or driver distribution sites produce truncated CAB files that fail during decompression. Re downloading the file and comparing its size against the published file size on the source website resolves this in most cases. Some older CAB files use the Quantum compression algorithm, which is less commonly supported than MSZIP and LZX. UnFox handles MSZIP and LZX natively through its libarchive backend. If a CAB file uses Quantum compression and extraction fails, the cabextract command line tool (installable via Homebrew) provides broader algorithm support as a fallback option.
