Key points:
- New Technology File System (NTFS) is the default file system for modern Windows operating systems, handling both system volumes and internal storage.
- In theory, the NTFS maximum file size limit is 16 EiB minus 1KB, but Windows caps it at 8 PB, depending on the OS version and cluster size.
- FAT32 maxes out at 4GB per file, while exFAT shares NTFS’s theoretical ceiling and works better for large files on portable or cross-platform drives.
- For most storage planning, areas like network speed, capacity, security, and backups require more attention than NTFS file size limits.
- Large-file errors in Windows usually trace back to FAT32 formatting, low disk space, app-specific limits, or long file paths rather than the NTFS limit itself.
The NTFS file size limit is theoretically just short of 16 EiB (exbibyte), or over 18446744 TB (terabytes). That’s an astronomically large size for a single file that you’ll never realistically reach. And, for practical reasons, won’t be able to.
This guide explains NTFS file size limits, from how they differ across operating systems to other practical factors that should be considered when planning storage.
What is NTFS?
New Technology File System (NTFS) is the file system used by modern Microsoft Windows operating systems for system volumes and internal storage.
Is there an NTFS max file size limit?
The maximum file size defined by the NTFS format is 16 EiB (exbibyte) minus one KB (kilobyte). This is an astronomical number – and is theoretical – as practically, you will reach volume limits determined by cluster size, operating system limits, or other ceilings before you can work with files of this size.
Windows operating systems impose limits separate to the NTFS format:
- Windows 7, Windows Server 2008 R2 and earlier: 16 TB minus 64 KB
- Windows 8, Windows Server 2012 and later: 256 TB minus 64 KB
- Windows 10 version 1709, Windows Server 2019 and later: 8 petabytes (PB) minus 2 MB
These limitations are due to the maximum cluster sizes supported by each OS. Independent of these, cluster size affects file size limits as follows:
- 4 KB (default cluster size): 16 TB
- 8 KB: 32 TB
- 16 KB: 64 TB
- 32 KB: 128 TB
- 64 KB: 256 TB
- 128 KB: 512 TB
- 256 KB: 1 PB
- 512 KB: 2 PB
- 1024 KB: 4 PB
- 2048 KB (current max cluster size, Windows 10 onwards): 8 PB
If you try to mount a volume with an unsupported cluster size in Windows, it will usually fail with the error STATUS_UNRECOGNIZED_VOLUME.
FAT32 vs. exFAT vs. NTFS file size limits
FAT32 is the legacy file system that was used by earlier consumer versions of Windows prior to Windows 2000. It’s remained popular due to its wide compatibility with PCs, as well as mobile and smart devices. FAT32 has a file size limit of 4 GB.
exFAT is designed for use on flash drives and other portable storage media to supplant FAT32, aiming for maximum compatibility while supporting larger files.
The exFAT file system has the same file size limit as NTFS (16 EiB minus 1 kilobyte). However, this is again theoretical: you’ll either run into one of the practical limitations explained, primarily the 128 PB maximum size that Windows supports for exFAT volumes.
While it’s possible to convert NTFS to FAT32, you should consider whether this is appropriate, as it’s generally only required for edge cases or compatibility with other devices. NTFS offers more features and better data protection.
What the NTFS file size limit means for storage planning
When choosing between FAT and NTFS, the former should only be used for legacy reasons.
From a planning perspective, the NTFS file size limit itself is not a concern. The NTFS max file size surpasses even the largest files almost any user or IT team is ever likely to encounter – even for use cases where incredibly large files are expected (for example, working with virtual machine images, logs, backups, and archives).
You should instead focus your planning on other factors, like network speed and availability for shared drives, overall capacity, security features, redundancy, compression, and backups.
How to troubleshoot large-file problems in Windows
It is unlikely that end users will see errors related to large file size that are actually caused by hitting the NTFS file size limit. Instead, check for the following problems and try these troubleshooting steps:
- The destination drive is formatted as FAT32.
- Check the file system of the drive.
- Confirm whether the file is larger than 4 GB.
- The destination volume does not have enough free space.
- Check the available free space.
- The application creating the file has its own size limit.
- Review the application limits.
- The file path is too long for the application or workflow.
- Confirm whether the file path is unusually long.
- Compression, encryption, or backup software has workload-specific restrictions.
- Reformat the drive only after backing up needed data.
- The target system or device does not support NTFS.
- Use exFAT for removable drives when large-file support and compatibility matter.
Backups are critical for all filesystem-related tasks: before reformatting, make sure no required data is stored only on the drive to be formatted, repartitioned, or converted. While data can sometimes be recovered after these operations, it is not a guarantee – and never worth the risk.
If you are working with business data, you can ensure that your network volumes are available, have sufficient capacity, and are properly backed up using the NinjaOne RMM platform.
