免费转换 CAB 文件

专业的 CAB 文件转换工具

将您的文件拖放到这里

或点击浏览文件

最大文件大小:100MB
10M+ 已转换文件
100% 永久免费
256位 安全加密

支持的格式

以高质量在所有主要文件格式之间转换

常见格式

ZIP

ZIP Archive - universal compression format developed by Phil Katz (1989) supporting multiple compression methods. Built into Windows, macOS, and Linux. Uses DEFLATE algorithm providing good compression (40-60% reduction) with fast processing. Supports file encryption, split archives, and compression levels. Maximum compatibility across all platforms and devices. Perfect for file sharing, email attachments, web downloads, and general-purpose compression. Industry standard with virtually universal software support including built-in OS tools, mobile apps, and command-line utilities.

RAR

RAR Archive - proprietary format by Eugene Roshal (1993) offering superior compression ratios (10-20% better than ZIP) through advanced algorithms. Popular on Windows with WinRAR software. Supports recovery records for damaged archive repair, solid compression for better ratios, strong AES encryption, and split archives up to 8 exabytes. Excellent for long-term storage, large file collections, and backup scenarios. Common in software distribution and file sharing communities. Requires WinRAR or compatible software (not built into most systems).

7Z

7-Zip Archive - open-source format by Igor Pavlov (1999) providing the best compression ratio available (20-40% better than ZIP, 10-15% better than RAR). Uses LZMA and LZMA2 algorithms with strong AES-256 encryption. Supports huge file sizes (16 exabytes), multiple compression methods, solid compression, and self-extracting archives. Free from licensing restrictions and patent concerns. Perfect for maximizing storage efficiency, software distribution, and backup archives where size matters. Requires 7-Zip or compatible software but offers exceptional space savings.

Unix Formats

TAR

TAR Archive - Tape Archive format from Unix (1979) bundling multiple files and directories into single file without compression. Preserves file permissions, ownership, timestamps, and symbolic links critical for Unix systems. Often combined with compression (TAR.GZ, TAR.BZ2, TAR.XZ) for efficient distribution. Standard format for Linux software packages, system backups, and cross-platform file transfer. Essential for maintaining Unix file attributes. Works with streaming operations enabling network transfers and piping. Foundation of Unix/Linux backup and distribution systems.

GZ/TGZ

GZIP/TGZ - GNU zip compression format (1992) using DEFLATE algorithm, standard compression for Linux and Unix systems. TGZ is TAR archive compressed with GZIP. Fast compression and decompression with moderate ratios (50-70% reduction for text). Single-file compression commonly paired with TAR for multi-file archives. Universal on Unix/Linux systems with built-in 'gzip' command. Perfect for log files, text data, Linux software distribution, and web server compression. Streaming-friendly enabling on-the-fly compression. Industry standard for Unix file compression since the 1990s.

BZ2/TBZ2

BZIP2/TBZ2 - block-sorting compression format by Julian Seward (1996) offering better compression than GZIP (10-15% smaller) at the cost of slower processing. TBZ2 is TAR archive compressed with BZIP2. Uses Burrows-Wheeler transform achieving excellent ratios on text and source code. Popular for software distribution where size matters more than speed. Common in Linux package repositories and source code archives. Ideal for archival storage, software releases, and situations prioritizing compression over speed. Standard tool on most Unix/Linux systems.

XZ/TXZ

XZ/TXZ - modern compression format (2009) using LZMA2 algorithm providing excellent compression ratios approaching 7Z quality. TXZ is TAR archive compressed with XZ. Superior to GZIP and BZIP2 with ratios similar to 7Z but as single-file stream. Becoming the new standard for Linux distributions and software packages. Supports multi-threading for faster processing. Perfect for large archives, software distribution, and modern Linux systems. Smaller download sizes for software packages while maintaining fast decompression. Default compression for many current Linux distributions.

TAR.7Z

{format_tar_7z_desc}

TAR.BZ

{format_tar_bz_desc}

TAR.LZ

{format_tar_lz_desc}

TAR.LZMA

{format_tar_lzma_desc}

TAR.LZO

{format_tar_lzo_desc}

TAR.Z

{format_tar_z_desc}

TGZ

