Create TAR.GZ tarballs.
Make tar.gz tarballs in your browser — nothing uploaded.
Drop any files here
or browse your files
Paste with ⌘V · or drop files anywhere on the page
Files never leave your device. Everything runs in your browser, nothing touches a server — tools you've used even work offline.
The tarball is how source code, releases and server payloads travel in the unix world. Drop files, get one .tar.gz — tarred and gzipped entirely in your browser. The format pills switch to tar.bz2 for a smaller file or tar.xz for the smallest, when the extra build time is worth it.
How it works
- Drop files anywhere on the page, click to browse, or paste with ⌘V.
- Pick a quality or preset — or set an exact target size and let the tool find it.
- Compress, compare before/after, and download — individually or as a ZIP.
One stream beats many small ones
ZIP compresses each file separately, so a thousand small source files each pay the overhead alone. A tarball compresses the whole tar as one stream, letting the compressor exploit repetition ACROSS files — that is why source releases ship as .tar.gz. Already have a ZIP? ZIP to TAR.GZ converts it; the other direction is TAR.GZ to ZIP.
Frequently asked questions
tar.gz or .tgz — is there a difference?
None — .tgz is just the DOS-era short spelling of .tar.gz. Every tool that opens one opens the other; this page names outputs .tar.gz, the long form most tooling writes today.
gzip, bzip2 or xz for my tarball?
gzip is the compatibility-and-speed default. bzip2 lands a bit smaller and slower. xz compresses smallest of the three at a real CPU cost — the usual pick for release artifacts that get downloaded many times but built once.
Why a tarball instead of a ZIP?
Unix toolchains, Makefiles, CI pipelines and package managers expect tarballs — and compressing the whole bundle as one stream squeezes source trees tighter than per-file ZIP compression. For sending files to people rather than machines, ZIP stays the friendlier pick.
Is it private?
Yes. Archives are built and converted entirely in your browser — neither the archive nor the files inside it are ever uploaded, and any password you set is applied locally. The server does nothing but deliver this page. Want proof? Run one file through, switch your connection off, and run another — it still works.