How To Unzip Files On Mac

Tips
1

I downloaded several large ZIP files on my Mac, but when I double-click them, some of the contents don’t open properly or show as corrupted. I’m not sure if I’m using the right built-in tools or if I need a third-party app. Can someone walk me through the best way to unzip files on macOS and avoid file errors, step by step?

2

First thing to check is what you use to unzip.

On macOS the default tool is Archive Utility.

Built in way:

  1. Control click the ZIP file.
  2. Choose Open With.
  3. Pick Archive Utility.
  4. Let it finish. Large ZIPs can take a bit.

If that still gives corrupted files, try these:

  1. Repair or re download
    • If the ZIP came from a browser download, compare file size with what the site says.
    If your file is smaller, the download broke.
    • Try a different browser. Safari sometimes truncates big files from flaky servers.
    • If it is a multi part archive (file.z01, file.z02, file.zip), all parts need to be in the same folder before you open file.zip.

  2. Use a better unzip tool
    Archive Utility fails on some formats, very large archives, or weird Windows ZIPs.

Solid options:
• The Unarchiver
Free in the Mac App Store.
After install
Open The Unarchiver
Go to Preferences
On the Archive Formats tab, tick ZIP and anything else you need
Then double click the ZIP again.

• Keka
From keka.io or the App Store.
Drag the ZIP onto the Keka icon instead of double clicking.
Good with large and password protected files.

  1. Check for password and encryption
    If the ZIP is password protected, Archive Utility sometimes fails with a vague error.
    Use The Unarchiver or Keka, they will prompt for the password.
    If you enter the wrong password, you get corrupted output or “file damaged” messages.

  2. Check disk space and file system
    Large ZIPs unpack to even larger folders.

Example
• 10 GB ZIP of videos might unpack to 12 to 15 GB.

Steps:
• Click Apple menu, pick About This Mac, then Storage.
• Make sure you have at least 2x the ZIP size free.
• If the ZIP is on an external drive with FAT32, single files over 4 GB fail.
In that case, move the ZIP to your internal drive before unzipping.

  1. Verify the ZIP file itself
    If you feel like using Terminal:

• Open Terminal.
• Run:
unzip -t /path/to/yourfile.zip

Example:
unzip -t ~/Downloads/bigfile.zip

If you see:
No errors detected in compressed data
then the ZIP structure is fine, and the problem sits in your unzip tool or disk.

If you see CRC errors or “End-of-central-directory signature not found” the archive is damaged.
You need a new copy from the source.

  1. Quick workflow you can try now
    • Install The Unarchiver.
    • Right click ZIP, Open With, The Unarchiver.
    • Point it to a local folder on your internal drive, not network or cloud sync.
    • Watch for any error popup.

If it still fails:
• Post the exact error message.
• Include ZIP size, where it came from, and if it is one file or multipart (z01, z02, etc.).

That info helps narrow it down fast.

3

Couple of extra angles to try that @chasseurdetoiles didn’t cover or I’d handle differently:

  1. Don’t always trust “double‑click = Archive Utility”
    Double‑click sometimes goes to Finder extensions from cloud apps (Dropbox, OneDrive, AV tools) instead of the real Archive Utility or The Unarchiver.

    • Right‑click the ZIP
    • Hover “Open With”
    • If you see anything like “Dropbox,” “OneDrive,” “CleanMyWhatever,” avoid those
      Those can silently mangle big archives.

  2. Avoid unzipping inside iCloud / Dropbox / OneDrive folders
    Huge zips + live‑sync folders = half‑synced, half‑locked files that look “corrupted.”

    • Move the ZIP to something like ~/Downloads or a local folder on your internal drive
    • Unzip there, then drag the finished folder into your sync service if needed

  3. Check your destination disk for errors, not just free space
    People always say “make sure you have space” which is true, but filesystem errors can also trash extracted files.

    • Open Disk Utility
    • Select your main disk
    • Click “First Aid” and run it
      If your drive is throwing errors, no unzip tool will save you.

  4. Try unzipping from Terminal to a new folder
    Sometimes this gives clearer errors than GUI tools and avoids weird Finder integrations. In Terminal:

    cd ~/Downloads   # or wherever your zip is
mkdir test_unzip
unzip yourfile.zip -d test_unzip

    Watch the output:

    • inflating: ... with no warnings: archive is likely fine
    • checksum error / bad CRC / skipping: ... means the archive really is damaged

  5. Multipart & “exotic” zips: open the right file
    If you have files like:

    • myarchive.zip.001, .002, etc.
      or
    • myarchive.z01, myarchive.z02, myarchive.zip
      You should usually open only the .zip (or sometimes only .001, depends on how it was made). Opening the wrong piece often gives “corrupt” results even when the data is fine.

  6. Check how the ZIP was created (Windows tools, split, solid, etc.)
    Some Windows backup tools create zips that are “valid” but weird, especially when solid-compressed or with non‑standard flags. Archive Utility sometimes chokes silently. If you know the source used WinRAR or some backup program, try using the same app (or at least a more advanced extractor) on macOS.

    • For really stubborn stuff, 7zz (command‑line 7‑Zip port for Mac) can sometimes open things nothing else will:
      brew install sevenzip
