Recovery methods · separate export drive
recovered-media validation: start safely
How do I start recovered-media validation without changing the source?
Short answer
First keep the original card or image unchanged and validate only exported copies on a separate drive. Opening a recovered clip in an editor can create caches, sidecars or rewritten metadata, so work on duplicates. Identify source and export drive by model and capacity, and reformat nothing until the review is finished.
The situation
The source and destination for recovered-media validation have not yet been safely separated.
Checking recovered material is itself an operation that writes. Editors build caches, cameras update databases, and preview tools create sidecar files, so the review has to happen on exported copies while the card or image stays sealed as the reference you can return to.
01 / Diagnose
Work out what actually disappeared
The risk sits in habit. Dropping a recovered clip into a timeline creates render and peak files next to it, opening a folder lets the system write thumbnail data, and putting the card back into the camera can trigger a database rebuild. None of that is malicious, but all of it changes the state you may still need.
Selecting the wrong device or export path can make a sound method destructive. For recovered-media validation, this matters because reliable validation combines size, container, streams, duration and production context
Check the last known path, trash and backups without writing to the original device.
02 / Protect the source
Preserve the best recovery chance
- 1
Disconnect the source card or park the image file on a drive you do not touch during the review.
- 2
Identify the export drive by model and capacity, and place the recovered files in a folder reserved for this review.
- 3
Duplicate that folder once, so the editor works on the copy while an untouched set remains for comparison.
- 4
Check the copies with a player and an information tool first, and only then load anything into an editing project.
Do not reformat the card because the export looks complete, and do not let an editing application write its caches next to the only copy. A review can fail halfway and send you back to the source, which is worthless once it has been reused or overwritten.
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.
File Recovery Hero exports copies and marks unconfirmed ones as .UNVERIFIED; it plays nothing back and repairs nothing, so the review needs a player, an information tool and your own shot notes. It also cannot keep a failing card alive while you work.
04 / Verify
Check the recovered content, not just its name
The setup is safe when source and review folder live on different devices, the source shows the same used space as before the export, and the untouched duplicate still matches the working copy in file count and byte size. Nothing new should appear inside the source folders.
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 separate export drive be recovered in this situation?+
Checking recovered material is itself an operation that writes. Editors build caches, cameras update databases, and preview tools create sidecar files, so the review has to happen on exported copies while the card or image stays sealed as the reference you can return to. The result still depends on what remains readable on the source.
What should I avoid before scanning?+
Do not reformat the card because the export looks complete, and do not let an editing application write its caches next to the only copy.
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?+
The setup is safe when source and review folder live on different devices, the source shows the same used space as before the export, and the untouched duplicate still matches the working copy in file count and byte size.