Universal Zip
Windows 10 & 11 Buy license · $24.95
Troubleshooting

How to Check If a ZIP File Is Corrupted (Before You Need It)

How to check if a zip file is corrupted on Windows: run an integrity test, compare checksums with PowerShell and spot the signs of a damaged archive early.

Updated 5 minute read The Universal Zip team

The reliable way to check if a ZIP file is corrupted is to run an integrity test in an archive program. The test decompresses every file inside the archive in memory and compares it with the checksum stored when the archive was made, without writing anything to disk. If every file passes, the archive is intact. Windows has no built-in test command, so without an archive program the closest check is to extract everything to a temporary folder and watch for errors, or to compare the file's hash with one published by the sender.

Here is how each method works, what the results mean, and when to test.

How ZIP files detect damage

When a file is added to a ZIP, the archive stores a CRC-32 checksum: a short number calculated from the file's original contents. When the file is extracted, the checksum is calculated again from the decompressed data. If the two numbers do not match, the data has changed, which means corruption. 7Z and RAR archives store similar checksums.

This is why a corrupted archive often opens normally and shows its file list, then fails on extraction with "CRC failed" or "data error". The list lives in one part of the file; the damage may be somewhere else.

Universal Zip includes an integrity test that checks an archive for damage before you rely on it. The general process in any archive program:

  1. Open the archive, or select it in the program.
  2. Choose the Test command.
  3. Enter the password if the archive is encrypted. Encrypted files cannot be checked without decrypting them.
  4. Wait for the test to finish and read the result.

A clean result says there are no errors. A failed result lists the files with CRC or data errors, which tells you exactly what is damaged. Testing works the same for ZIP, 7Z, RAR and the other formats the program opens, including multi-part sets. A test of a large archive takes roughly as long as extracting it, because every byte is decompressed, but nothing is written to disk and nothing is overwritten.

Method 2: Extract to a temporary folder

If you only have File Explorer, a full extraction is a rough substitute:

  1. Right-click the ZIP and choose Extract All.
  2. Extract to a temporary folder on a drive with enough room.
  3. Watch for error messages such as "the compressed (zipped) folder is invalid", "Windows cannot complete the extraction" or errors on specific files.
  4. Compare the number of files and total size with what you expect.
  5. Delete the temporary folder afterwards.

This uses disk space and time, and File Explorer's error messages are vague. It also cannot test password-protected AES archives, RAR files on Windows 10 or split archives. Still, an extraction that completes without errors is a reasonable sign the archive is healthy.

Method 3: Compare checksums

If the sender or download page publishes a hash, usually SHA-256, you can confirm your copy is byte-for-byte identical to the original. This does not test whether the archive's contents are valid, but it proves the file was not damaged or altered in transit.

  1. Open PowerShell in the folder with the file.
  2. Run Get-FileHash archive.zip (SHA-256 is the default).
  3. Compare the long string it prints with the published value. Every character must match; case does not matter.

In Command Prompt, certutil -hashfile archive.zip SHA256 does the same. If you want to send your own archive with a hash, run the command before sending and include the result in your message.

Reading the results

ResultWhat it meansWhat to do
Test passes, no errorsArchive is intactSafe to rely on
CRC failed on some filesData inside is damagedExtract the good files, get a fresh copy for the rest
Unexpected end of archiveFile is truncatedDownload or copy it again
Cannot open file as archiveHeader damaged or not really a ZIPCheck the file type, then get a new copy
Hash does not matchFile changed in transitDownload again from the original source
Wrong password errors during testPassword issue, or damage in encrypted dataConfirm the password first

If you see "unexpected end of archive", our guide to the unexpected end of archive error explains the fix.

Common causes of corrupted ZIP files

  • Interrupted downloads, especially large files over unstable connections.
  • Failing storage: aging hard drives, cheap or worn USB sticks and SD cards.
  • Unsafe removal of USB drives while data was still being written.
  • FTP transfers in text (ASCII) mode, which alter bytes in binary files.
  • Copying an archive while it was still being created, or syncing it before it finished.
  • Email systems that strip or mangle attachments, which is rare but does happen with very large messages.

When to test an archive

  • Right after creating a backup archive, before you delete the original files.
  • Before sending an important archive to a client or colleague.
  • After copying archives to removable media or cloud storage you plan to rely on.
  • Periodically for long-term archives, such as once a year, so damage is spotted while another copy still exists.
  • Before extracting a huge download, so you do not waste time on an archive that will fail at 95%.

Testing tells you an archive is damaged; it does not repair it. The real protection is keeping more than one copy of anything important, ideally in different places. Our guide to compressing files for backup builds testing into a simple routine.

Can a corrupted ZIP be repaired?

Sometimes partly. If only some files inside are damaged, you can usually still extract the others: open the archive, select the files that passed the test and extract them. Specialized repair tools exist that try to rebuild a damaged ZIP structure, with mixed results. RAR archives created with a recovery record can be repaired by the official RAR software if damage is limited. In most cases, getting a fresh copy from the source is faster and more reliable. Universal Zip's integrity test makes it quick to confirm the new copy is good before you delete anything.

Frequently asked questions

How can I tell if a zip file is corrupt?

Run an integrity test in an archive program. It decompresses every file in memory and checks it against the stored CRC values without writing anything.

Can I check a file's hash on Windows?

Yes. In PowerShell run Get-FileHash followed by the file path, then compare the SHA256 value with the one the sender published.

What causes zip files to become corrupted?

Interrupted downloads, failing drives, bad USB sticks, transfers in the wrong mode and copying files while they are still being written.

Get three guides like this every month, plus software update notices.Subscribe →