Repair a corrupted ZIP and extract what's inside — no upload

In short

This tool repairs corrupted and truncated ZIP archives: it rebuilds the missing table of contents and extracts every file whose data survived, even when one strict unzipper refuses the whole thing. It all runs in your browser — the archive is never uploaded, so 0 bytes leave your device, which you can confirm yourself in the browser's Network tab. The one honest limit: if a file's compressed data is itself damaged, that entry can't be recovered.

ZIP won't open or extract? Repair it now

1. Drop the archive
2. Repair and extraction run locally
3. Download your files

To fix a corrupted ZIP, you rebuild the archive's table of contents and pull out every file whose data survived. IntactFile does exactly that, in your browser: drop the archive, the engine scans it locally, reconstructs the structure, and hands back the salvageable files, even when the archive as a whole is past saving. Nothing is installed, and the archive is never uploaded anywhere.

How ZIP corruption works

A ZIP is a row of independently compressed files followed by a central directory: the archive's table of contents, stored at the very end. Extractors read that directory first to learn what's inside and where. That layout explains almost every broken archive you'll meet:

When a download or copy is cut short, the end of the file is what goes missing, which means the table of contents is lost while the files themselves sit intact in the earlier part of the archive. Your unzipper refuses the whole thing because its index is gone, not because your files are.

The same layout makes partial salvage possible: ZIP writes a small local header in front of every file it stores. By scanning for those headers, the engine finds each surviving entry and extracts it individually, no table of contents required. So the honest promise is not "fixed or failed" but every file whose data survived comes out.

The errors this covers

Different tools word the same damage differently. If you're seeing one of these, you're in the right place:

WinRAR — the file ends before the table of contents. Classic truncated download.

WinRAR — the structure can't be parsed at all; the start of the file may be damaged too.

7-Zip — no recognizable archive structure where it expects one.

unzip on the command line — the most literal of the four: the end record that anchors the table of contents is missing.

Windows Explorer has its own wording: if you're staring at The Compressed (zipped) Folder is invalid, there's a dedicated page for that error, including the free fixes to try first.

Why archives break

Three causes account for nearly all of it. Interrupted transfers: a download that stalled at 96% or a USB stick pulled mid-copy: the tail of the file, table of contents included, never arrived. Email and cloud mangling: gateways and sync clients occasionally truncate or re-encode attachments, and large multi-file cloud downloads are a known weak point. Storage trouble: bad sectors corrupt bytes in place, the only cause of the three that can hit the compressed data itself.

What this can and can't fix

If nothing can be salvaged, the tool says so and explains why, and you're never charged for a failed repair.