FAT32 vs NTFS (and exFAT): What Breaks on Each

Updated: October 2026

Somebody hands you a USB stick with a 6 GB file that won't copy, or a drive the Mac can open but not save to. Both tickets trace back to one decision made at format time. Here's FAT32 vs NTFS, plus exFAT, the third option that usually settles it: what each file system does, what breaks on each, and how to switch without losing data.

FAT32 vs NTFS vs exFAT at a Glance

A file system is the filing scheme a drive uses to track where every file lives. FAT32, NTFS and exFAT are the three Windows formats you'll meet on USB sticks, SD cards and external drives. They differ in three ways that matter day to day: how big a single file can be, which devices can read and write them, and what happens when something goes wrong mid-write.

The short version: FAT32 for anything that boots or flashes firmware, exFAT for moving large files between machines, NTFS for drives that stay in the Windows world.

FAT32: Works Everywhere, Stops at 4 GB

FAT32 dates back to Windows 95 OSR2, and that age is its strength. Every operating system, every UEFI firmware, every camera and nearly every smart TV can read it. When a device manual says "format the stick before updating," it means FAT32.

The catch is the file size ceiling. A single file can't be bigger than 4 GB minus one byte. Copy a 5 GB video or a disk image and Windows answers with "The file is too large for the destination file system," even when the drive has plenty of free space.

The other limit was Windows itself. For years the Format dialog and the format command refused to create a FAT32 volume bigger than 32 GB, which is why larger sticks arrived as exFAT. Microsoft lifted the command-line cap from 32 GB to 2 TB in Windows 11 builds 26100.8313 and 26200.8313, released to the Release Preview channel on 17 April 2026. The change covers the format command, so don't count on the Explorer dialog offering it.

The 4 GB wall bites hardest on Windows install media. A golden image with apps baked in often passes 4 GB, so its install.wim won't fit on a FAT32 stick. Two fixes work. Split the image with DISM into chunks Windows Setup reads natively, or build a two-partition stick: a small FAT32 partition for the UEFI boot files and an NTFS partition for everything else. Rufus does the second one for you.

The r/sysadmin consensus in that thread is the safe rule: the UEFI spec only requires FAT support, so anything else is a bonus your next batch of laptops might not have.

NTFS: The Windows Default, and Why Macs Can't Write to It

NTFS has been the Windows system drive format since Windows XP. It has no practical file size limit, and it brings the features FAT never had: file and folder permissions, EFS encryption, compression, quotas and a journal.

The journal is the part that saves you. Before NTFS changes its own records, it writes down what it's about to do. If the cable gets pulled halfway, Windows replays or rolls back that log on the next mount, and the file system comes back consistent. The file being copied at that moment can still be damaged, but the drive's structure survives.

Permissions matter on removable media too. On an NTFS drive, folder permissions travel with the disk. On FAT32 or exFAT there are none, so anyone who plugs the stick in can read everything. EFS encryption is NTFS-only as well: copy an EFS-encrypted file to a FAT32 or exFAT drive and Windows warns you it's about to drop the encryption. If the data needs protecting on a stick, use BitLocker To Go, which encrypts FAT32, exFAT and NTFS drives alike.

The weak spot is everything outside Windows. macOS reads NTFS but can't write to it without third-party drivers. Linux handles it through the ntfs3 kernel driver or ntfs-3g. Cameras, TVs and firmware tools mostly ignore it.

exFAT: The Middle Ground for Big Removable Drives

Microsoft built exFAT for flash storage that outgrew FAT32. It drops the 4 GB file limit, keeps the light structure that cameras and phones can handle, and works read-write on both Windows and macOS out of the box. SDXC cards, anything over 32 GB, ship formatted as exFAT by specification. Our exFAT vs FAT32 guide covers which devices need which.

That makes it the default answer for a drive that moves between a Windows laptop and a Mac, or for video files over 4 GB. What it gives up is safety. exFAT has no journal, no permissions and no EFS. The exFAT vs NTFS guide weighs that trade in detail.

The r/DataHoarder answer is blunt and fair: exFAT is fine as transient storage for moving data from one place to another, and a poor home for anything you'd hate to lose.

What Breaks on Each

File system tickets tend to fall into four patterns. Knowing which format is on the drive tells you which one you're looking at.

Pulled mid-write. FAT32 and exFAT have no journal, so a stick yanked during a copy can come back with a half-updated allocation table and a "Scan and fix" prompt. Since Windows 10 version 1809 the default removal policy for external drives is Quick removal, which turns off write caching so a finished copy is safe to unplug. A copy still in progress is not. NTFS drives recover their structure on the next mount.

Big file, small format. "File too large" on a drive with free space is always FAT32 and always the 4 GB limit. Reformat as exFAT, or as NTFS if the drive stays on Windows.

Mac can't save. The drive is NTFS. Move the data off, reformat as exFAT, move it back.

Device won't see the stick. Firmware updaters, USB BIOS Flashback ports and older TVs usually only read FAT32, and sometimes only on a drive with an MBR partition table. Our guide to BIOS updates covers the rest of that prep.

Converting and Formatting Without Losing Data

Only one conversion keeps your files: FAT or FAT32 to NTFS. Windows does it in place with the built-in convert command:

code
convert E: /fs:ntfs

It's one-way. There's no command to go back from NTFS to FAT32, and convert doesn't handle exFAT at all. Every other change means copying the data off, formatting and copying it back. Take a backup before running convert anyway. It's rewriting the drive's metadata, and a power cut halfway is a bad afternoon.

Formatting from the command line is faster than clicking through Disk Management, and it's the only route to FAT32 above 32 GB:

code
format E: /FS:FAT32 /Q /V:FLASH
format E: /FS:exFAT /Q /V:TRANSFER
format E: /FS:NTFS /Q /V:BACKUP

In PowerShell, Format-Volume -DriveLetter E -FileSystem exFAT -NewFileSystemLabel TRANSFER does the same job, and Get-Volume lists every drive with its current file system. For more one-liners like these, see our list of PowerShell commands.

For install media with an oversized image, split it instead of reformatting. This is the command Microsoft documents for FAT32 install sticks:

code
Dism /Split-Image /ImageFile:C:\images\install.wim /SWMFile:E:\sources\install.swm /FileSize:3800

If DISM itself throws errors on the source image, our DISM RestoreHealth guide walks through the repair side.

Which One to Pick

Pick by the job the drive has to do, not by habit.

A stick that boots a machine, flashes firmware or feeds a camera or TV gets FAT32. A drive that carries big files between Windows and Mac gets exFAT, and it gets treated as transport, not storage. A drive that lives on Windows, holds anything sensitive or needs permissions gets NTFS, with BitLocker To Go if it ever leaves the building.

On a fleet, the first question is what's already on the drives. Get-Volume answers that per machine. With OpenFrame you can run the same check as a script across every device and see where the FAT32 data drives are hiding.

That's FAT32 vs NTFS in practice: FAT32 for compatibility, NTFS for safety, exFAT for the space in between. If the drive in front of you won't format at all, start with the write-protection settings before blaming the file system.