Convert RZ to ZIP Online (Handing Rzip Output to Windows and macOS Users)
Almost nothing outside Linux and specialist Unix tools reads an .rz file directly — converting to ZIP is often the only practical way to reach a Windows or macOS recipient at all.
- Add a file Choose or drop it here
- Pick the format Change it whenever needed
- Download the result After conversion completes
A Specialist Linux Compressor Meeting the Most Universally Opened Archive Format
RZ is the output of rzip, written by Andrew Tridgell — also the creator of Samba and rsync — during his PhD research, with its last stable release, version 2.1, dating to February 2006. It compresses a single stream using a long-range matching pass across a window up to 900 MB, followed by bzip2. ZIP, by contrast, is PKWARE's decades-old container format built around local file headers and a central directory, and it opens natively in Windows File Explorer and macOS Finder without installing anything at all. Converting RZ to ZIP means fully decompressing rzip's output, then rebuilding the recovered data inside ZIP's own local-header-plus-central-directory structure.
This conversion exists largely because of that openability gap. Mainstream tools — WinRAR, Windows' and macOS's own built-in archive handling — have no documented native support for .rz at all, meaning a recipient without rzip or PeaZip specifically installed simply cannot open the original file, regardless of how well it compressed the underlying data.
This particular pairing tends to show up in one recognizable situation: someone on a Linux system compressed a backup, log set, or data export with rzip specifically because of its strong ratio on long-range-redundant data, and now needs to hand that content to a colleague, client, or archive system that only ever deals with ZIP files — a format nearly every operating system already understands without asking the recipient to install anything new.
Why There's No Direct Structural Bridge Between Rzip's Output and ZIP's Container
Rzip's compressed stream is not a container in ZIP's sense at all — it holds no per-entry headers, no central directory, and typically no concept of multiple files unless a tar archive was bundled underneath before rzip ever ran. ZIP's own structure is fundamentally per-file: each entry gets its own local header recording its compressed and uncompressed size, followed by the file's data, with a central directory at the end indexing every entry for quick listing. Because these two structures share no common representation, converting between them always means decompressing rzip's stream completely, then having a ZIP-writing tool re-encode each recovered file as its own ZIP entry from scratch.
If the original .rz file was compressing a tar archive — the standard approach, since rzip has no native multi-file container of its own — recovering that tar archive is only the first step; a ZIP-aware tool then has to unpack tar's own 512-byte header sequence too, since ZIP's per-file structure and tar's sequential header-plus-data layout are also two entirely different schemes.
What Converting RZ to ZIP Gains and What It Costs
- Gain — direct openability on Windows and macOS: ZIP support is built into both operating systems' file managers, unlike .rz, which needs rzip itself or a specific compatible tool like PeaZip.
- Gain — per-file access without full extraction: ZIP's central directory lets a program list or extract a single file without decompressing the entire archive, something rzip's single-stream design has no equivalent for.
- Lose — rzip's long-range matching advantage: on the project's own Samba source tree benchmark, rzip plus bzip2 reached 9.55x compression versus bzip2 alone's 4.78x — ZIP's own DEFLATE-based compression, with its 32 KB window, falls further behind still on data with that kind of far-apart redundancy.
- Lose — the original tar-layer metadata, if not carefully preserved: Unix permissions and ownership recorded in an intermediate tar archive depend on the specific ZIP-writing tool actually reading and translating that data into ZIP's own (inconsistently supported) Unix extended attribute field.
- Keep — the actual file content: the underlying bytes of every file carry over unchanged; only the surrounding container and compression algorithm differ.
Which Tools Actually Perform This Specific Conversion
The rzip binary, GPL-licensed and packaged in Debian and Ubuntu's repositories, decompresses the source with rzip -d filename.rz. If the recovered data is a tar archive, GNU tar extracts it (tar -xf recovered.tar), and then the Info-ZIP zip command or a graphical archiver bundles the extracted files into the final .zip — a multi-step, multi-tool sequence, since no single program natively bridges rzip's format directly to ZIP's.
PeaZip, the free graphical archiver for Windows and Linux, is the one program documented to handle both ends: it lists native support for reading .rz files and can also create ZIP archives, making it a practical single-application route for this conversion without switching between separate command-line tools.
7-Zip can create the ZIP output but has no documented native support for reading .rz files directly, so it can only take over once rzip or PeaZip has already decompressed the source — a genuine two-tool workflow on Windows for anyone without PeaZip installed.
There's no dedicated Windows binary maintained by the rzip project itself, so the decompression step specifically depends on either building rzip's source directly (it has no platform-specific dependencies beyond a standard C compiler and the bzip2 library) or installing PeaZip — a real extra step compared with ZIP, whose creation tools are already built into both major desktop operating systems.
Real Complaints From People Converting RZ Files Into ZIP
A recurring complaint involves someone receiving a .rz file from a Linux user and having no way to open it at all on a Windows or macOS machine, since mainstream archive tools on both platforms have no built-in support for the format — a direct consequence of rzip staying a specialist Unix tool after development effectively stopped in 2006, unlike gzip or bzip2, which achieved much broader mainstream adoption.
A second documented issue involves the resulting ZIP not preserving Unix ownership and permission bits from the original tar layer reliably — ZIP's extended attribute fields can technically hold this data, but support is inconsistent across ZIP-writing tools, and files extracted later on Windows, where Unix permission concepts don't directly apply, often show up as simply readable and writable rather than reflecting the original mode bits.
A third reported pattern involves expecting the ZIP file to end up close in size to the original RZ, then finding it noticeably larger — since ZIP's DEFLATE-based compression uses only a 32 KB window, it structurally cannot exploit the long-range repetition rzip's 900 MB matching pass was specifically built to catch.
A fourth issue, specific to symbolic links carried inside an intermediate tar archive, involves the link sometimes turning into a plain regular file containing the link's target path as text rather than a working symlink, once it passes through a ZIP archiver that doesn't specifically implement Unix symlink support — ZIP does have a way to record symlinks using the same Unix extended attribute mechanism as permission bits, but not every ZIP-writing tool implements it, so results vary by which archiver actually performs the final step.
RZ and ZIP Measured on the Details That Matter
| Feature | RZ (rzip) | ZIP |
|---|---|---|
| Container for multiple files | No — single stream only | Yes — local headers + central directory |
| Matching window / compression | Up to 900 MB, then bzip2 | 32 KB (DEFLATE) |
| Native support on Windows/macOS | No — needs rzip or PeaZip | Yes — built into both file managers |
| Per-file random access | No | Yes, via the central directory |
| Unix permission bits | Preserved inside an intermediate tar layer | Stored inconsistently, tool-dependent |
| Mainstream tool support | None besides PeaZip | Universal |
Common Questions About Converting RZ Files to ZIP
Why would I convert an RZ file to ZIP instead of just sending the original?
Mainly for openability. ZIP opens natively on Windows and macOS without any extra software, while .rz requires the recipient to have rzip or a specific compatible tool like PeaZip installed.
Will the ZIP file be smaller than the original RZ file?
Usually not. ZIP's DEFLATE compression uses only a 32 KB window, far smaller than rzip's 900 MB matching pass, so data with significant long-range repetition typically ends up larger after this conversion.
Is there a single tool that converts RZ directly to ZIP?
PeaZip is the one mainstream program documented to handle both — reading .rz natively and writing ZIP archives — without needing to combine rzip and a separate ZIP tool.
Do Unix permissions survive the conversion to ZIP?
Not reliably. ZIP has an extended attribute field that can hold Unix mode bits, but support varies between ZIP-writing tools, so permissions can come through inconsistently depending on which software performed the conversion.
Why can't 7-Zip open my RZ file directly?
7-Zip has no documented native support for the rzip format. The original .rz file needs to be decompressed with rzip itself or opened through PeaZip first before 7-Zip can build the resulting ZIP archive.
Do symbolic links inside the original archive survive as real symlinks in the ZIP?
It depends on the tool. ZIP can technically store symlinks using the same Unix extended attribute mechanism as permission bits, but support for writing and reading that field isn't consistent across every ZIP archiver, so a symlink can end up as a plain text file listing its target instead.