Corrupt ZIP File
Download a free corrupt ZIP archive file with intentionally damaged internal structures. The file has a valid ZIP signature but contains corrupted local file headers, truncated compressed data, and mismatched CRC checksums. Use it to test how your extraction library, backup verification tool, or file upload handler deals with damaged archives.
What Is Broken
The ZIP file has a valid PK signature (50 4B 03 04) but its internal structures are damaged: local file headers point to wrong offsets, compressed data is truncated mid-stream, CRC-32 checksums don't match the actual data, and the central directory is partially overwritten.
Why It Matters
Corrupt archives occur from incomplete downloads, disk errors, network transmission failures, and storage degradation. Any application that processes ZIP files — upload handlers, backup systems, package managers — must detect and report corruption rather than silently failing.
Expected Parser / Validator Behavior
Extraction tools should detect the corruption via CRC mismatch or header validation failure. They should report which files are damaged and which (if any) can still be recovered. The application should not crash or hang.
Related Invalid Files
Related Validators & Tools
Valid Sample Files
Frequently Asked Questions
How is this ZIP file corrupted?
It has valid ZIP magic bytes but damaged internal headers, truncated compressed data, and incorrect CRC checksums — simulating a real-world partial download or disk error.
Can any files be recovered?
Some extraction tools can recover individual files from partially corrupt archives. Testing this behavior is one of the main use cases for this file.