How to Fix The Extraction Operation Was Not Completed on Mac

The Extraction Operation Was Not Completed is one of the most frustrating errors Mac users encounter when trying to unzip a file. It appears without warning, gives almost no useful information about what went wrong, and can block access to files you need. Whether it happens to a single file or every ZIP you try to open, the cause is usually one of a small number of fixable problems.

This guide walks through eight proven fixes for the Extraction Operation Was Not Completed error on Mac, starting with the simplest solutions and working through to more advanced Terminal-based approaches. Most users will resolve the issue within the first two or three fixes.

What Does This Error Mean?

When macOS displays the Extraction Operation Was Not Completed message, it means the built-in Archive Utility was unable to fully decompress a ZIP or archive file. The process started but did not finish, either because something went wrong with the file itself, with the destination location, or with the extraction tool.

The error message is frustratingly vague – macOS does not tell you which of its possible causes applies to your situation. This is why a systematic approach works better than guessing. The fixes in this guide cover every common cause, ordered from the most frequently responsible to the least common, so working through them in order gives you the fastest path to a solution.

Why Does The Extraction Operation Was Not Completed Happen?

Understanding why the Extraction Operation Was Not Completed error occurs helps you choose the right fix. The table below lists every common cause and what it means in practice.

The most common cause by a significant margin is an incomplete or corrupted download. If a file was interrupted mid-download, the resulting ZIP will be structurally incomplete and will fail to extract regardless of what else you try. This is why Fix 1 is always to re-download before attempting anything more involved.

Fix 1: Re-Download the ZIP File

A partial or corrupted download is the most common reason the Extraction Operation Was Not Completed error appears on Mac. If the download was interrupted by a network drop, a browser crash, or a timeout, the resulting file is structurally incomplete and will fail every extraction attempt. Re-downloading from the original source is always the first thing to try.

1. Delete the existing ZIP file and any partial folder that was created alongside it.
2. Open your browser and navigate back to the original download source.
3. Download the file again, making sure the download completes fully before attempting extraction.
4. Check the file size after downloading. Compare it to the size shown on the download page if available. A significant discrepancy indicates the download is still incomplete.
5. Once the download is confirmed complete, double-click the ZIP to extract.

Fix 2: Free Up Disk Space

If your Mac does not have enough free disk space to write the extracted files, the extraction will fail partway through and display the Extraction Operation Was Not Completed error. This is particularly common with large archives or when extracting to a nearly-full drive.

6. Click the Apple menu and select About This Mac.
7. Click More Info, then scroll to Storage to see how much space is available.
8. If available space is less than twice the size of the ZIP file, free up space before attempting extraction.
9. Delete files you no longer need, empty the Trash, and clear Downloads of old items.
10. Alternatively, connect an external drive with sufficient free space and extract the ZIP there instead.

Fix 3: Use a Different Extraction Tool

macOS’s built-in Archive Utility has known issues with certain ZIP formats, particularly those created on Windows, those using compression methods Archive Utility does not fully support, and multi-part archives. If re-downloading and checking disk space did not resolve the Extraction Operation Was Not Completed error, switching to a third-party extraction tool is a highly effective next step.

The following free tools handle a wider range of archive formats and are more robust than Archive Utility for problem files:

•        The Unarchiver – Free on the Mac App Store. Handles ZIP, RAR, 7-Zip, tar, and most other formats. This is the most commonly recommended alternative for Mac users.
•        Keka – Free to download from the developer’s website, paid on the App Store. Handles virtually every archive format and is particularly strong with password-protected files.
•        BetterZip – Paid app with a free trial. Offers detailed error reporting that can help diagnose why an extraction is failing.

To use The Unarchiver after installing it:

11. Right-click the ZIP file in Finder.
12. Select Open With, then choose The Unarchiver from the list.
13. The tool will attempt extraction and provide a more detailed error message if it also fails, which can help identify the underlying cause.

Fix 4: Move the File Before Extracting

Extracting a ZIP file from a network drive, an external hard drive with a read-only file system, or a location where your Mac user account does not have write permissions will produce the Extraction Operation Was Not Completed error, even if the file itself is perfectly intact. macOS needs to write the extracted files to a location it has full access to.

14. Locate the ZIP file in Finder.
15. Copy or move it to your Desktop or to your Downloads folder – both are locations where your user account has full read and write access.
16. Attempt extraction from the new location by double-clicking the file.

