Initializing... drag & drop files here
Supports: TGZ
.tgz files (which are identical in content to .tar.gz). Drop in several at once — batch is supported.A .tgz file is a tar archive compressed with gzip — exactly the same thing as a .tar.gz file. The .tgz spelling is just a single-extension shorthand: the GNU gzip manual notes that gunzip treats .tgz as a stand-in for .tar.gz, a convention that started so the name wouldn't get truncated on old MS-DOS and Windows systems that only allowed an 8.3 filename (a three-letter extension). The contents are byte-for-byte identical; only the name differs.
That gzip-over-tar design is standard on Linux, macOS, and the BSDs, where tar and gzip are built in. The friction shows up elsewhere, which is why people convert:
.tgz. Converting TGZ to ZIP lets anyone open the contents without installing 7-Zip or WinRAR.| Format | What it is | Compression | Random access | Best for |
|---|---|---|---|---|
| TGZ / TAR.GZ | tar bundle + gzip (DEFLATE) | Good, fast | No — sequential stream | Linux/macOS distribution, the common default |
| ZIP | per-file DEFLATE + central directory | Good | Yes — extract one file directly | Windows/macOS double-click, sharing |
| TAR | uncompressed bundle | None | No | Stripping compression off already-compressed data |
| 7Z | LZMA / LZMA2 container | Very high | Yes (with 7-Zip) | Smallest archives, needs 7-Zip / p7zip |
| TAR.XZ | tar bundle + xz (LZMA2) | Highest of these | No | Smallest tar archive, slower to compress |
| TAR.BZ2 / TB2 | tar bundle + bzip2 | Higher than gzip | No | Better ratio than gzip, widely available |
The .tgz name hides a two-layer design that explains most of its behaviour — why it cannot extract a single file quickly, why it keeps Unix permissions, and why ZIP behaves differently:
| Property | Value |
|---|---|
| What it is | A tar bundle that has then been compressed with gzip — byte-for-byte identical to .tar.gz |
| Bundling layer | tar, in one of its POSIX-descended variants (ustar, GNU, or pax) |
| Compression layer | gzip, which wraps DEFLATE (RFC 1951) in the gzip file format (RFC 1952) |
| Compression scope | The entire tar stream at once, not each file separately |
| Extract one file quickly | No — the stream must be decompressed sequentially to reach it |
| Unix permissions and ownership | Preserved in the tar headers |
| Symlinks and hard links | Preserved |
| Empty directories | Preserved |
| MIME type | application/gzip for the outer gzip wrapper |
| Built in on | Linux, macOS, and the BSDs (tar -xzf archive.tgz) |
| Double-click extraction on Windows | Not dependable — ZIP is the safe pick for a Windows recipient |
That "compress the whole stream at once" design is the key difference from ZIP, which deflates each file individually and keeps a central directory. Solid compression usually makes a tar-based archive smaller than an equivalent ZIP of many small files, at the cost of random access.
Yes — they are identical. Both are a tar archive that has been compressed with gzip; .tgz is simply a single-extension shorthand for .tar.gz. The GNU gzip manual confirms that gunzip recognizes .tgz as a stand-in for .tar.gz. The convention dates back to systems that limited extensions to three characters (the MS-DOS 8.3 filename rule), where archive.tar.gz would otherwise get mangled. If you only need to rename, converting TGZ to TAR.GZ re-packs the same contents under the explicit two-part name.
ZIP. Windows File Explorer extracts ZIP archives by double-clicking but does not natively open .tgz. Converting TGZ to ZIP means the recipient can open the contents on any Windows or macOS machine without installing 7-Zip, WinRAR, or PeaZip. If you need a smaller file and don't mind the recipient using 7-Zip, 7Z compresses tighter.
No. Archive conversion is lossless — it unpacks the tar bundle and re-packs the same files into the new container, so every file, its bytes, and its folder structure come through intact. The only thing that changes is how the files are compressed (or, for TAR output, whether they are compressed at all). File contents are never re-encoded the way an image or video would be.
Among the options here, TAR.XZ (which uses the xz / LZMA2 compressor) and 7Z (LZMA) generally produce the smallest archives — meaningfully smaller than gzip-based TGZ at the cost of slower compression. bzip2-based TAR.BZ2 sits in between. In our testing, re-packing a TGZ of mixed source-code text typically shrinks another 15-30% as TAR.XZ versus the original gzip, while already-compressed media (JPEG, MP4) barely changes regardless of the target — those bytes are already near their compression limit.
Converting to TAR removes the gzip compression layer and leaves the bare uncompressed bundle. That sounds backwards, but it's useful when the archive mostly holds data that is already compressed — JPEGs, PNGs, MP4s, or nested archives — because gzip can't shrink that data and only adds processing overhead. A plain TAR is also the right input if you plan to re-compress with a different tool afterward.
The file contents always survive intact; the Unix metadata is the part to think about. A tar bundle stores permission bits, ownership, and symlinks in its headers, which is exactly why tar-based archives are the standard way to move a Linux directory tree around. ZIP was designed on a different platform and handles that metadata far less consistently across the tools that read and write it, so an executable script can arrive without its executable bit and a symlink can arrive as a plain file. The practical rule: if the archive is a deployment bundle, a source tree with shell scripts, or anything that will be unpacked back onto a Linux or macOS machine, stay in a tar-based target — TGZ to TAR, TAR.XZ, or TAR.BZ2 all keep the tar headers. Convert to ZIP when the point is simply handing documents or media to someone on Windows.
It depends on the Windows version, which is exactly why ZIP remains the reliable answer. ZIP has been extractable by double-clicking in File Explorer for two decades. Microsoft's own zip and unzip files documentation states that Windows 11 version 24H2 supports the ZIP, RAR, 7z, and TAR archive formats, with creation still limited to ZIP — so a plain .tar may well open on a current Windows 11 machine, while the gzip-compressed .tgz spelling is inconsistent and Windows 10 handles neither. Microsoft's guidance for anything beyond that is to use a third-party tool such as 7-Zip. If you do not know what the recipient is running, TGZ to ZIP removes the question entirely.
Yes. Your file is uploaded over an encrypted (TLS) connection, processed on our servers, and deleted automatically after a few hours. There is no sign-up, no watermark, and files are never shared or made public. The only practical limit on a very large archive is upload size and your connection speed, not a per-file format cap.