Convert XZ to LZMA

Why Convert XZ to LZMA?

Converting XZ to LZMA is primarily needed for backward compatibility with systems that only support raw LZMA streams. Embedded systems, older firmware bootloaders, and applications built with the LZMA SDK often require the legacy .lzma format rather than the modern .xz container.

Some proprietary systems and game engines use LZMA1 specifically for asset decompression. These systems have LZMA1 decompressors built into their runtime but do not understand the XZ container format. Converting XZ to LZMA strips the container and provides the raw stream these systems expect.

Android boot images and some Linux kernel configurations use raw LZMA for initramfs compression. If you have XZ-compressed data that needs to be used in these contexts, converting to LZMA produces the compatible format.

Important: converting XZ to LZMA loses SHA-256 integrity checking, multi-threading support, and BCJ filter benefits. Only convert when the target system specifically requires raw LZMA format.

Key Benefits of Converting XZ to LZMA:

• Embedded Compatibility: Required by LZMA SDK applications
• Firmware Use: Standard for bootloader decompression
• Simpler Format: No container overhead
• Legacy Support: Compatible with older 7z tools
• Android Boot: Used in Android initramfs
• Game Engines: Some require raw LZMA streams
• SDK Compatible: Direct input for LZMA SDK

Practical Examples

Example 1: Preparing Firmware Compression

Source: kernel_image.xz (8 MB)
Conversion: XZ → LZMA
Result: kernel_image.lzma (8.1 MB)

✓ Compatible with U-Boot LZMA decompressor
✓ Standard format for embedded Linux boot
✓ Minimal size increase from format change

Example 2: Game Asset Packaging

Source: game_textures.xz (500 MB)
Conversion: XZ → LZMA
Result: game_textures.lzma (505 MB)

✓ Compatible with game engine LZMA loader
✓ Runtime decompression via LZMA SDK
✓ Standard for asset bundle compression

Example 3: Android Boot Image Creation

Source: initramfs.xz (25 MB)
Conversion: XZ → LZMA
Result: initramfs.lzma (25.2 MB)

✓ Required format for Android boot.img
✓ Compatible with mkbootimg tool
✓ Kernel decompresses LZMA at boot

Frequently Asked Questions (FAQ)

Q: Will LZMA be larger than XZ?

A: Slightly — typically 0-3% larger. XZ uses LZMA2 which can be marginally more efficient. The container overhead removed is only a few dozen bytes, so the size difference comes from the algorithm version.

Q: Will I lose integrity checking?

A: Yes. XZ's SHA-256/CRC-64 checksums are not present in LZMA. You should verify data integrity by other means (external checksums, md5sum/sha256sum files) if corruption detection matters.

Q: Is there data loss?

A: No. Both use lossless compression. File contents are preserved exactly. Only container metadata (checksums, BCJ filter info) is not transferred.

Q: When should I NOT convert XZ to LZMA?

A: When the target system supports XZ, keep XZ. LZMA loses integrity checking, multi-threading, and BCJ filter benefits. Only convert when specifically required by legacy or embedded systems.

Q: What is the difference between LZMA1 and LZMA2?

A: LZMA1 (.lzma) is the original algorithm. LZMA2 (used in .xz) adds dictionary resets, better handling of uncompressible data, and multi-threading support. Converting XZ to LZMA recompresses with LZMA1.

Q: Can I convert back to XZ later?

A: Yes. Converting LZMA to XZ is straightforward and adds back integrity checking and modern container features.

Q: What about BCJ filters?

A: XZ BCJ filters (for executable optimization) have no equivalent in raw LZMA. If the XZ used BCJ filters, the LZMA file may have slightly worse compression on executable content.

Q: Is raw LZMA still used?

A: Yes, in embedded systems (U-Boot, Android), the LZMA SDK, some game engines, and 7z archives internally. While XZ is the modern standard, raw LZMA remains essential for these specialized environments.