Convert ISO to 7Z Online (Disc Image to LZMA2 Archive)

An ISO's Uncompressed Disc Data Meets 7z's LZMA2 Compressor

An ISO file is a complete ISO 9660 or UDF filesystem image — the standardized structure a CD, DVD, or Blu-ray actually carries, including volume descriptors, a path table, and directory records, all built around 2048-byte sectors matching physical optical media. Nothing in that structure is compressed; ISO 9660 was designed to represent exactly what sits on a disc, byte for byte. 7z, by contrast, is a pure compressed-archive container introduced by Igor Pavlov's 7-Zip project in 1999, built around the LZMA and LZMA2 algorithms, which use a much larger dictionary window than older compressors and routinely produce smaller output than DEFLATE-based formats on the same data.

Converting ISO to 7z means reading the disc image's filesystem — following its path table and directory records to find every actual file — and re-encoding those files with LZMA2 inside 7z's own container. It does not carry over the disc's own structure at all; the resulting 7z holds only the files a filesystem browser would show inside the mounted disc, not the volume descriptors, boot record, or sector layout underneath them.

El Torito's Boot Catalog Has No Equivalent in 7z's Container Format

A bootable ISO — the kind used to install an operating system — carries a boot record at logical block 0x11, pointing to a boot catalog that lists one or more boot images the disc can start from, following the El Torito specification jointly developed by IBM and Phoenix Technologies in 1995. That structure is what lets a computer's BIOS or UEFI firmware treat the disc as something it can boot directly, before any operating system is even running. 7z's format has no field, header, or convention for any of this; it was designed purely to store and compress an ordinary list of files.

This means a bootable installer ISO, once converted to 7z, becomes an archive of the installer's files — still useful for inspecting or extracting individual files — but it can never be used to boot a computer again, because the specific boot catalog structure that made booting possible simply isn't representable inside 7z's container. Rebuilding a bootable disc image from those extracted files afterward requires a disc-authoring tool capable of writing a new El Torito boot record, not just re-archiving.

The boot catalog itself can list more than one boot image, marked for different "platforms" in El Torito terms — an emulated floppy image, an emulated hard disk image, or a no-emulation image that the firmware loads directly — which is how a single installer disc can sometimes support both older BIOS booting and newer UEFI booting from the same file. None of that platform-specific detail has anywhere to go once the disc's files are pulled into a 7z archive; the archive simply doesn't model the concept of a boot platform at all, so the distinction disappears along with everything else disc-specific.

What Changes When an ISO Becomes a 7z Archive

• Gain — meaningfully smaller file size: LZMA2's large dictionary window typically compresses the same file data noticeably better than the essentially uncompressed sectors an ISO stores.
• Lose — the El Torito boot record and boot catalog: 7z has no equivalent structure, so a bootable installer ISO becomes a non-bootable archive of files once converted.
• Lose — the ability to mount it as a virtual drive: Windows and macOS mount ISOs directly as virtual optical drives; a 7z has to be extracted first, there's no equivalent mount behavior for it.
• Gain — AES-256 encryption as an option: 7z supports strong archive encryption of both file contents and filenames; ISO 9660/UDF define no encryption at all.
• Kept — every actual file's content: whatever files the disc's filesystem tree contained come through in the 7z unchanged; only the disc-specific wrapper around them is lost, not the file data itself.
• Lose — multi-tree filename redundancy: an ISO can carry a plain 8.3 tree alongside Joliet and Rock Ridge trees for the same files; a 7z extraction resolves to one final file list, not several parallel name sets.

Where 7-Zip Sits Between Reading ISOs and Writing Them

7-Zip is one of the few free tools that both reads ISO files directly — browsing them like any other archive, without needing to mount them first — and writes native 7z archives with full LZMA2 compression and optional AES-256 encryption. This dual capability is exactly why 7-Zip is commonly used for this specific conversion: the same program opens the ISO's file tree and produces the compressed 7z output, without a separate mounting step in between.

Windows has mounted ISO files natively without extra software since Windows 8, and 7-Zip itself doesn't require mounting to read one — it parses the ISO 9660/UDF structure internally. On the output side, 7z's file format is openly documented and supported by 7-Zip on Windows, p7zip on Linux and macOS, and numerous other archive managers, though it is not natively recognized by Windows Explorer or macOS's Archive Utility without 7-Zip or an equivalent tool installed first.

7z's LZMA2 compression is also multi-threaded in current 7-Zip versions, letting the compression step use multiple CPU cores — a real practical difference on a large ISO, where LZMA2 alone (single-threaded, as in older 7-Zip builds) can take noticeably longer to compress than DEFLATE-based formats, in exchange for the smaller final file size it produces.

7z also supports splitting an archive into fixed-size volumes, similar to ZIP's split-archive feature, which matters in practice for large disc images: a multi-gigabyte Blu-ray ISO converted to 7z can still exceed an upload limit or removable media's capacity even after compression, and 7-Zip's volume-splitting option divides the resulting 7z into a numbered sequence of parts that get reassembled automatically when a matching set is opened together.

Complaints That Show Up When People Try This Conversion

A common report on tech-support forums is a user converting an OS installer ISO to 7z to save space, then later trying to use that 7z file directly to reinstall the OS — only to find installers and boot menus have no way to boot from a 7z archive at all, since booting requires the El Torito structure that only exists inside the original ISO. The fix reported in these threads is keeping the original ISO for installation purposes and using the 7z copy purely for storage or transfer, not as a replacement disc image.

A second recurring issue is confusion over why a 7z made from an ISO is dramatically smaller than the source file — some users assume this means data was lost, when in fact ISO 9660/UDF images frequently contain large stretches of padding or filler sectors to round out to standard disc sizes, plus genuinely uncompressed file data; LZMA2 compressing that same file data, and the archive not needing to preserve any padding sectors, accounts for most of the size difference without anything actually being dropped.

A third complaint involves large ISOs (Blu-ray images in particular, which can run to tens of gigabytes) taking a long time to compress into 7z — this traces back to LZMA2's compression being considerably more CPU-intensive than the DEFLATE method used by ZIP, a real, documented trade-off for the smaller resulting file size.

ISO and 7z Side by Side for the Same File Contents

Questions About Repacking an ISO as 7z

Can I still boot from an ISO after converting it to 7z?
No. 7z has no equivalent to the El Torito boot record and boot catalog that make an ISO bootable, so a 7z built from a bootable ISO's files can be opened and extracted, but never booted.

Why is the 7z file so much smaller than the original ISO?
ISO 9660 and UDF store file data essentially uncompressed to match physical disc layout; LZMA2 compression in 7z shrinks the same file contents, and any disc padding sectors aren't carried over either.

Does 7-Zip need the ISO to be mounted first?
No. 7-Zip reads the ISO 9660/UDF structure directly and can browse or extract its contents without mounting the disc image as a virtual drive first.

Can I password-protect the 7z version of an ISO?
Yes. 7z supports AES-256 encryption of both file contents and filenames, something ISO 9660 and UDF have no equivalent for at all.

Why does compressing a large ISO into 7z take so long?
LZMA2, the algorithm 7z uses, is considerably more CPU-intensive than simpler compression methods, which is the trade-off for the smaller file size it typically produces, especially on large Blu-ray-sized images.