How to Recover a Corrupted ZIP File

Diagnose password, format, transfer, CRC, header, and storage errors before extracting recoverable members.

ZIP extraction can fail because the transfer stopped early, the archive is one part of a multipart set, a password is wrong, the compression method is unsupported, local paths are invalid, disk space is exhausted, or headers and member data are actually damaged. The same error dialog can therefore lead to very different remedies.

Compare file size and checksum with the source when available, confirm that every multipart segment is present, and list or test the archive before extraction. Python's zipfile test reads members and checks CRC values and headers; archive applications provide similar test commands. Work in an isolated directory with enough free space and scan untrusted contents before opening them.

A practical checklist

1Copy the archive and record its size, checksum, source, and exact error.
2Confirm password, file type, every multipart segment, disk space, and path support.
3List and test the archive before extracting any member.
4Extract recoverable members into a new isolated directory without overwriting files.
5Validate the member list and important files, then document anything missing.

Understand the situation

Recovery starts by preserving evidence. Work on a copy, stop syncing or writing to a failing source when appropriate, record the original size and checksum, and look for provider version history or backups before attempting a repair that may discard data.

Use a controlled workflow

Separate retrieval from repair. A previous healthy version is preferable to reconstructing a damaged file; if repair is necessary, save every output under a new name and validate content, pages, formulas, media duration, or archive members rather than trusting that an application opened it.

Make the final decision

If only some members extract, record which failed and request those originals separately. Do not repackage partial output under the original archive name because that hides the loss. For irreplaceable archives on failing storage, stop experimenting on the device and use a disk image or professional recovery service.

ClearCopies is not a repair or forensic-recovery product. It can help locate supported byte-identical cloud copies, but a repaired or partially recovered file will normally have different bytes and must be assessed with format-specific tools and human review.

Limits and risks to check

— A ZIP bomb or malicious member can exhaust space or escape unsafe extractors.
— CRC errors mean the extracted bytes cannot be assumed correct.
— Repairing central-directory metadata cannot reconstruct absent compressed data.
— Repeated work on failing media can reduce later recovery chances.

Official references

Frequently asked questions

What does a CRC error mean?

The extracted member does not match the checksum stored in the archive. Treat that member as damaged even if an application can partly open it.

Can I recover some files from a damaged ZIP?

Often yes, when their local headers and compressed data remain intact. Extract to a new directory and validate each member rather than treating partial success as a complete archive.

Why does extraction fail only on one computer?

The tool may lack a compression or encryption method, or the destination may have path, character, permission, memory, or free-space constraints. Test without altering the original archive.

Look for untouched exact copies.

ClearCopies is not a repair or forensic-recovery tool. It can identify supported byte-identical copies already present in OneDrive, Google Drive, or Dropbox, giving you another place to look before changing a damaged file.

Find exact cloud copies