7zz x yourfile.zip -otest_7z

  7. Check for specific file‑type corruption vs ZIP corruption
    Sometimes the ZIP is perfect, but what you’re opening is incompatible with macOS apps. Example:

    • A .psd that uses some feature older Photoshop on Mac can’t read
    • A .mov that uses a Windows‑only codec
      If unzip -t says the archive is fine and all files extract, the “corruption” might actually be the app that opens the extracted file, not the ZIP itself.

  8. Watch for antivirus or “system cleaner” interference
    Some security tools silently quarantine files as they are extracted, so it looks like the unzip failed. If you have anything like that installed, try temporarily disabling it or adding your downloads folder as an exclusion and then unzip again.

If you post:

  • exact error text
  • ZIP size
  • whether it sits on internal vs external vs cloud drive
    it will be easier to tell if this is a bad download, a disk problem, or just Archive Utility being picky.
4

Skip the double‑click stuff for a second and look at this from a “where can this fail” angle:

1. Rule out a bad download first

Before hunting for new tools:

  • Compare ZIP size with what the site says it should be. If you’re missing hundreds of MB, it is not a Mac issue.
  • If possible, re‑download one of the smaller archives using a different browser and see if that one unzips cleanly.
  • If these are very large single‑file zips from a web app (course platforms, cloud exports), they often truncate silently when the connection hiccups. That gives you “corrupted” contents regardless of unzip tool.

If re‑downloading one sample file fixes it, the culprit is the original transfer, not your Mac.

2. Use Archive Utility “properly” (and verify)

macOS’s Archive Utility is basic but not terrible. I partly disagree with the idea that it is the problem most of the time; for standard zips it is usually fine.

Try this:

  1. Right‑click the ZIP
  2. Open With → Archive Utility
  3. After extraction, open Terminal and run a quick integrity check on the extracted folder:
    cd /path/to/folder
ls > /dev/null
    If listing the directory hangs on an external drive, that points to disk or cable issues, not ZIP corruption.

You can also test the ZIP directly:

cd /path/to/zip
unzip -t yourfile.zip

If that says everything is OK but some files “won’t open,” the problem is likely the apps you use to open those files.

3. Think about the format of what is inside

A lot of “corrupted” reports are actually:

  • Old Mac app vs new file format (e.g., Office 2007+ documents on ancient Office for Mac).
  • Platform‑specific content (Windows‑only executables, installers, obscure codecs).

Try opening suspect files with:

  • Preview or Quick Look (spacebar in Finder) for images/PDF.
  • TextEdit for configs or plain text.
  • LibreOffice / latest Microsoft 365 for Office docs.

If they open in at least one modern app, the ZIP did its job.

4. External storage is a silent troublemaker

If you are unzipping to:

  • A cheap USB drive
  • An SD card
  • A spinning HDD in a flaky enclosure

you can get partial writes that make output look broken.

To test that:

  1. Copy one ZIP to your internal drive (e.g., Downloads).
  2. Unzip there.
  3. If it suddenly works, your external disk is the weak link. Back it up and consider replacing it.

5. When to actually grab a third‑party tool

After you have:

  • Verified the download
  • Tested with unzip -t
  • Tried internal vs external disk

then it is reasonable to use a more capable extractor.

People often mention things like The Unarchiver, which are fine, but I prefer heavier‑duty options for big or weird archives:

  • Tools based on 7‑Zip or p7zip handle odd compression methods better.
  • Power‑user style apps help with very large multipart archives, password protection, and repairing headers.

If you come across a guide titled something like “How To Unzip Files On Mac” that leans on a dedicated unzip product, keep an eye on pros and cons:

Pros of a dedicated unzip utility

  • Often handles damaged headers and partially corrupted archives better than Archive Utility.
  • Supports more formats than plain ZIP (RAR, 7z, etc.).
  • Sometimes offers repair tools and recovery for broken multipart zips.
  • Better status feedback while extracting multiple multi‑GB files.

Cons of a dedicated unzip utility

  • Extra app to install and maintain.
  • Some “free” tools bundle ads or background helper processes.
  • GUI‑only tools hide useful diagnostic messages you see in Terminal.
  • Can conflict with Finder’s default handler and cause the “wrong app opens the zip” confusion that @chasseurdetoiles already warned about.

In other words, use a third‑party unzipper as a problem solver, not as the very first move. Terminal plus Archive Utility give you enough signal to know whether the real issue is:

  • Bad download
  • Storage problem
  • App/format incompatibility
  • Or an archive that really needs a more advanced tool

If you can share one error message from Terminal (unzip -t or during extraction) and where the archive lives (internal / external / synced folder), it is usually possible to pinpoint which of those four buckets you are dealing with.