File too large for destination file system: check FAT32 before copying
What to do first
When a video or backup will not fit onto an otherwise empty USB drive, compare the individual file size with the destination format. Prefer testing suitable existing storage before changing a format.
This is a general troubleshooting guide, not an announcement of a current outage.
Affected products and symptoms
- Product
- Windows
- Versions and conditions
- Windows 11 / Windows 10; copying to USB drives, SD cards or external storage
- Error codes and identifiers
- FAT32
Symptoms
- Large files fail to copy despite available free space
- Windows reports that the file is too large for the destination file system
Causes and conditions
FAT32 has a per-file limit of about 4 GiB, separate from total free capacity. If the destination uses another file system, investigate a different cause.
Before you start
- Keep the original file and identify existing destination data
- Check the supported formats of the device that will read the file
Precautions
- Formatting erases existing data; it is not part of this diagnostic procedure
- Renaming the extension does not remove the file-size limit
Tools and official pages used in this guide
Step-by-step instructions
Open Properties for the failing source file and read Size. Record the individual file size, rather than the combined size of its containing folder.
A 6 GB video failing while a small document copies is a useful clue to a per-file limit. Keep access-denied and disconnection errors separate.
A 6GB video failing on a USB drive with 16GB free does not establish faulty hardware. Total capacity and single-file limits differ. Record the failed file byte size and destination filesystem, keeping the source during small-file comparisons. Do not substitute folder aggregate size for the failed file size.
In This PC, open the destination drive properties and read its file system. FAT32 cannot store an individual file larger than roughly 4 GiB.
If the format is exFAT or NTFS, this FAT32 limit does not explain the failure. Recheck the destination and exact error.
FAT32 permits a maximum single-file size of one byte below 4GiB. Use actual byte size rather than rounded GB labels. NTFS or exFAT calls for another diagnosis, especially with permission, space, write-protection or disconnect errors. Advertised device capacity does not identify the current partition filesystem.
Official links for this step
Copy the same source to a compatible exFAT/NTFS destination with sufficient space. Success supports a FAT32-limit diagnosis. Failure elsewhere requires source-read and connection checks rather than blaming format alone.
Check the free space in the same properties dialog. Freeing more space on FAT32 does not increase its per-file limit.
The alternative destination still needs enough capacity for the whole copy. Do not delete unfamiliar files merely to create room.
If a compatible exFAT or NTFS drive is available, copy and paste the file there. Keep the source in place during the test.
For a TV, camera or other device, verify format compatibility first. If it requires FAT32, use that product's supported export or split-file workflow.
Check the consuming device format support before choosing alternative storage. Windows readability does not prove television, camera or vehicle compatibility. For FAT32-only devices, inspect manufacturer or editor-supported split exports. Renaming an extension or compressing does not guarantee a file below the limit.
Official links for this step
For split backups or archives, verify reconstruction with the producing application and retain all parts. A split archive differs from playable segmented video; follow the consumer application or device workflow.
After copying finishes, compare the destination name and size, then open it with the appropriate application. For a backup, check whether its creating application recognizes it.
Eject the external device before disconnecting. Keep the original until the intended receiving device can also read the file.
Compare copied names and sizes and open the destination. For split content, verify all parts and the receiving device workflow. Copy rather than move to retain recovery options. Treat formatting as a separate operation requiring independent, verified copies of existing data, rather than an initial destructive fix.
Check the result
- The large file finishes copying and opens at the destination
- The intended device recognizes both the storage format and the file
- The copied file opens and the intended consuming device can read it
If the problem continues
- For FAT32-only devices, consult the manufacturer's supported export or split-file procedure
- If exFAT or NTFS also fails, inspect capacity, the exact error and connection stability
Scope of this guide
Troubleshooting guide — The copied file opens and the intended consuming device can read it
Frequently asked questions
Can it fail even with 100 GB free?
Yes. FAT32's individual-file limit applies independently of the drive's remaining capacity.
Can I choose either NTFS or exFAT?
Both support files beyond FAT32's limit, but the receiving device must support the selected format.
Will ZIP always make a large video fit?
Already compressed video may not shrink sufficiently. Check the resulting archive size. A device intended for direct playback may not read ZIP, so confirm its supported workflow first.
Official sources and dates
- File System Functionality Comparison ↗
- Free up drive space in Windows ↗
- Move your files to a new Windows PC using an external storage device ↗
- Troubleshoot Disk Management ↗
Source publication or resolution date: 2023-03-27. Sources checked: 2026-10-13. The check date is not the date the problem first occurred. Interface labels can vary between versions and display languages.
Related troubleshooting guides
Windows errors and troubleshooting →