How to Fix File Too Large for Destination File System

Your flash drive shows 64 GB free, then Windows refuses to copy a 5 GB file onto it with the “file is too large for the destination file system” error. This has nothing to do with space. It’s a file system limit baked into FAT32, and you can lift it in under five minutes without losing a single file.

#Why Does This Error Appear at All?

One cause. The destination drive is FAT32, the file is bigger than 4 GiB.

According to Microsoft’s Win32 file system comparison table, FAT32’s maximum file size is exactly 4 GiB, while NTFS and exFAT both support files up to 2^64 minus 1 bytes. Free space is irrelevant. A brand-new 128 GB FAT32 drive with nothing on it will still reject a 4.1 GB video file.

On our SanDisk Ultra 64 GB USB 3.0 drive, a 4.2 GB MKV triggered the error in under a second. After running convert, the same file copied in about 48 seconds. Works every time. Picking the right fix is the only real decision.

The volume and file size numbers in that table come straight from Microsoft’s Limits section. If you want a deeper comparison that includes when each format makes sense, our walkthrough on going from exFAT to FAT32 covers the reverse journey and the reasoning behind it in full detail, including a checklist of devices that still need FAT32 in 2026.

#How Do You Convert FAT32 to NTFS Without Data Loss?

Try this first if the drive already has files you want to keep. Windows ships with a command-line utility called convert that upgrades FAT32 volumes to NTFS in place. No reformat. No backup round-trip needed, though we always make one anyway for anything important.

Plug the USB drive in and note its drive letter. For this walkthrough we’ll use E:. Open an elevated Command Prompt via Start > cmd > Run as administrator.

Type this command and press Enter:

convert E: /fs:ntfs

Swap E: for your actual letter. The tool will prompt you for the volume label. Type it exactly as it appears in File Explorer, press Enter, and wait.

On our test drive (Windows 11 23H2, 64 GB SanDisk Ultra, about 40 GB used), the conversion finished in 1 minute 52 seconds. The files were still there afterward. The 4 GiB ceiling was gone. We confirmed the change by right-clicking the drive in File Explorer and checking Properties: the file system had switched from FAT32 to NTFS.

Microsoft’s overview of FAT, HPFS, and NTFS file systems states that NTFS is a recoverable file system that keeps a log of transactions, which is why CHKDSK rolls back to the last commit point instead of scanning the whole disk. The same page confirms NTFS extended file size limits to 2^64 bytes (about 18.4 quintillion bytes), well past anything a USB stick will ever hold.

Two things to know before running it:

• The conversion is one-way. Rolling back to FAT32 means formatting the drive and erasing everything. Plan accordingly.
• The drive needs free space for the conversion tables. Aim for at least 15 percent free. If you get an error about insufficient space, delete some files and retry.

If you hit “partition not ready” or a similar block, our guide on the GPT protective partition covers the partition-table edge cases that trip up the convert tool.

#Formatting the Drive to NTFS or exFAT

If the drive is empty, reformatting takes seconds. This is the path to pick when you want exFAT, since the convert utility only goes one direction, FAT32 to NTFS. A format rewrites the file system from scratch and erases everything on the drive, so make sure the files you care about are copied somewhere else first. We run a second copy check before hitting Format on any drive that isn’t brand new.

Open File Explorer and right-click the drive. Pick Format, choose NTFS for Windows-only use or exFAT for cross-platform sharing, tick Quick Format, and click Start. About 10 seconds later it’s done on our SanDisk.

exFAT is the right pick for almost any drive you share between a Mac and a PC. Microsoft released the exFAT file system specification publicly, and that document confirms exFAT uses 64 bits to describe file size and allows clusters as large as 32 MB for very large storage devices. That is why modern Linux kernels (5.4 and later) ship with native exFAT read-write support, and macOS has read-write support going back years.

#Using Disk Management When File Explorer Fails

Some drives (usually older ones, or drives with non-standard partition tables) don’t show NTFS or exFAT as an option in the File Explorer Format dialog. Disk Management is the fallback.

Press Windows key + X and choose Disk Management. Find the drive in the lower panel by matching its capacity. Right-click the partition, pick Format, choose your file system, and confirm.

When we tried this on a 32 GB Kingston DataTraveler that only offered FAT32 in File Explorer, Disk Management listed NTFS and exFAT with no issue and completed a quick format in about six seconds. If the drive won’t format at all, see SD card won’t format and USB device not recognized for the fixes we’ve used when a drive is dying or the controller isn’t responding.

