everyday mac tools

The Mac says it is unable to expand a zip file

· 6 min read

When a Mac says it is “Unable to expand” a zip file, the archive is usually one of three things: not fully downloaded, damaged somewhere inside, or in a format Archive Utility does not handle. Checking the file size and running one Terminal command tells you which, and in many cases a different extraction method gets your files out without any new software.

Work through the checks below in order. The early ones take seconds and solve the most common cases.

What the error numbers are telling you

Archive Utility, the built-in app that runs when you double-click a zip, usually adds a short code in brackets. They are vague, but they point in a direction.

  • Error 1, Operation not permitted. Often a permissions or location problem rather than a broken file: the destination folder is protected, the disk is full, or a path inside the archive is too long. It also appears with damaged archives, so do not stop at the first explanation.
  • Error 2, No such file or directory. The zip was moved, renamed or is still being written while Archive Utility tried to read it.
  • Error 79, Inappropriate file type or format. The file is not a valid zip as far as the Mac can see. That typically means a truncated download, a file that was never a zip (an HTML error page saved with a .zip name is common), or damage to the central directory at the end of the archive.

Check the download first

A large share of these errors come from a file that simply is not all there.

  1. Select the zip in Finder and press Command-I. Note the size.
  2. Compare it to the size shown on the page or in the message you got it from. If it is noticeably smaller, the download stopped early.
  3. Look for a .download or partial extension, or a progress bar still visible on the icon. If there is one, the browser is still writing the file.
  4. Download it again, ideally on a stable connection, and try the fresh copy before anything else.

If the file came from someone else, ask whether their copy opens. A zip that was damaged before it was sent cannot be fixed by downloading it a second time.

Also check free space. Expanding needs room for everything inside the archive, which can be several times the size of the zip. System Settings, General, Storage shows what you have.

Test the archive in Terminal

Terminal gives you a far more specific answer than Archive Utility does. Open Terminal, type unzip -t with a space after it, drag the zip onto the window to fill in its path, and press Return.

The test reads every file in the archive without extracting anything and reports on each one. Three outcomes are common:

  • “No errors detected”: the archive is fine, and the problem is the destination, permissions or space. Try expanding into a new folder on the Desktop.
  • A list with some files marked bad: the archive is partly damaged. Most of it is probably still recoverable.
  • “End-of-central-directory signature not found”: the end of the file is missing or wrecked. This is the classic sign of a truncated download.

If the test mentions an unsupported compression method or asks for a password it cannot use, the zip was made with encryption or compression that the built-in tools do not support. That is not damage; it needs an archive app that handles that format, or the sender can recreate it with standard settings.

Try a different way to extract it

Archive Utility is not the only extractor on the Mac, and the others are sometimes more forgiving.

Use ditto. This is the command macOS itself uses for many archive jobs. In Terminal:

ditto -x -k ~/Downloads/archive.zip ~/Desktop/extracted

Replace the paths with your own (dragging the file in works here too). It creates the destination folder if needed.

Use unzip directly. unzip ~/Downloads/archive.zip -d ~/Desktop/extracted extracts everything it can and names the files it cannot read, rather than giving up on the whole archive the way Archive Utility tends to.

Ask zip to rebuild the index. When the central directory at the end is damaged, the zip tool can scan the file and build a new one:

zip -FF ~/Downloads/archive.zip --out ~/Desktop/archive-fixed.zip

Then test and extract the new file. This writes a separate copy and leaves the original untouched, which is the right habit with anything damaged: never experiment on your only copy.

Check for a split archive. If you have files ending .z01, .z02 alongside the zip, it is one archive in several parts. All the parts must be in the same folder before anything will open it, and a single missing part means the files that span it cannot be rebuilt.

When the zip holds something you cannot get again

If the tests show real damage and there is no clean copy to download, you are into repair. Manatee accepts zip files and attempts container repair, alongside repairing the video, PDF and Word documents that often arrive inside archives. It reports honestly: Fixed, Partial if only some of the contents come back, or Not fixable. It never modifies the original and always writes a new copy next to it, so trying it cannot make things worse. It runs entirely on the Mac with no upload, which matters if the archive contains anything private. It is free for 24 hours with every feature, then $9 once.

What repair cannot do is invent data. If a download stopped at 60 percent, the files that were in the missing 40 percent are not in the file on your Mac, and nothing will produce them. In that case the only real fix is another copy from the source.

A related case: the archive expands fine but one document inside will not open. That is a problem with that file, not the zip, and it is a separate repair job. A Word document is itself a zip container internally, which is why the same kind of damage can affect it.

Stop it happening next time

  • Let downloads finish before double-clicking them, particularly large ones on a laptop that might sleep. Stopping a Mac sleeping during a long download covers the settings.
  • When sending a big archive, check the size on your side and ask the recipient to confirm theirs matches.
  • Prefer fewer, smaller archives over one enormous one. Damage in one part then costs you less.

Questions

Can I open a damaged zip in Finder at all? Double-clicking always hands it to Archive Utility, which tends to stop at the first problem. The Terminal commands above will usually extract the undamaged files that Archive Utility refuses to touch.

Why does the zip open on another computer but not on my Mac? Usually a compression method or encryption the Mac’s built-in tools do not support, or file names inside the archive that are too long or use characters the Mac rejects. Run unzip -t and read the message; it normally names the reason.

Is it safe to expand a zip that gave an error? The error itself is not a danger sign, but a file that is not what it claims to be deserves caution. If a supposed zip turns out to be a web page or an app, delete it and get the file from the original source.