APFS, the Apple File System, is the default file system of macOS and all other Apple operating systems, designed for flash storage, strong encryption and copy-on-write metadata. It replaced HFS+ on Mac startup disks with macOS High Sierra in 2017 and is the foundation of every modern Mac’s storage layout, snapshots and backups. In macOS storage & backup, APFS is the layer on which Time Machine, Disk Utility, startup disks and FileVault all depend.
Its central ideas are containers that share free space among volumes, instant file clones, read-only snapshots and crash protection through copy-on-write. Together these make updates safer, copies faster and backups more reliable than on the older HFS+ format.
How APFS organizes a disk
APFS separates physical and logical storage into containers and volumes. A partition holds one APFS container, and the container holds several APFS volumes that draw from a shared pool of free space instead of fixed sizes. A volume can have an optional reserve, which guarantees it space, and a quota, which caps it.
Since macOS Catalina, the startup disk uses a volume group: a read-only System volume with the operating system and a writable Data volume with user files and apps, presented to the user as a single disk. Since macOS Big Sur, the system is additionally a signed system volume, sealed with a cryptographic hash tree so that any modification is detected at boot.
| Volume | Contents | Access |
|---|---|---|
| System | macOS itself, booted from a sealed snapshot | Read-only |
| Data | User accounts, apps, settings, documents | Read and write |
| Preboot | Boot files and encryption unlock data | Managed by macOS |
| Recovery | recoveryOS for repair and reinstall | Managed by macOS |
| VM | Swap files and sleep image | Managed by macOS |
Key APFS features and how they work
Most APFS features follow from its copy-on-write design: instead of overwriting metadata in place, APFS writes changes to new blocks and then switches a pointer. If power fails midway, the old consistent state remains, which provides crash protection without a separate journal.
| Feature | Mechanism | Practical benefit |
|---|---|---|
| Clones | New file shares blocks with the original until edited | Near-instant copies that use no extra space |
| Snapshots | Read-only, point-in-time image of a volume | Safe updates, local backups, rollback |
| Space sharing | Volumes allocate from one container pool | No fixed partition sizes to resize |
| Native encryption | Single-key or multi-key per-file encryption | FileVault without a separate layer |
| Sparse files | Unwritten regions take no space | Efficient disk images and databases |
| Fast directory sizing | Sizes tracked as files change | Quicker space reports |
| 64-bit identifiers | 64-bit inode numbers, nanosecond timestamps | Very large file counts and precise times |
Clones explain a frequent surprise: duplicating a 10 GB video in Finder completes instantly and free space barely changes, because both files reference the same blocks until one is modified. Disk usage figures therefore cannot simply be summed.
Snapshots are also the basis of local Time Machine snapshots, which macOS keeps on the startup disk for roughly a day so that recently deleted files can be restored even when the backup drive is not connected. These snapshots are deleted automatically when free space runs low, which is one reason why available space on a Mac can fluctuate without user action.
APFS compared with other file systems
APFS is designed around SSD characteristics, which shapes its strengths and weaknesses compared with HFS+ and cross-platform formats.
| File system | Design focus | Snapshots | Best use on a Mac |
|---|---|---|---|
| APFS | SSDs, encryption, copy-on-write | Yes | Startup disks, SSDs, Time Machine disks |
| HFS+ | Hard disks, journaling | No | Older Macs, legacy Time Machine disks |
| exFAT | Simple cross-platform exchange | No | Drives shared with Windows |
| NTFS | Windows journaling file system | Via Windows services | Read-only on macOS without extra software |
On mechanical hard disks, copy-on-write scatters file blocks over time and increases seek activity, so APFS can feel slower than HFS+ on an old external drive. Apple nevertheless uses APFS for Time Machine since macOS Big Sur and for Fusion Drive since macOS Mojave.
Working with APFS in practice
Disk Utility exposes APFS as containers and volumes, and the diskutil apfs command family offers finer control in Terminal. Choosing the right variant at format time matters, because changing it later requires erasing the volume.
| Variant | When to choose it | Caution |
|---|---|---|
| APFS | Default for internal and Mac-only external SSDs | None for normal use |
| APFS (Encrypted) | Portable drives with sensitive data | Losing the password loses the data |
| APFS (Case-sensitive) | Specific development or server needs | Some apps expect case-insensitive names |
| APFS (Case-sensitive, Encrypted) | Combination of both needs | Same cautions as above |
Adding a second volume to an existing container, for example for a beta version of macOS or a separate work area, needs no repartitioning, because the new volume simply shares the container’s free space.
Health checks use First Aid in Disk Utility or fsck_apfs, which verify container and volume metadata. Running First Aid on the container first and then on each volume is the usual order, and running it from recoveryOS avoids interference from the live system when the startup disk itself reports errors.
Limitations and common misunderstandings
- APFS checksums metadata, not user data, so it relies on the storage hardware to detect silent data corruption.
- Snapshots consume space as the live volume changes, which often appears as growing System Data or purgeable space.
- Windows cannot read APFS natively, so drives shared with PCs are better formatted as exFAT.
- Free space reported by Finder may include purgeable space that macOS frees only on demand.
- Older macOS versions before High Sierra cannot mount APFS volumes at all.
In simple terms
APFS is the filing system a Mac uses to keep track of everything on its disk. Think of a library that never erases a catalog card. When something changes, it writes a new card and only then removes the pointer to the old one, so a sudden power cut never leaves the catalog half finished.
This approach also lets the Mac take instant pictures of the whole disk, called snapshots, and make copies of large files in a moment. The result is a Mac that updates more safely and backs up more reliably.
A practical example
A video editor works on a MacBook Pro with a 1 TB internal SSD. Before applying a major macOS update, the system creates an APFS snapshot, so if the installation fails, the previous state remains intact. The update completes and the old snapshot is removed automatically.
During editing, the editor duplicates a 40 GB project folder to try a different cut. The copy finishes in a few seconds and free space drops by only a few megabytes, because APFS creates clones that share blocks with the originals. Only the edited clips take new space.
For backups, the editor formats a 4 TB external SSD for Time Machine, which uses APFS and snapshots. The outcome is fast copies, safer updates and hourly backups without extra software.