Microsoft Cabinet MIME Type

Learn what application/vnd.ms-cab-compressed means, how to identify and extract CAB archives, and how Poly handles .cab files.

MIME type details for application/vnd.ms-cab-compressed

In active use
MIME typeapplication/vnd.ms-cab-compressed
Extensions
.cab
Magic number4D 53 43 46
First standardized2005
Created byMicrosoft Corporation
Browser supportNo native browser support
Example applicationsWindows expand, 7-Zip
Poly supportPartial. Poly recognizes .cab as application/vnd.ms-cab-compressed and stores, syncs, shares, and versions the archive, but does not extract it.
Indexed by PolyPartial. Poly indexes the CAB archive's filename and ordinary file properties, but not its member names or contents.
Preview in PolyNo. Poly has no in-app CAB browser or extractor; download the archive and open it with a compatible utility.
Poly agentNo. The Poly agent cannot read or reason about files packed inside a CAB archive.

What does application/vnd.ms-cab-compressed mean?

The application/vnd.ms-cab-compressed media type identifies a Microsoft Cabinet archive. A CAB file is a binary container, normally named with the .cab extension, that packages one or more related files and can compress their data.12

Microsoft designed the format for Windows software distribution and installation workflows. Windows Installer can keep a cabinet either as a separate file or as a data stream embedded inside an .msi package.3 CAB is still its own archive format, however. A .cab file is not an MSI database, ZIP archive, or executable.

The vnd. portion marks this as a vendor-tree media type. IANA registered the subtype in December 2005 and lists Microsoft Corporation as its author and change controller.1 That date belongs to the media-type registration, not the much older CAB format itself.

How do you identify a CAB file?

A standard CAB file starts with the ASCII characters MSCF, represented by the bytes 4D 53 43 46. Microsoft's format specification defines this four-byte signature as the first field in the cabinet header and uses it to confirm that the file is a cabinet.2

The opening bytes typically look like this:

4D 53 43 46 00 00 00 00 ...
 M  S  C  F

IANA's 2005 registration says “Magic number(s): none,” while Microsoft's later published format specification explicitly defines the MSCF signature.12 This page uses the format specification for file identification and notes the discrepancy rather than treating the registration's older field as a description of the current specification.

An extension or four-byte signature is only an initial check. A valid parser must also read the header offsets, folder and file records, data blocks, and checksums. Renaming package.zip to package.cab does not convert it.

How is a Cabinet archive organized?

The CAB format groups file data into folders. In CAB terminology, a folder is a compression unit, not necessarily a directory from the original file system. Every stored file belongs completely to one folder, while a folder can continue across multiple cabinet files in a linked set.2

PartWhat it records
Cabinet headerSignature, total cabinet size, file-table offset, version, folder count, file count, and set information
Folder recordsWhere each folder's compressed data begins, its data-block count, and its compression method
File recordsUncompressed size, offset within a folder, date, time, attributes, and filename
Data blocksChecksummed chunks containing stored or compressed bytes

Microsoft's specification supports uncompressed data, MSZIP, and LZX compression.2 Compression can work across file boundaries within a folder, which Microsoft notes can improve the ratio when several related files are packaged together.4 The tradeoff is that a program may need to decode a shared stream to recover an individual member.

CAB sets were designed for distribution media with size limits. A large folder may span several numbered cabinets, and each cabinet header can name the logically previous and next files in the set.2 If you receive only one part of such a set, extraction may fail even though its MSCF header is valid.

How do you open an application/vnd.ms-cab-compressed file?

Web browsers do not provide a native CAB archive browser. They normally hand the file off as a download. Use an archive utility and inspect the member list before extracting.

Windows includes the expand command. Microsoft documents these forms for listing and extracting cabinet contents:5

expand -d package.cab
expand package.cab -f:* output

The destination directory must already exist when extracting multiple files. The -d form lists members without writing them. Microsoft also provides makecab for creating cabinets.6

7-Zip is a cross-version Windows option with a graphical file manager and command-line interface. Its official format list includes CAB as an unpack-only format, so it can extract a CAB but does not create one.7

Extract an unfamiliar cabinet into a new, empty directory. This keeps its members separate from trusted files and makes unexpected executables, scripts, or duplicate names easier to review.

Support in Poly

Poly recognizes .cab filenames as application/vnd.ms-cab-compressed and classifies them as archives. You can store, sync, share, version, download, and find the CAB file by name.

Poly treats the payload itself as opaque:

  • It does not extract the cabinet or index member filenames and contents.
  • It does not generate a thumbnail or provide an in-app archive browser.
  • Search can match the CAB file's name and ordinary Poly properties, but not text packed inside it.
  • The Poly agent cannot inspect or reason about the archived members.

Download and extract the cabinet with a trusted utility when you need its contents. If you add the extracted files to Poly separately, each file can use the processing pipeline available for its own format.

Is a CAB file the same as an MSI file?

No. A CAB is an archive of file payloads. An MSI is a Windows Installer package whose database describes components, features, installation actions, and source media.

The two formats often work together. Windows Installer may reference a separate cabinet at the root of its source tree, or store a cabinet as a stream inside the MSI package.3 Extracting that cabinet reveals payload files, but it does not reproduce or execute the installation logic held in the MSI database.

Do not change a CAB extension to .msi or .exe. If your goal is only to inspect files, extract them. If the cabinet is part of a trusted driver, update, or application installer, follow the publisher's installation instructions instead of guessing from the extension.

How do you convert CAB to ZIP?

Archive conversion is a two-step operation: extract the CAB members, then create a new ZIP archive from those files. It changes the container, not the formats of the member files.

ZIP is usually a practical choice when recipients need broad archive-tool compatibility. Keep the original CAB when it belongs to an installer or a linked cabinet set. Repacking can discard CAB-specific organization and will not update an MSI or other package that expects the original cabinet name, layout, or checksums.

Avoid uploading private or proprietary cabinets to an online conversion service. Conversion requires the service to receive and extract every archived member. Local tools keep that content on your machine.

Security considerations

IANA's registration says the security issues for this media type had not been assessed.1 That is not a claim that CAB files are safe. A cabinet can carry programs, scripts, drivers, or other active content, and extraction turns those members into ordinary files on disk.

List the archive first, extract it into an isolated directory, and scan the results before opening or running anything. Be especially careful when a cabinet arrived unexpectedly or asks to be installed with elevated privileges. A valid header confirms the container format, not the trustworthiness of its contents.

Footnotes

  1. Internet Assigned Numbers Authority. application/vnd.ms-cab-compressed Media Type Registration. The registration documents the subtype, .cab extension, December 2005 date, Microsoft change control, and unassessed security considerations. 2 3 4
  2. Microsoft Corporation. MS-CAB: Cabinet File Format. The specification defines the MSCF signature, headers, folders, files, data blocks, cabinet sets, and compression methods. 2 3 4 5 6
  3. Microsoft Learn. Cabinet. The Windows Installer documentation distinguishes external cabinets from cabinet streams embedded in MSI packages. 2
  4. Microsoft Learn. Cabinet Files. Microsoft describes CAB as a compressed file library and explains compression across file boundaries.
  5. Microsoft Learn. expand. The command reference documents listing and extracting files from cabinets.
  6. Microsoft Learn. makecab. The command reference documents packaging existing files into a cabinet.
  7. 7-Zip. 7-Zip. The official feature list includes CAB among its unpack-only formats.
© Poly Corp. 2026