How to fix the WinZip central and local directory mismatch error
This means the ZIP's index does not match its actual file entries, a sign of a corrupt or truncated archive. A fresh copy is usually the fix. Jump to your situation below or work through the methods in order.
By Neeraj Singh ~6 min Updated Jun 2026 86% found this helpful
Error message
Central and local directory mismatch. Local and central compressed size values don't match.
Summary
The WinZip central and local directory mismatch error means the ZIP's central directory (the index of contents at the end of the file) does not match the local file headers that precede each entry, for example the compressed size recorded in the index differs from the actual entry. This is a clear sign the archive is corrupt or truncated, almost always from a broken or interrupted transfer or a faulty tool that wrote the file. Because the structural data is inconsistent, WinZip cannot trust the archive. The reliable fix is to obtain a fresh, complete copy from the source. If none is available, WinZip's repair can sometimes rebuild the index from the local headers and recover files, and an alternative extractor may salvage the intact entries. Verifying the transfer completed prevents it happening again.
What this error means
A ZIP has two records of its contents: local headers before each file, and a central directory at the end. They should agree. This error means they do not, the sizes or offsets recorded in the index do not match the actual entries, so the archive's structure is inconsistent.
That inconsistency comes from corruption, typically a transfer that was cut short or a tool that wrote the file incorrectly. Since the file itself is damaged, a fresh copy is the dependable fix, with repair and alternative extractors as recovery options when no clean copy exists.
Common causes
The archive is corrupt or truncated.
A broken or interrupted transfer.
A faulty tool wrote the ZIP incorrectly.
Media or disk damage on the file.
Expert insight
“Central and local directory mismatch is the zip contradicting itself, the index at the end says one thing, the file headers say another. That only happens when the archive is corrupt, usually a transfer that got cut off. So the honest fix is a fresh copy from the source. If you cannot get one, WinZip's repair can sometimes rebuild the index from the local headers and pull the files out, and another extractor might grab the intact ones, but the file is damaged either way.”
Manager, Tech Support & Operations · 19+ years fixing Windows and system errors
✓ How to fix it
Method 1
Get a fresh copy of the archive
1Download or obtain a complete, fresh copy from the original source.
2The mismatch means the current file is corrupt.
3Open the new copy.
Method 2
Repair the archive
1Use WinZip's repair, which can rebuild the central directory from the local headers in some cases.
2Then try extracting.
3Recovery depends on the extent of damage.
Method 3
Recover files with another extractor
1Open the archive in a different tool to salvage the intact entries.
2Recover what you can.
3Get a clean copy for anything missing.
Method 4
Verify the transfer
1Confirm the file size matches the source so the transfer completed.
2Re-transfer over a reliable connection if it did not.
3Then reopen the archive.
This mismatch means the ZIP's index does not match its file headers, so the archive is corrupt or truncated. Get a fresh, complete copy from the source. If none exists, WinZip repair can sometimes rebuild the index and recover files, and an alternative extractor may salvage intact entries. Verify the transfer to prevent recurrence.
Frequently asked questions
What does central and local directory mismatch mean?
It means the ZIP's central directory index does not match the local file headers, for example the recorded compressed sizes differ. It indicates the archive is corrupt or truncated.
How do I fix it?
Obtain a fresh, complete copy of the archive from the source, since the file is corrupt. If none is available, use WinZip's repair to rebuild the index, or another extractor to salvage intact files.
What causes the mismatch?
Corruption, almost always from a broken or interrupted transfer, or a faulty tool that wrote the ZIP. The index and the actual entries end up inconsistent, so WinZip flags the mismatch.
Can WinZip repair it?
Sometimes. WinZip's repair can rebuild the central directory from the local headers and recover files when the damage is limited, but a badly truncated archive usually needs a fresh copy.
Will another tool open it?
It may recover the intact entries. A different extractor sometimes salvages files despite the mismatch, though it cannot restore data that is genuinely missing from a truncated file.
How do I stop it happening again?
Verify the file size against the source after transferring, and use a reliable connection. Confirming the transfer completed prevents the truncation that causes the mismatch.
Still not working?
If repair cannot rebuild the index and no clean copy exists, the archive is likely truncated past the point of recovery for the missing entries; restoring the original from a backup is then the dependable path. You can also submit your error to us for a tailored fix.