Convert GZIP to TAR
Free online converter for GZIP files. Uncompressed Unix archive stream. Nothing to install, no watermark, and every file is deleted automatically.
Drag and drop your files
or
Upload a GZIP file to convert it to TAR. Up to 3 files at once, 100 MB each.
Free · up to 3 files · 100 MB each · files deleted automatically after 1 hour.
About GZ and TAR
GZIP .gz
A single-stream compressor, not an archive. Gzip compresses one file; bundling many requires tar first, which is why tar.gz is so common.
Good for
- Fast to compress and very fast to decompress
- Universal on Unix systems and across the web
- Streams cleanly through pipes
Trade-offs
- One file only — it cannot hold a directory
- Compresses less than LZMA
- No integrity protection beyond a basic checksum
application/gzip
TAR .tar
Not a compressor at all — a way of concatenating many files into one while preserving Unix permissions, ownership and symbolic links. Compression is applied afterwards, if at all.
Good for
- Preserves Unix permissions, ownership and links exactly
- The standard for backups and software distribution
- Streams, so it works down a pipe
Trade-offs
- No compression by itself — a tar is as big as its contents
- No random access without reading through the file
- Awkward on Windows without extra software
application/x-tar
GZ and TAR side by side
| GZ | TAR | |
|---|---|---|
| Compression | Single stream (DEFLATE) | None — container only |
| Typically used for | Compressing one file, web transfer encoding | Unix backups, software packaging |
What changes when you convert GZ to TAR
The archive is rebuilt, not renamed
Your GZ is unpacked in full and its contents are written into a new TAR. Nothing is passed through untouched, so the compression is done again from scratch at the level you choose, and the resulting size depends on that setting rather than on how the GZ was originally made. The folder structure inside is preserved exactly.
These two store files differently
GZ compresses a single stream and has no concept of multiple files, so must be decompressed from the start. TAR applies no compression whatsoever — it only concatenates, so reading one file means reading through everything before it. That difference is the real reason to pick one over the other: per-file compression lets a tool pull out a single entry cheaply, while compressing everything as one stream finds patterns across files and usually ends up smaller.
Unix file modes have somewhere to go
TAR records Unix permissions and symbolic links as a matter of course, which is why it is the format of choice for anything destined for a server. Note that it can only record what it is given: metadata the GZ never stored cannot be recovered by converting.
Why GZ is read-only here
Plain gzip compresses a single stream and has no concept of files or folders — which is why it is nearly always paired with tar. We accept it as a source and write open multi-file formats instead.
You choose how hard it compresses
Because the archive is built again from scratch, the compression level is yours to set rather than inherited from the GZ. It defaults to 6 — the setting that has been the sensible middle ground for deflate for thirty years. Raising it buys a few percent for a disproportionate amount of time; lowering it is worth doing for large archives of already-compressed material such as photographs or video, where there is nothing left to squeeze.
TAR does not compress at all
A tar file only concatenates — it makes one file out of many and applies no compression whatsoever, so the result will be roughly the combined size of everything inside it. That is deliberate: tar handles the bundling and a separate compressor handles the squeezing. If you want the file smaller, TGZ is the same tar with gzip applied over it.