Mac Error Codes Explained: A Complete Troubleshooting Guide

What Mac error codes actually represent

A Mac error code is a short numeric result passed back by the system, an app or a framework when an operation could not be completed. The number is a label for a condition, not a diagnosis of a cause. That distinction explains why the same code can appear in wildly different situations: the condition ('the operation failed in this general way') is the same, while the reason behind it differs.

Some codes are long-standing system result codes that have been in use for decades and have reasonably well understood historical meanings. Others are produced by individual applications and mean whatever that developer decided they mean. A third group is effectively undocumented for end users. Any source that gives a single confident sentence for every possible number is overstating what is knowable.

The error category matrix

Rather than memorising numbers, group them. Almost every error a home user meets belongs to one of the families below, and each family has a characteristic first move.

File-system, copying and moving errors

File-transfer errors are the largest family by far. A copy involves reading every byte from a source, writing it to a destination, and recording a name and metadata that the destination volume can represent. Any of those three can fail independently.

• Volume format: a destination formatted for broad compatibility may reject very large single files or characters that are legal on macOS.
• Interrupted connections: a bus-powered drive that briefly drops power ends the transfer mid-stream.
• Free space: destinations report space, but sparse files, hidden snapshots and recycle folders can consume more than expected.
• File names: unusual characters, trailing spaces and extreme lengths cause failures that look random until you notice the pattern.
• Source readability: a single unreadable file can stop an otherwise healthy batch copy.

The most efficient diagnostic is a narrowing test. Copy one small file with a plain name to the same destination. If that works, the destination is broadly fine and the problem lies with specific items. If it fails, the destination, connection or format is implicated and there is no point working through individual files.

Finder, Trash and permission errors

Finder is a front end to the file system, so its errors usually reflect an underlying refusal rather than a Finder defect. An item that will not rename may be in use. An item that will not delete may be locked, may be owned by another account, or may live on a volume mounted read-only.

1. 1

   Confirm the item is not in use

   Quit apps that may have the file open, including preview panes and media players. Files held open by a running process commonly resist deletion.

2. 2

   Check the item's locked state and permissions

   The Get Info panel shows whether an item is locked and who has read or write access. Both are reversible settings.

3. 3

   Check the volume

   External and network volumes can mount read-only. Nothing on the Mac side will make a read-only volume writable.

4. 4

   Restart before anything structural

   A restart clears held file handles and stale mounts, and costs a minute. It resolves a meaningful share of Finder and Trash errors.

Disk problems and when hardware becomes plausible

Most single errors are not evidence of a failing disk. Patterns are. If errors appear across many unrelated files, if reads slow dramatically, if the machine stalls when a particular drive is attached, or if a drive makes new noises, hardware moves up the list of explanations.

Disk Utility concepts are relevant here — first aid can identify and sometimes correct file-system inconsistencies — but they are a step to take with a backup in place, not a reflex.

Installer, system and app errors

Installer errors have a narrow set of common practical causes: not enough free space, an incomplete or corrupted download, an interrupted previous attempt, power interruption during installation, or an installer that is not valid for the hardware. Because installations touch the system volume, they deserve a verified backup beforehand.

App-specific errors are best isolated by asking whether the problem follows the app or the account. Creating or switching to a second user account and reproducing the problem there is one of the most informative reversible tests available on a Mac: if the app behaves in the new account, the fault likely lies in the original account's app data rather than the app itself.

Server and network-related errors

Errors raised while connecting to a file share, a service or a website say something about the path between your Mac and the other end. They rarely indicate a defect in macOS. The useful questions are whether other devices on the same network can reach the same destination, whether other destinations work from this Mac, and whether the network is one you control.

• Only one destination fails from every device: the destination is the most likely cause.
• Every destination fails from one device: look at that device's network configuration.
• Everything fails from every device: look at the router or the internet connection.
• Failures only on a particular network: filtering, interception or isolation on that network is plausible.

How to document an error correctly

Good documentation shortens troubleshooting more than any single fix. Before changing anything, record the following. It takes two minutes and prevents the common situation where three changes have been made and nobody can say which one mattered.

1. The exact wording and number of the message, transcribed rather than paraphrased.
2. The app or process displaying it.
3. What you were doing at the moment it appeared.
4. Whether external storage, a network location or a peripheral was involved.
5. Whether it reproduces reliably, intermittently or only once.
6. Your macOS version and Mac model.

A safe troubleshooting sequence for any error

1. 1

   1. Describe the symptom precisely

   Replace 'it doesn't work' with the specific operation, the specific item and the specific message.

2. 2

   2. Establish scope

   One file, one folder, one app, one drive, or everything? Scope eliminates whole families of cause immediately.

3. 3

   3. Protect data

   If anything irreplaceable is involved, copy it elsewhere before you continue. This is the only step that cannot be done later.

4. 4

   4. Try reversible fixes

   Restarting, reconnecting, renaming a file, updating an app, testing a different cable. None of these can lose data.

5. 5

   5. Test one change at a time

   Change, test, record. Batched changes produce ambiguous results.

6. 6

   6. Escalate deliberately

   Only then consider steps that repair, reinstall, reformat or erase — and only with a verified backup.

Backup checklist before destructive steps

• A current copy of your documents and photos exists on separate storage.
• You have opened at least one file from that copy to confirm it is readable.
• Anything stored only in a single app's local database has been exported or noted.
• You know which accounts you will need to sign back into afterwards.
• The backup drive is not the drive you are about to repair, erase or reformat.

When professional diagnosis may be appropriate

Some situations are not troubleshooting problems. If a drive is making unfamiliar mechanical noises, if data is irreplaceable and no backup exists, if the machine shows physical damage or liquid exposure, or if the next step you can think of would erase something, stop. Hands-on assessment by a repair professional or data-recovery service is the appropriate next move, and continuing to experiment can reduce what is recoverable.

Apple Support 247 is an independent publication. We do not perform repairs, and we will always tell you when the sensible answer is to involve someone who can physically examine the hardware.