Fix 5: Disable Gatekeeper Temporarily

macOS Gatekeeper is a security feature that restricts the execution of files from unverified or unknown sources. In some cases, it can interfere with the extraction of ZIP files that contain executables or application bundles, producing the Extraction Operation Was Not Completed error even when the file is otherwise intact.

To bypass Gatekeeper for a specific file:

17. Right-click the ZIP file in Finder.
18. Hold the Option key and select Open. This bypasses Gatekeeper’s warning for that specific file.
19. If prompted with a security warning, click Open to proceed.
20. Attempt extraction again.

If you want to allow extraction without the right-click workaround:

21. Open System Settings and go to Privacy and Security.
22. Scroll to the Security section. If the file was blocked, you will see an option to allow it.
23. Click Allow Anyway, then attempt extraction again.

Fix 6: Extract Using Terminal

If the graphical extraction tools are all failing with the Extraction Operation Was Not Completed error, using Terminal to extract the file directly often succeeds where the GUI methods fail. Terminal’s unzip command provides more control and more detailed error output that can pinpoint exactly what is wrong.

To extract a ZIP file using Terminal:

24. Open Terminal from Applications > Utilities, or search for it with Spotlight.
25. Type the following command but do not press Enter yet: unzip
26. Drag the ZIP file from Finder into the Terminal window. This automatically inserts the correct file path.
27. Press Enter to run the command.

If the file has a password, use:

To extract to a specific folder rather than the current directory:

Terminal will display detailed output as it extracts each file, and if the extraction fails it will show a specific error message that is far more useful than the generic Extraction Operation Was Not Completed message from Archive Utility. Common Terminal error outputs include warnings about unsupported compression methods, CRC errors indicating file corruption, and permission denied messages that confirm a location issue.

Fix 7: Check and Repair Disk Permissions

Corrupted disk permissions can prevent macOS from writing extracted files to certain locations, causing the Extraction Operation Was Not Completed error to appear consistently regardless of which file you are trying to extract. Running First Aid on the affected volume through Disk Utility can resolve permission issues that individual file fixes cannot address.

28. Open Disk Utility from Applications > Utilities.
29. Select your Mac’s main drive (usually named Macintosh HD) in the left sidebar.
30. Click First Aid at the top of the window.
31. Click Run and allow the process to complete. This may take several minutes.
32. Restart your Mac after First Aid finishes.
33. Attempt the extraction again after the restart.

Fix 8: Update macOS

Specific versions of macOS have contained bugs in Archive Utility that cause the Extraction Operation Was Not Completed error to appear with certain file types or sizes. Apple has released patches for several of these issues in minor updates. If all other fixes have failed, checking for and installing macOS updates is worth attempting before concluding the file itself is irreparably corrupt.

34. Click the Apple menu and select System Settings.
35. Click General, then Software Update.
36. If an update is available, click Update Now and follow the prompts.
37. Allow the update to install fully and restart your Mac.
38. Attempt the extraction again after updating.

If you are already on the latest version of macOS and the Extraction Operation Was Not Completed error persists across multiple files from different sources, the issue is most likely environmental – related to disk permissions, available space, or a conflict with security software – rather than a software bug. Working back through Fixes 2, 4, and 7 with those possibilities in mind is the recommended next step.

How to Prevent This Error in the Future

Most occurrences of the Extraction Operation Was Not Completed error are preventable with a few straightforward habits. The following practices address the most common causes before they become a problem.

Always verify downloads are complete before opening

Wait until the download indicator in your browser shows the file as fully downloaded before double-clicking it. Large files in particular can appear in Finder before they have finished downloading, especially on slower connections. A file that is still being written to disk will fail to extract every time.

Keep at least 10 to 15 percent of your drive free

Consistent free space on your Mac’s main drive prevents not just extraction failures but a range of other performance and reliability issues. macOS uses free space for virtual memory, temporary files, and system operations. Keeping below 10 percent free space creates conditions where the Extraction Operation Was Not Completed error and similar failures become more frequent.

Install The Unarchiver as your default extraction tool

Replacing macOS’s built-in Archive Utility with The Unarchiver as the default handler for ZIP files and other archive formats eliminates an entire class of Archive Utility-specific failures. The Unarchiver is free, handles more formats, and produces clearer error messages when something does go wrong. Right-click any ZIP file, select Get Info, and under the Open With section set The Unarchiver as the default application.

Download files directly to your Desktop or Downloads folder

