LZH to TAR.XZ Converter
Processing entirely on your device — large files may take a moment.
Produce a TAR.XZ for the smallest possible release artifact, or to match the format a build system expects. If your files are still in LZH format, this page is the shortcut: LZH (LHA) is the archive format of the Japanese PC-98 era and Amiga scene — still attached to old downloads and doujin material.
This converter runs entirely in your browser using WebAssembly — your files never leave your device, nothing is uploaded, and there are no watermarks, sign-ups or queues. Drop in several files at once to convert them as a batch.
How LZH compares to TAR.XZ
| LZH | TAR.XZ | |
|---|---|---|
| Compression | LZ (LHA variants) | LZMA2 |
| Encryption | None | None |
| Bundling | Multi-file | tar container, single stream |
| Best for | Retro software archives | Smallest release artifacts |
How to convert LZH to TAR.XZ
- 1
Select your files
Drag & drop your LZH files onto the area above, or click to browse. You can add multiple files at once for batch conversion.
- 2
Convert instantly
Click "Convert to TAR.XZ". The conversion runs entirely inside your browser using WebAssembly — no upload, no queue, no waiting.
- 3
Download results
Download each converted TAR.XZ file individually, or grab everything at once as a ZIP archive.
About the LZH format
LZH (also LHA) is the archive format that ruled Japanese PCs in the 8.3-filename era and the Amiga scene elsewhere. It compresses with a simple LZ scheme, predates ZIP's dominance, and still shows up attached to retro software, doujin archives and old BBS downloads.
No modern OS opens it natively, and LHA tools are niche. Converting LZH to ZIP is the one-step rescue: same files, universal container, no retro software hunt required.
+ Strengths
- ✓The retro Japanese/Amiga archive standard
- ✓Simple, well-documented compression
! Limitations
- −No native OS support today
- −Weak compression by modern standards
About the TAR.XZ format
TAR.XZ is the smallest common release artifact on Linux: a tar container squeezed with LZMA2. Source distributions, distro packages and countless GitHub release assets use exactly this combination — maximum compression at an acceptable speed.
Compared to TAR.BZ2 it is both smaller and usually faster; compared to tar.gz it is considerably smaller. When a build system, mirror or repository asks for .tar.xz, producing it byte-exact is what keeps CI pipelines and maintainers happy.
+ Strengths
- ✓Highest-ratio common release format
- ✓The default for source distributions on Linux
- ✓Built-in integrity checks (CRC per block)
! Limitations
- −Decompression is memory-hungrier than gzip
- −No random access to individual files
- −Multi-threaded xz is not always compatible
Why convert LZH to TAR.XZ?
Converting makes sense where the strengths of TAR.XZ meet what LZH cannot give you. Highest-ratio common release format Meanwhile No native OS support today One pass through the converter above puts your file on the right side of that trade-off.
Frequently asked questions
Is this LZH to TAR.XZ converter really free?
Yes — completely free, with no sign-up, no watermark and no daily conversion limits. The site is supported by advertising.
Are my files uploaded to a server?
No. The conversion runs entirely inside your browser using WebAssembly, so your files never leave your device — that is what makes it instant and private.
Does it work on Windows, Mac, iPhone and Android?
Yes. Anything with a modern browser works: Windows, macOS, Linux, Android and iOS. No software installation is required.
Is there a file size limit for LZH to TAR.XZ?
The only limit is your device's memory, since nothing is uploaded. Files up to a few hundred megabytes work fine on a modern desktop browser; very large files simply take a little longer.
Is there a size limit for archive conversion?
There is no upload cap because nothing is uploaded — the practical limit is your device memory. A few hundred megabytes of unpacked content works comfortably on a modern computer.
What about folders and directory structure?
The full directory tree is preserved: folders stay folders, and deep paths arrive exactly as they were packed in the LZH file.