TGZ - TAR archive compressed with GZIP compression. Combines TAR's file bundling with GZIP's compression in single extension (.tgz instead of .tar.gz). Standard format for Linux software distribution and source code packages. Maintains Unix file permissions and attributes while reducing size 50-70%. Fast compression and decompression speeds. Universal compatibility on Unix/Linux systems. Perfect for software releases, backup archives, and cross-platform file transfer. Abbreviated form of TAR.GZ with identical functionality and structure.

TBZ2

TBZ2 - TAR archive compressed with BZIP2 compression. Better compression than TGZ (10-15% smaller) but slower processing. Uses Burrows-Wheeler block sorting for excellent text compression. Common in Linux distributions and software packages where size is critical. Maintains Unix file permissions and attributes. Perfect for source code distribution, archival storage, and bandwidth-limited transfers. Abbreviated form of TAR.BZ2 with identical functionality. Standard format for Gentoo Linux packages and large software archives.

TXZ

TXZ - TAR archive compressed with XZ (LZMA2) compression. Modern format offering best compression ratios for TAR archives (better than TGZ and TBZ2). Fast decompression despite high compression. Supports multi-threading for improved performance. Becoming standard for Linux distributions (Arch, Slackware use TXZ). Maintains Unix permissions and symbolic links. Perfect for large software packages, system backups, and efficient storage. Abbreviated form of TAR.XZ representing the future of Unix archive compression.

LZMA

LZMA/TAR.LZMA - Lempel-Ziv-Markov chain Algorithm compression format (2001) offering excellent compression ratios. TAR.LZMA combines TAR archiving with LZMA compression. Predecessor to XZ format using similar algorithm but older container format. Better compression than GZIP and BZIP2 but superseded by XZ/LZMA2. Still encountered in older Linux distributions and legacy archives. Slower compression than GZIP but better ratios (similar to XZ). Modern systems prefer TAR.XZ over TAR.LZMA. Legacy format for accessing older compressed archives from 2000s era.

LZO

LZO/TAR.LZO - Lempel-Ziv-Oberhumer compression format prioritizing speed over compression ratio. TAR.LZO is TAR archive compressed with LZO. Extremely fast compression and decompression (faster than GZIP) with moderate ratios (30-50% reduction). Popular in real-time applications, live systems, and scenarios requiring instant decompression. Used by some Linux kernels and embedded systems. Common in backup solutions prioritizing speed. Perfect for temporary compression, live CD/USB systems, and high-speed data transfer. Trade-off: larger files than GZIP/BZIP2/XZ but much faster processing.

Z

Z/TAR.Z - Unix compress format from 1985 using LZW (Lempel-Ziv-Welch) algorithm. TAR.Z is TAR archive compressed with compress command. Historical Unix compression format predating GZIP. Patent issues (until 2003) led to GZIP replacing it. Legacy format with poor compression by modern standards. Rarely used today except in very old Unix systems and historical archives. If you encounter .Z or .tar.Z files, convert to modern formats (TAR.GZ, TAR.XZ) for better compression and wider support. Important for accessing ancient Unix archives from 1980s-1990s.

专业格式

ISO

ISO Image - ISO 9660 disk image format containing exact sector-by-sector copy of optical media (CD/DVD/Blu-ray). Standard format for distributing operating systems, software installations, and bootable media. Can be mounted as virtual drive without physical disc. Contains complete filesystem including boot sectors, metadata, and file structures. Essential for Linux distributions, system recovery media, and software archives. Used by burning software, virtual machines, and media servers. Universal standard with support in all major operating systems for mounting and burning.

CAB

Cabinet Archive - Microsoft's compression format for Windows installers and system files. Used extensively in Windows setup packages, driver installations, and system updates. Supports multiple compression algorithms (DEFLATE, LZX, Quantum), split archives, and digital signatures. Built into Windows with native extraction support. Common in software distribution for Windows applications, particularly older installers and Microsoft products. Maintains Windows-specific attributes and can store multiple files with folder structures. Part of Windows since 1996.

AR

AR Archive - Unix archiver format (1970s) originally for creating library archives (.a files). Simple format storing multiple files with basic metadata (filename, modification time, permissions). Used primarily for static libraries in Unix development (.a extension). Foundation format for DEB packages (Debian packages are AR archives containing control and data). Minimal compression support (none by default). Essential for Unix library management and Debian package structure. Standard tool 'ar' included on all Unix/Linux systems. Simple and reliable for static file collections.

