免费转换 TAR 文件
专业的 TAR 文件转换工具
将您的文件拖放到这里
或点击浏览文件
支持的格式
以高质量在所有主要文件格式之间转换
常见格式
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 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).
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 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.
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.
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 - 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.
{format_tar_7z_desc}
{format_tar_bz_desc}
{format_tar_lz_desc}
{format_tar_lzma_desc}
{format_tar_lzo_desc}
{format_tar_z_desc}
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 - 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 - 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/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/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/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 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.
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 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.
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 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档案 - 基于ZIP压缩的Java档案格式,用于打包Java应用程序。包含编译后的Java类(.class文件)、应用程序资源和清单元数据。Java应用程序和库的标准分发格式。支持数字签名以进行代码验证。可以是可执行的(带有Main-Class清单的可运行JAR文件)。非常适合Java应用程序部署、库分发和插件系统。与ZIP工具兼容,但包含Java特定功能。自1996年以来,Java开发和部署的基本格式。
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档案 - 1988年开发的日本压缩格式(也称为LZH),在日本和Amiga用户中极为流行。使用LZSS和LZHUF压缩算法,提供良好的压缩比。1990年代日本软件分发中常见。支持档案头、目录结构和文件属性。遗留格式,现在大多被现代替代品取代。在复古计算、日本软件档案和Amiga社区中仍然可以遇到。提取需要LHA/LZH兼容软件。对于访问日本和Amiga软件档案非常重要。
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 TAR file and why is it widely used on Unix and Linux systems?
A TAR file (short for Tape Archive) is a container format that bundles multiple files and directories into a single archive without applying compression by default. Originally designed for backup operations on magnetic tape drives, TAR remains a foundational tool in Unix-like environments because it preserves directory structure, file permissions, symlinks, ownership metadata, and timestamps—details critical for system backups, software packaging, and server deployments.
与 ZIP 或 RAR 不同,TAR 本身并不会缩小文件大小;它只是将文件组合在一起。压缩通常是在之后通过外部算法如 Gzip、Bzip2、XZ、LZMA 或 Zstandard 应用,从而创建复合格式,如 .tar.gz、.tar.bz2 或 .tar.xz。这种归档与压缩的分离为开发人员提供了灵活性和对性能、速度和压缩比的控制。
TAR’s simplicity, predictable structure, and robust metadata preservation make it the default archive format in Linux distributions, web servers, Docker images, software sources, configuration backups, and shell scripting workflows.
为什么TAR本身不压缩文件?
TAR最初设计用于顺序写入数据到磁带,压缩并不是这个过程的一部分。它的目的是维护文件结构,而不是减少文件大小。
The Unix philosophy of modularity influenced TAR’s design—archiving and compression were treated as separate steps. Users can pair TAR with any external compression algorithm based on their needs.
这种设计使得TAR保持灵活性,让高级用户可以选择以速度为重点的压缩工具(gzip)、高比率压缩工具(xz)或现代平衡压缩工具(zstd)。
为什么TAR归档能够很好地保留文件权限和元数据?
TAR stores Unix permissions such as read/write/execute flags, user/group ownership, and symbolic link data—crucial for script execution and server migration.
它还保留时间戳、目录层次、设备节点、FIFO管道和扩展属性,允许系统环境的完全准确恢复。
这使得TAR非常适合打包源代码、配置目录、容器数据和依赖于精确重建的备份系统。
为什么TAR提取命令有时会覆盖现有文件?
TAR假设您正在恢复与归档时完全相同的目录结构。它会替换文件,除非另有指示。
大多数TAR工具不会提示确认,除非使用了额外的标志,优先考虑性能和自动化。
可以使用标志如--keep-old-files或提取到空目录来防止覆盖。
为什么某些TAR文件会变得非常大?
一个TAR文件包含原始数据加上元数据而不进行压缩,因此大小等于所有包含文件的总大小。
用户常常将.tar与压缩的tarball(.tar.gz,.tar.xz)混淆,期望有压缩,但实际上并没有。
包含日志、虚拟机镜像或未压缩媒体的备份可能会大幅扩展TAR归档。
为什么某些TAR文件提取速度慢?
如果与重压缩(例如,xz或lzma)配对,解压缩可能需要大量CPU时间。
巨大的归档需要顺序读取,这意味着提取必须处理所有数据,即使是单个文件。
慢速IO设备——尤其是外部驱动器或旧HDD——会显著增加提取时间。
为什么某些TAR文件报告'意外的EOF'或损坏?
中断的下载或部分上传会导致不完整的TAR流,无法完全解析。
缺失的块或不匹配的尾记录会导致提取工具因结构错误而停止。
在压缩的tarball中,损坏的可能性更高,因为单个损坏的字节可能会破坏整个流。
Why do TAR archives behave differently on Windows?
Windows historically lacked native support for Unix permissions and symbolic links, leading to incomplete metadata restoration.
Tools like WinRAR or 7-Zip can extract TAR but do not always replicate Unix file semantics accurately.
Windows Subsystem for Linux (WSL) finally added full TAR compatibility, restoring proper permission handling.
TAR归档可以修复吗?
部分可以——如果损坏发生在文件末尾附近,许多提取的文件仍然可用。
像tar --ignore-zeros或使用dd手动修复的工具有时可以挽救内容。
压缩的tarball(.gz/.xz)更难修复,因为压缩损坏会传播。
为什么开发者更喜欢使用TAR打包软件?
TAR确保可重复构建,其中文件顺序、权限和元数据在不同环境中保持一致。
It integrates seamlessly with Unix tools, package managers, and automated pipelines.
Many open-source ecosystems—Linux kernels, Python packages, Node modules—standardize on TAR for distribution.
为什么Docker镜像和容器层使用TAR?
TAR preserves Unix permissions and symlink behavior, essential for containerized environments.
它的顺序结构与Docker和OCI镜像使用的分层文件系统概念完美契合。
它允许在任何主机系统上进行确定性解包,结果一致。
TAR对敏感数据安全吗?
不——TAR本身不支持加密,这意味着内容在没有加密层的情况下是完全可读的。
为了保护TAR归档,用户必须应用外部加密,如GPG、OpenSSL或加密容器。
加密的tarball(例如,.tar.gz.gpg)在安全备份系统中很常见。
为什么TAR列出目录而不是单独压缩文件?
TAR顺序写入文件,保留它们的顺序和结构,以便进行精确恢复。
这种方法使TAR保持快速、可预测,并与流式工作流程兼容。
It also enables efficient piping, such as tar -cvf - directory | ssh user@server tar -xvf -.
与ZIP或7Z相比,TAR是否过时?
No—TAR remains essential in Unix ecosystems due to metadata support, scripting integrations, and flexible compression.
它简单的结构确保了长期可访问性和对部分损坏归档的易修复性。
因为TAR可以与任何压缩算法配对,它在压缩技术发展时保持未来兼容性。
我应该使用TAR作为我的主要归档格式吗?
Use TAR if you work in Linux, macOS, servers, programming, DevOps, or need accurate metadata preservation.
根据速度与大小的偏好,将TAR与gzip、xz或zstd结合使用以获得最佳压缩。
对于与非技术用户的跨平台共享,ZIP可能更容易——但对于技术工作流程,TAR仍然是更优的选择。