Test ZIP Integrity
Verify a ZIP archive end to end: every entry is decompressed and its CRC-32 (or AES authentication code) checked, and the archive structure is scanned for problems such as overlapping entries or mismatched headers. You get a clear pass/fail report per file.
Test ZIP Integrity
Decompress every file and check it against its stored checksum, without saving anything.
Drop the ZIP you want to test
or choose one from your device
Files stay on your device. Nothing is uploaded.
How to use Test ZIP Integrity
- 1
Open the ZIP
Drop the archive you want to check, or choose it with the file picker.
- 2
Add a password if needed
For an encrypted archive, enter the password to verify the protected files too. Without it, those files are reported as “needs password”.
- 3
Run the test
Every file is decompressed in a background worker and checked against its stored CRC-32, and the archive structure is scanned for problems.
- 4
Read the report
Each file gets a clear status, with structural warnings listed separately. Nothing is written to disk.
Why use Aback ZIP's Test ZIP Integrity?
Full CRC verification
Every entry is decompressed and its CRC-32 compared with the value recorded when the archive was made. AE-2 encrypted entries, which store no CRC, are checked with their AES authentication code instead.
Structural checks
Catches overlapping entries, duplicate names, unsafe paths, mismatched local and central headers, entry-count mismatches and data prepended to the archive.
Works with encrypted ZIPs
Enter the password to verify protected files as well, which also confirms the password is correct before you send it to someone.
Nothing extracted to disk
Files are decompressed in memory only to be checked, then discarded. The test runs locally in your browser and nothing is uploaded.
Common use cases
After a large download
Confirm a big archive arrived intact before you delete the download link or rely on its contents.
Before deleting originals
Verify a backup ZIP thoroughly before wiping the source folder it was made from.
When an extractor complains
Got “unexpected end of archive” or “the compressed folder is invalid”? Find out which files are actually damaged and which are fine.
After joining or repairing
Check the result of Join ZIP Parts or Repair ZIP before sharing it.
Before sending a protected ZIP
Test with the password you are about to share, to be sure every file decrypts with it.
Release and CI artifacts
Spot-check a release ZIP before publishing it, so users don't find the corrupt entry for you.
About Test ZIP Integrity
Reading the results
| Status | Meaning | What to do |
|---|---|---|
| OK | The file decompressed and matches its checksum | Nothing |
| CRC error | The file decompressed, but the data doesn't match its checksum, so it is damaged | Get a fresh copy, or recover what you can with Repair ZIP |
| Corrupt | The file's data or headers can't be read | Try Repair ZIP |
| Needs password | The file is encrypted and no password was given | Enter the password and test again |
| Wrong password | The password doesn't decrypt this file | Check the password; some archives use different passwords per file |
| Unsupported method | The file uses a method such as Deflate64 or PPMd that can't be decompressed here | Test it with 7-Zip |
Test, view or checksum?
- ZIP Viewer reads only the archive's index. It is fast, but it doesn't prove the data is intact.
- Test ZIP decompresses every file and checks it. It takes longer and tells you whether the archive is internally consistent.
- ZIP Checksum computes SHA-256 or MD5 so you can compare against a value published by the sender, which also detects deliberate changes.
A test checks files against checksums stored in the same archive. It catches damage that happened after the archive was made, but if a file was already broken before it was zipped, or the archive was rebuilt with new checksums, it will still pass.
Limitations
- A passing test means each file matches the checksum stored in the archive. It can't detect files that were already damaged before zipping, or deliberate changes made with recalculated checksums; compare a published SHA-256 with ZIP Checksum for that.
- Entries using Deflate64 or PPMd can't be decompressed here, so they are reported as unsupported rather than tested. Store, Deflate, BZIP2, LZMA, XZ and Zstandard entries are all tested.
- The archive's index must be readable. If it is missing, for example after an interrupted download, use Repair ZIP instead.
- Testing decompresses every file, so it takes longer than viewing, and very large archives may hit memory limits on phones and low-memory devices.
Processing happens locally in your browser. Your files are not uploaded, and closing the tab discards everything.
Related tools
Test ZIP Integrity: frequently asked questions
No. Every file is decompressed and checked in a Web Worker in your browser, and only the report is shown to you. Nothing is sent to a server and no account is needed.
Open it here and run the test. Every file is decompressed and its CRC-32 compared with the stored value, and the structure is checked. A report shows each file as OK, CRC error, corrupt, needs password, wrong password or unsupported method.
The file could be decompressed, but the result doesn't match the checksum recorded when the archive was created, so at least part of the file is damaged. The usual causes are an incomplete download, a failing disk or a faulty transfer. A fresh copy is the best fix.
Yes. Enter the password to verify the encrypted files. Without it, those files are listed as “needs password” and the unencrypted ones are still tested. The password is used only inside this page.
Common causes: the built-in Windows or macOS extractor doesn't support AES encryption, Windows hits its path-length limit on deeply nested folders, or the disk is full. Try 7-Zip, or extract to a short path like C:\x.
The file is most likely truncated, usually by an interrupted download or copy. Download it again if you can. If not, Repair ZIP scans for the files that are still intact and rebuilds a valid archive from them.
No. The archive is only read. Nothing is extracted to disk and no new file is created; you just get the report.