You try to drag a 6 GB game backup or a single large video onto a USB stick and Windows throws an error: “The file is too large for the destination file system.” The drive clearly has room, so what is going on? The culprit is almost always the FAT32 file system, and the fix takes about a minute.
The 4GB wall explained
FAT32 is an old file system from the late 1990s, and by design it cannot store any single file larger than 4 GB minus one byte. That limit is baked into how FAT32 records file sizes, using a 32-bit field. It does not matter whether the drive is 32 GB or 512 GB; no individual file can cross 4 GB. Total capacity is unrelated to the per-file cap.
Why drives still ship as FAT32
Manufacturers format flash drives and SD cards as FAT32 because it is universally readable: cameras, car stereos, game consoles, smart TVs, and every operating system understand it. That compatibility is the whole reason the aging format survives, and for small files it works fine.
Your two better options
| File system | Max file size | Best for |
|---|---|---|
| FAT32 | 4 GB | Max compatibility, small files |
| exFAT | 16 exabytes (no practical limit) | Large files, cross-platform |
| NTFS | 16 TB per file | Windows drives, permissions |
For a USB stick that needs to hold big files and still work on both Windows and macOS, exFAT is the answer. It removes the 4 GB limit, keeps broad device support, and is the default for SD cards above 32 GB. Choose NTFS only if the drive will live on Windows machines and you want file permissions or journaling.
How to reformat
Back up the drive’s contents first, because formatting erases everything. In File Explorer, right-click the drive, choose Format, pick exFAT from the file-system dropdown, leave the allocation unit at default, and click Start. Thirty seconds later you can copy files of any size. If you must keep FAT32 for an old device, the workaround is to split the large file into parts with an archive tool.
Watch out for device support
Before committing to exFAT, confirm the target device reads it. Most gear made after about 2011 does, but some older car head units and cameras only speak FAT32, in which case you are stuck splitting files or upgrading the device.
Choosing an allocation size
When you reformat, Windows asks for an allocation unit, sometimes called cluster size. The default is almost always correct. A larger unit wastes space on small files but can slightly speed sequential transfers of huge files, while a smaller unit packs many tiny files efficiently. For a drive that holds big videos and game backups, the default or a slightly larger unit is fine; there is no need to overthink it.
Game consoles and external drives
If you are formatting an external drive for a game console, follow the console’s own format process rather than Windows, because consoles often use their own layout and will re-initialize the drive anyway. For general cross-platform use between Windows, macOS, and modern TVs, exFAT remains the safest large-file choice, striking the best balance between capacity support and broad device compatibility.
Quick reference
Fixing the 4 GB copy error, at a glance:
- The limit is a FAT32 restriction, not a lack of space on the drive.
- Reformat to exFAT for large files plus broad Windows and macOS support.
- Choose NTFS only if the drive stays on Windows and you want permissions or journaling.
- Back up the drive first; formatting erases everything on it.
- Confirm your other devices read the new format before committing.
FAQ
Will reformatting to exFAT lose my data?
Yes, formatting wipes the drive, so copy everything off first. Once reformatted, you can copy the files back and add ones larger than 4 GB without any error.
Is exFAT as reliable as NTFS?
For portable drives it is fine, but exFAT lacks journaling, so always eject the drive safely to avoid corruption. If reliability and permissions matter and the drive stays on Windows, NTFS is the sturdier choice.
Bottom line
The 4 GB block is a FAT32 limitation, not a lack of space. Reformat the drive to exFAT for the best mix of large-file support and cross-device compatibility, or to NTFS if it will only ever touch Windows. Back up first, and confirm your other devices can read the new format before you commit.
