Выбор файловой системы для внешнего диска: когда FAT32, exFAT или NTFS?

Once you've formatted your external drive, you expect it to work everywhere. But in reality, compatibility depends heavily on the filesystem you choose. A perfectly working drive on one system may reject the next big file, and it may even fail if used on a different device. The common advice I've seen is simply to pick NTFS or switch to exFAT, but neither of these explains why. Neither NTFS, exFAT, nor FAT32 is inherently better or worse, but each filesystem is built to prioritize different things. The moment you understand their tradeoffs, picking the right filesystem stops being guesswork. FAT32 It keeps compatibility by enforcing a file-size cap You shouldn't be surprised if your drive shows several free gigabytes yet refuses a single 5GB file. In this instance, the file transfer may fail, and you may notice the copy dialog fails. Your free space remains untouched, but it's not a glitch. FAT32 uses a 32-bit field to record a file's size, which caps an individual file at 4,294,967,295 bytes, just under 4GB, regardless of how much free space remains on the drive. This is a limitation caused by how FAT32 records a file's length. This may seem like a huge disadvantage, but the limit is actually one of the reasons FAT32 remains relevant. It remains one of the most widely supported file systems that car stereos, older digital cameras, and many game consoles understand. Because the format was cheap to support and broadly compatible, manufacturers had little incentive to update firmware. So, even though this same format will block a 4K phone video, it's also why your USB stick may still be readable when used on a 2012 dashboard. I experienced this trade-off when I tried to move a large video file to a USB stick that had always worked. The stick was empty, but the file would simply not transfer. This isn't a trade-off you can reverse without changing the drive's format. It's the price you pay for universal readability. exFAT It removes the cap without inheriting NTFS’s weight The most direct answer to FAT32's 4GB cap is exFAT. This format was designed by Microsoft. Its primary goal was to overcome FAT32's file and volume limitations while maintaining a lightweight filesystem. It doesn't adopt NTFS's complex and high-overhead features that make it a full-featured enterprise filesystem. By default, it doesn't have journaling; it also lacks access-control lists and built-in filesystem-level encryption and compression. Its lightweight nature becomes immediately apparent if a transfer is interrupted. It offers fewer recovery options than a journaled volume if you accidentally pull a cable or lose power midway through writing a large file. When this happens, at best you may end up with an incomplete file; at worst, you may need repair tools to restore the directory. This doesn't imply that an exFAT drive is guaranteed to be corrupted; however, it has fewer mechanisms for performing a clean rollback of its structure. exFAT is supported by Windows, macOS, cameras, and consoles mainly because of its simple design. If you need a drive to move between these systems seamlessly, exFAT becomes a very reliable format to turn to. Its relevance comes from not being as robust or advanced as NTFS. NTFS It works best when the drive stays in Windows In a general hierarchy, NTFS doesn't automatically stay at the top of the pack when compared to FAT32 and exFAT. It's the format that assumes your drive belongs to Windows; it's built for the ecosystem it's meant to stay in. A good example is journaling. On Windows, when there's a crash or power loss, the filesystem isn't left half-finished. Also, a full repair is often unnecessary because the OS can recover the filesystem using its journal. However, once you take this drive out of a Windows environment, that protection comes at a cost. macOS can normally read an NTFS drive, but it doesn't provide native write support. You need a third-party NTFS driver or another workaround to write to it. However, these come with other variables that aren't the native NTFS experience. The ability to read a file doesn't guarantee that you can use a drive the same way you do on Windows. The drawback isn't a flaw. NTFS is built around Windows features such as permissions, journaling, and recovery rather than cross-platform portability. So, which filesystem should you use? Ordinary day-to-day use determines the formats that are best. If I need a USB stick to be recognized by an older car stereo, it must be formatted as FAT32. For drives I use constantly across multiple operating systems, exFAT is the most sensible option. The backup drives that I don't expect to use outside Windows need to remain in NTFS. None of these formats are universal. Each one focuses on an important element to protect, and for someone who works across multiple devices, I see the value in having them all.