Initializing... drag & drop files here
Supports: TGZ
.tgz / .tar.gz archives from your computer. Batch upload is supported — queue several archives in one go..7z, or Individual Archives to produce one .7z per input file (handy when you want to keep nightly backups separate).7z. If you change your mind, the same upload can be redirected to zip, rar, or tar.xz instead..7z when the job finishes — no sign-up, no watermark.TGZ is the de-facto Unix bundle: a tar archive piped through gzip. It's universal on Linux and macOS but its compression is DEFLATE, the same algorithm ZIP has used since 1989. 7Z, created by Igor Pavlov in 1999, ships with LZMA2 — a modern dictionary coder that routinely produces noticeably smaller archives on source code, logs, JSON dumps, and uncompressed media. Converting TGZ → 7Z trades a small one-time CPU cost for a permanently smaller file on disk and over the wire.
tar.gz has no native encryption; you have to layer on GPG or openssl. The 7z container supports AES-256 directly, with optional encrypted headers so even filenames aren't leaked..tar.gz requires streaming through the entire gzip pipe. 7Z stores a per-file index, so 7-Zip / p7zip can seek directly to one entry..7z directly with the free 7-Zip GUI, while Mac users can use Keka or The Unarchiver. .tar.gz works there too, but .7z is friendlier when the recipient isn't on the command line..7z finishes uploading faster on tight links and stays under per-attachment limits on services like Gmail (25 MB per message) more often than the same payload as .tgz.| Property | TGZ (TAR + GZIP) | 7Z |
|---|---|---|
| Created | tar (1979), gzip (1992) | 1999 (Igor Pavlov, 7-Zip) |
| Default codec | DEFLATE (gzip) | LZMA2 |
| Typical extra savings on text/code | baseline | ~20-40% smaller than gzip on the same data |
| Solid archives | No (each file in stream) | Yes — groups files for better ratio |
| Random access to one file | Streaming only | Per-file index (fast seek) |
| Built-in encryption | None (use GPG/openssl) | AES-256, optional encrypted headers |
| Unicode filenames | Yes (POSIX ustar / pax) | Yes |
| Max file size in archive | Effectively unbounded | 16 EB (16,000,000,000 GB) per 7-Zip spec |
| Splitting into volumes | Manual (split) |
Built-in (-v switch) |
| Native on Linux/macOS | Yes (tar -xzf) |
Requires p7zip / 7zz |
| Native on Windows | Needs WSL or third-party | 7-Zip (free), NanaZip, PeaZip |
| Level | 7-Zip name | LZMA2 dictionary | Speed vs ratio |
|---|---|---|---|
| 0 | Store | n/a | No compression; bundle only |
| 1 | Fastest | 64 KB | ~5x faster than Normal, ~15% larger |
| 3 | Fast | 1 MB | Good for many small text files |
| 5 | Normal (default) | 16 MB | Balanced — what xconvert uses |
| 7 | Maximum | 32 MB | ~10% smaller than Normal, ~2x slower |
| 9 | Ultra | 64 MB | Best ratio; needs ~700 MB-1 GB RAM to compress |
Per the official 7-Zip site, LZMA compresses at roughly 2-8 MB/s and decompresses at 30-100 MB/s on a 4 GHz CPU, so most users sit at level 5.
LZMA2 uses a larger sliding-window dictionary (up to 64 MB) than gzip's 32 KB window, so it can spot repeated patterns across far more of the archive. On source code, JSON, CSV, and log files, that typically yields archives 20-40% smaller than the gzip-based .tgz. Already-compressed payloads (JPEG, MP4, PDF) won't shrink much because the redundancy was already removed.
On Windows install 7-Zip (free, open source) or NanaZip from the Microsoft Store. On macOS use Keka or The Unarchiver. On Linux install p7zip-full (Debian/Ubuntu) or p7zip (Fedora/Arch) and run 7z x archive.7z. The 7-Zip team's reference command-line is also distributed as 7zz on Linux/macOS since version 21.x.
Folder structure and modification times are preserved. POSIX permissions and ownership stored in the tar header are not round-tripped through 7Z by default — 7Z stores Windows-style file attributes. If you need to preserve Unix mode bits exactly, keep the file as .tar.xz or .tar.zst instead, or re-tar inside the 7z. See our TGZ to TAR tool if you only need to drop gzip without changing the container.
The server-side conversion uses 7-Zip's default settings without a password. If you need AES-256 encryption with encrypted filenames, do the conversion here to get the LZMA2-compressed .7z, then re-pack it locally with 7z a -p -mhe=on encrypted.7z file.7z — that step needs the password and can't be done without it ever leaving your machine.
7-Zip 9.20 (2010) and later read and write LZMA2 transparently, so the output works with any 7-Zip released in the last 15 years, plus p7zip on Linux/macOS and PeaZip / NanaZip on Windows. The current 7-Zip release (26.x, April 2026) is fully backward compatible.
TGZ is the right choice when you're streaming over a Unix pipe or when the recipient runs tar -xzf from muscle memory — gzip's decompression is faster (30-100+ MB/s) and the format is everywhere. Switch to 7Z when storage size matters (long-term archives, big email attachments), when you need encryption inside the container, or when the recipient is on Windows.
Both LZMA2-encode the data, so the compression ratio is similar. The difference is the container: .tar.xz keeps the POSIX tar structure (preserving Unix permissions/ownership), while .7z uses 7-Zip's own format with per-file indexing, optional AES-256, and built-in volume splitting. Pick .tar.xz for Linux-to-Linux backups, .7z for cross-platform delivery. We also offer direct TGZ to TAR.XZ and TAR.GZ to 7Z — same engine.
Each input file is capped by your browser session's upload budget; very large multi-GB archives are better handled by installing 7-Zip locally and running 7z a -mx=5 out.7z extracted-folder/ after a one-time tar -xzf in.tgz. For typical source drops, log bundles, and document archives under a couple of gigabytes, the online converter handles the whole pipeline (extract → repack) in one step.