Mac Says "Unable to Expand" ZIP File — Here's the Fix

If you've landed on this specific error message and want a direct answer rather than general troubleshooting advice, the sections below are organized by root cause so you can jump straight to whichever one matches your situation.

"Unable to expand" is the single most common error message you'll see when a ZIP file fails to open on a Mac. It's also frustratingly vague — the message itself gives almost no indication of what actually went wrong. This guide walks through exactly what's happening behind that message, how to figure out which specific cause applies to your situation, and the fix for each one.

How common this specific error actually is

This isn't a rare edge case — "unable to expand" is consistently one of the most frequently searched macOS error messages related to file handling, precisely because ZIP is used so heavily and Archive Utility's error reporting is so generic. The upside of that ubiquity is that the underlying causes are well understood and predictable, even if the error message itself doesn't tell you which one applies directly. Working through the diagnostic list below systematically resolves the overwhelming majority of cases without needing to guess randomly at fixes.

What "unable to expand" actually means

This message comes from Archive Utility, the background process that handles ZIP extraction when you double-click a file in Finder. It's a generic catch-all error, meaning Archive Utility encountered some kind of problem processing the archive but doesn't distinguish between the several different possible causes in its user-facing messaging. This is the core reason the error is so frustrating to troubleshoot from the message alone — "unable to expand" could mean an incomplete download, a corrupted file, or a handful of other issues, and you have no way to tell which from the error dialog itself.

Cause 1: incomplete or interrupted download (most common)

By far the most frequent cause. If a download was interrupted — a dropped connection, closing the browser too early, a network hiccup — the resulting file is smaller than it should be and structurally incomplete, which Archive Utility cannot process correctly. The fix: compare the downloaded file's size against what the source page, email, or sender listed. A mismatch confirms this cause — simply re-download the file, ideally with a stable connection, and the error typically resolves completely.

Cause 2: the ZIP was corrupted before you received it

Less common but real: sometimes the archive was already damaged at the point of creation or upload, before you ever downloaded it. This happens when the original ZIP-creation process was interrupted, or when an upload to a file-sharing platform got corrupted server-side. The fix: if the file size matches what was expected exactly but the error persists, re-downloading won't help since you'd just be re-downloading the same corrupted source file. You need the original sender to re-create and re-upload the archive from scratch.

Cause 3: the ZIP is password-protected

Archive Utility doesn't support password-protected ZIP files at all — rather than showing a password prompt, it sometimes fails with a generic "unable to expand" error instead of a clear message indicating encryption is the issue. The fix: this isn't something Archive Utility can be configured to handle; you need a third-party archive tool that explicitly detects password protection and prompts you for the password, like Unzipr, rather than attempting to extract encrypted content as if it were standard.

Cause 4: the file extension doesn't match the actual format

Occasionally a file gets renamed, either intentionally or through a bug in whatever created or transferred it, so it has a .zip extension but isn't actually a valid ZIP file internally — or conversely, is a valid ZIP but was saved with a different extension. The fix: if you're unsure whether the extension matches the real format, Terminal's file yourfile.zip command reports the file's actual detected type regardless of its extension, which can quickly confirm or rule out this cause.

Cause 5: insufficient disk space during extraction

Less commonly discussed but genuinely possible: if your Mac's available storage runs low mid-extraction, particularly for a very large archive, the process can fail partway through with an error that presents similarly to a corrupted file. The fix: check available disk space (Apple menu → About This Mac → Storage) before retrying extraction of a large archive, and free up space if it's running low.

A step-by-step diagnostic process

• Compare the downloaded file size against the source — mismatch means re-download
• If size matches exactly, try opening with a different archive tool to rule out a Finder-specific limitation like password protection
• Run file yourfile.zip in Terminal to confirm the file is actually recognized as a ZIP
• Check available disk space if the archive is unusually large
• If none of the above resolves it, ask the original sender to re-create and re-send the file, since the corruption likely originated before you received it

Getting more specific error information

Since Finder's dialog gives you almost nothing to work with, running the extraction manually through Terminal often surfaces more useful detail: unzip yourfile.zip in Terminal will print a more specific error message than Archive Utility's generic dialog — sometimes explicitly stating "encrypted" or pointing to a specific corrupted entry within the archive, which immediately narrows down which of the causes above actually applies.

Why a third-party tool sometimes succeeds where Finder fails

For the password-protection and certain corruption-tolerance cases specifically, a more capable third-party archive tool can succeed where Archive Utility fails outright — not through any special trick, but because these tools are built with broader error handling and format support than Apple's built-in utility. Password detection with a proper prompt is the most common example: the underlying archive isn't actually broken, Archive Utility just can't handle the encryption, while a dedicated tool handles it as expected functionality rather than an edge case.

A realistic scenario: troubleshooting a specific failed download

Picture downloading a 2GB dataset ZIP for a project, and getting "unable to expand" the moment you double-click it. Rather than guessing, work through the diagnostic process methodically: first check the file size in Finder's "Get Info" panel against the 2GB the source page advertised. If it shows 1.3GB instead, that's your answer immediately — an interrupted download, fixed by re-downloading, ideally on a stable connection this time rather than one prone to dropping mid-transfer. If the size matches exactly at 2GB, move to the next diagnostic step (trying a different tool, checking with Terminal's file command) rather than repeatedly re-downloading an identical file expecting a different result.

Why re-downloading resolves the majority of cases

It's worth understanding why this single fix — simply downloading the file again — resolves such a large share of "unable to expand" errors specifically. Network interruptions during a download are common and often invisible to the user in the moment; browsers and download managers don't always clearly surface a failed or truncated transfer, sometimes showing "download complete" even when the file is missing its final portion. Re-downloading essentially gives the transfer a second, hopefully uninterrupted attempt, and on a reasonably stable connection, most interrupted downloads succeed cleanly the second time. This is precisely why checking file size first, before trying anything more elaborate, is the highest-value first diagnostic step rather than an afterthought.

When the problem is upstream, not on your Mac at all

It's easy to assume a persistent "unable to expand" error reflects something wrong with your specific Mac, but in most cases the actual problem originates entirely outside your control — either at the point the file was originally created, or during whatever transfer or hosting service delivered it to you. If you've confirmed the file size matches expectations and tried a different extraction tool without success, the most productive next step is usually contacting whoever provided the file rather than continuing to troubleshoot locally, since no amount of local troubleshooting fixes a file that was already corrupted before it reached you.

Frequently asked questions

Does this error mean my Mac has a problem? No — "unable to expand" is almost always specific to the individual file in question, not a sign of a broader system issue with your Mac.

Can I fix a corrupted ZIP myself without re-downloading? Rarely, for consumer tools. Some archive utilities include a "repair" feature that can recover partially-intact data from a corrupted archive, but success depends heavily on how much of the file is actually damaged — severe corruption often isn't recoverable regardless of tool.

Is there a way to prevent this from happening on future downloads? Using a stable network connection for large downloads and avoiding closing the browser or interrupting the download process before it completes addresses the most common cause directly.

The bottom line

"Unable to expand" is a generic error covering several distinct underlying causes, and the fix depends entirely on which one applies — usually an incomplete download solved by re-downloading, occasionally password protection solved by switching tools. Unzipr handles password-protected ZIP files directly with a proper prompt, removing one of the most common sources of this exact error, and its instant preview lets you sanity-check a large archive's contents the moment a download finishes, before committing to a full extraction.