Initializing... drag & drop files here
This tool packs any set of files into a single .tgz archive — a TAR bundle compressed with gzip, the default way the Unix and Linux world ships and stores file collections. TGZ and .tar.gz are the same format under two names: first your files are concatenated into one TAR stream (names, folders, and permissions preserved), then the whole stream is gzip-compressed. That two-layer design is why the format has survived since the era of tape drives — and why it beats plain TAR whenever the archive has to travel or sit in storage. Files upload over an encrypted connection, are processed on our servers, and are deleted automatically after a few hours — no sign-up, no watermark.
.tgz file. Extract with tar -xzf on Linux/macOS, or 7-Zip / WinRAR / Windows 11's File Explorer on Windows.| Property | Value |
|---|---|
| Structure | TAR bundle + gzip compression (whole-stream, not per-file) |
| Equivalent names | .tgz and .tar.gz — identical format |
| Preserves | File names, directory structure, Unix permissions, timestamps |
| Compression | DEFLATE (gzip) — strong on text, code, and documents |
| Native on | Every Unix/Linux/macOS system; Windows 11 extracts natively |
| Best for | Source distribution, server deployment, log and backup storage |
| Contents | Expected result |
|---|---|
| Source code, logs, CSV, JSON, HTML | Shrinks dramatically — text is gzip's best case |
| Office documents (DOCX, XLSX) | Modest — they're already ZIP archives internally |
| JPG, PNG, MP4, MP3 | Barely shrinks — already compressed; the TGZ mainly bundles |
| Mixed folders | Somewhere in between; the text portion carries the savings |
.tar to open in a second step; 7-Zip's "Extract Here (smart)" or Windows 11 do both at once.Nothing but the spelling — .tgz is a compact alias for .tar.gz, dating from systems that disliked double extensions. Every tool that opens one opens the other; renaming between them changes nothing about the contents. This page writes .tgz, and any Unix pipeline expecting .tar.gz will consume it happily.
Two structural reasons. TGZ compresses the whole bundle as one stream, so redundancy across files gets squeezed out — a folder of similar log files compresses far better than ZIP's file-by-file approach. And the TAR layer preserves Unix permissions and ownership that ZIP historically mangles. Choose ZIP instead when the recipient is a non-technical Windows or macOS user who just wants to double-click.
Because gzip can't re-compress what's already compressed. Photos, videos, music, and existing archives are near-incompressible, so a TGZ of media files is essentially a bundle at the sum of their sizes. The dramatic shrinkage happens on text-like content — code, logs, exports — where cutting to a fraction of the original is normal.
Linux/macOS: tar -xzf archive.tgz in a terminal, or double-click in the file manager. Windows: 7-Zip and WinRAR handle it, and Windows 11's File Explorer extracts .tgz natively — older Windows versions need one of those free tools. The format is among the most universally supported archives in existence.
Yes — the TAR layer stores directory structure, Unix permission bits, and timestamps, and extraction recreates them. One caveat mirrors plain TAR: files uploaded from Windows don't carry meaningful Unix permission bits in the first place, so deployment-critical modes should be set with chmod after extraction on the Linux side.
When the next step decompresses anyway or the contents won't shrink: some build pipelines want uncompressed input they can stream, and a folder of already-compressed media gains nothing from gzip but CPU time. Create a TAR for those; TGZ for everything that travels or gets stored.
Within this family, yes — tar.xz (LZMA2) and tar.bz2 compress harder than gzip at the cost of speed, and 7Z plays the same role outside the TAR world. Gzip's virtue is the sweet spot: respectable compression, very fast, and readable literally everywhere. For routine sharing and storage it remains the sane default.
Files are uploaded over an encrypted connection, packed and compressed on our servers, and deleted automatically a few hours after archiving — never shared or made public, no sign-up, no watermark. In our testing, a folder of source code and logs compressed to a small fraction of its original size, while a folder of JPGs came out barely smaller than the inputs — exactly the split the table above predicts.