Windows IT Pro is the leading independent community for IT professionals deploying Microsoft Windows server and client applications and technologies.
  
  
  Advanced Search 


Return to article

Understanding File-Size Limits on NTFS and FAT
 

In the April 17 Windows Client UPDATE, I wrote about the 4GB file-size limit in FAT32. In response, I've received dozens of email messages telling me that FAT32 isn't limited to 4GB but rather that the 4GB limit is a FAT16 artifact. I also received messages questioning my assertion that NTFS is appropriate for small office/home office (SOHO) and small business users, but my point didn't center on NTFS's general appropriateness. I stand by my conclusion that if you're doing video editing on Windows, you need to use NTFS.

I've run into the 4GB wall when creating files on FAT32 partitions. Because I realized that the problem might have been caused by the video-creation software I was using, I tried again with different software to create an AVI file larger than 4GB. No dice: As soon as the file size reached 4GB, the application failed.

With that 4GB figure stuck in my head, I went to my accustomed research tools and found plenty of references to the FAT32 4GB limit. To back up that number, I searched the Microsoft Web site and found numerous articles confirming that the file-size limit on FAT32 is (2^32)-1 bytes, or one byte less than a full 4GB.

The confusion about FAT file size seems to stem from the fact that FAT16 has a 4GB limit on partition size, whereas FAT32 has a 2TB limit on partition size. A large number of my respondents appear to have confused "partition" with "file." To add a little additional confusion, many respondents commented that they're running large drives as one partition on FAT32. In these days of inexpensive 120GB+ hard disks, I guess my definition of "large" differs from that of these readers.

Windows XP and Windows 2000 limit partition creation to no larger than 32GB on FAT32. This limitation is by design: Microsoft wants you to use NTFS for large drives. If you use Windows Me or Windows 98 to format a drive, XP and Win2K can use a FAT32 partition larger than 32GB; however, these OSs can't create the partition. Also, keep in mind that when you use ATA/IDE hard disks larger than 127GB, you might need to update your computer's or hard disk controller's BIOS to properly support those larger drives.

More reading is at Microsoft's website

"Limitations of FAT32 File System"

"Limitations of the FAT32 File System in Windows XP"

and you can find Windows IT Pro resources on NTFS and FAT at

"NTFS5 vs. FAT32"

"Leverage the Advantages of NTFS"

"JSI Tip 9225: What is the maximum file size for the FAT16, FAT32, and NTFS file systems?"







Reader Comments

Thanks, this has helped to explain how I might be able to make DVD images larger than 4gb. I run win98SE, can I run a drive as NTFS in 98SE?

Doug -November 09, 2003

Thanks, but I heard there was a patch somewhere in the microsoft site (I couldnt find it) to avoid this limit while using win98se! Could you help me with that?

Roberto Ortega -December 03, 2003

just run into the same problem :-) i also understand you can apply a patch to windows to overcome this... wheres the patch lol? i cant find it anywhere? im running windows millenium your help would be well appreciated as i dont want to use xp

rich -December 04, 2003

-------------------------------------------------- Hi. I have used this File Generator to generate huge files (over 2GB or 4GB) and it worked. So David Chernicoff is right. The tool is available here: http://www.soft.tahionic.com/download-file-generator/index.html --------------------------------------------------

dotniet -June 11, 2009
Windows IT Pro Home Register FAQ for Windows WinInfo News
Europe Edition About Us Contact Us/Customer Service Media Kit Affiliates / Licensing  
SQL Server Magazine Office & SharePoint Pro DevProConnections IT Job Hound
Left-Brain.com Technology Resource Directory asp.netPRO ITTV Windows SuperSite 
 
 Windows IT Pro is a Division of Penton Media Inc.
 © 2009 Penton Media, Inc. Terms of Use | Privacy Statement