Avoiding the extraction of files from network locations, external drives, or cloud-synced folders eliminates the permissions-related causes of the Extraction Operation Was Not Completed error. Local folders your user account owns are the most reliable extraction destinations.

Scan files with an antivirus before extracting from unknown sources

Some security software interferes with extraction in a way that produces the Extraction Operation Was Not Completed error rather than a clear security warning. Running a scan before extraction both confirms the file is safe and reduces the likelihood of mid-extraction interference from real-time protection tools.

Some security software interferes with extraction in a way that produces the Extraction Operation Was Not Completed error rather than a clear security warning.

If the archive contains apps or social media tools that use AI features, it is also worth reviewing their privacy settings and permissions before installing them.

Conclusion

The Extraction Operation Was Not Completed error looks alarming, but it is rarely a sign of a serious problem. In the overwhelming majority of cases, the fix is straightforward: re-download the file, free up some disk space, or switch to The Unarchiver instead of Archive Utility. Most users never need to go beyond Fix 3.

If you have worked through all eight fixes and the error still appears on every ZIP file you try to open, the problem is almost certainly a disk permissions issue or a conflict with security software rather than anything wrong with the files themselves. Running Disk Utility’s First Aid and checking whether your antivirus is interfering with file writes will resolve it in most of those cases.

The single most useful thing you can do going forward is install The Unarchiver and set it as your default extraction tool. It handles more formats, produces clearer errors when something goes wrong, and eliminates the class of Archive Utility-specific bugs that cause this error to appear in the first place. It is free, takes two minutes to set up, and means you are unlikely to see the Extraction Operation Was Not Completed message again.

Frequently Asked Questions

Why does The Extraction Operation Was Not Completed keep happening on every ZIP file?

If the Extraction Operation Was Not Completed error appears consistently across all ZIP files rather than just one specific file, the problem is almost certainly environmental rather than file-specific. The most likely causes are insufficient disk space, corrupted disk permissions, or a conflict with security software. Run Fix 2 (disk space check), Fix 7 (Disk Utility First Aid), and check whether any antivirus software is interfering with file writes. If the issue appeared after a macOS update, Fix 8 may also be relevant.

Can a corrupted ZIP file be repaired?

In some cases, yes. Terminal’s unzip command with the -o flag (overwrite) can sometimes extract partial content from a damaged archive. The command zip -FF /path/to/damaged.zip –out /path/to/repaired.zip attempts to repair a corrupted ZIP by rebuilding its internal structure. For severely damaged files, third-party tools like Disk Drill or recovery-focused archive utilities offer more advanced repair options. However, if the corruption is extensive, some or all of the file contents may be unrecoverable and re-downloading from the source is the only reliable solution.

Does The Extraction Operation Was Not Completed error mean the file has a virus?

Not typically. The Extraction Operation Was Not Completed error is almost always caused by technical problems – an incomplete download, insufficient disk space, permissions issues, or an incompatible archive format – rather than by malware. That said, some security software does block extraction of files it considers suspicious and produces a generic extraction error rather than a clear security warning. If your antivirus software is active and the error appeared without any other obvious cause, temporarily disabling real-time protection and attempting extraction again can confirm or rule out security software interference.

How do I extract a ZIP file on Mac without Archive Utility?

The easiest way is to install The Unarchiver from the Mac App Store and set it as the default handler for ZIP files. Once installed, double-clicking any ZIP file will use The Unarchiver instead of Archive Utility. You can also use Terminal’s unzip command as described in Fix 6, which works without any additional software installation and provides detailed output that helps diagnose any issues.

Why does the ZIP extract on Windows but not on Mac?

ZIP files created on Windows sometimes use compression methods, path formats, or character encodings that macOS’s Archive Utility handles poorly. Windows ZIP files may also contain files with names that use characters or lengths that are valid on Windows but problematic on macOS. The Unarchiver and Keka are both better at handling Windows-created ZIP files than Archive Utility, and using either of them (Fix 3) typically resolves the Extraction Operation Was Not Completed error for files that work on Windows but not on Mac.

Is it safe to use Terminal to extract files?

Yes. The unzip command in Terminal is a standard macOS utility and is entirely safe to use. It does the same job as Archive Utility but with more detailed output and without the bugs that affect Archive Utility on some macOS versions. The only precaution worth taking is to confirm the file path you type is correct before pressing Enter, to avoid accidentally overwriting files in the wrong location.