A USB drive can show tens or hundreds of gigabytes of free space and still refuse to accept a single large video, archive, or backup file. The error may say that the file is too large for the destination even though the drive clearly has enough room.
The apparent contradiction comes from confusing two different limits: how much data the drive can hold in total and how large one individual file is allowed to be. The second limit is controlled largely by the drive’s file system, not by its remaining capacity.
Understanding that distinction helps you diagnose the problem without deleting files unnecessarily or assuming the USB drive is defective.
Free space and maximum file size are different limits
Think of storage capacity as the total amount of room available on a drive. If a 64 GB drive has 30 GB free, it can potentially store another 30 GB of data, allowing for the way capacity is measured and space is allocated.
But the drive also has a file system. A file system is the structure that an operating system uses to organise files and directories and keep track of where their data is stored. Common file systems on removable storage include FAT32 and exFAT. Other file systems are also used, depending on the device and operating system.
A file system has rules and limits of its own. One of those rules can be the maximum size of a single file.
This means a drive may have enough total free space for a file while its file system cannot represent a file that large. Adding up the free gigabytes does not remove that structural limit.
FAT32 is a common reason large files fail to copy
FAT32 is an older file system that remains useful because many kinds of devices understand it. Its important limitation for modern large files is that one file cannot reach 4 GiB. More precisely, the maximum is one byte less than 4 GiB, or 4,294,967,295 bytes.
That limit applies to each individual file, not to the total amount of data stored on the drive.
For example, imagine a FAT32 USB drive with 20 GB of free space. Copying twenty separate 500 MB files can fit within that free capacity because every file is comfortably below the per-file limit. Trying to copy one 6 GB video can fail even though the same drive has far more than 6 GB available.
This is why deleting more files often does not solve this particular error. The problem is not a shortage of free space.
You may also see slightly different numbers in software because storage sizes can be displayed using decimal gigabytes or binary units such as gibibytes. The practical point is unchanged: FAT32 cannot store one file of 4 GiB or more.
exFAT removes that everyday FAT32 file-size barrier
exFAT was designed for removable storage and supports files far larger than the FAT32 limit. For ordinary consumer storage, its theoretical file-size ceiling is so high that device capacity and implementation limits become relevant long before the FAT32-style 4 GiB barrier does.
That makes exFAT useful when removable storage needs to hold large videos, disk images, archives, or other files that FAT32 cannot store.
There is a trade-off, however: a file system is useful only if the devices that need the drive can read it.
Modern computers and many current consumer devices support exFAT, but support should not be assumed for every television, car stereo, camera, game device, printer, media player, or older operating system. Some products accept only particular file systems or partition layouts on removable media.
The right format therefore depends on where the drive will be used, not simply on which file system has the larger limits.
The same idea applies to memory cards
Memory cards use file systems too. The SD standards provide a useful example of why the format matters.
SDHC cards, which cover capacities above 2 GB through 32 GB in the SD standard, use FAT32. SDXC cards, covering capacities above 32 GB through 2 TB, use exFAT. The newer SDUC standard also uses exFAT.
A device designed for a particular card standard may have expectations about both capacity and file system. Reformatting a card to something a computer understands does not guarantee that a camera or other appliance will accept it.
For cameras and similar devices, the manufacturer’s recommended format and any built-in formatting function are usually the appropriate starting points.
Check the file system before changing anything
If a large file will not copy despite ample free space, first compare the file’s size with the available space. If the free space is genuinely smaller than the file, the explanation is simple: more capacity is needed.
If there is enough free space, check which file system the destination uses. Operating systems normally show this information in the drive’s properties, information panel, disk-management utility, or a similar storage view. Exact labels vary between platforms and versions.
If the destination is FAT32 and the file is 4 GiB or larger, you have identified a direct explanation for the failure.
If the drive uses another file system, do not assume the same diagnosis. Copy failures can also result from a damaged file system, a read-only destination, connection problems, device-specific restrictions, filename or path rules, or errors in the storage hardware. The wording of the error and the context matter.
Reformatting changes the file system, but it normally erases the drive
Formatting prepares a storage volume with a file system. Reformatting a USB drive from FAT32 to exFAT can therefore remove the FAT32 per-file limit.
But formatting is not a harmless setting change. Standard formatting operations normally make the existing files on that volume unavailable, so anything important should be copied elsewhere and verified before you proceed.
Before reformatting, also check the requirements of every important device that will use the drive. A USB drive intended only for current computers has different compatibility needs from one that must also work in an older television or an embedded device.
If compatibility requires FAT32, changing the file system may simply exchange one problem for another.
Splitting a file can be an alternative
Sometimes the destination must remain FAT32. In that case, software can divide some kinds of large data into multiple smaller files, each below the file-system limit.
Archive tools, for example, can create multi-part archives. Some backup applications can also split their output into pieces. The receiving computer then needs suitable software to reconstruct or use those parts.
This approach is not equivalent to copying the original large file intact. A television or camera expecting one normal video file, for example, will not automatically understand a set of archive pieces. Splitting is useful only when the software at the destination knows how to handle the result.
For media, another option may be to create a smaller version through proper conversion or compression, but that changes the file’s data and can affect quality. Simply renaming the file or changing its extension does not reduce its size or bypass a file-system limit.
A bigger drive does not automatically solve the problem
Buying a higher-capacity USB drive can appear to fix the issue if the new drive happens to come formatted with a file system that supports larger files. But capacity itself is not what removed the limit.
A very large drive formatted as FAT32 still has FAT32’s per-file restriction. Conversely, a smaller drive using a suitable file system can store one large file as long as the file fits within its available capacity and the relevant file-system limits.
Keeping capacity and file-system rules separate is the useful mental model.
The practical takeaway
When a drive says a file is too large, start with two questions: Is there enough total free space? and Can this file system store one file of this size?
If the drive is FAT32, a file of 4 GiB or more exceeds its single-file limit regardless of how much empty space remains. A different file system such as exFAT can support much larger files, but changing formats must be weighed against device compatibility and the fact that formatting normally erases existing data.
Once you know which limit you are dealing with, the error stops being mysterious. Free space tells you how much more data can fit overall; the file system determines how that data is allowed to be organised.