FAT32 is a file system that organizes a disk volume through a File Allocation Table whose entries are 32 bits wide, of which 28 bits address clusters. In OS storage, it is the most widely compatible format for removable drives and small partitions, readable and writable by Windows, macOS, Linux, cameras, game consoles, car audio systems and most firmware.
Introduced with Windows 95 OSR2 in 1996, FAT32 extended the older FAT16 to much larger volumes. Its strengths are simplicity and universal support; its weaknesses are a 4 GB maximum file size, no permissions, no journaling and poor behavior on very large disks. In operating systems today, it survives mainly where interoperability matters more than features, including the EFI system partition used for booting.
How FAT32 stores files
A FAT32 volume consists of a reserved area with the boot sector, two copies of the File Allocation Table, and a data region divided into clusters. Each cluster has one table entry, and each entry either points to the next cluster of the same file, marks the end of a chain, or marks the cluster as free or bad.
A file is therefore stored as a linked chain of clusters. Its directory entry records the name, attributes, timestamps, size and the first cluster; the operating system follows the chain in the table to read the rest. The root directory is itself an ordinary cluster chain, unlike FAT16, where it had a fixed size.
FAT32 also introduced an FSInfo sector that caches the free-cluster count and a hint for the next free cluster, plus a backup boot sector, normally at sector 6. These structures speed up allocation and give repair tools a second copy of the volume parameters, but the cached free count can become stale after an unclean removal, which is why disk checks sometimes correct it.
Original directory entries hold only 8.3 short names. The VFAT extension adds long file names of up to 255 characters stored in extra hidden entries, which is why every long name on FAT32 also has a short alias.
Key limits and parameters
The most important FAT32 limits come directly from its on-disk structures. The 4 GB file limit follows from the 32-bit size field in each directory entry, while volume limits depend on the 28-bit cluster numbers and on sector size.
| Parameter | Limit | Reason |
|---|---|---|
| Maximum file size | 4 GiB minus 1 byte | 32-bit file size field |
| Maximum volume size | About 2 TiB with 512-byte sectors | Sector count and cluster addressing |
| Windows format tool limit | 32 GB volumes | Policy choice, not a format limit |
| Cluster size | 512 bytes to 32 KB | Set when the volume is formatted |
| Long file name length | 255 characters | VFAT extension |
| Minimum cluster count | 65,525 clusters | Smaller volumes are treated as FAT16 |
The allocation unit size determines how much space small files waste. With 32 KB clusters, a 1 KB file still occupies 32 KB, so volumes holding many small files lose noticeable capacity to slack space.
| Volume size | Default cluster size | Practical effect |
|---|---|---|
| Up to 8 GB | 4 KB | Little wasted space |
| 8 GB to 16 GB | 8 KB | Moderate slack per file |
| 16 GB to 32 GB | 16 KB | Noticeable slack with small files |
| Above 32 GB | 32 KB | Large slack, long table scans |
FAT32 compared with other file systems
FAT32 is best understood against its successors and alternatives. exFAT keeps the simple FAT design but removes the file-size limit, while NTFS, APFS and ext4 add journaling, permissions and much better scaling for internal disks.
| File system | Maximum file size | Journaling | Typical use |
|---|---|---|---|
| FAT32 | 4 GiB minus 1 byte | No | Small removable media, EFI partitions |
| exFAT | Practically unlimited | No | Large USB drives, SDXC cards |
| NTFS | Practically unlimited | Yes | Windows system and data disks |
| APFS | Practically unlimited | Copy-on-write | Mac internal and external disks |
| ext4 | 16 TiB with 4 KB blocks | Yes | Linux system and data disks |
Because FAT32 has no journaling file system protection, an interrupted write can leave the allocation table and directory entries inconsistent. The two table copies help recovery tools, but they do not replace a journal.
When FAT32 is still the right choice
FAT32 remains the right choice when a volume must be readable by the widest range of devices. Many embedded systems, older cameras, printers, televisions and car stereos support only FAT32, and the UEFI specification requires FAT support for the EFI system partition.
| Situation | Recommended format | Reason |
|---|---|---|
| EFI system partition | FAT32 | Required by UEFI firmware |
| USB drive for firmware updates | FAT32 | Many devices read nothing else |
| USB drive with video files over 4 GB | exFAT | No file-size limit |
| Internal Windows disk | NTFS | Journaling and permissions |
| Drive shared between Mac and PC | exFAT | Large files, broad support |
Formatting a large drive as FAT32 is possible with third-party tools or command-line utilities, but it is rarely wise: mount times, free-space calculation and fragmentation all degrade as the table grows.
Limitations and common mistakes
- Copying a file over 4 GB fails, often with a misleading message about insufficient space even though the drive has room.
- No permissions or ownership, so FAT32 cannot protect files on a shared or system disk.
- No built-in encryption or compression at the file system level.
- Timestamps use local time with two-second resolution for modification times, which can confuse synchronization tools.
- Unsafe removal can corrupt the table, so ejecting the drive before unplugging it matters more than on journaled systems.
- Fragmentation builds up over time, which slows mechanical disks and makes disk defragmentation more relevant than on modern formats.
The idea in brief
FAT32 is like a simple table of contents at the front of a notebook that says which pages belong to which story. Almost any reader in the world understands this format, which is why it works in so many devices.
The catch is that each story can only be so long. FAT32 cannot hold a single file larger than 4 GB, and it has no locks or safety log. It is the most compatible choice for small drives, but not a good choice for large, important disks.
A practical scenario
A technician needs to update the firmware of a network-attached television in a hotel. The manufacturer instructions say the update file must be on a USB drive formatted as FAT32, because the television’s firmware reads no other format.
The technician formats a 16 GB drive as FAT32 with the default 8 KB cluster size, copies the 600 MB update file to the root directory and starts the update from the service menu. The television detects the file immediately and installs it.
Later the same day, a colleague tries to copy a 7 GB training video to a FAT32 drive and gets an error. Reformatting that drive as exFAT solves the problem, because the file exceeds the 4 GB FAT32 file limit.