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
Convert ADF to LZ
Convert ADF to LZ online for free with no sign up, with quality-focused workflow guidance.
ADF at a glance
ADF
ADF became the practical exchange format of the early Amiga emulation era, where getting software off physical disks and into UAE-style workflows mattered more than modeling every copy-protection detail.
LZ at a glance
LZ
Before newer compressor families took over, Unix environments relied heavily on older LZW-style compression conventions that now survive mainly in archives and legacy systems.
Format comparison
| Feature | ADF | LZ |
|---|---|---|
| File type | Archive | Archive |
| Extensions |
|
|
| MIME type |
|
|
| Compression / quality | lossless | lossless |
| File size characteristics | depends | depends |
| Compatibility | broad | broad |
| Editability | low | low |
| Created year | 1985 | 2008 |
| Inventor | Commodore International | Antonio Diaz Diaz |
| Status | legacy | active |
| Primary use cases |
|
|
| Common software |
|
|
| Archival suitability | moderate | moderate |
| Metadata handling | moderate | moderate |
| Delivery profile | strong | strong |
| Workflow fit | packaging | packaging |
When to use each format
When to use ADF
- download packaging
- backup exchange
- cross-platform sharing
- Simple sector-by-sector representation that is widely supported by emulators.
When to use LZ
- download packaging
- backup exchange
- cross-platform sharing
- Historically important in compression history.
FAQs
Why convert ADF to LZ?
Choose LZ as target when only when a legacy Unix or archival workflow explicitly expects it.
What changes when converting ADF to LZ?
Convert to LZ only when a legacy Unix or archival workflow explicitly expects it. Typical use involves recovering older compressed files, normalizing inherited asset stores, or maintaining format compatibility for systems that were built around historical compression utilities. For new work, newer stream compressors are usually more practical.
What should I review after converting ADF to LZ?
After conversion, review these destination checks: Open converted output in legacy Unix tools and verify behavior on real samples; Compare output against the expected lossless quality profile; Obsolete for most new workflows.
How can I keep quality stable in ADF to LZ conversion?
Run representative samples, keep settings deterministic, and monitor these risks: Far less common than newer compressors; Obsolete for most new workflows; Validate destination compatibility before large-batch conversion.