Few things are more anticlimactic than double-clicking a ZIP file on your Mac and watching Archive Utility fail with the vague message that it cannot expand the file because of Error 640. The archive is right there, the progress bar may even start moving, and then macOS gives up without explaining much. Fortunately, Error 640 is usually not mysterious once you understand what macOS is trying to do behind the scenes.
TLDR: macOS Error 640 during archive extraction usually means Archive Utility could not read, verify, or write part of the archive successfully. The most common causes are a corrupted download, an unsupported archive format, permission problems, unusual filenames, or trouble writing to the destination disk. Try downloading the file again, moving it to a simple local folder like Downloads, checking available disk space, and using a dedicated extraction app or Terminal command if Archive Utility keeps failing.
What Error 640 Actually Means
Error 640 is not a friendly, human-readable diagnosis. It is a broad failure code that appears when macOS Archive Utility encounters a problem during extraction but does not surface the deeper reason in the dialog box. In plain English, your Mac is saying: “I tried to unpack this archive, but something about the file, the destination, or the contents stopped me.”
That makes the error frustrating because it does not point to a single cause. It can happen with a ZIP archive from a website, a compressed folder sent by email, a backup downloaded from a cloud service, or a software package created on Windows or Linux. Sometimes the archive itself is damaged. Other times, the archive is perfectly fine, but macOS cannot place one of the extracted files where it needs to go.
Cause 1: The Archive Is Corrupted or Incomplete
The most common explanation is also the simplest: the archive did not download or transfer correctly. Compressed files are sensitive to missing data. A normal document may still open if a small piece is damaged, but an archive often depends on internal indexes, checksums, and file tables. If those are incomplete, extraction can fail immediately or near the end.
This often happens when:
- The internet connection dropped during the download.
- The browser reported the download as complete when it was not.
- The file was copied from a USB drive with read errors.
- The archive was attached to an email and modified by a mail server.
- A cloud storage service did not fully sync the file before you opened it.
A quick way to test this is to compare the file size with the original source, if available. If a website says the ZIP is 800 MB and your file is only 623 MB, the mystery is solved. Re-download the file, preferably using a stable connection, and avoid opening it until the download is fully complete.
Cause 2: Archive Utility Does Not Support the Compression Method
macOS includes a built-in tool called Archive Utility, and it works well for ordinary ZIP files. However, not every file ending in .zip is created the same way. ZIP is a container format, and archives can use different compression methods, encryption styles, file permissions, metadata structures, or multi-part layouts.
Archive Utility may struggle with:
- Password-protected archives using newer encryption methods.
- Split archives, such as files ending in .z01, .z02, and .zip.
- RAR or 7z files renamed incorrectly as ZIP files.
- Archives created on Linux with symbolic links, special permissions, or unusual metadata.
- Very large archives with many thousands of small files.
In this case, the archive may not be broken at all. It may simply be using features that Apple’s basic extractor does not handle gracefully. A more capable extraction tool, such as The Unarchiver, Keka, BetterZip, or command-line utilities like unzip, ditto, or 7zz, may unpack it without complaint.
Cause 3: macOS Cannot Write the Extracted Files
Error 640 can also appear when Archive Utility can read the archive but cannot save one or more extracted files. Extraction is not just “opening” a compressed file; macOS must create folders, write files, apply dates, restore permissions, and sometimes preserve metadata. If any of those steps fails, the whole operation may stop.
Common destination-related problems include:
- You are extracting into a folder where your user account lacks permission.
- The destination is inside a protected system location.
- The external drive is mounted as read-only.
- The disk is nearly full.
- The archive contains files with names that conflict with existing files.
A simple test is to move the archive to your Downloads folder or Desktop and try extracting it there. These locations are normally writable by your user account. If extraction works there but fails on an external disk, network share, or protected folder, the archive was probably not the problem.
Cause 4: Strange Filenames and Path Problems
Archives often travel between operating systems, and filenames that are harmless on one system can be troublesome on another. macOS is flexible, but it still has limits. Very long file paths, odd Unicode characters, invisible control characters, or names that differ only by capitalization can cause extraction problems.
For example, a ZIP created on a case-sensitive Linux system might contain two files named Report.txt and report.txt. On a typical Mac volume, those names may conflict because the file system is usually case-insensitive. Similarly, an archive containing deeply nested folders may produce a path so long that the extractor fails while trying to create it.
This is one reason Error 640 may appear after extraction has already started. Archive Utility might successfully unpack hundreds of files and then stop when it reaches a filename it cannot create. A third-party extractor may show a clearer message, skip the problematic item, or let you rename files during extraction.
Cause 5: Cloud, Network, or External Drive Issues
Modern Macs often work with files that are not truly local. Your archive may appear in Finder inside iCloud Drive, Dropbox, OneDrive, Google Drive, a network share, or an external disk. These locations introduce extra variables. A cloud file may be visible but not fully downloaded. A network connection may pause. An external drive may use a format with limitations.
For example, a FAT32-formatted USB drive cannot store individual files larger than 4 GB. If the archive contains a 6 GB video file, extraction may fail when macOS tries to write it. Network folders can also cause permission mismatches, especially if the archive contains Unix-style ownership or symbolic links.
If you suspect this, copy the archive to your Mac’s internal storage first. Then extract it in a local folder. After extraction succeeds, move the resulting files to the external or network location.
Cause 6: Security and Quarantine Flags
When you download files from the internet, macOS may attach a quarantine attribute. This is part of Apple’s security system and usually helps protect you from unsafe software. In most cases it does not prevent extraction, but it can complicate workflows involving scripts, app bundles, installers, or archives created by automated systems.
Security tools can also interfere. Antivirus scanners, endpoint management software, or corporate device policies may block certain files as they are being extracted. This is especially common with archives containing executable files, scripts, old installer packages, or items that resemble malware even if they are legitimate.
If you are using a work Mac, your organization’s security settings may be involved. In that case, it is better to ask IT before disabling protection or forcing extraction.
How to Fix macOS Error 640
Because Error 640 has several possible causes, the best approach is to troubleshoot from simplest to most specific. The following steps solve most cases:
- Download the archive again. A fresh copy fixes incomplete or corrupted downloads.
- Move the file to a local folder. Try extracting from Downloads or Desktop, not directly from iCloud, a network share, or an external drive.
- Check free space. Make sure you have more space available than the size of the archive. Extraction can temporarily require extra room.
- Shorten the path. Place the archive in a simple folder such as ~/Downloads/Test and try again.
- Use another extractor. If Archive Utility fails, try a dedicated archive app that supports more formats.
- Test with Terminal. The command line may reveal a more useful error message.
For ZIP files, you can open Terminal and run:
cd ~/Downloads
unzip archive-name.zipIf the archive is damaged, Terminal may say something like “End-of-central-directory signature not found” or identify a specific file that cannot be created. That message is often more informative than the graphical Error 640 dialog.
When the Archive Itself Needs to Be Recreated
Sometimes the only real fix is to ask the sender to create the archive again. This is especially true if multiple extraction tools fail or if the file size does not match the expected size. Ask the sender to compress the folder using a standard ZIP method, avoid extremely long folder nesting, and remove unusual characters from filenames.
If the archive is large, it may help to split it using a reliable tool and provide all parts together. If it contains software, the sender should consider distributing it as a disk image or installer package instead of a plain compressed folder.
How to Avoid Error 640 in the Future
You cannot prevent every archive problem, but you can reduce the odds. Download large files over stable connections, avoid interrupting cloud sync, keep archives on local storage while extracting, and use trustworthy compression tools. If you regularly receive archives from Windows or Linux users, keep a more capable extractor installed so you are not limited to Archive Utility.
It also helps to keep filenames simple. Avoid excessive nesting, decorative symbols, trailing spaces, and names that differ only by case. These details may seem minor, but they matter when files move between file systems and operating systems.
The Bottom Line
macOS Error 640 is annoying primarily because it is vague, not because it is rare or catastrophic. In most cases, it points to a practical issue: a broken archive, an unsupported compression feature, a permissions problem, a destination disk issue, or a filename macOS cannot safely create. Start with the easy fixes: re-download the file, move it to a local folder, verify disk space, and try another extraction tool. If those steps fail, Terminal output or a recreated archive will usually reveal the real cause.
The good news is that Error 640 rarely means something is wrong with your Mac. More often, it means the archive and macOS simply disagree about how the files should be unpacked. Once you identify where that disagreement is happening, extraction usually becomes straightforward again.