"Unable to expand": reading the error properly

Archive Utility's failure message always looks the same:

Unable to expand "file.zip" into "Downloads". (Error 79 - Inappropriate file type or format.)

Most people read the first half and give up. The useful part is the bit in brackets. That number is not specific to Archive Utility — it is a standard Unix error code, the same one any program on your Mac would report for the same underlying problem. Read it, and you know which kind of failure you are dealing with.

We covered the general causes of a ZIP that will not open earlier, including the .cpgz loop. This is the companion: what each error number means.

Error 1 — Operation not permitted

What it means: the system refused an action on security grounds, not because the file is damaged.

Common causes:

• The destination folder is protected, and the process doing the extracting does not have permission to write there.
• The archive or destination is on a volume with restrictions — a locked network share, an external drive formatted for read-only access.
• Quarantine or security restrictions on the downloaded file are interfering.

What to try: move the archive to a plain folder in your home directory — a new folder in Documents, for instance — and expand it there. If that works, the original location was the problem.

Error 2 — No such file or directory

What it means: something the extraction needed was not where it expected.

Common causes:

• The download was incomplete, and the file ends before the archive's index.
• The file was moved or renamed while extraction was starting — common with files still syncing from cloud storage.
• A multi-part archive is missing parts.
• The archive contains paths too long for the destination.

What to try: check the file size against what it should be, and redownload if it is smaller. For cloud-synced folders, wait until the file is fully downloaded — or copy it to a local folder first.

Error 22 — Invalid argument

What it means: the extractor was handed something it could not interpret — a value, a name or a structure that is not valid.

Common causes:

• Filenames in the archive contain characters that are not valid on macOS, or are encoded in a way macOS cannot convert.
• The archive uses features Archive Utility does not support, such as certain compression methods.
• Very large archives with unusual structures.

What to try: test the archive with unzip -t file.zip in Terminal. If it reports no errors, the archive is fine and a different extractor is likely to succeed.

Error 28 — No space left on device

What it means: exactly that. The disk filled up during extraction.

Common causes: archives can expand to many times their compressed size. A 3 GB archive of text or databases might need 20 GB.

What to try: check the uncompressed size first — unzip -l file.zip shows a total at the bottom — then free space or extract to a larger drive. Delete the partial output, which may be large.

Error 63 — File name too long

What it means: a path inside the archive exceeds what the file system allows.

Common causes: deeply nested folders with long names, often from archives made on other systems.

What to try: extract to a folder with a very short path, such as a new folder at the top of your home directory. If that is not enough, an extractor that lets you flatten or rename entries is needed.

Error 79 — Inappropriate file type or format

What it means: the file is not the kind of archive its name claims, or it is damaged enough that it no longer looks like one.

Common causes:

• The file is not actually a ZIP — a website served an error page, or a different archive type was given a .zip extension.
• The archive is truncated or corrupted.
• It is a format Archive Utility does not handle, such as RAR or 7z with the wrong extension.

What to try: check what the file really is:

file ~/Downloads/file.zip

This reads the file's contents, not its name, and reports what it is: "Zip archive data", "RAR archive data", "7-zip archive data", or "HTML document" if you downloaded an error page.

Error 92 — Illegal byte sequence

What it means: text that should be valid in the current encoding is not.

Common causes: filenames inside an archive made on Windows in a legacy code page — frequently Turkish, Cyrillic, Greek or East Asian names — that cannot be converted to the UTF-8 macOS expects.

What to try: an extractor that lets you choose the filename encoding. The file contents are usually fine; only the names are misread.

Looking up any other code

For codes not listed here, Terminal will tell you what the number means:

perl -e '$!=79; print "$!\n"'

Replace 79 with your number.

Where Ziploom fits

Ziploom is an archive utility for Apple silicon Macs that extracts RAR, ZIP and 7Z — including the formats that produce error 79 in Archive Utility — with optional password support, and creates ZIP and 7Z.

Several of the errors above are caught before extraction rather than halfway through: Ziploom checks available disk space, oversized jobs, unsafe paths, symbolic links and suspicious compression ratios before files are installed at the destination. You decide how existing destinations are handled, follow progress, and reveal the output in Finder.

It cannot repair a truncated download. All processing stays on your Mac, with no accounts, analytics, advertising, telemetry or network features.