DEB

Debian Package - software package format for Debian, Ubuntu, and derivative Linux distributions. Contains compiled software, installation scripts, configuration files, and dependency metadata. Used by APT package manager (apt, apt-get commands). Actually a special AR archive containing control files and data archives. Essential format for Debian-based Linux software distribution. Includes pre/post-installation scripts, version management, and dependency resolution. Standard packaging for thousands of Ubuntu/Debian applications. Can be inspected and extracted as regular archive.

RPM

RPM Package - Red Hat Package Manager format for Red Hat, Fedora, CentOS, SUSE, and derivative Linux distributions. Contains compiled software, installation metadata, scripts, and dependency information. Used by YUM and DNF package managers. Includes GPG signature support for security verification. Standard for Red Hat Enterprise Linux ecosystem. Supports pre/post-installation scriptlets, file verification, and rollback capabilities. Essential format for RHEL-based Linux software distribution. Can be extracted as archive to inspect contents without installation.

JAR

JAR档案 - 基于ZIP压缩的Java档案格式,用于打包Java应用程序。包含编译后的Java类(.class文件)、应用程序资源和清单元数据。Java应用程序和库的标准分发格式。支持数字签名以进行代码验证。可以是可执行的(带有Main-Class清单的可运行JAR文件)。非常适合Java应用程序部署、库分发和插件系统。与ZIP工具兼容,但包含Java特定功能。自1996年以来,Java开发和部署的基本格式。

ARJ

ARJ Archive - legacy DOS compression format by Robert Jung (1991). Popular in DOS and early Windows era for its good compression ratio and ability to create multi-volume archives. Supports encryption, damage protection, and archive comments. Largely obsolete today, replaced by ZIP, RAR, and 7Z. Still encountered in legacy systems and old software archives. Requires ARJ or compatible decompression software. Historical format important for accessing old DOS/Windows archives from 1990s. Better converted to modern formats for long-term accessibility.

LHA

LHA档案 - 1988年开发的日本压缩格式(也称为LZH),在日本和Amiga用户中极为流行。使用LZSS和LZHUF压缩算法,提供良好的压缩比。1990年代日本软件分发中常见。支持档案头、目录结构和文件属性。遗留格式,现在大多被现代替代品取代。在复古计算、日本软件档案和Amiga社区中仍然可以遇到。提取需要LHA/LZH兼容软件。对于访问日本和Amiga软件档案非常重要。

CPIO

CPIO Archive - Copy In/Out archive format from Unix (1970s) for creating file archives. Simpler than TAR, often used for system backups and initramfs/initrd creation. Standard format for Linux initial RAM disk images. Supports multiple formats (binary, ASCII, CRC). Better handling of special files and device nodes than TAR. Common in system administration, bootloader configurations, and kernel initrd images. Universal on Unix/Linux systems. Essential for system-level archiving and embedded Linux systems. Works well for streaming operations.

如何转换文件

上传您的文件,选择输出格式,立即下载转换后的文件。我们的转换器支持批量转换并保持高质量。

常见问题

What is a CAB file and why was it widely used on Windows for software distribution?

A CAB (Cabinet) file is Microsoft’s native compressed archive format introduced in the Windows 95 era. It was designed to deliver software components, drivers, and installers efficiently while preserving file integrity and minimizing download or installation sizes.

Unlike general-purpose archives, CAB files support multiple compression algorithms (LZX, MSZIP, Quantum) and internal indexing optimized for fast extraction by Windows setup tools.

CAB archives became essential for Windows installers, system updates, component packages, and deployment tools, even though modern formats have largely replaced them in consumer workflows.

Why are CAB files still used inside Windows even though ZIP and MSI are more common?

CAB files integrate deeply with the Windows servicing stack, making them ideal for packaging system components, update payloads, and driver bundles.

Windows Installer (MSI) and DISM rely on CAB structures for storing features, patches, and optional Windows components due to their predictable structure and fast parsing.

旧版工具继续依赖CAB档案,因为它们保证了现代压缩格式可能无法提供的确定性行为。

