Why a ZIP File Will Not Open, and How to Fix Each Cause

Windows and macOS both open ZIP files out of the box. So when one refuses, there is a specific reason, in the file or in the environment. There are about six of them, and which one you have is nearly always settled by the error wording plus whether you get a file listing at all. This article walks through telling them apart and fixing each.

First: do you get a listing?

Start with one question. When you open the ZIP, do you see the names of the files inside? If you do, the archive's index — the directory it keeps at the end — is intact, and your problem is a password, a split archive, garbled names, or a compression method.

If there is no listing at all, and you get "the folder is empty" or "the archive is damaged", the index could not be read. Either the download was cut short, or the file is not a ZIP. To check the listing without extracting, drop the file into the extractor.

Cause 1: the download never finished

This is the most common one. A ZIP keeps its index of what-is-where at the end of the file, so an incomplete copy yields nothing at all. Having the first 99% is worth no more than having none of it.

How to tell, and what to do:

• Compare the file size with what the source says. Even a few bytes short means the index is cut off.
• Look for .crdownload or .part on the end of the name. If it is there, the download itself never completed.
• Download it again from scratch. A browser's resume can splice onto a bad partial file; delete it first, then fetch it fresh.

For email attachments, a size limit somewhere along the way may have truncated it, in which case re-downloading will never help. Ask the sender to use a file transfer service instead.

Cause 2: it needs a password

A password-protected ZIP has a giveaway: you can see the file names, but opening one prompts for a password. If the listing appears, nothing is damaged.

If you do not have the password, there is nothing to be done at your end; ask the sender. Sending the password in a second email over the same channel adds very little security, and a number of organisations have moved away from the practice. If it keeps happening, suggesting a file transfer service is the practical fix.

If instead you need to send a password-protected ZIP yourself, the ZIP password tool makes one in your browser (Windows 11 has no built-in way to put a password on a ZIP). Send the password by some other route than the ZIP.

Cause 3: it is split across files

Names like data.zip.001, data.z01 or data.part1.rar mean one archive was cut into pieces. Put every piece in the same folder and open only the first one. If any piece is missing, nothing extracts.

Numbered extensions are beyond the built-in Windows handler, so you need an archiver such as 7-Zip. Split formats vary by the software that made them, so knowing which tool the sender used shortens the problem considerably.

Cause 4: the names are garbled

If the listing is full of characters like 縺ｯ縺ｾ縺, the encoding of the file names does not match what the reader assumed. ZIP does not record the encoding of names, so an archive made on one system garbles on another. A macOS "unable to expand (Error 1)" can also come from this, but that error does not distinguish causes, so do not stop here if nothing else fits.

The contents are untouched; only the names are affected. Use the extractor and pick the encoding, or use CubeICE or Explzh on Windows, or The Unarchiver on a Mac. The mechanism, and how to avoid causing it when you send, is in why file names in a ZIP come out garbled.

Cause 5: it is not really a ZIP

A file named .zip is not necessarily one. Two cases turn up often:

• It is actually a RAR or 7z. The sender renamed it, or picked the wrong format when saving.
• It is actually HTML. A failed download saved the error page under the .zip name. Suspect this whenever the file is only a few kilobytes.

The contents settle it. Drop the file into the file identifier: it reads the format from the bytes rather than the name, and offers to save a copy with the correct extension.

Cause 6: your archiver is too old for it

ZIP dates from 1989 and has been extended since. These variants defeat older software:

• Archives over 4 GB, or with more than 65,535 files. These need the ZIP64 extension.
• Compression other than Deflate. Choosing LZMA or PPMd in 7-Zip produces a ZIP the built-in handlers cannot read.
• AES encryption. The Windows built-in handler only understands the old, weak scheme.

A current version of 7-Zip handles all three. It is free, and its coverage is far wider than the built-in tools.

Summary

• Check first whether you get a file listing. If you do, the index is fine and it is a password, a split, garbled names, or a compression method.
• No listing means a truncated download or not a ZIP at all. Compare the size against the source and run it through the file identifier.
• For split archives, gather every piece in one folder and open the first. One missing piece stops everything.
• Garbled names leave the contents intact; choose the encoding and extract.
• If an old archiver is the obstacle, a current 7-Zip resolves nearly all of it.