Recovery methods · exFAT memory card
exFAT metadata analysis: start safely
How do I start exFAT metadata analysis without changing the source?
Short answer
First confirm the card really uses exFAT, not FAT32: SDXC cards over 32 GB ship with exFAT, smaller SDHC cards usually with FAT32. Check the file system in Disk Utility or the drive properties without running First Aid or error checking, then prepare a different physical drive as the only export destination.
The situation
The source and destination for exFAT metadata analysis have not yet been safely separated.
This approach reads the directory structures the file system itself wrote, so it only makes sense on a volume that really is exFAT. Before touching anything, the file system has to be confirmed, because the same card size can carry exFAT from the factory or FAT32 after a reformat.
01 / Diagnose
Work out what actually disappeared
Capacity gives a strong hint but no certainty. SDXC cards above 32 GB ship with exFAT, SDHC cards from 4 to 32 GB usually with FAT32, and a camera or computer can change that at any time. The distinction matters because FAT32 stops single files at 4 GB while exFAT does not, which shapes how long recordings were stored.
Selecting the wrong device or export path can make a sound method destructive. For exFAT metadata analysis, this matters because deleted entry sets can retain names, sizes and cluster positions
Check the last known path, trash and backups without writing to the original device.
02 / Protect the source
Preserve the best recovery chance
- 1
Connect the card and read the reported file system in Disk Utility or in the drive properties without starting First Aid or error checking.
- 2
Note capacity, file system and the model of the reader, and check whether a microSD adapter sits between card and computer.
- 3
Prepare a second physical drive as the export target, then open the card read-only so no repair prompt can be accepted by accident.
- 4
Run the analysis across the whole volume and keep the proposed names and folder paths with the exported files.
Do not accept an offer to repair the volume and do not run a check-disk pass to make the card readable first. Those tools rewrite the very directory entries this method depends on, and once they are replaced the names, sizes and positions they carried are gone.
03 / Choose the method
Match the tool to the source
For stable, readable exFAT, NTFS and FAT16/FAT32 or uncompressed IMG, DD, RAW and BIN images.
Unconfirmed exports are marked .UNVERIFIED.
If the volume turns out to be APFS, HFS+ or ext4, File Recovery Hero stops there, since it reads exFAT, NTFS and FAT16/FAT32 only. A card that reads unreliably or is encrypted is also out of range, and scanning is free while export needs a licence.
04 / Verify
Check the recovered content, not just its name
You started correctly when the card is reported as exFAT, the analysis lists filenames in a recognisable camera pattern with plausible sizes, and the export path lies on a different device. Free space on the card should be identical before and after the run.
Keep the source until two verified copies exist. One working preview is not enough.
Sources and technical references
FAQ
Questions about this recovery case
Can exFAT memory card be recovered in this situation?+
This approach reads the directory structures the file system itself wrote, so it only makes sense on a volume that really is exFAT. Before touching anything, the file system has to be confirmed, because the same card size can carry exFAT from the factory or FAT32 after a reformat. The result still depends on what remains readable on the source.
What should I avoid before scanning?+
Do not accept an offer to repair the volume and do not run a check-disk pass to make the card readable first.
Does scanning write to my memory card?+
Your memory card is only read. Nothing is saved to it.
How do I know whether the result is complete?+
You started correctly when the card is reported as exFAT, the analysis lists filenames in a recognisable camera pattern with plausible sizes, and the export path lies on a different device.