File Too Large for the Destination File System: Fixed

FAT32 stores file sizes in a 32-bit field, which maxes out at 4,294,967,295 bytes — 4GB minus one byte. Any single file larger than that simply cannot exist on a FAT32 volume, and Windows tells you so the moment the copy starts. This bites hardest with USB flash drives and SD cards because manufacturers format them FAT32 at the factory: it is the one file system that Windows, macOS, Linux, cameras, TVs, and car stereos all read without extra software. So the most compatible drive you own is also the one with the strictest single-file limit. The classic triggers are video files (a 4K home movie crosses 4GB fast), disk images (Windows install.wim files routinely exceed 4GB), and large backups. Note the important subtlety: the limit is per file, not per drive. Ten 3GB files (30GB total) copy to a FAT32 drive fine; one 4.1GB file does not, even on an empty 128GB drive.

Some hardware will not accept anything but FAT32 — older car stereos, many dashcams, some cameras, game consoles, and embedded devices. Reformatting those drives to NTFS or exFAT "fixes" the copy error and breaks the device: it simply will not see the drive anymore. If the drive lives in such a device, do not reformat. The correct fixes are the non-destructive ones: split the file into sub-4GB volumes with 7-Zip (the device never needs to know), or use a second drive formatted appropriately for the transfer and keep the FAT32 drive as the device expects it. Always check the device manual before reformatting any drive that did not come from a computer store shelf.

A depressingly common trap with cheap high-capacity USB drives and SD cards: the drive reports 128GB or 256GB to Windows but physically contains far less flash memory — sometimes as little as 8GB. Everything works until you exceed the real capacity, at which point writes fail with confusing errors, occasionally including the "too large" message. If your drive is a no-name bargain and the math does not add up (a "256GB" drive choking on a 5GB file), suspect this. Test tools exist that write patterns across the full advertised capacity and verify them; a genuine drive passes, a fake one fails at its real size. There is no software fix for fake flash — the only remedy is a refund and a drive from a reputable brand.

Windows Security includes ransomware protection called Controlled Folder Access, which blocks unauthorized programs from writing to protected folders — and occasionally to removable drives. When it blocks a copy, the error surfaced can misleadingly read as a file-size problem rather than a permission problem. Suspect this when the drive is already NTFS or exFAT (so the FAT32 explanation cannot apply) and the file is well under any limit. Check it via Windows Security > Virus & threat protection > Ransomware protection: if Controlled Folder Access is on, temporarily toggle it off and retry the copy. If the copy succeeds, do not leave protection off — instead, add your file manager or copy tool to the allowed-apps list and re-enable it.

Sometimes the boring answer is the right one: the file plus what is already on the drive genuinely exceeds capacity, or the "free space" reading is stale. This typically shows up as the copy failing partway through rather than instantly — an instant failure at 0% is the FAT32 signature; a failure at 90% is a space problem. Also watch for the Recycle Bin: deleted files on removable drives can sit in a hidden trash folder still consuming space. Empty it (or hold Shift while deleting) and recheck. And remember that drive manufacturers count gigabytes decimally while Windows counts in binary — a "16GB" drive shows about 14.9GB in Windows before you put a single file on it.