Home/How we verify

Verification method

How we verify that a file is really recovered

A file name proves nothing. A thumbnail proves little. Structure is what decides.

The short answer

We verify the file, not the hit.

File Recovery Hero judges a candidate neither by its name nor by a preview, but by its internal structure. Video and audio are additionally analysed with established media tools. Anything that cannot be fully confirmed is visibly marked .UNVERIFIED instead of being counted as a success.

01 / Signature

Step one: is this even that file type?

Every media format begins with a recognisable structure. JPEG starts with a fixed byte sequence, MP4 and MOV begin with a box structure, WAV with a RIFF header. The first step therefore checks whether the beginning of a candidate actually matches the format its extension claims.

That step alone is never sufficient. A correct beginning says nothing about whether the rest of the file is present and contiguous. This is exactly where many tools stop and report success anyway.

02 / Structure

Step two: is the file consistent with itself?

The second step reads the internal structure. For container formats that means: do the declared sizes of the individual sections match the actual file size? Do index structures point at ranges that really exist? Does the file end where its own layout says it should?

For fragmented recordings that is the decisive question. A video file whose management data sits at the end can look entirely unremarkable at the start and still break off in the middle.

03 / Decoding

Step three: can it actually be read?

For video and audio, structural checking is not always enough. Bundled media tools are therefore used to analyse containers and streams and, where needed, to actually demux and decode them. Only when the tracks can be read across the expected duration is a recording dependably confirmed.

This check costs time. It is why a clean run takes longer than a plain hit list, and it is the difference between a number in a results window and a file that genuinely opens in your editing software.

What this check does not do

A passed check states that the file is structurally complete and readable. It does not state that the content is the one you were looking for. Only a person can decide whether a clip shows the right scene, so check every important recording yourself as well.

04 / Export

Step four: the export must not break anything

  1. 1

    The export first writes to a file ending in .partial, so an interruption never leaves behind an apparently finished file.

  2. 2

    Once written completely, the destination file is checked a final time and only then given its final name.

  3. 3

    Destination file names are assigned uniquely. An existing file at the destination is never overwritten.

  4. 4

    Exporting to the source device is blocked and cannot be bypassed with a setting.

  5. 5

    Results that were not fully confirmed keep the .UNVERIFIED marking in their file name.

05 / Repair

Repair leaves the original untouched

When a damaged recording is repaired, the unmodified reconstruction is preserved. You therefore always keep the state the recovery actually found, plus the repair result. That keeps it traceable which part of the result comes from the source and which from a reconstruction.

Common questions

What exactly does the .UNVERIFIED extension mean?

It marks a result whose completeness could not be confirmed. The file may still be usable, but it has not been verified. The marking stays with the file after copying and is a technical file suffix that is not translated.

Why does a scan with verification take longer?

Because containers and streams are actually read instead of merely recognising the start of a file. That effort is the difference between a hit count and a dependable statement about completeness.

Can I rely on the verification alone?

No. Verification confirms technical readability and completeness, not content. Open important recordings fully and check picture, sound and duration yourself before you reuse the source.

Does verification write anything to my card?

Your memory card is only read. Nothing is saved to it. All verification happens on the exported copy or in memory.

Verify instead of hope.

See how the source stays protected throughout.

View the read-only principle