CONVERT
LZ → ZST
Tap to choose your fileDRAG. DROP. DONE.
Upload any file and our engines will handle format detection automatically.
Max 25 MB · Free plan · No signup required
Convert to:
Detecting available formats...
Optimize for
Leave empty to use original name. Extension added automatically.
Uploading...
Processing your file...
Fast, secure LZ to ZST conversion. No registration required.
LZ is a compression/archive format used to package or shrink files. Reaching a ZST from there is one hop. A LZ becomes a ZST by opening the source archive in memory and writing every entry into a new container using the ZST codec. No files touch disk in cleartext, which is handy when the LZ is password-protected or contains sensitive folders. Context: LZ is a compression/archive format used to package or shrink files. ZST is a compression/archive format used to package or shrink files.
Lzip Compressed
Source formatLzip uses LZMA compression with error detection for reliable archiving.
Zstandard Compressed
Target formatZstandard (Zstd) is a fast lossless compression algorithm developed by Yann Collet at Facebook. It provides compression ratios comparable to zlib while being 3-5x faster at both compression and decompression, making it ideal for real-time data processing.
Why convert LZ to ZST
ZST is supported by more systems out of the box than LZ. Windows reads ZST without extra software; macOS and most Linux distros ship decoders too. Converting upstream saves every downstream user from installing a utility just to read your bundle.
HOW TO CONVERT
LZ → ZST
Upload the LZ
Send the archive file to KaijuConverter. Entries are never written to disk in cleartext.
Repack through 7-Zip
Our pipeline opens the LZ in streaming mode, walks every entry and writes it into a fresh ZST container.
Download the ZST
The new archive is ready in seconds. Both files auto-delete within two hours.
Common Use Cases
Share across platforms
Send ZST files to anyone without worrying about whether they have the right software for LZ.
Embed in documents
Drop ZST output into Word, Google Docs, PowerPoint, Notion or a website without conversion warnings.
Optimize size
ZST often produces smaller files than LZ for web, email and storage.
Archive & future-proof
Store in a widely-supported format that will still open on future operating systems without legacy plugins.
LZ vs ZST — Strengths and limitations
What each format does best, and where it falls short.
LZ Strengths
- LZMA compression without xz complexity.
- Per-segment CRC32 integrity.
- Multi-threaded plzip variant.
- GNU FSF endorsement.
Limitations
- Tiny ecosystem vs xz.
- No native Windows GUI tools.
- Rarely default anywhere.
ZST Strengths
- Extremely fast decompression (~2 GB/s on modern CPU).
- Scalable: very fast at level 1, near-xz ratios at level 22.
- Dictionary support for small-payload efficiency.
- Multi-threaded by default.
- Standardized (RFC 8478), BSD-licensed reference.
Limitations
- Newer than gzip/bzip2 — some legacy tools still lack support.
- At extreme compression levels, xz can still win on ratio.
- Memory usage at high levels is significant.
LZ vs ZST — Technical specifications
Side-by-side comparison of the technical details.
LZ
- MIME type
- application/x-lzip
- Extension
- .lz
- Algorithm
- LZMA
- Maintainer
- Antonio Diaz Diaz
ZST
- MIME type
- application/zstd
- Extension
- .zst
- Algorithm
- LZ77 variant + entropy coding (FSE/Huffman)
- Standard
- RFC 8478 (2018)
- Compression levels
- 1-22 (plus negative "fast" levels)
| Specification | LZ | ZST |
|---|---|---|
| MIME type | application/x-lzip | application/zstd |
| Extension | .lz | .zst |
| Algorithm | LZMA | LZ77 variant + entropy coding (FSE/Huffman) |
| Maintainer | Antonio Diaz Diaz | — |
| Standard | — | RFC 8478 (2018) |
| Compression levels | — | 1-22 (plus negative "fast" levels) |
LZ vs ZST — Typical file sizes
Approximate file sizes for common scenarios.
LZ
- Source tarball compressed 15-25% of original
ZST
- Default level 3 on source code 28-35% of original
- Level 22 ultra on source code 14-18% of original
- Linux kernel (.tar.zst, level 19) ~130 MB
Quality & Compatibility
Archive conversion is strictly lossless. Byte-for-byte the files inside the ZST are the same as those that were inside the LZ; hashes of individual entries match pre- and post-conversion. Only the container wrapper changes.
Tips for Best Results
- For maximum compression, pick the slowest level in Advanced — the decoder speed of ZST is unaffected by how hard we crunch on our side.
- Keep a LZ backup until you have verified the ZST opens correctly in the destination tool; archives occasionally expose codec bugs at the edge.
- Do not convert already-compressed payloads (video, music, images) expecting smaller output — archive converters cannot compress what is already at the entropy limit.
Frequently Asked Questions
Yes. The free tier accepts files up to 25 MB without registration, email capture or watermarks; paid plans go up to 2 GB. Paid plans raise the size cap, enable batch conversions and provide a REST API for automation, but nothing on the free tier is quality-limited — the output is exactly the same as on any paid plan.
Yes — because LZ and ZST use different compression codecs, every entry is decompressed from the LZ and re-compressed for the ZST. The uncompressed data is identical on both sides, and the re-compression happens entirely inside our processing container.
Uploads run over HTTPS, files are processed in isolated containers, and both the source LZ and the ZST output are auto-deleted within two hours. No account is required, file contents are never logged, and KaijuConverter does not use uploads for AI training. The paid plan adds a signable data-processing agreement for regulated workflows.
Usually yes, modestly, when the original LZ used an older codec like Deflate. Against modern LZMA2 / Zstd ZST containers expect 10-30% savings on mixed content and almost no change on pre-compressed payloads. Advanced → compression level lets you trade speed for ratio.
Most files finish in well under a minute. Small images and documents are typically ready in a few seconds; large video or audio files scale roughly with duration. Upload speed from your network is usually the dominant factor, not server time.
Yes. Provide the password during upload; we use it only to decrypt inside the processing container and never log or persist it. The resulting ZST can be re-encrypted with a password of your choice (AES where the target format supports it).
Related comparisons
See these formats side by side to understand which fits your use case best.
Related Guides
Zstandard & LZ4: The Modern Compression Formats Replacing Gzip
Complete guide to Zstandard (ZST) and LZ4 — the modern compression algorithms replacing Gzip in Linux, Docker, databases, and package managers.
Read guideCompressing Files with Python: zip, tar, gzip and lzma
Learn to compress and decompress files with Python: zipfile for ZIP, tarfile for TAR.GZ and TAR.XZ, lzma for maximum compression, and shutil for high-level archive operations.
Read guideArchive Formats Compared: ZIP, 7Z, RAR, TAR, and ZSTD
Complete comparison of ZIP, 7-Zip, RAR, TAR.GZ, TAR.XZ, and Zstandard archive formats. Compression ratio, speed, encryption, and when to use each format.
Read guideSecure & Private Conversion
Your files are encrypted during transfer, processed in isolated containers, and automatically deleted within 60 minutes. We never read, share, or store your data.