A USB drive has space but rejects a large video
Free space is not the only limit on a video copy. A FAT32 destination has a per-file ceiling of about 4 GiB, so one large file can fail even when the drive has much more room overall. Check the destination filesystem and the actual file size before blaming the download or changing the media.
Open the relevant downloader · Platform tools and access limits
Identify a per-file failure rather than a full drive
Check that the video already exists as a complete local file and opens normally. Read the copy error, identify the destination volume and inspect its filesystem in the operating system's storage tools. Do not assume that every USB stick uses FAT32 or that its advertised capacity describes the maximum individual file.
Microsoft's filesystem comparison distinguishes maximum file size from volume size. That distinction explains why a collection of smaller recordings can fit while one larger recording fails. A successful small-file test does not establish that the same destination can accept your larger file. Keep the original intact while diagnosing the destination.
Choose a compatible destination without erasing a drive
A different existing volume may support the file and avoid any need to alter the current USB device. Confirm write access and free capacity there, then make and verify a copy. If the intended recipient is a television or another appliance, check its documented filesystem support as well as the computer's support.
Apple documents several filesystem choices in Disk Utility, including formats compatible with Windows. That is not a promise that every receiving appliance understands them. Reformatting is a separate storage-management task that can erase existing data. Preserve everything needed and use the device manufacturer's instructions if you deliberately choose that task; it is not a routine fix to apply blindly to an unfamiliar drive.
Keep storage compatibility separate from playback compatibility
A drive that accepts the bytes can still deliver a file the receiving player cannot decode. The filesystem controls storage organization; the video container, codecs and encoding constraints control a different part of the playback path. Changing a drive format cannot add a missing audio codec to a television.
Similarly, renaming an MP4 does not make it smaller or change its encoded content. If a smaller viewing copy is needed, use a genuine smaller available source option or an authorized external conversion workflow. Preserve the retained source and identify any derivative. Reducing bytes is a separate choice from solving the destination's filesystem limit.
Verify the chosen copy and keep the diagnostic evidence
After the transfer finishes, inspect the destination's actual size and test representative playback. Where exact preservation matters, compare algorithm-labelled checksums for the source and copied file. Eject the storage device through the supported operating-system workflow after copying completes.
If the copy still fails on a filesystem that supports its size, investigate the new error: write permissions, available space, connection or storage health can be separate causes. Keep the destination type, file size and exact message in a sanitized report. A server-side preparation budget is also separate; moving a previously completed local file does not change what the download service is allowed to prepare.
Worked example
An authorized recording larger than 4 GiB plays from the computer's internal disk but fails when copied to a roomy FAT32 stick. Several smaller videos copied successfully earlier. Those observations are consistent with a per-file limit, not proof of a damaged recording. Use a verified compatible destination and retain the original while checking the receiver's own storage and codec requirements.
Related guidance
Sources and verification
Reviewed 2026-10-08. Product behavior is limited to available source formats and provider access; it is not a promise that every public link works.