When macOS shows Error 79 while unzipping a file, it is usually telling you that the archive cannot be interpreted in the way Archive Utility expects. The message may appear as “Unable to expand”, “Error 79”, or “Inappropriate file type or format.” Although it can look like a serious system failure, the cause is most often the file itself, the way it was downloaded, or a compatibility issue with the compression method used to create it.

TLDR: macOS Error 79 generally means the ZIP file is not in a format that Archive Utility can properly read. The most common causes are a corrupted or incomplete download, a file with the wrong extension, unsupported compression settings, or a password-protected archive that macOS cannot handle correctly. Try downloading the file again, checking its source, using Terminal, or opening it with a more capable archive tool. If multiple ZIP files fail, investigate disk permissions, storage issues, or macOS system problems.

What Error 79 Means on macOS

On macOS, Error 79 is commonly associated with the phrase “Inappropriate file type or format.” In practical terms, Archive Utility is saying: “This file does not look like the kind of archive I know how to expand.” That does not always mean the file is fake or dangerous. It may simply mean that the archive is damaged, incomplete, incorrectly named, or compressed using features macOS does not support well.

ZIP is a familiar format, but it is not as simple as many users assume. A file ending in .zip can contain different compression methods, encryption types, metadata, split volumes, and directory structures. Most ordinary ZIP files open without difficulty on macOS. Problems arise when the archive was created by unusual software, transferred incorrectly, or renamed from another format.

Common Causes of Error 79 When Unzipping Files

The following causes account for most cases of Error 79. In many situations, more than one factor may be involved, especially when files are downloaded from email attachments, cloud drives, file sharing services, or older systems.

1. The ZIP File Is Corrupted

A corrupted ZIP file is the most common explanation. Corruption can happen during downloading, uploading, copying to a USB drive, syncing through cloud storage, or transferring over an unstable network. Even a small interruption can damage the internal structure of the archive.

Signs of corruption include:

  • The ZIP file size is much smaller than expected.
  • The download finished unusually quickly.
  • Other people can open their copy, but your copy fails.
  • The file produces different errors in different unzip tools.
  • The archive opens partially, but some files are missing or fail to extract.

If corruption is likely, the best first step is simple: download the file again. If possible, use a stable connection and avoid opening the archive before the download is fully complete.

2. The File Has the Wrong Extension

macOS often relies on file extensions to decide which application should open a file. If a file is named example.zip but is actually a .rar, .7z, .tar.gz, or another archive type, Archive Utility may fail with Error 79.

This can happen when files are renamed manually, exported incorrectly by a web application, or downloaded from a server that assigns a misleading filename. Some websites also wrap files in download containers or generate temporary files that look like ZIP archives but are not valid ZIP files.

To investigate, select the file in Finder and choose File > Get Info. Look at the file name, size, and kind. If you received the file from someone else, ask what compression format they used. A file that is not really a ZIP file should be opened with the appropriate tool instead of Archive Utility.

3. The Archive Uses Unsupported Compression or Encryption

Not all ZIP files are created with the same settings. Some use compression methods, encryption standards, or ZIP64 features that older versions of macOS may not support fully. Password-protected ZIP files are a frequent source of confusion because different tools implement encryption differently.

For example, a ZIP file encrypted using older ZipCrypto may open in many utilities, while one using stronger AES encryption may fail in some built-in tools depending on the macOS version and the way the archive was produced. In those cases, Error 79 does not mean the password is wrong; it may mean Archive Utility cannot process the archive correctly.

4. The Download Is Incomplete

An incomplete archive can look normal in Finder because it still has a ZIP extension and may even show a plausible file size. However, ZIP files contain directory information that is usually checked during extraction. If the ending portion of the file is missing, macOS may be unable to read the archive’s index and will report the format as inappropriate.

This is especially common with large downloads, files stored on unreliable external drives, or archives retrieved through a browser after a suspended network connection. Compare the file size against the size listed on the download page or ask the sender to confirm the expected size.

5. The ZIP File Is Split Into Multiple Parts

Some large archives are divided into multiple parts, such as archive.zip, archive.z01, archive.z02, and so on. If you try to open only one part, macOS cannot reconstruct the full archive and may show Error 79.

Split archives usually require all parts to be present in the same folder. They may also require a third-party archive utility rather than the built-in macOS Archive Utility. If you see multiple similarly named files, do not rename them randomly. Keep the original names and extract from the first file or the main .zip file using suitable software.

6. File Permissions or Location Problems

Sometimes the problem is not the archive format itself but the location where macOS is trying to read or extract it. If the ZIP file is stored in a restricted folder, a read-only disk image, a network share, or an external drive with permission issues, extraction can fail.