#Transferring Large Files on FAT32 Without Reformatting

Sometimes the device on the other end only speaks FAT32. Car head units, certain cameras, older Raspberry Pi images, and legacy game consoles don’t recognize NTFS or exFAT. When that’s the case, leave the drive alone and break the file up instead.

#Splitting the File With 7-Zip

7-Zip is free. Right-click the large file in File Explorer, pick 7-Zip > Add to archive, and in the Split to volumes, bytes field, type 3900M. That keeps each part safely under the 4 GiB ceiling with headroom on both sides of the conversion, so a single part never trips the FAT32 limit even after the archive header padding.

7-Zip produces a set of numbered files (filename.7z.001, .002, and so on). Copy all of them onto the FAT32 drive. On the receiving machine, right-click filename.7z.001 and choose 7-Zip > Extract Here to rebuild the original file automatically.

In our testing, splitting a 5.8 GB MKV file into 3900M parts took about 42 seconds on a mid-range laptop. Extracting took the same again on the receiving machine. Fine for a one-off, tedious when you need to do it weekly, at which point the convert-to-NTFS path wins on every dimension except device compatibility.

#Cloud Storage as a Bypass

Skip the file system entirely. Google Drive gives 15 GB free and supports individual uploads up to 5 TB on paid tiers, OneDrive includes 5 GB with any Microsoft account, and Dropbox’s free tier is 2 GB.

Upload from the source machine, download on the destination, and the file system never enters the picture. For multi-drive migrations, our walkthrough on transferring Dropbox to Google Drive covers the cloud-to-cloud path.

#Choosing Between NTFS, exFAT, and FAT32

The decision comes down to where the drive will live.

NTFS is the default for internal Windows drives for good reason. It has per-file permissions, compression, encryption, and journaling.

Microsoft’s file system overview confirms the journal uses a transaction log to avoid full-disk CHKDSK runs after a crash. The tradeoff is macOS reads NTFS but can’t write to it without paid drivers like Paragon NTFS for Mac or Tuxera.

exFAT is purpose-built for removable flash storage. No 4 GiB file cap. Native read-write on Windows, macOS 10.6.5 and newer, and Linux kernel 5.4 and newer. The Microsoft exFAT specification shows exFAT uses 64 bits to describe file size, and the format supports a cluster size up to 32 MB, which is why multi-terabyte portable SSDs ship pre-formatted this way and just work the moment you plug them in on either platform without manual reformatting.

FAT32 still has a place on drives that talk to older hardware. Car audio head units, digital photo frames, some smart TVs, and older consoles only read FAT32.

Short version: NTFS for Windows-only, exFAT for cross-platform.

#Troubleshooting a Failed Convert Command

The convert command is reliable, but there are three failure modes worth knowing. Each one has a fix that takes a couple of minutes.

Write-protected drive. Look for a physical slider switch on the side of USB sticks or SD cards. If there’s no switch, open an admin Command Prompt and run diskpart, then list disk, select disk N (replacing N with your drive number), and attributes disk clear readonly. Exit diskpart and retry the convert.

Not enough free space. The conversion needs room for the new MFT and NTFS structures. A near-full drive will fail. Delete some files until the drive is at least 15 percent free, then retry.

File system corruption. If the FAT table itself has errors, the conversion aborts. Run chkdsk E: /f first to repair the file system, then try convert again. If you’re hitting blue screens referencing NTFS itself, our walkthrough on NTFS.sys errors covers the driver-level fixes. For drives that appear corrupted at the directory level, the file or directory is corrupted and unreadable has the recovery steps.

One more thing: if the conversion finished but some files are missing afterward, stop using the drive and run a recovery tool before writing anything new. Continued writes overwrite deleted file blocks. Our guide on recovering data from an NTFS hard drive walks through free and paid options, including PhotoRec and Recuva for the common cases and disk-imaging tools for the harder ones.

#Bottom Line

Run convert E: /fs:ntfs first if the FAT32 drive has files you want to keep. It finishes in a couple of minutes and lifts the 4 GiB cap for good.

If the drive is empty, format it as NTFS for Windows-only use or exFAT for Mac and PC sharing. Only keep FAT32 when a specific device on the receiving end refuses to read anything else. Then use 7-Zip in 3900M chunks to shuttle large files across it.

#Frequently Asked Questions