Mac Error 79: Fix ZIP Extraction Failures
If you see “Unable to expand zip file� with error 79 on your Mac, it usually means the ZIP archive is corrupted, incomplete, or uses a compression method that the built-in Archive Utility cannot handle. The fix is to verify the file, try a different extraction tool, or repair the archive with a command-line utility.
What Error 79 Actually Means
Error 79 is a generic code returned by the macOS Archive Utility when it fails to decompress a ZIP file. It is not a specific error like “file not found� or “permission denied�; instead, it signals that the extraction process hit an unexpected condition. Common triggers include:
- A truncated download — the ZIP file is smaller than it should be.
- Corruption introduced during transfer or storage.
- Use of a newer compression algorithm (like Zstandard) that older macOS versions don’t support.
- File system permissions or disk space issues.
Because the code is generic, the same error can appear for a 1 MB file or a 10 GB archive. The first step is always to rule out the simplest cause: a bad download.
Quick Fixes to Try First
- Re-download the file — If you got it from a website, download it again, preferably using a different browser or a download manager that resumes interrupted transfers.
- Check disk space — Open Apple Menu → About This Mac → Storage. If you have less than a few GB free, the extraction may fail mid-way.
- Restart the Mac — This clears temporary caches that might interfere with Archive Utility.
- Try a different extraction tool — The built-in Archive Utility is minimal; apps like The Unarchiver or Keka often handle problematic archives better.
If none of these work, move on to the command-line method below, which gives you more control and better error messages.
Using Terminal to Diagnose and Fix
The unzip command in Terminal can often extract files that the GUI tool refuses. It also shows exactly what went wrong. Here’s how:
- Open Terminal (Finder → Applications → Utilities → Terminal).
- Navigate to the folder containing the ZIP file:
cd ~/Downloads - Run
unzip filename.zip— replacefilename.zipwith the actual name.
If the file is corrupt, unzip will stop and print an error like “invalid compressed data� or “CRC failed�. In many cases, you can still extract most of the contents with:
unzip -o filename.zip -d output_folderThe -o flag overwrites files, and -d specifies a destination folder. Even if the archive is damaged, this often recovers the undamaged files. For a more aggressive repair, try zip -FF damaged.zip --out repaired.zip — this attempts to reconstruct a new archive from the readable parts. It’s not always successful, but it’s worth trying before giving up.
Why Some ZIP Files Fail on Mac but Work on Windows
ZIP is a container format, and not all ZIPs are created equal. The compression method is stored in the file’s header; if the method is not supported by the decompressor, you get an error. macOS’s Archive Utility supports the standard Deflate method and a few others, but it does not handle every extension. For example, ZIP files compressed with Zstandard (a modern algorithm) or using the “bzip2� method may fail on older macOS versions. Windows’ built-in extractor has its own limitations, but it often handles a wider range of methods because it relies on a different library.
Another common culprit is the “split� or “spanned� ZIP format, where the archive is broken into multiple files (e.g., .z01, .z02). Archive Utility cannot handle these; you need a tool like The Unarchiver or a dedicated splitter/joiner.
How to Prevent Error 79 in the Future
- Always verify downloads — If the site provides a checksum (MD5, SHA-1, SHA-256), compute it and compare. On Mac, use
shasum -a 256 filename.zipin Terminal. - Use a reliable download manager — Browsers can interrupt downloads; a manager will resume and check integrity.
- Keep macOS updated — Apple periodically updates Archive Utility; newer versions may support more compression methods.
- When creating ZIPs on a Mac, choose “Standard� compression — The “Compress� option in Finder uses standard Deflate, which is widely compatible.
Alternative Extraction Tools
If you prefer a GUI over Terminal, several free apps handle ZIP files more robustly than the built-in tool. The Unarchiver is a popular choice because it supports a vast range of formats, including RAR, 7z, and older ZIP variants. Keka is another option that also creates archives. Both are available on the Mac App Store or their official websites. These tools often succeed where Archive Utility fails because they use different decompression libraries and are more forgiving with minor corruption.
When the ZIP File Is Beyond Repair
If both the GUI and command-line tools fail, the archive is likely too damaged to recover. In that case:
- Check if the sender has a backup or can re-upload the file.
- If the ZIP was created from a cloud service (like Google Drive or Dropbox), try downloading it directly from the web interface instead of the sync client.
- If the file came from an email, ask the sender to re-send it, preferably as a fresh ZIP.
Sometimes the data is simply lost. No tool can recreate missing bytes.
Frequently Asked Questions
Can I fix error 79 by renaming the file?
No. The file extension does not affect the internal structure. Renaming a .zip to .zip again won’t change anything. The error is about the archive’s contents, not its name.
Does error 79 mean the file is infected with malware?
No. Error 79 is a decompression failure, not a security warning. However, if you downloaded the file from an untrusted source, it’s wise to scan it with a security tool before attempting extraction, especially if you manage to repair it.
Why does the same ZIP work on my friend’s Mac but not mine?
If your friend’s Mac is running a newer version of macOS, their Archive Utility may support a compression method that your older system doesn’t. Alternatively, they might be using a third-party extractor. Compare your macOS versions and try a third-party tool.
How do I check if a ZIP file is complete without extracting it?
Use the zip -T command in Terminal: zip -T filename.zip. This tests the archive’s integrity and reports if it’s corrupt. A message like “tested OK� means the file is structurally sound.
What if the ZIP is password-protected?
Password-protected ZIPs use encryption. If the password is wrong, you’ll get a different error (usually “wrong password�). Error 79 is not related to passwords. If you have the correct password and still get error 79, the encryption method might be unsupported by Archive Utility; try The Unarchiver.
Can I extract only some files from a corrupt ZIP?
Yes, often you can. Use unzip filename.zip file1.txt file2.jpg to extract specific files. The command will skip damaged parts and extract what it can. This is a good way to recover at least some data.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.