NTFS, exFAT, FAT32 and APFS: Choosing the Right File System for a Drive

Understand what a file system does and how NTFS, exFAT, FAT32, APFS and ext4 differ, so you can format drives without losing compatibility.

Share on Linkedin Share on WhatsApp

Estimated reading time: 7 minutes

Article image NTFS, exFAT, FAT32 and APFS: Choosing the Right File System for a Drive

Plug in a new external drive and your computer will eventually ask a question that stops most people cold: which file system should it use? Choosing wrongly is rarely catastrophic, but it can mean a drive that refuses to accept a large video file, or one that your other computer can read but not write to. This guide explains what a file system actually does and how the main options compare.

What a file system is

A storage device, at the hardware level, is just a huge sequence of numbered blocks. It has no notion of “documents”, “folders” or “names”. A file system is the organisational layer that turns those blocks into something usable: it keeps a table of where each file’s data lives, stores the names and folder structure, records metadata such as creation date and permissions, and tracks which space is free.

Formatting a drive means writing a fresh, empty version of that structure. The old data blocks are usually still physically present, which is why formatting is not the same as securely erasing — but the map that points to them is gone, so the operating system treats the drive as blank.

The main options

FAT32

The veteran. FAT32 is old, simple and understood by practically every device ever made: cameras, car stereos, game consoles, TVs, printers, routers. Its two well-known limitations are what push people away from it — a maximum individual file size of 4 GB, and a practical ceiling on volume size that makes it unsuitable for large modern drives. It also has no journaling, so it is more vulnerable to corruption if a transfer is interrupted.

exFAT

Designed as the successor to FAT32 for flash storage. It removes the 4 GB file limit, handles large capacities comfortably and is readable and writable on both Windows and macOS, plus most Linux systems and many modern devices. It is the default answer for a USB stick or external SSD that has to move between different operating systems. The trade-off is that it lacks journaling and advanced permissions, so it is less resilient and less suitable as a system drive.

NTFS

The standard file system for Windows. NTFS supports journaling, file permissions, compression, encryption, large files and large volumes. It is the right choice for an internal Windows drive or an external drive used mainly with Windows machines. On macOS, NTFS volumes are typically read-only without extra software, which is the single most common reason people find they “can’t copy anything” onto a drive borrowed from a Windows user.

APFS and HFS+

APFS is Apple’s modern file system, built with SSDs in mind. It offers strong support for snapshots, space sharing between volumes, cloning of files without duplicating data, and encryption. HFS+ is the older Apple format still found on some drives. Both are the natural choice for Mac internal drives and Time Machine-style backups, but Windows cannot read them without third-party tools.

ext4 and friends

ext4 is the traditional default on many Linux distributions: journaled, mature and reliable. Alternatives such as Btrfs and XFS add features like snapshots or better handling of very large files. These are excellent for Linux systems but are not natively readable by Windows or macOS, so they are a poor choice for a drive you plan to share widely.

Quick comparison

File systemBest forWindowsmacOSJournaling
FAT32Maximum device compatibility, small drivesRead/writeRead/writeNo
exFATCross-platform external drivesRead/writeRead/writeNo
NTFSWindows internal and Windows-only external drivesRead/writeRead-only by defaultYes
APFSModern Mac internal drives and SSDsNot nativeRead/writeYes
ext4Linux systemsNot nativeNot nativeYes

Journaling, and why it matters

A journaling file system keeps a short log of the changes it is about to make before making them. If the power is cut mid-write, the system can consult that log on the next boot and either finish or roll back the incomplete operation. The result is far fewer corrupted volumes after crashes and unplanned shutdowns.

This is a strong argument for using a journaled file system on anything holding important data, and a good reason to always eject removable media properly rather than pulling it out mid-transfer, especially with exFAT and FAT32.

Choosing in practice

  • USB stick shared between Windows and Mac: exFAT.
  • Memory card for a camera, console or car stereo: whatever the device manual specifies — often FAT32 or exFAT.
  • External drive used only with Windows: NTFS.
  • External drive used only with a Mac: APFS.
  • Drive for a Linux server or desktop: ext4 or another Linux-native option.
  • Drive holding files larger than 4 GB: anything except FAT32.

Before you format anything

Formatting removes access to everything on the volume, so back up first — and verify that the backup actually opens. Double-check that you have selected the correct drive letter or device identifier, because this is one of the easiest mistakes to make and one of the hardest to undo. Prefer a quick format for a healthy drive; a full format additionally checks the surface and takes considerably longer.

One more distinction worth knowing: the partition scheme (MBR or GPT) is separate from the file system. GPT is the modern standard and is required for very large drives and for booting on modern systems, while the file system determines how files are stored inside each partition.

Conclusion

There is no universally best file system — only the best fit for how a drive will be used. Compatibility, maximum file size and resilience are the three axes that matter, and once you can weigh them, that format dialogue stops being intimidating.

If you want to build stronger fundamentals in operating systems, storage and IT support, the free courses in hardware, operating systems and computer basics available on Cursa are a practical place to continue.

NTFS, exFAT, FAT32 and APFS: Choosing the Right File System for a Drive

Understand what a file system does and how NTFS, exFAT, FAT32, APFS and ext4 differ, so you can format drives without losing compatibility.

Text Encoding Explained: ASCII, Unicode and Why You Sometimes See Strange Symbols

Learn how computers store text, what ASCII and Unicode actually are, why UTF-8 became the standard, and how to fix files that display garbled characters.

Idempotency in APIs: Why Retrying a Request Should Be Safe

Learn what idempotency means in backend development, which HTTP methods provide it, and how idempotency keys prevent duplicate operations.

What Is a CDN? How Content Delivery Networks Make Websites Fast

Learn what a CDN is, how edge caching and cache headers work, what a cache hit means, and when a CDN helps — or does not.

Semantic Versioning Explained: What a Number Like 2.4.1 Actually Tells You

MAJOR.MINOR.PATCH is a promise, not decoration. Learn to read version numbers and understand dependency range symbols.

What Is a Virtual Machine? Virtualization Explained for Beginners

Learn what a virtual machine is, how hypervisors work, how VMs differ from containers, and when to use each one.

How HTTPS Works: Certificates, the TLS Handshake and What the Padlock Really Means

A beginner-friendly walkthrough of HTTPS: what TLS certificates prove, how the handshake works, and what the browser padlock does not guarantee.

Big O Notation Explained: How to Talk About Code Efficiency

A beginner-friendly guide to Big O notation: what it measures, the most common complexity classes, and how to reason about the cost of your code.