If a Blu-ray ISO, MKV, or MP4 will not copy to a USB drive despite enough free space, check the drive’s file system before buying a larger one or formatting it. FAT32 has a per-file limit of about 4 GiB. That limit is separate from the free space available on the volume.
For example, a hypothetical 12 GB file can fail to copy to FAT32 even with 80 GB free. These numbers illustrate the problem; they are not measurements of a disc or USB device. Microsoft’s file-system comparison lists the limit, and Buffalo’s support guide describes the resulting large-file copy failure.
Use this workflow for self-authored or authorized media you can already access. Keep the source file while diagnosing the destination.
Check three things without changing the drive
Record these details before clicking Format or Erase:
| Check | What to record | Why it matters |
|---|---|---|
| Largest individual file | Its size in bytes, not just the total folder size | One oversized file can block a copy even when the folder would fit |
| Destination volume | File system and available space | Both the per-file limit and total space must be sufficient |
| Intended reader | Computer OS or exact television/player model | The destination must support the storage format and the media inside it |
On Windows, inspect the file and destination drive in File Explorer’s Properties. On a Mac, inspect the file with Get Info and the selected volume’s information in Disk Utility. Read the information; do not start an erase operation.
An ISO is one large file. A BDMV folder contains multiple files, but a file inside that folder can still exceed FAT32’s limit. Changing the filename from .iso to .mkv does not change its size or convert its contents. See the ISO workflow if you are deciding which archive form to keep.
Choose a file system for both ends of the transfer
| Format | Large-file consideration | What to verify before choosing it |
|---|---|---|
| FAT32 | About 4 GiB per file; additional free space does not remove the limit | Every individual file must fit, and the reader must support the volume |
| exFAT | Supports files beyond FAT32’s limit | Confirm the writing computer and intended reader support it |
| NTFS | Supports files beyond FAT32’s limit | Confirm read/write support on each computer and support on any playback device |
Microsoft’s table supports the file-size distinction; it is not a compatibility list for televisions or players. For a Windows–Mac transfer, Apple documents exFAT as a shared external-disk option. That does not establish support on your television.
For a playback device, look up its exact model manual. Check file systems, partition scheme or volume-size conditions, and supported containers, video, audio and subtitles. Treat these as three separate questions:
- Can the computer copy the file onto this volume?
- Can the destination device recognize and read the volume?
- Can its player decode this particular file and its selected tracks?
Passing the first two does not establish the third. A readable USB drive is not evidence of ISO-menu playback or support for every MKV track.
Before formatting, preserve and check the existing data
Formatting or erasing the disk or volume deletes its files. Apple explicitly requires saving needed files to another volume first. A change of file system is not a harmless playback setting.
Copy the existing USB contents to a separate location, open needed files there, and check that the backup is complete. Confirm the correct physical drive and volume by name, capacity and contents. If you cannot make that backup, use another suitable destination rather than proceeding.
When the required reader only accepts FAT32, changing to exFAT may simply replace a copy failure with an unrecognized drive. Options include another confirmed storage/playback path, or a smaller access copy made from your authorized source while retaining the full archive. Measure the completed access copy; do not assume a chosen quality setting guarantees a particular size. Check its audio and subtitles too.
Splitting an ISO into arbitrary pieces or putting it into a ZIP archive is not a general playback solution. It adds a reconstruction or extraction step that the reader may not support.
Verify the copied file before removing any source
Compare source and destination sizes, then compare hashes with the same algorithm. On Windows, these read-only PowerShell examples calculate SHA-256; replace both example paths with your actual files:
Get-FileHash -LiteralPath 'C:\Media\home-video.mkv' -Algorithm SHA256
Get-FileHash -LiteralPath 'E:\home-video.mkv' -Algorithm SHA256Compare the returned Hash values. Microsoft’s Get-FileHash documentation explains content comparisons. A matching hash checks the copied content against that source; it does not prove playback compatibility or future drive reliability. A mismatch means the copy is not verified: keep the source and investigate before deleting anything.
Finally, try the intended playback device, including seeking and the audio/subtitle tracks you need. Keep a separate verified copy under your personal archiving plan. If total capacity is also a problem, use the storage worksheet to budget the archive, access copies and independent backup separately.
If the file system is already suitable
Do not assume every failed transfer is a FAT32 problem. Record the exact error, check destination free space and write access, and determine whether other files fail too. Preserve the source and existing USB contents before following device-specific diagnostics. Reformatting without identifying the failure can erase useful data while leaving the original problem unresolved.