为什么我无法用普通的档案工具打开某些CAB文件?

某些CAB文件包含专用的数字签名、内部修复表或多卷结构,通用提取器无法解释。

Advanced compression modes like LZX or Quantum may not be fully supported outside Windows tools such as `expand.exe` or DISM.

System-level CAB archives created for updates may contain metadata blocks that require Windows-specific extraction behavior.

为什么CAB文件有时包含多个压缩部分而不是一个?

大型安装程序将内容拆分为多个压缩单元,以加快提取速度并避免在安装过程中内存过度使用。

这种结构允许增量解压缩,这意味着只有在需要时才会解压缩相关组件。

多部分内部结构优化了在CAB文件起源的旧硬件上的安装速度。

为什么CAB压缩有时比ZIP或7Z差?

CAB优先考虑确定性和快速解压缩,而不是最大压缩比。

Its algorithms are optimized for Windows installer scenarios, not general-purpose compression.

像7Z这样的格式使用了更先进的现代算法,而CAB从未设计成与之竞争。

从未知来源安装或提取CAB文件是否安全?

CAB文件可以包含可执行二进制文件、脚本、DLL或系统驱动程序,如果来自不可信的位置,可能会很危险。

Many Windows updates rely on digital signatures inside CAB archives—lack of valid signatures is a red flag.

在提取或安装CAB内容之前,始终验证来源或签名。

Why do Windows drivers often come packaged as CAB files?

驱动程序元数据、配置文件和二进制块在CAB内部由于可预测的文件结构而高效压缩。

The Windows Driver Store and PnP framework expect CAB-based driver bundles for streamlined installation.

Microsoft’s deployment infrastructure uses CAB as a uniform format for distributing certified drivers.

为什么某些CAB文件需要像DISM或pkgmgr这样的特殊工具来安装?

System component CABs contain manifests, dependencies, and metadata that must be processed by Windows component servicing rather than normal extraction tools.

DISM验证签名完整性,检查兼容性,并将组件注册到操作系统中。

这些CAB档案修改操作系统环境,需要提升权限和专业处理。

CAB文件容易损坏吗?

CAB档案包括内部校验和,但部分下载或中断可能会损坏容器或单个块。

多卷CAB特别脆弱,因为单个缺失部分会使整个集合无法使用。

Windows tools typically detect corruption instantly due to built-in validation structures.

CAB文件可以存储非常大的档案吗?

经典CAB格式由于32位结构限制,每个文件的最大大小限制约为2 GB。

现代软件很少使用CAB来处理超大档案,因为像ZIP64或7Z这样的格式处理大型数据集要好得多。

对于操作系统组件,内容通常被拆分为较小的CAB,以保持在兼容性边界内。

为什么安装程序在设置过程中经常临时提取CAB文件?

许多MSI、EXE和安装框架内部嵌入CAB文件,并在安装开始时动态提取它们。

这使得安装程序更小、模块化,并且更易于更新或修补。

临时提取还允许根据用户配置选择性安装组件。

CAB文件支持加密或密码保护吗?

标准CAB格式不支持任何形式的加密或密码保护。

安全性必须在CAB内部的文件级别应用(例如加密的EXE),而不是对CAB容器本身。

由于这个限制,CAB不适合存储敏感或机密数据。

多卷CAB文件是如何工作的?

大型安装程序有时将CAB内容拆分为多个文件(例如,`data1.cab`、`data2.cab`)。

每个部分包含内部结构的片段,提取时需要所有卷存在。

这种设计反映了软盘安装的时代,并继续支持向后兼容性。

CAB格式在今天仍然相关吗?

CAB is still widely used in Windows Update packages, driver distributions, and system components.

然而,普通用户由于现代压缩和打包替代品很少手动遇到CAB文件。

Despite its age, CAB remains embedded deeply in Microsoft’s infrastructure and is unlikely to disappear.

你应该使用CAB进行一般归档或压缩吗?

不——与ZIP、7Z或TAR.XZ相比,CAB在压缩比、灵活性和现代功能方面已经过时。

它缺乏加密、扩展元数据支持和大文件能力。

Use CAB only when interacting with Windows drivers, installers, updates, or legacy deployment systems.