FAT (File Allocation Table)

FAT (File Allocation Table)
Name	FAT (File Allocation Table)
Caption	Logical layout of a FAT volume
Introduced	1977
Developer	Microsoft Corporation
Latest release	exFAT
Type	File system
Os	MS-DOS, Microsoft Windows, macOS, Linux, FreeBSD, embedded systems

FAT (File Allocation Table)

FAT is a family of legacy file system formats introduced for Microsoft Corporation products and widely implemented across platforms and devices. It traces origins to early Microsoft Disk Operating System development and remains influential in interoperability for removable media, embedded controllers, and legacy computing environments. FAT's simplicity and broad support have led to long-term use across IBM PC compatibles, consumer electronics, and cross-platform utilities.

History

The table-driven storage approach originated in the late 1970s during design work by engineers at Microsoft Corporation for MS-DOS and related projects, contemporaneous with hardware efforts by IBM for the IBM PC. Evolution continued through collaborations and legal interactions involving Microsoft Corporation, Compaq, and the broader PC industry during the 1980s and 1990s. Major milestones include the introduction of FAT12 with early floppy implementations used in MS-DOS, expansion to FAT16 with larger hard disks amid the rise of Microsoft Windows 95, and the later development of FAT32 in response to growing storage demands during the era of Microsoft Windows 98. The exFAT specification emerged from Microsoft Corporation to address large-file and flash-storage requirements encountered in consumer devices produced by companies such as SanDisk, Samsung Electronics, and Kingston Technology.

Design and Structure

FAT organizes disk allocation using a central table mapping clusters to file chains, a design influenced by simplicity priorities in early Microsoft Corporation operating systems and compatibility needs with IBM PC hardware. The on-disk layout comprises a reserved region containing boot code tied to firmware from vendors like Phoenix Technologies and AMI, followed by copies of the allocation table and a data region holding cluster chains referenced by directory entries. Directory entries use fixed-size records influenced by designs in CP/M heritage and the MS-DOS ecosystem and store metadata such as timestamps compatible with conventions used in Microsoft Windows file timekeeping. The boot sector includes BIOS Parameter Block (BPB) fields standardized across implementations and referenced by system utilities from vendors including Microsoft Corporation, Symantec, and Acronis International.

FAT Variants (FAT12, FAT16, FAT32, exFAT)

FAT12 was tailored for floppy volumes common in systems by IBM and OEMs like Commodore International and adopted by utilities distributed by Microsoft Corporation. FAT16 increased cluster addressing capacity and was widely used in the era of IBM PC/AT compatibles and in shipping versions of Microsoft Windows 95 OSR2 and Microsoft Windows NT derivatives. FAT32 expanded addressable clusters and was introduced in Microsoft Windows 95 OSR2 to reduce cluster waste on larger partitions, influencing device makers such as Dell, HP, and Acer Inc. ExFAT, developed by Microsoft Corporation and adopted in standards and licensing agreements with companies like Samsung Electronics, Sony Corporation, and Toshiba Corporation, targets removable flash storage and large-file support used in digital cameras from Canon Inc. and Nikon Corporation.

File and Directory Management

Files are represented by directory entries that reference the starting cluster and attributes originally standardized in MS-DOS and extended in Microsoft Windows. Subdirectory handling employs special directory entries for "." and ".." similar to semantics used in UNIX-influenced filesystems but implemented in a manner compatible with utilities from Microsoft Corporation and third-party vendors such as NortonLifeLock and Paragon Software. File attributes include archive, read-only, hidden, and system flags used by backup tools like those from Symantec and system installers from Microsoft Corporation. Long filename (LFN) support introduced by Microsoft Corporation preserves compatibility with legacy directory schemes and is parsed by cross-platform libraries used in Linux, FreeBSD, and NetBSD distributions.

Compatibility and Use Cases

Due to widespread implementation by Microsoft Corporation and hardware manufacturers such as Sony Corporation, Panasonic Corporation, and Microsoft Xbox, FAT is the de facto choice for cross-platform removable media interoperability between Microsoft Windows, macOS, and Linux hosts. Embedded systems from vendors like STMicroelectronics, Texas Instruments, and NXP Semiconductors often include FAT support in bootloaders and firmware alongside RTOS products from Wind River Systems and Micrium. Consumer electronics including digital cameras by Canon Inc. and Nikon Corporation, MP3 players by Apple Inc. and SanDisk, and gaming consoles such as Microsoft Xbox 360 have relied on FAT or exFAT for storage compatibility. File-system drivers and userland tools are maintained in projects and organizations including The Linux Foundation, Free Software Foundation, and SUSE.

Limitations, Performance, and Scalability

FAT's limitations stem from cluster-chain fragmentation, lack of journaling, and constrained metadata compared to modern filesystems pioneered by projects like Oracle Corporation's ZFS and The Linux Foundation's ext4. Maximum volume and file sizes vary by variant, with FAT32 imposing a 4 GiB file-size limit that affects multimedia workflows in production environments by companies such as Adobe Systems and Autodesk. The absence of native access-control lists limits deployment in enterprise domains managed by Microsoft Active Directory and forces reliance on host-side permission models used by Samba and Windows Server. Performance degrades on large volumes due to linear cluster-chain traversal, a problem addressed in part by defragmentation utilities from Piriform and Microsoft Corporation but fundamentally solved by advanced allocation strategies in Apple Inc.'s APFS and The Linux Foundation's Btrfs.

Implementation Details and Utilities

Implementations appear in operating systems and projects such as MS-DOS, Microsoft Windows NT, Linux kernel, FreeBSD, and embedded SDKs from ARM Holdings toolchains. Utilities for checking and repairing FAT volumes include commands and packages from Microsoft Corporation (chkdsk), e2fsprogs-adjacent ecosystems, and cross-platform tools from Sysinternals and GParted. Driver and library implementations exist in open-source projects like Samba, Dosfstools, and FUSE modules used in macOS ports and distributions maintained by Canonical Ltd. and Red Hat, Inc.. Commercial storage vendors such as Western Digital, Seagate Technology, and SanDisk publish interoperability notes and firmware updates addressing wear-leveling interactions with exFAT on flash media.

Category:File systems