Few things are more frustrating than downloading a ZIP file, double-clicking it, and being greeted by a vague Mac message such as “Unable to expand… Error 640”. The error does not explain much, and it can make a perfectly ordinary archive look broken or suspicious. In most cases, though, Error 640 is not a disaster; it usually points to a problem with the ZIP file, the destination folder, permissions, macOS’s built-in Archive Utility, or the way the file was downloaded.
TLDR: Error 640 when unzipping files on a Mac usually means macOS cannot properly read, access, or write the contents of the archive. Start by moving the ZIP file to your Desktop, downloading it again, and checking that you have enough disk space. If that fails, try unzipping with Terminal or a third-party extraction app, then check file permissions and possible archive corruption. For files from Windows or cloud services, renaming the file and removing special characters can also help.
What Does Error 640 Mean on a Mac?
macOS does not provide a highly detailed public explanation for every Archive Utility error code. Error 640 generally appears when the system fails to expand a compressed archive, most commonly a .zip file. It may happen immediately after you double-click the file, or it may appear after the progress bar starts and then stops unexpectedly.
In practical terms, Error 640 usually means one of these things:
- The ZIP file is incomplete or corrupted.
- The Mac cannot write the extracted files to the selected location.
- The file name or folder path contains problematic characters.
- The archive was created in a way macOS Archive Utility does not handle well.
- There is a permissions issue with the file, folder, or external drive.
- The file was interrupted during download or sync.
The good news is that you can usually fix the problem with a few straightforward checks.
1. Move the ZIP File to Your Desktop
The simplest fix is often the most effective. If the ZIP file is inside a synced folder, external drive, network location, email attachment preview, or protected system folder, macOS may have trouble accessing or writing the extracted contents.
Try this first:
- Drag the ZIP file to your Desktop.
- Make sure the file has fully copied.
- Double-click the ZIP file again.
The Desktop is a local, user-accessible location, which makes it a good testing area. If the file extracts successfully there, the original location was likely the issue. This is especially common with files stored in iCloud Drive, Dropbox, Google Drive, OneDrive, external USB drives, or shared network folders.
2. Download the File Again
A very common cause of Error 640 is an incomplete download. A ZIP archive must have all of its internal structure intact. If your internet connection dropped for a moment, the browser stopped early, or the file was still syncing from the cloud, the archive may appear normal but fail when opened.
Before trying complicated fixes, download the file again from the original source. If possible, use a different browser. For example, if you used Safari, try Chrome or Firefox. Also compare the file size with the size listed on the download page. If the website says the file should be 2.4 GB but your Mac shows 700 MB, the download is incomplete.
If someone sent you the archive by email or messaging app, ask them to resend it. Large ZIP files can be damaged during transfer, especially if they pass through systems that scan, compress, or split attachments.
3. Check Your Available Disk Space
Unzipping a file requires more space than many people expect. You need space for the original ZIP file and the extracted contents. Some archives expand to several times their compressed size. For example, a 3 GB ZIP file might extract into a 12 GB folder.
To check your storage:
- Click the Apple menu in the top-left corner.
- Select System Settings.
- Go to General > Storage.
- Check how much free space is available.
If your Mac is nearly full, delete unnecessary files, move large media to an external drive, or empty the Trash. After freeing space, restart your Mac and try extracting the archive again.
4. Try Unzipping the File with Terminal
macOS includes command-line tools that can sometimes extract archives even when the graphical Archive Utility fails. Terminal also gives more useful feedback if something is wrong.
Here is a simple method:
- Open Terminal from Applications > Utilities.
- Type
unzipbut do not press Return yet. - Drag the ZIP file into the Terminal window. This inserts the file path automatically.
- Press Return.
The command will look something like this:
unzip /Users/yourname/Desktop/archive.zipIf the file extracts, you are done. If Terminal reports messages such as “End-of-central-directory signature not found”, “cannot find zipfile directory”, or “bad zipfile offset”, the archive is probably corrupted or incomplete.
You can also extract the archive into a specific folder:
unzip /Users/yourname/Desktop/archive.zip -d /Users/yourname/Desktop/extractedThis creates a clearer destination and avoids some permission problems.
5. Use a Different Extraction App
Apple’s built-in Archive Utility is convenient, but it is not always the most flexible tool. Some ZIP files are created on Windows, Linux servers, or older compression software and may include unusual metadata, password protection, long paths, or encoding that Archive Utility dislikes.
Try extracting the file with a reputable third-party archive utility such as:
- The Unarchiver
- Keka
- BetterZip
- WinZip for Mac
After installing one, right-click the ZIP file, choose Open With, and select the new app. If the archive opens in another tool, the problem is probably not the ZIP file itself but the way macOS Archive Utility is handling it.
This is particularly useful for archives that contain files with Windows-style names, older character encodings, or nested folders with very long paths.
6. Rename the ZIP File and Remove Special Characters
Sometimes the issue is not inside the ZIP file but in the file name or folder path. macOS is generally good with special characters, but certain symbols can still confuse extraction tools, scripts, password-protected archives, or cloud-synced paths.
Rename the ZIP file to something simple, such as:
archive.zipAvoid characters like:
#%&?:- Quotation marks
- Emoji or unusual symbols
Also move the file into a simple folder path, such as your Desktop. A clean path like /Users/name/Desktop/archive.zip is easier for extraction tools to process than a deeply nested cloud folder with special characters in several folder names.
7. Check File and Folder Permissions
Error 640 can appear if macOS cannot access the archive or cannot create the extracted files in the destination folder. This is more likely if the ZIP file came from another user account, an external drive, a network share, or a restored backup.
To check permissions:
- Control-click the ZIP file.
- Select Get Info.
- Look at the Sharing & Permissions section.
- Make sure your user account has Read & Write access.
If the file is on an external drive, also check the permissions for the drive or destination folder. You may need to copy the ZIP file to your Mac’s internal storage before extracting it. If the file is locked, uncheck Locked in the Get Info window.
If you understand Terminal permissions, you can also use:
chmod u+rw /path/to/archive.zipHowever, if you are not comfortable with command-line permissions, the Finder method is safer.
8. Make Sure the Archive Is Not Still Syncing
Cloud storage can create confusing ZIP problems. A file may appear in Finder before it has fully downloaded to your Mac. When Archive Utility tries to expand it, only part of the archive is actually available, which can trigger Error 640.
If the ZIP file is in iCloud Drive, OneDrive, Dropbox, or Google Drive, look for a cloud icon, sync indicator, or progress symbol. Right-click the file and choose an option such as Download Now, Make Available Offline, or the equivalent for your cloud service.
Once the file is completely local, copy it to your Desktop and try again.
9. Test Whether the ZIP File Is Corrupted
If you suspect corruption, Terminal can test the archive without extracting it. Open Terminal and run:
unzip -t /path/to/archive.zipAgain, you can type unzip -t and drag the ZIP file into Terminal to insert the path automatically. If Terminal reports that the archive is OK, the contents are probably readable. If it reports errors, you may need a fresh copy of the file.
For important archives, check whether the sender provides a checksum such as SHA-256 or MD5. A checksum is like a fingerprint for a file. If your downloaded file’s checksum does not match the original, the file has changed or downloaded incorrectly.
10. Update macOS
If the problem happens with many different ZIP files, not just one, your Mac’s Archive Utility or system components may be misbehaving. Updating macOS can fix bugs and compatibility issues.
Go to System Settings > General > Software Update. Install any available updates, restart your Mac, and try extracting the archive again.
You should also restart your Mac before spending too much time troubleshooting. A temporary Finder, permissions, or background process issue can sometimes disappear after a reboot.
11. Look for Password Protection or Split Archives
Some ZIP files are password-protected or split into multiple parts. Archive Utility may not handle every variation gracefully. If a ZIP file is part of a larger set, you may see names like:
archive.ziparchive.z01archive.z02
All parts must be in the same folder before extraction. If one part is missing, Error 640 or a similar extraction failure may appear. For password-protected files, try a third-party app that clearly prompts for the password.
When Should You Ask for a New File?
If you have tried moving the file, downloading it again, using Terminal, testing it, and opening it with another extraction app, the archive itself is likely damaged. In that case, ask the sender to recreate the ZIP file and send it again. They should ideally compress the original folder into a new archive and avoid interrupting the upload.
If the file came from a website, try another mirror, contact support, or check whether other users are reporting the same broken download.
Final Thoughts
Error 640 on a Mac is annoying because it is vague, but it is usually fixable. Start with the easy solutions: move the file to your Desktop, redownload it, and check storage space. Then move on to Terminal, alternative extraction apps, permissions, and corruption testing.
The key is to determine whether the problem is with the file, the location, or the extraction tool. Once you isolate that, the fix is usually simple. And if Terminal or another archive app confirms the ZIP is corrupted, you can stop fighting your Mac and get a clean copy instead.