Free space and file size answer different questions
A drive can have enough total free space and still reject one large file. Filesystems have their own limits for individual files. FAT32's approximately four-gibibyte single-file boundary is a common example; the maximum is just under that boundary. A copy failure near this size therefore deserves a filesystem check before anyone deletes unrelated media or assumes the video is corrupt.
Inspect the source file's size and the destination filesystem through the operating system's normal file or drive information. Keep those observations separate from the drive's advertised capacity. This article concerns media you are authorised to store locally. It does not imply that a streaming subscription includes downloads or that a provider permits saving its streams.
Work through an explicit example
Suppose a creator exports a five-gibibyte video they own and tries to copy it onto a FAT32 drive with twenty gibibytes free. Deleting another small file does not address the individual-file boundary. The correct next question is which supported destination format can hold the file and still be read by the intended playback device.
Now change the hypothetical file to one gibibyte. Its failure would not be explained by the same size boundary alone. The drive might be unavailable, write-protected, damaged or subject to another restriction. This contrast matters: recognising a familiar filesystem limit is useful, but using it to explain every failed copy would be another unsupported diagnosis.
Do not format before checking the reader
A computer's ability to write exFAT or another filesystem does not guarantee that a particular television, set-top box or media player can read it. Consult the destination device's exact model manual and any stated capacity or partition requirements. A brand-level compatibility claim is too broad. The intended reader, not just the preparation computer, must support the chosen arrangement.
Formatting is destructive to existing files on the selected volume. Back up the drive's contents and verify the backup before considering it. Check the selected drive carefully, especially when several removable devices are attached. If you only need to test compatibility, use a spare empty drive that can be safely prepared rather than experimenting on the only copy of important files.
Test both the copy and playback
After using a supported storage arrangement, verify the copied file and test it on the intended device. A completed copy proves that bytes were written; it does not prove the media container, audio codec or video profile can be decoded there. Conversely, a file listed in the device's browser may still fail at playback. Record these as separate stages.
Keep a short preparation note with the filesystem, device model and authorised sample used. That makes future transfers more predictable and avoids repeating a risky format operation. The useful conclusion is specific: this file fits the filesystem and plays on this documented setup. It is not a general claim that every USB drive or large video will work on every television.
Questions answered
Why does deleting files not always fix the copy error?
Total free space does not remove a filesystem's individual-file limit. Check both the file size and destination filesystem.
Should I immediately format the drive as exFAT?
First verify that the playback device supports it, then back up existing files. Formatting removes data from the selected volume.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.