Choosing the Right File System: FAT32, exFAT, NTFS, APFS, ext4, XFS & Btrfs

FAT32

Legacy Microsoft file system introduced in 1996. Provides the highest cross‑platform compatibility for removable media.

Maximum file size: 4 GB (4,294,967,295 bytes)

Maximum partition size: 2 TB

Permissions, compression, encryption, journaling: not supported

Pros: universal read/write, fast formatting, low resource usage, works on very old devices.

Cons: 4 GB file‑size limit, no security features, prone to fragmentation.

Typical use cases: small‑file exchange, bootable USB/PE drives, generic flash‑media storage.

Formatting tips:

Windows built‑in formatter (volumes ≤32 GB)

For larger volumes use third‑party tools such as Rufus or

DiskGenius

exFAT

Successor to FAT32 (released 2006) optimized for flash storage. Removes the 4 GB file‑size ceiling while keeping broad OS support.

Maximum file size: up to 16 EB (theoretical), practical limit >4 GB

Maximum partition size: 128 PB+

Permissions, encryption, journaling: not supported

Pros: supports very large files, fast read/write on flash, native support on Windows 7+ and macOS 10.6.5+

Cons: no built‑in security or journaling, fragmentation can affect performance over time.

Typical use cases: large‑media storage on USB/SD cards, cross‑platform data exchange where files exceed 4 GB.

Formatting tips:

Windows: right‑click the drive → Format → select exFAT macOS: use Disk Utility and choose exFAT Linux: install exfatprogs and run

mkfs.exfat /dev/sdX1

NTFS

Default Windows file system since Windows NT 3.1 (1993). Provides ACL‑based permissions, journaling, compression, EFS encryption, disk quotas, sparse files, and more.

Maximum file size: 16 EB (theoretical)

Maximum partition size: 16 EB

Permissions, journaling, encryption, compression: supported

Pros: handles very large files and volumes, rich security and management features, reliable for system and data drives.

Cons: poor cross‑platform compatibility (macOS read‑only without drivers, Linux needs ntfs-3g), higher write overhead on flash devices.

Typical use cases: Windows system disks, internal HDD/SSD, enterprise data storage where ACLs and encryption are required.

Formatting tip (Windows): format X: /FS:NTFS. Linux:

mkfs.ntfs /dev/sdX1

HFS+ (Mac OS Extended)

Apple’s primary file system from 1998 until APFS replaced it in 2017. Supports optional journaling, Unicode filenames, case‑sensitivity, POSIX + ACL permissions, and FileVault encryption.

Maximum file/partition size: 8 EB (theoretical)

Permissions: POSIX + ACL

Journaling: optional (enabled by default on macOS)

Encryption: supported via FileVault

Pros: native macOS features (Spotlight, Time Machine), reliable journaling, large‑file support.

Cons: limited Windows/Linux compatibility (requires third‑party drivers), higher fragmentation on SSDs, superseded by APFS.

Typical use cases: legacy macOS installations, external drives used exclusively with macOS ≤10.12.

APFS (Apple File System)

Modern Apple file system introduced in 2017, optimized for SSDs. Features copy‑on‑write, snapshots, native multi‑key encryption, space sharing, and fast directory indexing.

Maximum file/container size: 8 EB (theoretical)

Permissions: POSIX + ACL

Journaling: transactional (copy‑on‑write)

Encryption: multi‑key native encryption

Snapshots & space sharing: supported

Pros: excellent SSD performance, instant snapshots, strong encryption, flexible volume management.

Cons: not readable/writable by Windows or Linux without special tools, not ideal for mechanical HDDs, Time Machine support only on macOS Big Sur+.

Typical use cases: macOS system disks (10.13+), iOS devices, SSD‑based external drives used only with Apple platforms.

ext4 (and ext3)

Default Linux file system for most distributions. Ext4 adds larger limits, extents, delayed allocation, and performance improvements over ext3.

Maximum file size: 16 TB (ext4) / 2 TB (ext3)

Maximum partition size: 1 EB (theoretical)

Permissions: POSIX + ACL

Journaling: supported (multiple modes)

Encryption: kernel‑level via fscrypt (optional)

Pros: high performance, robust journaling, wide Linux tool support, open source.

Cons: no native cross‑platform support, lacks built‑in snapshots or RAID.

Typical use cases: Linux system disks, servers, containers, workstations.

XFS

High‑performance 64‑bit journaling file system originally from SGI (1994), now default on many enterprise Linux distributions (RHEL 7+, CentOS).

Maximum file/partition size: 8 EB (theoretical)

Permissions: POSIX + ACL

Journaling: metadata‑only

Online resize: grow only (no shrink)

Pros: excellent scalability, parallel I/O via allocation groups, reliable for large files and high‑throughput workloads.

Cons: cannot shrink partitions, less efficient for small‑file intensive workloads, no native cross‑platform support.

Typical use cases: database servers, large‑scale data warehouses, high‑concurrency web services.

Common commands (Linux):

df -Th | grep xfs
mkfs.xfs /dev/sdX1
xfs_growfs /mount/point
xfs_repair /dev/sdX1

Btrfs

Modern Linux file system implementing copy‑on‑write, native snapshots, subvolumes, built‑in RAID, compression, and self‑healing checksums.

Maximum file/partition size: 16 EB (theoretical)

Snapshots & subvolumes: supported

Compression: zlib, zstd, lzo (optional)

RAID: integrated RAID 0/1/5/6/10 (RAID 5/6 experimental)

Self‑healing: checksums for data and metadata

Online resize: grow and shrink supported

Pros: powerful data protection (snapshots, checksums), flexible volume management, on‑the‑fly compression, built‑in RAID.

Cons: RAID 5/6 considered unstable, higher write amplification on SSDs, not default on most distros, no Windows/macOS support.

Typical use cases: NAS devices, backup drives with snapshot needs, testing environments, systems where data integrity is critical.

Common commands (Linux):

mkfs.btrfs /dev/sdX1
mount -t btrfs /dev/sdX1 /mnt
btrfs subvolume create /mnt/myvol
btrfs subvolume snapshot /mnt/myvol /mnt/snap
btrfs filesystem df /mnt

Comparison Overview

File System | Max File | Max Partition | Permissions | Journaling | Snapshots | Typical Use
------------|----------|---------------|-------------|------------|-----------|--------------------------
FAT32      | 4 GB    | 2 TB          | No          | No         | No        | Small removable media
exFAT      | >4 GB   | 128 PB+       | No          | No         | No        | Large cross‑platform files
NTFS       | 16 EB   | 16 EB         | Yes (ACL)   | Yes        | No        | Windows system & data drives
HFS+       | 8 EB    | 8 EB          | Yes (POSIX) | Optional   | No        | Legacy macOS disks
APFS       | 8 EB    | 8 EB          | Yes (POSIX) | COW        | Yes       | Modern macOS SSDs
ext4       | 16 TB   | 1 EB          | Yes (POSIX) | Yes        | No        | Default Linux distro
XFS        | 8 EB    | 8 EB          | Yes (POSIX) | Yes (meta) | No        | High‑throughput Linux servers
Btrfs      | 16 EB   | 16 EB         | Yes (POSIX) | Yes (COW)  | Yes       | Linux NAS, snapshots, RAID

Choosing the Right File System

There is no one‑size‑fits‑all solution. Use FAT32 or exFAT for simple cross‑platform removable media, NTFS for Windows‑centric environments, APFS for modern Apple SSDs, ext4 for general Linux workloads, XFS for high‑performance servers, and Btrfs when you need built‑in snapshots, compression, and RAID on Linux.