“The file is too large for the destination file system” means your destination drive’s file system can’t handle files over a certain size – FAT32 caps out at 4 GB per file, which trips up anyone copying large videos, ISOs, or VM files. Here are four ways to fix it, starting with the least disruptive.
Fix #1: Reformat the drive as exFAT (recommended)
exFAT is the best choice for most USB drives and external hard drives in 2026 as it supports files well beyond 4 GB and works on Windows, macOS, gaming consoles, and smart TVs. The catch: formatting erases everything on the drive, so back it up first.
- Back up any files you want to keep from the destination drive.
- Open File Explorer and right-click the destination drive.
- Select Format.
- In the File system dropdown, select exFAT.
- Give the drive a label if you want, then click Start.
- Click OK to confirm and this will erase the drive.
Once formatting completes, try copying your large file again. It should transfer without errors.
Fix #2: Reformat as NTFS (Windows-only environments)
If the drive will only ever connect to Windows PCs, NTFS is a solid choice. It has no practical file size limit and adds features like file permissions and journaling. It’s not ideal if you also plug the drive into a Mac or a TV, since those devices can’t always write to NTFS.
- Back up any files on the destination drive.
- Open File Explorer, right-click the drive, and select Format.
- In the File system dropdown, select NTFS.
- Click Start, then OK to confirm.
Alternatively, if you want to convert FAT32 to NTFS without erasing the drive, see our guide on how to convert a drive from FAT32 to NTFS without losing data.
Fix #3: Upload the file to cloud storage instead
If you only need to move the file once and don’t want to reformat the drive, cloud storage sidesteps the file system limit entirely. OneDrive, Google Drive, and Dropbox all handle files well over 4 GB.
- Upload the large file to OneDrive, Google Drive, or Dropbox.
- Access it from the destination device by downloading it directly, or share a link.
This works well for one-off transfers and requires no changes to either drive.
Fix #4: Split the file into smaller parts
If you can’t reformat the drive and cloud storage isn’t an option, splitting the file into sub-4 GB chunks lets you copy it to a FAT32 drive. You’ll need a free tool like 7-Zip to split and later reassemble the file.
- Right-click the large file and select 7-Zip > Add to archive.
- In the Split to volumes, bytes field, enter
3900M(3,900 MB — safely under the 4 GB FAT32 limit). - Click OK. 7-Zip creates numbered archive parts (e.g.,
filename.7z.001,filename.7z.002). - Copy all the parts to the destination drive.
- To reassemble, right-click the first part (
.001) on the destination and select 7-Zip > Extract here.
If you’re getting this error on an NTFS drive
If Windows reports this error on a drive that’s already formatted as NTFS, the file system itself isn’t the problem. First, confirm the actual file system: open Command Prompt and run fsutil fsinfo volumeinfo D: (replace D: with your drive letter). If it says NTFS, check whether Windows 11’s Controlled Folder Access (ransomware protection) is blocking the copy — it can trigger a misleading “file too large” message. To check:
- Open 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, add the source app to the allowed list instead of leaving protection off permanently.
Which file system should you use?
Not sure which format to pick? Here’s a quick reference:
| File System | Max File Size | Works With | Best For |
|---|---|---|---|
| FAT32 | 4 GB | Windows, macOS, Linux, consoles, TVs | Small files, legacy compatibility |
| exFAT | 16 EB (no practical limit) | Windows, macOS, Linux, most consoles and TVs | Large files, cross-device use |
| NTFS | 16 EB (no practical limit) | Windows (read-only on macOS without extra software) | Windows-only environments |
Conclusion
Reformatting to exFAT (Fix #1) resolves this for most people and is the right long-term choice for any drive you use across multiple devices. If the error shows up on a drive that’s already NTFS, Controlled Folder Access is worth checking before you do anything more drastic as it’s an easy fix that’s easy to miss.
