Video · exFAT camera card
H.264 MP4: find after an import failure
Where are H.264 clips in an MP4 container after a failed import?
Short answer
First search the import destination, trash and editing-project folders by clip name. A move that failed can leave MP4 copies at the target that stop early or have 0 bytes. Compare sizes with the source; if clips are gone from the card as well, stop using it and scan it read-only.
The situation
H.264 clips in an MP4 container is incomplete at the destination and no longer appears reliably on the source.
Nothing here says the footage is gone yet. A failed import leaves two places to check: a destination that may hold half-written copies, and a card whose clips were deleted after a transfer that never finished properly. Look at both before touching the card.
01 / Diagnose
Work out what actually disappeared
An import is several operations in a row: copy, verify, catalog, then optionally delete the originals. If it breaks between them you can end up with MP4 files at the target that are zero bytes or stop mid-scene, while the card has already been cleared. The H.264 data itself is rarely the problem.
Move, rename, catalog and delete-after-import steps can fail at different moments and leave source and destination in different states. For H.264 MP4, this matters because ISO-BMFF boxes and an H.264 stream must agree on offsets, timing and length
Check the last known path, trash and backups without writing to the original device.
02 / Protect the source
Preserve the best recovery chance
- 1
Leave the card in the reader but stop writing to it, and stop the import software from retrying automatically while you look around.
- 2
Search the destination volume, the trash and your editing project's media folder for the clip names, then compare file sizes against the card.
- 3
If the originals really are missing on both sides, scan the card read-only instead of importing again, or work from an image of it.
- 4
Export recovered clips to a drive that is not the import target, and only then repeat the transfer with the card write-protected.
Do not start the same import a second time over the top of the broken one; a half-copied MP4 that gets overwritten again loses even the part that survived. Emptying the trash or letting the software delete originals now makes the source unrecoverable too.
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 destination is an APFS or HFS+ disk, File Recovery Hero cannot read it; it handles exFAT, NTFS and FAT16/FAT32 plus uncompressed images, so use it on the camera card and recover the destination side with the trash, a backup or a snapshot.
04 / Verify
Check the recovered content, not just its name
Compare byte counts first: a good copy matches the size on the card exactly. Then play the clip to the end and check resolution and frame rate against the camera setting. A file that opens but stops after a few seconds is a truncated transfer, not a recovery.
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 camera card be recovered in this situation?+
Nothing here says the footage is gone yet. A failed import leaves two places to check: a destination that may hold half-written copies, and a card whose clips were deleted after a transfer that never finished properly. Look at both before touching the card. The result still depends on what remains readable on the source.
What should I avoid before scanning?+
Do not start the same import a second time over the top of the broken one; a half-copied MP4 that gets overwritten again loses even the part that survived.
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?+
Compare byte counts first: a good copy matches the size on the card exactly.