File system
Also known as: filesystem, file systems
A file system is the method an operating system uses to organize, store, and find files on a drive, keeping track of names, folders, sizes, permissions, and where each piece of data lives.
Common file systems include NTFS on Windows, APFS on Macs, ext4 on Linux, and FAT32 or exFAT on USB drives and memory cards. While you rarely see the file system, it explains why a drive works on one computer but not another, and why formatting erases data.
File system, explained at three levels
At home
A file system is like a library's catalogue. The drive is a huge set of numbered shelves, and your files are books, often split across several shelves. The catalogue records each book's title, which shelves hold its pages, and who may borrow it, and it tracks which shelves are empty. When you save a file, the system finds free shelves and updates the catalogue, so it can find everything again.
At work
A file system is the method an operating system uses to organize data on a drive into files and folders, tracking each file's name, location, size, and permissions. Windows uses NTFS, Macs use APFS, and USB drives often use exFAT. Businesses care because the file system controls who can open which files, helps data survive crashes, and decides which drives work on which computers.
At home
A drive is just billions of numbered storage blocks. The file system is the index that turns them into files and folders. It records each file's name, size, location on the drive, dates and permissions, and keeps track of which blocks are free. When you save a file, it finds free space and updates the index. Different operating systems use different file systems, which is why a drive formatted for one may not be fully readable on another.
At work
Common file systems include NTFS on Windows, APFS on Macs, ext4 on Linux and exFAT for portable drives shared between systems. They differ in maximum file size, permissions, encryption, compression and snapshot support. Journaling file systems record pending changes before making them, so a power cut leaves the index consistent rather than corrupt. Copy-on-write designs such as APFS, ZFS, Btrfs and Microsoft's ReFS never overwrite data in place, which makes instant snapshots possible.
At home
When you delete a file, the file system usually removes it from the index and marks its blocks as free, but the data remains on the drive until something overwrites it. That is why recovery tools can often bring deleted files back. On SSDs, a feature called TRIM tells the drive to erase freed blocks, so recovery becomes much harder. In my view, turning on full-disk encryption before you sell a device is the simplest way to make leftover data unreadable.
At work
Choose file systems by workload: NTFS for general Windows servers, ReFS for Hyper-V and Storage Spaces with integrity checks, and XFS or ext4 for Linux. Use snapshots as a fast recovery layer for accidental deletion and ransomware, but remember they share the same hardware and are not a backup. Monitor for corruption and disk errors, test restore procedures, and audit NTFS and share permissions regularly, since permission sprawl is a common data exposure risk.
Real-world examples
At home
Carlos couldn't copy a large movie file to his USB stick. It was formatted with FAT32, which has a 4 GB file limit, so he reformatted it as exFAT.
At work
Fatima manages a Halifax law firm's file server. Its file system snapshots let her restore a folder accidentally deleted by a staff member within minutes.
How it compares
| feature | NTFS | APFS | exFAT |
|---|---|---|---|
| Main platform | Windows | Apple devices | USB drives, SD cards |
| Large files | Yes | Yes | Yes |
| Permissions | Yes | Yes | No |
| Cross-platform | Limited | Limited | Wide |
Each file system suits a platform. exFAT is the best for sharing drives.
For analysts
When planning data migrations, I'd check file system limits such as path length and permission models early. They cause surprising failures in large moves.
History & origin
Microsoft's FAT file system originated in the late 1970s and became standard on floppy disks and MS-DOS PCs. Unix file systems from the 1970s introduced hierarchical folders and permissions. Microsoft introduced NTFS with Windows NT in 1993, adding journaling for crash recovery and permissions, with built-in encryption following in Windows 2000. Apple's HFS+ arrived in 1998, replaced by APFS in 2017, which was designed for SSDs. Linux's ext4 became common from 2008, and newer file systems such as ZFS and Btrfs added features like snapshots and self-healing. exFAT, designed for flash drives, became the standard for large SD cards. In my view, file systems are a perfect example of invisible engineering that only gets noticed when it fails.