Move the ZIP file to a simple local folder such as Downloads or Desktop, then try again. Also make sure you have enough free disk space. Extracting an archive often requires more space than the compressed file size suggests, especially if the contents are large media files, application bundles, or development projects.

How to Fix macOS Error 79

The correct fix depends on the cause, but the following steps are a sensible, low-risk sequence for most users.

  1. Download the file again. This resolves many cases caused by corruption or incomplete transfer.
  2. Move the file to a local folder. Try extracting it from Desktop or Downloads instead of a network drive, external disk, or cloud-synced folder.
  3. Check the file extension. Confirm that the file is really a ZIP archive and not another format with the wrong name.
  4. Try another unzip tool. A dedicated archive utility may support formats or encryption methods that Archive Utility does not.
  5. Use Terminal for more information. Terminal may produce a clearer error message than Finder.
  6. Ask the sender to recreate the archive. If the file was compressed with unusual settings, a standard ZIP archive may solve the problem.

Using Terminal to Diagnose the ZIP File

Terminal can help determine whether the archive is readable. Open Terminal, then type unzip -t followed by a space. Drag the ZIP file into the Terminal window to insert its path, then press Return. The command tests the archive without extracting it.

If the archive is valid, you should see messages indicating that the files are OK. If it is damaged or unsupported, Terminal may report a more specific issue, such as a missing end signature, unsupported compression method, or invalid archive structure.

You can also try extracting with:

unzip /path/to/file.zip

This is not guaranteed to work when Archive Utility fails, but it can provide useful diagnostic output. If Terminal also fails, the issue is more likely to be the file rather than the graphical extraction tool.

When to Use a Third-Party Archive Tool

There are legitimate cases where macOS Archive Utility is not the best tool. Third-party archive applications often support more formats, better handling of encrypted ZIP files, recovery from minor archive irregularities, and split archive extraction.

Consider using another archive utility if:

  • The ZIP file is password protected.
  • The archive was created on Windows or Linux with specialized compression settings.
  • The file is part of a multi-volume archive.
  • The file may actually be RAR, 7Z, TAR, or another format.
  • You need to inspect the archive contents before extracting everything.

Use reputable software from trusted sources. Archive files can contain executable scripts, applications, or documents with macros, so avoid opening unknown files from suspicious senders.

Security Considerations

Error 79 is usually a technical problem, not proof of malware. However, caution is still appropriate. Attackers sometimes disguise files with misleading extensions, double extensions, or corrupted archives designed to confuse users. If a ZIP file came from an unknown sender, an unexpected email, or a questionable website, do not repeatedly try to force it open without verifying its origin.

Before extracting an unfamiliar archive, consider these precautions:

  • Confirm the sender. If the file came by email, verify that the sender intentionally sent it.
  • Check the file name carefully. Be wary of names like invoice.pdf.zip or files pretending to be documents.
  • Keep macOS updated. Security updates improve how the system handles risky files.
  • Do not run extracted applications blindly. Inspect what was extracted before opening anything.

What If Every ZIP File Fails?

If macOS shows Error 79 for one specific file, the archive is probably the issue. If it happens with many unrelated ZIP files, investigate your Mac. Start by restarting the computer, installing available macOS updates, and checking available storage. Then test with a small ZIP file you create yourself: right-click a simple folder and choose Compress, then try expanding the resulting archive.

If your own test archive fails, the problem may involve Archive Utility preferences, disk errors, permissions, or a broader system issue. Testing in another user account can help determine whether the issue is limited to your profile. You can also run Disk Utility and use First Aid on the relevant volume to check for file system problems.

How to Prevent Error 79 in the Future

Prevention is mostly about reliable file handling. Download large files over stable connections, wait for cloud syncing to finish before opening archives, avoid renaming file extensions unless you know the real format, and use standard ZIP settings when sharing files with Mac users. If you are creating archives for others, avoid unusual encryption or obscure compression methods unless the recipient knows which tool to use.

For important transfers, it is wise to provide a checksum, file size, or alternative download link. These details make it easier to confirm whether a recipient received the complete file. In professional environments, this simple practice can save significant time and reduce confusion.

Final Thoughts

macOS Error 79 when unzipping files is best understood as a format or readability problem. The built-in Archive Utility expected a valid, supported archive but encountered something it could not process. In most cases, the solution is straightforward: re-download the file, verify the extension, move it to a local folder, or use a more capable archive tool.

If the file is important and still will not open, do not keep guessing. Ask the sender to recreate the archive using standard ZIP settings, confirm the file size, or send it through a different method. A careful, methodical approach is the safest way to distinguish a simple download problem from a genuinely damaged or suspicious file.