exFAT file corruption on Mac: why it happens and how to prevent it
exFAT has no journal and doesn't checksum file contents, so an interrupted write or a bad transfer can leave a file damaged with no error message. On a Mac, the usual causes are unplugging without ejecting, unreliable cables and hubs, and moving drives between computers mid-write. Disk Utility's First Aid repairs the file system but not damaged files. To catch those, verify each copy against the original.
A familiar story
VerifiedCopy exists because of exactly this problem. I kept copying videos to an exFAT drive on my Mac, ejecting it safely, and plugging it into the TV, only to find some of them corrupted. macOS said every copy succeeded. Nothing warned me. The only way to know was to read the files back and compare them with the originals, so I built a tool that does that.
Why exFAT is more fragile than APFS
exFAT is popular because Macs and Windows PCs can both read and write it. That compatibility comes at a cost. According to Microsoft's exFAT specification:
- There's no journal. Journaled file systems record changes before making them so they can recover cleanly from a crash. exFAT only sets a "volume dirty" flag and relies on a repair tool to sort out inconsistencies afterwards.
- There's one allocation table. A standard exFAT volume keeps a single File Allocation Table. The second copy exists only in TexFAT, a variant used by Windows CE.
- File contents aren't checksummed. exFAT checksums its own structures (the boot region, directory entries, and the up-case table) but not the data inside your files. If a file's bytes are stored wrongly, the file system has no way to notice.
So if a write is interrupted, or bad data reaches the drive, exFAT will often report nothing wrong. You find out when the file won't open.
Common causes of exFAT corruption on Mac
- Unplugging without ejecting, or the Mac sleeping or losing power with the drive mounted. Writes still in progress, or still in the cache, never make it to the drive.
- Flaky connections. Worn cables, unpowered USB hubs, and cheap adapters can drop out briefly during long transfers.
- Moving the drive between Mac and Windows without ejecting on both sides, so each system finds the volume marked dirty.
- Failing or counterfeit flash. Old USB sticks and fake-capacity SD cards can accept writes and then return different data.
- Large files and long transfers, which simply give the problems above more time to happen.
Symptoms
- Videos that freeze, glitch, or stop playing partway through
- Photos with grey bands or blocks, or that won't open
- Files that show the right size but contain garbage, or show as zero bytes
- Windows offering to "Scan and fix" the drive when you plug it in
- The drive failing to mount, or mounting read-only
How to repair an exFAT drive on Mac
Back up anything you can still read first. Then repair the file system:
- Open Disk Utility and select the exFAT volume in the sidebar.
- Click First Aid, then Run. (Apple's guide)
- If it reports errors it couldn't fix, try again from Terminal with
diskutil repairVolume /Volumes/NAME, or on a Windows PC withchkdsk X: /f.
How to fix damaged files
If you still have the originals, the fix is to copy the damaged files again and check the new copies. To find which files are damaged, compare the drive with the originals using diff -rq or checksums (see how to verify a file copy on Mac).
VerifiedCopy can do this in one pass: Verify & Repair scans the exFAT copy against the known-good originals, chunk by chunk, and rewrites only the chunks that don't match. For a large video with a few bad sectors, that's much faster than copying everything again.
How to prevent exFAT corruption
- Always eject before unplugging, on both Mac and Windows, and wait for the drive to disappear from the sidebar.
- Connect directly to the Mac for big transfers instead of through a hub, and replace cables that disconnect when bumped.
- Format the drive on the Mac in Disk Utility (exFAT, GUID Partition Map) if you see repeated problems after using it elsewhere.
- Don't use exFAT if you don't need it. If the drive only ever connects to Macs, use APFS.
- Verify every copy. This is the only step that catches problems the file system can't see. VerifiedCopy re-reads each copy from the exFAT destination and compares SHA-256 hashes with the source before you hand the drive over.
exFAT vs APFS vs Mac OS Extended vs NTFS
| Format | Mac | Windows | Crash protection | Best for |
|---|---|---|---|---|
| APFS | Read/write | No (without extra software) | Copy-on-write metadata | Mac-only drives and SSDs |
| Mac OS Extended | Read/write | No (without extra software) | Journaled | Older Macs, spinning backup disks |
| exFAT | Read/write | Read/write | None | Drives shared with Windows, cameras, TVs |
| NTFS | Read-only | Read/write | Journaled | Windows-only drives |
| FAT32 | Read/write | Read/write | None | Small drives; files under 4 GB only |
If a drive has to work with both Mac and Windows, exFAT is usually the only practical choice. That's fine, as long as you eject properly and verify what you copy.
Frequently asked questions
Is exFAT bad for Mac?
No, but it's less forgiving than APFS. exFAT has no journal and no checksums on file contents, so interrupted or bad writes are more likely to go unnoticed. It's the right choice for drives shared with Windows; use APFS for Mac-only drives.
Why does Windows ask to scan and fix my exFAT drive?
Windows found the volume's dirty flag set, usually because the drive was unplugged from the Mac without ejecting or while a write was still in progress. Let it scan, then check that your important files still match their originals.
Will First Aid fix my corrupted videos?
No. First Aid repairs the file system's structures so the drive mounts and files are listed correctly. It can't restore bytes inside a file that were damaged during the copy. Copy those files again from the originals and verify them.
What are the ._ files on my exFAT drive?
They're AppleDouble files that macOS creates on non-Mac file systems to store extra metadata such as Finder tags. They aren't corruption. You can merge and remove them with dot_clean /Volumes/NAME in Terminal before giving the drive to a Windows user.
How do I know if a file on exFAT is corrupted?
Compare it with the original. Run shasum -a 256 on both files; if the hashes differ, the copy is damaged. To check every file on a drive at once, use diff -rq against the source folder, or an app like VerifiedCopy.