RESOURCES
Published 2026-11-08 · 3 min read
How to create an ISO from a ZIP or RAR (and when not to)
ZIP and RAR compress files; ISO is a disc image. What converting one to the other really does, when the ISO mounts or boots, and when to use another tool.
Three container formats, three different jobs
A ZIP or RAR file is an archive: it stores a list of files and usually compresses each one. An ISO is a disc image: a picture of an ISO 9660 or UDF filesystem, with no compression of its own.
Converting between them is therefore not a recompression. The archive is unpacked into a temporary directory and a new filesystem image is built from that directory. You get the same files in a different container — and the ISO is usually larger than the archive it came from, because the compression is gone.
- ZIP and RAR are for transfer and storage; every system needs an unpacker to read them.
- ISO is for mounting, virtual machines, disc emulation and archival; most systems open it without extra software.
What the conversion does, step by step
Convyx extracts the archive into an isolated temporary directory, rejecting absolute paths, parent-directory entries and symlinks, then builds the ISO from the resulting file tree with xorriso. Folder structure and file names are preserved, subject to ISO 9660 naming rules.
Nothing is kept: source and result are deleted on the retention schedule you choose. Choosing immediate deletion still leaves a five-minute grace window so the download can finish.
ZIP to ISO
Upload the ZIP, choose ISO, download the image. The result mounts by double-clicking on Windows and macOS, and on Linux with mount -o loop file.iso /mnt.
The Free plan caps the input at 100 MB. Larger archives need a paid plan; the conversion engine itself accepts up to 512 MB.
RAR and WinRAR to ISO
RAR is the container WinRAR produces, so the two names describe the same input. Extraction uses a bundled UnRAR decoder, which means a normal RAR4 or RAR5 archive converts without WinRAR installed.
Password-protected and multi-volume archives (part1.rar, part2.rar) are not supported: there is no password field, and a single volume is treated as an incomplete archive.
When the ISO will not boot
A data ISO and a bootable ISO are different objects. Booting needs an El Torito boot catalog, and usually a hybrid MBR, written by whatever authored the image. The conversion here builds a data filesystem, so the result mounts and reads correctly but will not start an installer.
For bootable media, keep the original image and write it with Rufus, balenaEtcher or Ventoy, or author it with oscdimg or xorriso -b. Converting a bootable ISO to ZIP and back does not work either: the boot records are not files and do not survive the round trip.
When an ISO is the wrong target
If the goal is to send files to another person, keep the ZIP or RAR: it is smaller and every system opens it. An ISO makes sense when the next tool expects a disc image — a virtual machine, a disc emulator, a legacy application, or an archive that must present a stable filesystem.
ISO 9660 also has naming and size limits that a modern archive does not. Very large single files are usually better kept in ZIP or 7Z.
The command-line equivalents
On Linux or macOS the same steps are: unzip file.zip -d tree, then xorriso -as mkisofs -o file.iso tree. For RAR, unrar x file.rar tree/ first. On Windows, 7-Zip extracts either archive and oscdimg can build the image.
These are the steps the online converter performs. Doing it locally avoids the upload entirely when the file is sensitive or very large.
Checking the result
Mount the ISO and compare the file list and sizes with the original archive before deleting either. If the archive contained symlinks, empty directories or unusual permissions, expect differences: ISO 9660 stores a simpler metadata model than a Unix archive.