When a ZIP file will not expand on a Mac, start by checking whether the download is complete, whether the archive is really a valid ZIP, and whether Finder can write to the destination folder. The same “Unable to expand” message may come from a damaged archive, insufficient storage, a locked location, or an unsupported archive feature. Avoid deleting the original file or changing system permissions before you know which of those conditions applies. A few controlled tests can separate a broken download from a Mac storage or access problem.
What the error message does and does not tell you
Double-clicking a ZIP in Finder normally opens it using Archive Utility, which extracts its contents near the original file unless the user’s settings or workflow specify otherwise. The Archive Utility error can be frustratingly brief. “Unable to expand” by itself does not prove that macOS is damaged, that the file contains a virus, or that the archive’s owner blocked access.
Pay attention to the precise wording and where the ZIP came from. “Operation not permitted” suggests an access issue worth checking. “Decompression failed” can indicate an invalid or incomplete archive, but it can also arise with unsupported compression or encryption methods. If the error identifies a file or folder path, that path may show exactly which destination cannot be written.
Check that the file finished downloading
Find the ZIP in Downloads and inspect its file size. A file that is unusually small compared with what the sender advertised, or that stops downloading before the expected size, may be only a partial copy. If you received it from a website, download it again directly from the trusted original source. Do not rename a partial download to add “.zip”: changing the extension cannot reconstruct missing bytes.
In Safari, use the Downloads list to see whether the transfer completed and whether a separate temporary download file is still present. If Safari itself is failing to finish downloads, follow the checks in how to fix stalled or incomplete Safari downloads on Mac before blaming the archive. Also check whether a cloud storage service has downloaded the actual file locally rather than showing a placeholder.
Compare two downloads of the same file if a replacement is available. If both fail in the same way and have the same size, the source archive itself may be defective. If one download expands and the other does not, the transfer or local copy is the more likely cause.
Move a copy to a simple local folder
Archive Utility needs a destination where it can create files and directories. A ZIP stored on an external drive, shared network folder, read-only volume, restricted folder or cloud-synchronized location may fail to extract even when its data is intact. Copy the ZIP to a folder within your home directory, such as Downloads, and try again. Keep the original untouched so that a failed test does not destroy your only copy.
If Finder says the destination is locked or you do not have permission, inspect the folder using File → Get Info. Check the location and ordinary sharing permissions before making changes. Avoid running extraction with sudo or altering permissions on large parts of the startup disk. Those shortcuts introduce unnecessary security and ownership risks.
If the ZIP lives on an external drive, test writing a new harmless text file to that drive first. If ordinary writes fail, the issue may involve its file system or mounting mode rather than the archive. Consult why an external drive can be read-only on a Mac before reformatting anything. Reformatting erases data and should never be a first step in ZIP troubleshooting.
Make sure the destination has enough free space
A small-looking compressed archive can expand into a much larger folder. For example, a ZIP containing text or database exports may be much smaller than its unpacked contents. Finder may report an error if the target volume has insufficient free storage, especially when additional temporary space is needed during extraction. Check available disk space in macOS storage settings and allow a comfortable margin for the uncompressed files.
Be careful with deletion as a quick fix. Moving files to the Trash may not immediately return usable space until the Trash is emptied, and the files might still be needed. If Trash items cannot be removed due to permission or “item in use” errors, safe troubleshooting steps for a Mac Trash that will not empty are more appropriate than force-deleting unrelated system files.
Test whether Archive Utility works with another ZIP
Create a small folder containing a harmless note, select the folder in Finder, and choose Compress from the context menu. Double-click the resulting ZIP. If your own test archive expands successfully but a downloaded one does not, the Mac’s basic extraction capability is working. The remaining problem is more likely related to the specific source file, archive format, or location.
If neither archive can expand in Downloads, repeat the test in another ordinary folder that you own. This isolates a folder access issue. If both fail everywhere, investigate available storage, permissions and the behavior of Archive Utility rather than repeatedly downloading the same external ZIP.
Is the archive actually a supported ZIP?
Some files end in “.zip” even though they were generated incorrectly or transferred using a system that altered their contents. Others use special compression or encryption features that the built-in macOS extraction tool may not handle as expected. Password-protected archives are especially variable: support depends on how they were encrypted, not simply whether the sender supplied a password.
Ask the sender how the archive was created and whether it can be provided using an ordinary compatible ZIP format. If an extraction tool reports an unsupported method, use software from a trustworthy source rather than downloading the first program suggested by an unfamiliar error page. For business documents, confirm the sender and the intended contents before opening anything extracted.
Optional check in Terminal: test without extracting
Users comfortable with Terminal can inspect a ZIP’s structural integrity without writing its contents to disk. Open Terminal and type unzip -t , including the trailing space, then drag the ZIP file from Finder into the Terminal window to insert its quoted path. Press Return. The test attempts to read archive entries and reports whether it found errors; it does not extract the files into a destination folder.
A successful test does not guarantee that every application inside is safe or usable, but it suggests that the ZIP structure is readable by that tool. A failure can help identify corruption or a method the tool does not support. Terminal output is diagnostic information, not a reason to run commands copied blindly from forums. The macOS command-line tools may also differ from a third-party archive app in supported formats.
What if the ZIP expands but some files cannot be opened?
Extraction and opening are separate operations. A PDF can extract normally but fail to open in Preview because it is damaged, restricted or incomplete. A disk image, application or document inside the archive may need a compatible application. If only the extracted PDF fails to save, the checks for Preview permission and PDF export errors address a different stage of the problem.
Never turn off macOS security protections simply to make an unknown downloaded app run. Verify the sender, scan unusual files with appropriate tools if needed, and obtain a fresh trusted copy when the archive’s provenance is uncertain.
Practical troubleshooting order
- Read the full Archive Utility message and keep the original ZIP.
- Check the file size and whether the browser or cloud download completed.
- Copy the ZIP to a normal writable local folder and try expanding it there.
- Verify that the Mac has enough free disk space for the uncompressed contents.
- Create and expand a small ZIP of your own to test the built-in extraction process.
- For a questionable source archive, request a fresh standard ZIP from the sender.
- If needed, run a read-only structural test with
unzip -tand interpret the specific result.
Apple’s documentation on compressing and uncompressing files on Mac describes the standard Finder workflow. If the current macOS version displays slightly different menu wording, use the equivalent Finder compression and extraction actions.
Frequently asked questions
Does renaming a file to .zip repair it?
No. The extension tells the operating system which type of file to try opening. It does not rebuild a damaged archive or download missing content.
Why does the ZIP work on another computer but not my Mac?
The two machines may have different extraction tools, supported methods, free space, or destination permissions. Compare the exact file size and copy to a writable local folder before concluding that the Mac itself is faulty.
Should I extract a ZIP using sudo?
Not as a routine fix. Administrative extraction can create files with unexpected ownership and hides the actual destination or access issue. Resolve the folder permissions or choose a writable location first.
Can a compressed file be much larger after expansion?
Yes. The compressed download size can be far smaller than the total size of the contents. Leave enough free space for the uncompressed data and temporary extraction work.