File Doctor

Check what is wrong with a file before guessing.

Inspect one selected file for readable facts, known format clues, basic validation, integrity evidence, and receipt relationships — without changing the source.

Inspection model · named checks, not a universal verdict
Selected fileSource remains read-only
INSPECT
Readability
Named check
Format signature
Compared
Basic structure
Where supported
Receipt evidence
When a candidate exists

Check it before guessing

A finding is strongest when its test is named.

File Doctor uses bounded local checks. A PDF end marker, an image dimension, a ZIP container check, or a format signature can support a specific conclusion — never a blanket promise about the file.

CheckQuestionBoundary
ReadableCan the selected file be opened for the named checks?File access
IdentityDo known format signatures agree with the extension?Format clues
StructureDo supported basic checks find partial markers or malformed structure?Named validation
IntegrityWhat hash can be recorded, and does matching receipt evidence exist?Evidence

Evidence boundary

Know what the inspection establishes — and what it leaves open.

What it can know
Readability, file metadata, known signatures, named structural checks, a local hash, and a matching receipt candidate where supported.
What it cannot know
Whether every application can open the file, whether unknown content is safe, or whether damaged information can be reconstructed.
What it changes
Nothing in the selected source. Inspection is read-only; generated health reports are separate output.

A safer next decision

The report should reduce uncertainty, not manufacture an answer.

A readable file with the wrong format may have a supported conversion path. A partial or structurally inconsistent file may need a new source copy or its originating application instead.

Check whether a supported conversion profile fits

Continue with the evidence

Choose the next action the findings actually support.

Explore supported format conversion when compatibility is the problem, or return to the Product map for another workflow.