CONVERT
CAB → ZST
Tap to choose your fileDRAG. DROP. DONE.
Upload any file and our engines will handle format detection automatically.
Max 25 MB · Free plan · No signup required
Convert to:
Detecting available formats...
Optimize for
Leave empty to use original name. Extension added automatically.
Uploading...
Processing your file...
Fast, secure CAB to ZST conversion. No registration required.
Why this pair exists — CAB is Microsoft's Cabinet archive format used in Windows installer packaging. Ergo, the ZST route. Going from CAB to ZST converts the wrapper around a collection of files. If your workflow speaks ZST and the backup you were sent is a CAB, this tool rewraps the bundle for you without asking you to extract and re-compress by hand — and without leaving a scratch folder behind. Background. CAB is Microsoft's Cabinet archive format used in Windows installer packaging. Destination side, ZST is a compression/archive format used to package or shrink files.
Windows Cabinet
Source formatCAB (Cabinet) is a Windows archive format used for software installers.
Zstandard Compressed
Target formatZstandard (Zstd) is a fast lossless compression algorithm developed by Yann Collet at Facebook. It provides compression ratios comparable to zlib while being 3-5x faster at both compression and decompression, making it ideal for real-time data processing.
Why convert CAB to ZST
Some ZST formats support features CAB lacks: solid compression across many small files, per-file encryption, streamable headers. Repacking a legacy CAB into a modern ZST is how you opt into those features without changing any of the files inside.
HOW TO CONVERT
CAB → ZST
Start the job
Upload a CAB; we read its header to learn how many entries it carries and the compression method used.
Transcode container
Every entry is decompressed, then recompressed with the ZST codec at a balanced default level.
Save the result
Download the ZST when ready. Nothing about the original contents is logged or retained.
Common Use Cases
Share across platforms
Send ZST files to anyone without worrying about whether they have the right software for CAB.
Embed in documents
Drop ZST output into Word, Google Docs, PowerPoint, Notion or a website without conversion warnings.
Optimize size
ZST often produces smaller files than CAB for web, email and storage.
Archive & future-proof
Store in a widely-supported format that will still open on future operating systems without legacy plugins.
CAB vs ZST — Strengths and limitations
What each format does best, and where it falls short.
CAB Strengths
- Multi-volume — designed for disk-spanning archives.
- Multiple compression algorithms in one format.
- Native Windows support for 30+ years.
- Authenticode signing integrates with Windows security stack.
- Microsoft-maintained tooling (MAKECAB, EXTRAC32, expand.exe).
Limitations
- Windows-only ecosystem — limited Mac/Linux tooling.
- Proprietary container with partial public documentation.
- Overtaken by MSI (which uses CAB internally) for new installers.
ZST Strengths
- Extremely fast decompression (~2 GB/s on modern CPU).
- Scalable: very fast at level 1, near-xz ratios at level 22.
- Dictionary support for small-payload efficiency.
- Multi-threaded by default.
- Standardized (RFC 8478), BSD-licensed reference.
Limitations
- Newer than gzip/bzip2 — some legacy tools still lack support.
- At extreme compression levels, xz can still win on ratio.
- Memory usage at high levels is significant.
CAB vs ZST — Technical specifications
Side-by-side comparison of the technical details.
CAB
- MIME type
- application/vnd.ms-cab-compressed
- Extension
- .cab
- Compression
- MSZIP (DEFLATE), Quantum, LZX
- Max volume size
- 2 GB per file
- Multi-volume
- Yes (split archive spanning)
ZST
- MIME type
- application/zstd
- Extension
- .zst
- Algorithm
- LZ77 variant + entropy coding (FSE/Huffman)
- Standard
- RFC 8478 (2018)
- Compression levels
- 1-22 (plus negative "fast" levels)
| Specification | CAB | ZST |
|---|---|---|
| MIME type | application/vnd.ms-cab-compressed | application/zstd |
| Extension | .cab | .zst |
| Compression | MSZIP (DEFLATE), Quantum, LZX | — |
| Max volume size | 2 GB per file | — |
| Multi-volume | Yes (split archive spanning) | — |
| Algorithm | — | LZ77 variant + entropy coding (FSE/Huffman) |
| Standard | — | RFC 8478 (2018) |
| Compression levels | — | 1-22 (plus negative "fast" levels) |
CAB vs ZST — Typical file sizes
Approximate file sizes for common scenarios.
CAB
- Single driver package 100 KB - 20 MB
- Windows Update patch 1-500 MB
- Service pack archive 200 MB - 2 GB
ZST
- Default level 3 on source code 28-35% of original
- Level 22 ultra on source code 14-18% of original
- Linux kernel (.tar.zst, level 19) ~130 MB
Quality & Compatibility
File attributes that both formats understand (modification time, Unix permissions, symlinks) round-trip cleanly. Obscure metadata that one side lacks (e.g., advanced ACLs in one direction) is dropped silently rather than causing the conversion to fail.
Tips for Best Results
- Archives with thousands of tiny files benefit hugely from "solid" compression (one of the Advanced options) — ZST formats that support it can shrink 20-50% over per-file compression.
- When the CAB contains symlinks, test that they still resolve after conversion; some ZST formats represent them differently on Windows vs Unix.
- Deterministic timestamps (via Advanced → reset mtimes) make the ZST reproducible for CI artefact verification; otherwise two "identical" conversions will produce slightly different bytes.
Frequently Asked Questions
Yes. The free tier accepts files up to 25 MB without registration, email capture or watermarks; paid plans go up to 2 GB. Paid plans raise the size cap, enable batch conversions and provide a REST API for automation, but nothing on the free tier is quality-limited — the output is exactly the same as on any paid plan.
Yes — because CAB and ZST use different compression codecs, every entry is decompressed from the CAB and re-compressed for the ZST. The uncompressed data is identical on both sides, and the re-compression happens entirely inside our processing container.
Uploads run over HTTPS, files are processed in isolated containers, and both the source CAB and the ZST output are auto-deleted within two hours. No account is required, file contents are never logged, and KaijuConverter does not use uploads for AI training. The paid plan adds a signable data-processing agreement for regulated workflows.
Usually yes, modestly, when the original CAB used an older codec like Deflate. Against modern LZMA2 / Zstd ZST containers expect 10-30% savings on mixed content and almost no change on pre-compressed payloads. Advanced → compression level lets you trade speed for ratio.
Most files finish in well under a minute. Small images and documents are typically ready in a few seconds; large video or audio files scale roughly with duration. Upload speed from your network is usually the dominant factor, not server time.
Yes. Provide the password during upload; we use it only to decrypt inside the processing container and never log or persist it. The resulting ZST can be re-encrypted with a password of your choice (AES where the target format supports it).
Related comparisons
See these formats side by side to understand which fits your use case best.
Related Guides
Zstandard & LZ4: The Modern Compression Formats Replacing Gzip
Complete guide to Zstandard (ZST) and LZ4 — the modern compression algorithms replacing Gzip in Linux, Docker, databases, and package managers.
Read guideArchive Formats Compared: ZIP, 7Z, RAR, TAR, and ZSTD
Complete comparison of ZIP, 7-Zip, RAR, TAR.GZ, TAR.XZ, and Zstandard archive formats. Compression ratio, speed, encryption, and when to use each format.
Read guideSecure & Private Conversion
Your files are encrypted during transfer, processed in isolated containers, and automatically deleted within 60 minutes. We never read, share, or store your data.