For backups, zip vs rar vs 7z corruption behaviour matters more than compression ratios. Each format handles bit rot and bad sectors differently. ZIP keeps files separate, so a bad file rarely touches the rest. RAR offers an optional recovery record that can fix limited damage. 7z is usually solid, meaning one corrupted block can destroy many files. This article compares how each format behaves when damaged and what built-in protection each offers, so you can pick the right one before you archive.
How ZIP Handles Corruption
Independent Files, Isolated Damage
ZIP compresses each file independently. If a ZIP archive gets damaged, the error affects only the file whose data was hit. Other files remain readable. ZIP is a strong choice when you want to minimise the fallout from partial damage.
Standard ZIP has no recovery record. It relies on a CRC-32 checksum per file to detect errors. The checksum tells you a file is corrupt, but it cannot repair it. If the archive header is damaged, you may lose access to all files. The independent compression means the data blocks themselves are often still present. Some tools can scan the raw data and extract undamaged files.
For backups where you need to know if a file is bad but don't need automatic repair, ZIP is a simple, reliable option.
RAR and the Recovery Record
Built-In Repair Data
RAR supports an optional recovery record. When you create an archive in WinRAR, check the option "Add recovery record" in the archive options. This adds redundant data that can repair some damage. The recovery record size is a percentage of the archive size; a larger record can fix more damage.
RAR also compresses each file independently by default, though it can create solid archives. Independent compression means damage to one file does not spread. Combined with the recovery record, RAR gives you both error detection and a built-in repair tool.
If you need a format that can heal itself from moderate damage, RAR with a recovery record is the most practical choice among the three. Without the recovery record, RAR behaves much like ZIP on the corruption front.
Why 7z is Riskier with Corruption
Solid Archives and Header Fragility
7z archives are usually created as solid archives. In a solid archive, many files are compressed together as one stream. Damage in a solid block can make every later file in that block unrecoverable. A single bad bit can wipe out dozens of files.
7z also stores its main header near the end of the archive, pointed to by a small start header at the beginning. If the start header or the main header is damaged, the whole archive can become unreadable. This design makes 7z more fragile than ZIP or RAR when facing corruption.
When 7z Makes Sense
If your archive sits on a reliable medium and you prioritise compression over safety, 7z is still useful. For backups on fallible drives or transfers over unreliable connections, the risk of losing many files from one error is high.
Comparing Built-In Protection
- ZIP: No recovery record. CRC-32 detects errors per file. Damage usually affects only one file.
- RAR: Optional recovery record can repair some damage. Independent compression by default limits spread.
- 7z: Often solid, so damage can corrupt many files. Headers at the end increase vulnerability.
None of these formats can recover data that was never written. Redundancy only helps with partial damage. A completely wiped sector cannot be brought back by any built-in feature.
External Repair Options PAR2 Parity Files
PAR2 parity files are a separate, format-independent way to add repair data to any set of files. Create PAR2 files alongside your archive. If the archive gets damaged, the parity files can reconstruct the missing or corrupted data. PAR2 works with ZIP, RAR, 7z, or any other file type.
Use this when you want the compression of 7z or the simplicity of ZIP but need a safety net. PAR2 does not replace the recovery record; it adds an extra layer that you control.
How to Choose a Format for Backups
Match the Format to Your Risk Tolerance
Your choice depends on your tolerance for risk and your ability to add extra protection.
- For simplicity and minimal risk of cascade failure: Use ZIP. Each file stands alone. Test your archives regularly with the CRC-32 checksum to catch damage early.
- For built-in repair: Use RAR with a recovery record. This gives you the best chance of fixing damage without external tools.
- If you must use 7z for its compression: Create non-solid archives if your tool allows it. Alternatively, add PAR2 parity files to protect against damage.
No format is immune to corruption. The most reliable archive format is the one you test and back up in multiple copies.
Recovering a Corrupted Archive
If you already have a damaged archive, your options depend on the format and the extent of the damage.
For ZIP
Use a tool that can scan the raw data and extract undamaged files. The CRC-32 checksum tells you which files are bad, but you cannot repair them without a backup.
For RAR
If you added a recovery record, open the archive in WinRAR and use the repair command. The recovery record will attempt to fix the damage. Without it, you can only extract undamaged files.
For 7z
If the start header is intact, you may be able to extract undamaged files before the corruption point. If the main header is damaged, recovery is much harder. Non-solid archives give you a better chance.
If none of the above works, try using PAR2 parity files if you created them beforehand. Online services like zip.repair may also help with certain types of ZIP corruption.