Convert anything, at global scale.
200+ formats and automation APIs that feels instant.
CONVERT
From
To
Drop files or choose a source
Upload multiple files at once, mix formats, and fine-tune every conversion with format-aware settings.
Max 2GB per file · Drag & drop ready · Mixed file types welcome
ARCHIVE
LZH Converter
Convert LZH files with ConverterHQ using workflows tuned for archive compatibility, predictable output, and practical downstream use.
Quality and compatibility profile
Core technical and historical facts used for conversion quality, compatibility decisions, and SEO uniqueness.
| Feature | Fact sheet |
|---|---|
| Category | ARCHIVE |
| Extensions | lzh |
| MIME types | application/x-lzh-compressed |
| Created | 1988 |
| Inventor | Haruyasu Yoshizaki (Yoshi) |
| Status | legacy |
| Compression type | lzss+huffman |
| Multi File Container | ✅ |
| Transparency support | ❌ |
| Animation support | ❌ |
| Layer support | ❌ |
| Vector scaling | ❌ |
| Reflowable text | ❌ |
| Multitrack content | ❌ |
| Camera raw data | ❌ |
| HDR content | ❌ |
| Structured data | ❌ |
| Streaming delivery | ❌ |
About this format
LZH format context
Format: LZH
Overview
LZH matters because it is the most common extension-level identity for the LHA/LHarc archive family, making it the practical label many preservation workflows encounter even when the underlying history is really the broader LHA ecosystem.
Archive tooling needed a practical file-extension identity for the LHA/LHarc family so compressed multi-file packages could circulate predictably across operating systems and software catalogs.
LZH is mainly a legacy-preservation and compatibility extension today, important when inherited archives must be identified correctly and distinguished from unrelated uses of the same letters.
LZH is closely associated with Public domain.
LZH is usually selected for workflows that center on download packaging, backup exchange, cross-platform sharing.
Typical Workflows
- download packaging
- backup exchange
- cross-platform sharing
Common Software
- LHa for UNIX
- lhasa
- libarchive
- Kaitai parsers
Strengths
- Widely recognized extension for the LHA family in preservation work.
- Backed by modern parser specifications and legacy unpacker support.
- Useful for disambiguating archive collections that still contain LHA-family members.
Limitations
- The label is ambiguous unless explicitly anchored to the LHA/LHarc family.
- Mostly a legacy-identification concern rather than a current packaging choice.
Related Formats
- LHA
- ZIP
- ARC
- ZOO
Interesting Context
In archive collections from DOS, Japanese PC, and Amiga-adjacent software exchange, .lzh often served as the visible extension for the same family that users also referred to as LHarc, LHa, or LHA.
LZH is supported by retro archive tools, preservation workflows, Japanese legacy software collections, and a handful of modern extractors that maintain backward compatibility.
It is not common in default desktop OS workflows or cloud packaging, but remains important for accessing older material that was distributed in LZH form.
Its ecosystem is narrower than ZIP but still relevant to archival access.
Status: legacy. Introduced: 1988. Invented by: Haruyasu Yoshizaki (Yoshi). Stewarded by: Public domain.
How LZH fits into workflows
Workflow role: LZH
Convert to LZH when a preservation or legacy software workflow explicitly requires that format, especially when matching historical distributions or exchanging files with retro-computing environments.
In most modern workflows the goal is to read LZH content and move it to contemporary archive formats.
Use it when historical fidelity or compatibility outweighs mainstream support.
History of LZH
Format history: LZH
In archive collections from DOS, Japanese PC, and Amiga-adjacent software exchange, .lzh often served as the visible extension for the same family that users also referred to as LHarc, LHa, or LHA.
Original problem: Archive tooling needed a practical file-extension identity for the LHA/LHarc family so compressed multi-file packages could circulate predictably across operating systems and software catalogs.
Why LZH still matters
Current role: LZH
LZH matters because it is the most common extension-level identity for the LHA/LHarc archive family, making it the practical label many preservation workflows encounter even when the underlying history is really the broader LHA ecosystem.
Modern role: LZH is mainly a legacy-preservation and compatibility extension today, important when inherited archives must be identified correctly and distinguished from unrelated uses of the same letters.
When to use LZH
- download packaging
- backup exchange
- cross-platform sharing
Advantages of LZH
- Widely recognized extension for the LHA family in preservation work.
- Backed by modern parser specifications and legacy unpacker support.
- Useful for disambiguating archive collections that still contain LHA-family members.
Limitations of LZH
- The label is ambiguous unless explicitly anchored to the LHA/LHarc family.
- Mostly a legacy-identification concern rather than a current packaging choice.
Formats related to LZH
LZH technical profile
| Feature | Fact sheet |
|---|---|
| Category | archive |
| Extensions | .lzh |
| MIME types | application/x-lzh-compressed |
| Created year | 1988 |
| Inventor | Haruyasu Yoshizaki (Yoshi) |
| Status | legacy |
| compression_type | lzss+huffman |
| multi_file_container | True |
| supports_transparency | False |
| supports_animation | False |
| supports_layers | False |
| supports_vector_scaling | False |
| supports_reflowable_text | False |
| supports_multitrack | False |
| camera_raw | False |
| hdr_capable | False |
| structured_data_capable | False |
| streaming_ready | False |
| sources | {'url': 'https://github.com/jca02266/lha', 'title': '.lzh file format of LHA (AKA LHarc)', 'relevance': 'Official specification', 'source_type': 'official'}, {'url': 'https://formats.kaitai.io/lzh/', 'title': 'Reference Documentation', 'relevance': 'Technical reference', 'source_type': 'reference'}, {'url': 'http://justsolve.archiveteam.org/wiki/LHA', 'title': 'Reference Documentation', 'relevance': 'Technical reference', 'source_type': 'reference'} |
LZH quality and compatibility
Format profile: LZH
Size profile: depends. Quality profile: lossless. Editability profile: low. Compatibility profile: broad. Archival profile: moderate. Metadata profile: moderate. Delivery profile: strong. Workflow profile: packaging. Status: legacy.
Software that opens LZH
- LHa for UNIX
- lhasa
- libarchive
- Kaitai parsers
Conversion options
Convert LZH to
Convert to LZH from
FAQs
Q: What is LZH typically used for?
A:
LZH is commonly used for download packaging, backup exchange, cross-platform sharing.
Q: What are the advantages of LZH?
A:
LZH is broadly compatible across common software.
Q: What should I watch out for when converting LZH?
A:
Check output quality and compatibility on representative sample files.
Sources
Official specification
Technical reference
Technical reference