exFAT vs FAT32: Pick by the Device, Not the Drive

Updated: October 2026

The stick works fine on your laptop, then the car stereo, the camera or the BIOS flash tool says there's nothing on it. Usually the drive is exFAT and the device only reads FAT32. Here's exFAT vs FAT32 in practice: what each one can hold, which devices read which, and how to format a drive so the thing you plug it into accepts it.

exFAT vs FAT32: The Short Answer

Both are members of the FAT family, the simple file systems built for removable storage. FAT32 is the old one that everything reads. exFAT is the newer one Microsoft built for flash drives and memory cards that outgrew FAT32.

Neither one has a journal, permissions or encryption of its own. Those live on NTFS, which our exFAT vs NTFS guide covers. So exFAT vs FAT32 comes down to two questions: how big are the files, and what's reading the drive?

Why FAT32 Stops at 4 GB and exFAT Doesn't

FAT32 stores each file's size in a 32-bit field. The biggest number that fits is 4,294,967,295 bytes, one byte short of 4 GB. Copy anything larger and Windows says the file is too large for the destination file system, even with 200 GB free.

exFAT uses a 64-bit size field. The exFAT specification puts the ceiling around 16 exabytes, so file size stops being your problem.

exFAT also changed how it tracks space. FAT32 finds every file by following a chain of cluster entries, one hop at a time. exFAT keeps a bitmap of free and used clusters, and it can flag a file as one contiguous run so nothing has to walk the chain. On a big video file that means less metadata churn on every write, which is where the "exFAT feels faster on large files" reputation comes from.

The format tools used to add a second limit. Windows refused to create FAT32 volumes over 32 GB, which is why bigger sticks arrive formatted exFAT. The file system itself goes further, and newer Windows builds lift that cap on the command line.

Which Devices Read Which

This is where exFAT vs FAT32 tickets usually start. The PC is fine with either. The device on the other end isn't.

UEFI firmware and boot sticks. The UEFI spec guarantees FAT support, not exFAT. That's why bootable USB tools default to FAT32, at least for the boot partition. As one r/Ubuntu thread points out, the 4 GB limit only touches that small EFI partition, not the files you store later.

BIOS flashback ports and firmware updaters. Stick with FAT32. Our guide to BIOS updates covers the rest of that prep.

Car stereos, older TVs and printers. Head units and appliances built before exFAT went mainstream often read only FAT32, sometimes only on an MBR-partitioned stick. A large new stick formatted exFAT out of the box shows up as "No USB device."

Cameras. Cameras follow the SD card spec, covered next. Format the card in the camera and it picks the right one.

macOS and Linux. Both read and write FAT32 and exFAT. Apple's Disk Utility suggests MS-DOS (FAT) for volumes of 32 GB or less and exFAT above that. On Linux, exFAT stopped being a patent headache when Microsoft published the spec and backed its addition to the kernel on 28 August 2019.

SD Cards: The Spec Picks the Format for You

The SD Association defines a file system per capacity class. SDHC cards (over 2 GB up to 32 GB) use FAT32. SDXC cards (over 32 GB up to 2 TB) and SDUC cards (up to 128 TB) use exFAT.

So a 64 GB card in a camera should be exFAT. Reformat it FAT32 on a PC and the camera may refuse it or insist on reformatting, and anything recording long 4K clips hits the 4 GB wall mid-take. The camera's own format menu is the safe route.

Cluster Size: The Hidden Cost on Small Files

Both formats hand out space in clusters, also called allocation units. A file always takes whole clusters, so a 6 KB file on a 128 KB cluster uses 128 KB of the drive.

That rarely matters for video. It matters a lot for a stick full of small files: scanned receipts, config backups, a music library with album art. Ten thousand 6 KB files hold about 59 MB of data. On 4 KB clusters they take 78 MB. On 128 KB clusters they take 1.22 GB.

You choose the cluster size when you format, in the "Allocation unit size" box or with /A: on the format command. To see what a drive already uses, run chkdsk E: and read the "bytes in each allocation unit" line. Pick small clusters for many small files and large ones for a drive of big video files.

Formatting a Drive So the Device Accepts It

For exFAT, the Windows Format dialog works. So does the command line:

code
format E: /FS:exFAT /Q /V:TRANSFER

For a picky device, FAT32 alone often isn't enough. The partition table has to be MBR too. The r/CarAV thread below is the clearest walkthrough of that combination, and the poster found that other utilities failed because they defaulted to GPT.

On Windows, diskpart sets both in one pass. clean wipes the whole stick, so check the disk number twice:

code
diskpart
list disk
select disk 3
clean
convert mbr
create partition primary
format fs=fat32 quick label=CAR
assign

On a Mac, diskutil eraseDisk FAT32 CAR MBRFormat /dev/disk4 does the same. On Linux, mkfs.vfat -F 32 makes FAT32 and mkfs.exfat makes exFAT. Get-Volume in PowerShell shows what every drive is using now, and our list of PowerShell commands has more checks like it.

exFAT or FAT32: Which One to Pick

Start with the device, not the drive. If a manual, a firmware updater or a car stereo asks for FAT32, give it FAT32 on MBR and keep single files under 4 GB. If any file is over 4 GB, or the drive moves between Windows, macOS and Linux, use exFAT. For SD cards, let the camera format them.

Treat both as transport. Neither has a journal, so a stick pulled mid-copy can come back asking to be scanned and fixed. For drives that stay on Windows and hold anything you'd hate to lose, NTFS is the better home. For all three side by side, see FAT32 vs NTFS.

That's exFAT vs FAT32: FAT32 for the devices that only speak it, exFAT for big files and everything modern. If the drive won't format at all, check whether the disk is write-protected before you blame the file system.