Record the exact error first
Write down the error word for word before you do anything else. “The archive is invalid,” “incorrect password,” “unexpected end of archive” and a tool that opens but shows an empty list are four different diagnoses. Treating them all as “the ZIP is broken” sends you down the wrong path and risks overwriting your only copy.
Then test whether the problem is this archive or your tool. Open a different ZIP you know works — any small archive will do. If that one also fails, investigate the application or the download location. If only this archive fails, the file itself is the subject of the investigation.
Keep the archive unchanged while you work. Do not rename it, do not extract over the top of a previous attempt, and do not delete the copy in your downloads folder. Each of those removes evidence, and one of them may be the thing that still opens.
| What you see | Most likely cause | Where to go |
|---|---|---|
| “Unexpected end of archive” | Download did not finish | Section 2 |
| “Not a valid archive” / nothing recognises it | File is not actually a ZIP | Section 3 |
| Password prompt | Encrypted archive | Section 4 |
| Opens, but the list is empty or short | Partial or oddly built archive | Section 5 |
Confirm the download actually finished
An incomplete download is the most common reason a genuine ZIP fails, and it is also the easiest to confirm. Check the file size against the size quoted at the source — a download page, the email attachment list, or the sender. A zero-byte file contains nothing at all; a file noticeably smaller than advertised stopped partway.
Download again using the source’s real download action rather than a preview link, and save it under a new name so you can compare the two. Saving the page that surrounds a download often produces an HTML file with a .zip name, which no archive tool can read. If you were signed in when the first attempt was made, confirm you still are.
Interrupted transfers also come from the network rather than the file. A connection that drops mid-download, a VPN that reconnects, or a mail client that truncates large attachments all produce the same symptom. If two downloads both arrive short at the same size, suspect a limit somewhere in the path rather than bad luck.
Check whether it is really a ZIP
A name ending in .zip guarantees nothing about the contents. Error pages, login redirects and plain documents all get saved with misleading names, especially when the download came from a link rather than an attachment. Opening the file in a text editor is a quick sanity check: if you see recognisable HTML or an error message in English, you have a webpage, not an archive.
Drop the file into Unzip as a second opinion. Because it reads the archive structure and lists the entries, a file that produces no list at all is telling you something different from one that lists forty files and then fails on extraction. The first is probably not a ZIP; the second probably is.
Check what the sender meant to send. An export that was supposed to be a folder of documents and arrived as a 4 KB file was likely an error response from the system that generated it, not a compressed archive. In that case the fix is on their side — re-running the export — not on yours.
Rule out passwords and unsupported formats
A password prompt is not a damaged-file error. The archive is intact and encrypted, and it needs the password. Browser-based tools cannot open encrypted archives at all, so use your operating system’s archive tool with the password, or ask the owner for an unprotected copy if you are entitled to one. Watch for a space accidentally copied onto the end of a pasted password.
If no password was ever mentioned, check the extension properly. RAR and 7z archives are not ZIPs and will not open in a ZIP tool, regardless of what you rename them to — the internal layout is different, so the label is cosmetic. Those need the matching application, or a replacement archive in ZIP format.
Self-extracting archives are a third case: an .exe that unpacks itself. Treat an unexpected one with suspicion, particularly if it arrived by email. Ask the sender for a plain .zip instead. There is rarely a good reason to run an unfamiliar program when a standard archive would have done the job.
Handle archives that extract but are incomplete
An archive can extract without error and still be missing things. Compare the extracted file count against the list the archive showed, and look inside subfolders rather than only the top level. The shortfall is easy to overlook when the files you happened to check are present.
If extraction stops partway on a large archive, memory is a plausible cause, particularly in a phone browser or a tab that has been open for a long time. Move the archive to a desktop, close other tabs and try again. Repeating the same attempt on the same device rarely changes the outcome.
When one specific file inside fails and everything else is fine, the archive has done its job and that file is the problem. Pull it out on its own and diagnose it as an ordinary file — a PDF that will not open has its own set of causes, none of which are about the archive it travelled in.
Ask for a replacement that is easier to open
If the file is genuinely damaged, a new copy beats attempted repair. There is no reliable way to reconstruct data that never arrived, and tools promising guaranteed recovery of a truncated archive are overstating what is possible. Go back to the source and ask for a fresh export.
Be specific about what you need: a standard .zip, no password, and the expected file count so you can verify it. If the archive was large, suggest a shared link instead of an attachment, or ask for it in two halves — both avoid the size limits that caused the truncation in the first place.
When you are the one sending, you can prevent most of this. Build the archive with Create ZIP, open your own file before sending it, and state the file count in your message so the recipient can check. The guide to emailing large files covers staying under the limit that caused the problem.
Test the archive in your browserList the contents to see whether the archive is readable at all.
Open Unzip →Frequently asked questions
Can a damaged ZIP file be repaired?
Sometimes partially, but there is no reliable fix for missing data. Requesting a fresh archive from the source is faster and gives you a complete copy.
Does renaming a .rar file to .zip make it open?
No. The extension is only a label; RAR and 7z use different internal structures. Renaming leaves the contents unreadable to a ZIP tool.
Why does one file inside the archive fail while the rest work?
The archive is fine and that single file is the problem — it may be corrupted, empty or in a format your application cannot open. Diagnose that file on its own.