Choosing a Mac Filesystem: APFS, Mac OS Extended, and Cross-Platform Media
Compare APFS volumes and encryption with Mac OS Extended and Windows-compatible FAT formats, then choose a filesystem for the workload instead of by habit.
Choosing a filesystem is a compatibility and recovery decision, not just a formatting preference. A Mac’s internal startup storage, an external SSD shared with Windows, and a disk passed between older Macs can have different requirements. The right choice depends on which operating systems must read and write the device, which filesystem features the workload needs, and how the data will be backed up.
For current Mac workflows, APFS is the normal choice for Mac-only storage. Mac OS Extended (HFS+) remains relevant when a workflow or older system specifically requires it. For removable media that must be writable on both macOS and Windows, exFAT is usually the practical interchange format. MS-DOS (FAT) is a narrower compatibility option for small or legacy devices. None of these choices replaces a separate backup.
APFS: the default for modern Mac storage
Apple File System became the default filesystem for Macs using macOS 10.13 and later. Apple documents encryption, snapshots, space sharing, and support for startup and data volumes among its features. APFS is especially suited to contemporary flash storage, though Apple also supports it on hard drives and directly attached external storage.
An APFS container owns a pool of space. Multiple APFS volumes in the same container share the container’s available capacity instead of requiring each volume to be assigned a fixed partition size up front. A volume can also have a reserve or quota when the workload needs a capacity boundary. This makes separate volumes useful for organizing related Mac data, but it does not make them separate disks: capacity, device failure, and the container remain shared.
Disk Utility exposes standard, encrypted, case-sensitive, and case-sensitive encrypted APFS formats. Case sensitivity is a compatibility choice, not a performance toggle. An application or build tool that assumes Assets.png and assets.png refer to the same path can fail on a case-sensitive volume. Test software and deployment workflows before placing their working trees there.
Use APFS for a Mac startup disk, a Mac-only SSD, or a Mac backup/work volume when its features match the task. Use a separately tested backup even when snapshots are available: a snapshot on the same physical device cannot protect against device loss, and snapshot retention is not a substitute for an independent copy.
Mac OS Extended: compatibility for specific older workflows
Mac OS Extended, also known as HFS+, is an older Mac filesystem. Keep it when an older Mac, legacy software, or a documented media workflow explicitly requires it. Do not choose it for a new Mac startup volume simply because a previous external disk used it; first check whether the target operating system and application need HFS+ compatibility.
Formatting a volume in a new filesystem can make existing contents unavailable, and repartitioning or erasing is destructive. Before migrating HFS+ media to APFS, copy the data elsewhere, verify the copy, confirm the target Mac can read the chosen format, and retain a recoverable backup until the migration has been tested.
exFAT and MS-DOS (FAT): interchange, with reduced semantics
Apple identifies exFAT and MS-DOS (FAT) as Windows-compatible formats in Disk Utility. Apple recommends MS-DOS (FAT) for Windows volumes of 32 GB or less and exFAT for larger volumes. Those are Disk Utility selection recommendations; they should not be mistaken for a universal compatibility guarantee for cameras, consoles, firmware tools, or other embedded devices. Check the device manufacturer’s requirements first.
exFAT is a common choice for large removable media that must be read and written by both current Macs and Windows PCs. It is designed for interchange, not to reproduce all of APFS’s Mac-specific behavior. Test the actual workflow before using it for a shared working tree, a disk with important permissions requirements, or a device that must survive unexpected power loss without an independent copy.
FAT is useful when a device requires it, but it is usually the wrong choice for a modern large-file workload. A compatibility label alone does not imply support for every file size, filename, permission model, or device. Validate a representative file from end to end, including copy, eject, reconnect, and checksum comparison.
Choose by workload
| Workload | Starting point | Verify before committing |
|---|---|---|
| Mac startup or internal data volume | APFS | macOS version, volume role, encryption and recovery plan |
| Mac-only external SSD | APFS | Case-sensitivity expectations and independent backup |
| External drive shared with current Windows PCs | exFAT | Device compatibility, file-size limits, eject/reconnect and integrity checks |
| Older Mac or application that explicitly requires HFS+ | Mac OS Extended | Exact compatibility requirement and migration path |
| Small legacy device that explicitly requests FAT | MS-DOS (FAT) | Device’s supported format and maximum file size |
Inspect before erasing. In Disk Utility, choose View → Show All Devices to understand the physical disk, partition scheme, and volumes. On the command line, diskutil info /Volumes/NAME and diskutil apfs list report current storage information without formatting the device. Match the volume by device identity and size rather than relying only on its display name.
Treat erase and migration as change operations
Disk Utility warns that formatting erases files. Before clicking Erase, verify the selected physical device, partition scheme, format, and backup. If a drive has more than one volume or contains a Time Machine backup, stop and identify each one before changing anything. Never use a destructive command copied from an example against an unverified /dev/diskN identifier.
After formatting, write a test file from each required operating system, safely eject the device, reconnect it, and compare a checksum or application-level result. Confirm that dates, Unicode names, large files, and permissions behave as the application expects. If the drive is used for backups, complete a restore test rather than treating a successful copy as proof of recoverability.
Related:
- APFS Explained: Snapshots, Clones, and Space Sharing in Apple’s Filesystem
- Creating and Managing APFS Containers and Volumes with diskutil
Sources: