When you format an external drive, a USB stick or a memory card, the system offers a list of formats: NTFS, exFAT, FAT32, sometimes APFS. The choice looks harmless, yet it decides which devices the storage will work with, how large a file it can hold and, above all, how it behaves the day it is unplugged carelessly or hit by a fault. Here are the benchmarks for choosing with full knowledge of the trade-offs.
What a file system actually does
A file system is the index that lets a computer know where each file sits, what it is called, which folder it belongs to and which blocks it occupies on the device. The data can be perfectly intact and still become unreachable if that index is damaged. How well a format protects (or fails to protect) its own structure during writes therefore weighs almost as much on reliability as the quality of the hardware.
NTFS: the native Windows format
NTFS is the default file system of modern Windows. It relies on a central table, the Master File Table, which describes every file and its attributes. It supports access control lists (permissions per user or group), file-system-level encryption (EFS), compression, quotas and links. It handles very large volumes: up to 8 PB on Windows 10 version 1709 and later or Windows Server 2019 and later, and 256 TB on earlier versions, depending on cluster size.
Its main reliability strength is journaling. NTFS keeps a transaction log: after a sudden stop, it uses that log at the next startup to bring the volume structure back to a consistent state. One important caveat, though: the journal protects metadata (the structure), not file contents. A document being saved at the moment of a power cut can still end up truncated on a volume that Windows considers clean.
exFAT: built for removable media
Microsoft created exFAT for USB sticks, memory cards and external drives, removing the limits of FAT32. File size is stored on 64 bits, which makes the theoretical limit irrelevant for everyday use, and the maximum volume size exceeds 100 PiB. The format stays deliberately lightweight: no permissions, no native encryption, no compression, and a ceiling of 2,796,202 files per folder that is rarely reached. It is also the format defined by the SD specification for SDXC cards (32 GB to 2 TB).
The flip side is the lack of a journal. The specification includes a “dirty volume” flag, which signals that a mount did not finish cleanly, and directory entries carry a checksum, which helps spot an anomaly. But nothing allows an interrupted operation to be replayed or rolled back: the consistency of the volume depends entirely on writes running to completion.
FAT32 and APFS in brief
- FAT32: compatible with almost everything, but a single file cannot exceed 4 GiB minus 1 byte, and the Windows graphical formatting tool does not offer it above 32 GB. No journal either. It remains relevant for small media and older devices.
- APFS: the default format on Macs since macOS 10.13, with strong encryption and snapshots. Windows does not handle it natively, so keep it for storage that will never leave the Apple ecosystem.
| Criterion | NTFS | exFAT | FAT32 |
|---|---|---|---|
| Maximum file size | Up to 8 PB depending on cluster size | Far above 4 GiB (limited by the volume) | 4 GiB minus 1 byte |
| Journaling | Yes (metadata) | No | No |
| Permissions and ownership | Yes | No | No |
| Native file-system encryption | Yes (EFS) | No | No |
| Native compression | Yes | No | No |
| Native write support on macOS | No | Yes | Yes |
| Linux support | ntfs3 kernel driver since version 5.15 | Kernel driver since version 5.7 | Yes |
| Typical use | Internal drives, external drives kept for Windows | USB sticks, SD cards, exchange between systems | Small media, older devices |
Compatibility across Windows, macOS, Linux and devices
- Windows reads and writes all three formats; NTFS is mandatory for the system partition.
- macOS reads NTFS volumes but does not modify them without a third-party driver or tool. exFAT and FAT32 are fully readable and writable. In Disk Utility, Apple recommends FAT for Windows volumes of 32 GB or less and exFAT above that.
- Linux includes an exFAT driver since kernel 5.7 and an NTFS driver (ntfs3) since kernel 5.15, alongside the older user-space NTFS-3G.
- TVs, cameras, game consoles: many accept exFAT or FAT32, less often NTFS. The device manual has the final word.
Pulling the plug: what really happens
Yanking a device during a write can interrupt three things: the file contents themselves, the structures that describe them (allocation table, directory) and the writes still waiting in the system cache. Since Windows 10 version 1809, the default policy for external devices is “Quick removal”: Windows does not cache writes to them, so the device can be unplugged without ejecting it, at the cost of somewhat lower performance. With the “Better performance” policy, ejecting is mandatory. Quick removal lowers the risk without removing it: unplugging in the middle of a write remains dangerous.
On NTFS, the next mount replays the journal and the structure becomes consistent again, even if the last file may be incomplete. On exFAT there is nothing to replay: if the interruption lands between two updates of the allocation table and the directory, the two can drift apart. Symptoms range from missing files or a wrong free-space figure to, in severe cases, a volume that no longer mounts. Windows usually offers to scan and repair the device at that point.
One habit worth keeping: if the device holds irreplaceable data, it is better not to launch that automatic repair right away. It rewrites volume structures, and a prior copy (ideally a full image) keeps every option open.
Which format for which device
- Internal drive or SSD on Windows: NTFS.
- External drive used only with Windows, important data: NTFS, with BitLocker or an equivalent if the data is sensitive.
- Storage shared between Windows and Mac: exFAT, with disciplined ejecting and a second copy of the files.
- SD cards and camera memory: the format required by the card standard (exFAT for SDXC), preferably formatted in the camera itself.
- Drive for a TV or console: whatever the manual specifies, often exFAT or FAT32.
- Files over 4 GiB: rule out FAT32.
- Mac only: APFS.
How the format affects data recovery
The file system shapes the recovery method, not only the odds. On NTFS, the Master File Table keeps each file’s name, dates, location and place in the folder tree. Even when damaged, it offers many entry points to rebuild the original folders, and the journal can shed light on recent operations.
On exFAT, names and folders live in directory entries. A file written in one contiguous run can be described without going through the allocation table (the NoFatChain flag in the specification), which makes it easier to locate; a fragmented file is harder to rebuild. When the directories themselves are lost or overwritten, recovery falls back on signature-based searching: the content is found, but without original names or folders. FAT32, with even less metadata, follows the same logic.
In every case, a few habits protect the chances of success:
- stop writing to the device as soon as a problem appears;
- do not reformat “just to see”, because a new format overwrites precisely the structures recovery depends on;
- avoid automatic repairs on critical data before making a copy;
- have a professional clone the device if the drive makes unusual noises or is no longer detected.
Depending on the device, the approach differs: see our pages on logical faults, external USB hard drives and Mac data recovery, along with our guides on damaged USB drives and recovery after formatting.
No format is “the right one” in absolute terms: NTFS protects structure best, exFAT travels everywhere, FAT32 remains a common denominator and APFS belongs to the Apple world. The right choice is the one that matches how the device is really used, backed by an independent backup, because no file system replaces a second copy.