Backup Drive File Systems: exFAT vs NTFS vs APFS, and the One to Pick for Your Computers
Formatting is the one storage decision you cannot undo politely: it erases the drive. Yet most people make it in a hurry, with a new drive on the desk and a dialog box waiting, and discover the mistake months later — usually at the worst possible moment, when the backup drive plugs into a different computer during a restore and that computer can see the files but cannot write, or cannot see the drive at all.
The fix is to decide by the computers you own rather than by feature lists. There are only three realistic candidates for a modern backup drive, and each has one job it does best and one failure that rules it out for the other jobs.
The three candidates, honestly described
NTFS is Windows’ native file system: journaled, permission-aware, and the format Windows backup tools expect. Its flaw is travel — macOS reads NTFS natively but needs third-party tools for full write access, so a Windows-formatted backup drive is a read-only guest on a Mac. APFS is Apple’s native system for modern macOS and SSDs, with snapshots and strong encryption, and the format Time Machine uses; its flaw is the mirror image — Windows cannot use it natively at all. exFAT is the diplomat: readable and writable on both Windows and macOS with no practical file-size limit, which is why it is the default recommendation for drives that move between systems. Its flaw is integrity: exFAT has no journaling, so an improper ejection or a power loss mid-write carries a real corruption risk that the journaled formats largely shrug off.
And FAT32 appears in format dialogs out of habit and history, but its 4 GB file-size limit disqualifies it for modern backups — a single disk image, video project, or virtual machine file breaks it.
| Your computers | Format | Why |
|---|---|---|
| Windows only | NTFS | Native, journaled, expected by Windows backup tools |
| Mac only | APFS | Native, snapshot-capable, required for modern Time Machine |
| Windows + Mac, drive moves files | exFAT | Read/write on both, no 4 GB limit; eject carefully every time |
| Windows + Mac, dedicated backup | Native format per machine (two drives or two partitions) | A backup’s job is integrity and restorability, not diplomacy |
The transfer drive and the backup drive are different jobs
Most format confusion comes from giving one drive two jobs. A transfer drive carries copies — the originals live elsewhere, so exFAT’s missing journal is an acceptable price for universal access, and one specialist view goes further, recommending exFAT only for transferring between computers rather than as an actively-worked drive. A backup drive holds the copy you will beg for on a bad day. That job rewards journaling, native tool support, and a restore you have actually rehearsed — and punishes clever cross-platform compromises, because the restore happens on whatever computer is alive that day, with whatever it can mount.
Households with both Windows and Mac machines therefore usually need one of two honest setups: two backup drives, each in its machine’s native format, or one drive partitioned into an NTFS section and an APFS section. A single exFAT drive backing up both machines is the popular third option and the weakest: it works right up until an unclean eject corrupts the file system holding both backups.
Choose and verify, step by step
- List every computer that must restore from this drive — not just the one that writes the backup today. The restore list decides the format.
- Pick from the table above. One operating system means its native format; a drive that only ferries files between systems means exFAT.
- Copy anything worth keeping off the drive first. Formatting erases everything on it, without exception or undo.
- Format, then label honestly. Name the drive with its format and role (for example, “Backup-NTFS”) so a future reader in a hurry knows what they are holding.
- Run a restore rehearsal. Copy a folder on, eject properly, plug the drive into the other computer (or the same one, for single-system setups), and restore the folder somewhere new. Open the files.
- Eject properly, every time. This is a genuine integrity step on exFAT, and good hygiene on every format.
What success looks like: the drive mounts on every computer on your restore list, a test folder survives the round trip and opens correctly, and the drive’s name tells you its format at a glance. If any computer on the list cannot write to or mount the drive, the format is wrong for that job — change it now, while changing it costs nothing.
Edge cases worth one minute
Game consoles, TVs, and car systems are their own world and often accept only exFAT or FAT32; give them their own cheap stick rather than bending the backup drive to suit them. Encryption follows the format: BitLocker belongs with NTFS, FileVault with APFS, and an exFAT drive that needs encryption needs a file-level tool instead. Finally, whatever you choose, one backup drive is one copy — the format decision protects the copy’s readability, and the 3-2-1 habit protects you when readability is not the problem.
Two worked households, start to finish
Household one: a Windows desktop and a Windows laptop. There is no decision to agonize over. Format the backup drive NTFS, let the built-in backup tool use it, and spend the saved deliberation on the restore rehearsal instead. The second machine can both read and write the drive in an emergency, the journal protects the backup against the occasional unplugged cable, and permissions behave exactly as the operating system expects. Choosing exFAT here 'for flexibility' would buy compatibility with computers the household does not own, paid for with the backup's integrity - a bad trade made only because the format dialog made it look modern.
Household two: a Mac at home and a Windows machine at work, with family photos living on both. Separate the jobs. The photo transfer stick is exFAT: small, cheap, and readable everywhere, holding copies whose originals live on the machines. Each machine's backup drive stays native - APFS for the Mac so Time Machine works as designed, NTFS for the Windows machine - and neither backup ever visits the other computer. If the budget allows only one large drive today, partition it into APFS and NTFS sections and accept the fixed split of capacity as the price of correctness. What this household should not do is the instinctive thing - one big exFAT drive backing up both machines - because that arrangement concentrates both backups onto the one file system in the comparison with no journal, guarded by nothing but the hope that everyone always ejects properly, including on the bad day when the backup is needed.
FAQ
Can a Mac write to an NTFS backup drive?
Not natively. macOS reads NTFS out of the box, but full write access needs third-party tools — which is why a Windows backup drive is effectively read-only on a Mac.
Why not just use exFAT for everything?
exFAT is the right default for a drive that moves files between Windows and Mac, but it has no journaling, so an improper ejection risks corruption. For the dedicated backup holding your only copy, a native journaled format is the safer choice.
Can I use one drive for both my Windows PC and my Mac backups?
Yes, by partitioning it: an NTFS partition for the Windows machine and an APFS partition for the Mac. A single shared exFAT partition for both backups is possible but is the weakest option for integrity.
Does formatting really erase the drive?
Yes — formatting erases everything on it. Copy anything you need off the drive before you format, and verify that copy before proceeding.