Re-wrap an xz tarball as plain tar.gz
For older systems and stubborn scripts that never learned xz: same tree, friendlier wrapper.
Runs in your browser. Your file never leaves your computer.
- ForSystems that predate xz
- KeepsThe exact file tree
- TradesSome ratio for acceptance
- RunsLocally
Embedded systems, older servers and long-lived scripts sometimes predate xz and refuse its tarballs. Re-wrapping restores harmony: the xz layer is undone, the tar inside is preserved as a tree, and gzip re-wraps it into the .tar.gz such environments have always accepted. File contents do not change; the archive gets somewhat larger, gzip being the gentler compressor. The exchange happens in your browser's memory, no server party to it.
Questions
Which systems actually need this?
Older enterprise servers, embedded devices and scripts hard-coded for gzip; anything modern reads xz directly.
Any data difference after re-wrapping?
None within: identical files, identical layout, different outer compression.
Uploaded?
No, memory-local throughout.
Related conversions
- XZ to ZIPSource releases and heavy tarballs from the xz world, opened up as ordinary ZIPs for any machine.
- Extract XZThe heavily compressed release format unpacked into ordinary folders, tarball layer and all.
- RAR to tar.gzArchives headed to servers and build systems, repacked into the bundle Linux tools expect.
- 7z to tar.gzFrom the Windows power-user format to the Unix standard bundle, restructured in one pass.
- TAR to tar.gzThe missing compression layer added: same bundle, gzip-packed, as the tools always intended.
- BZ2 to tar.gzOld bzip2 tarballs re-wrapped in the compression today's pipelines default to.
Part of convert archives in your browser. Every other conversion is on the conversions index.