
An ExifTool validation warning does not by itself mean that a photograph's visible pixels are corrupt. Validation can identify metadata-structure issues; it is not a universal image decoder or a certificate that every pixel and application workflow is sound. Keep the exact diagnostic and separate it from what the image actually does.
Request the diagnostics together
For a read-only first pass on a local file, use:
exiftool -validate -warning -error -a sample.jpg
The -a option matters because several warnings can share the same tag name. Without it, an apparently short report may omit additional messages.
ExifTool FAQ 25 explicitly limits the validator's role and describes its main usefulness for JPEG and TIFF metadata. A clean result from this request therefore is not proof that an unfamiliar RAW decoder, online uploader or printer will accept the file.
Save the exact message, file type and ExifTool version. A report that says only “validation failed” discards the detail needed to distinguish a questionable metadata entry from a serious read error.
Classify what failed
Use three separate observations rather than one damaged/not-damaged label:
| Observation | What it establishes |
|---|---|
| ExifTool reports a metadata warning | That diagnostic occurred on this file with this version |
| An image application cannot decode the file | That decoding route failed; its reason still needs investigation |
| A file differs from an independently preserved copy | The copies differ; the changed region and cause remain to be identified |
These are proposed diagnostic categories, not results from a tested image. A file can display normally while containing malformed metadata. Conversely, a blank metadata-warning list cannot rule out a visual defect or incomplete transfer.
Open a separate working copy in an appropriate decoder and check the visible region relevant to the reported problem. If a saved reference exists, compare the same image area and dimensions. Do not create a “repaired original” by repeatedly resaving the only source.
Do not silence the message before understanding it
The -m option can ignore minor errors in some operations. It is not a repair procedure and should not be the automatic next step. First identify the specific diagnostic in the current documentation or request qualified help with the precise message.
If the complaint concerns a field value, determine its group and meaning before changing it. A catalog can also disagree with a file without either file being structurally corrupt; metadata conflict resolution addresses that different problem.
Define the evidence needed for the next action
For a metadata correction, require a known intended value and a verified copy on which to rehearse it. For a transfer problem, seek an intact source copy. For a decoder failure, record the decoder, version and file type instead of assuming every metadata warning explains it.
A useful support package contains the exact diagnostics and a permitted sample, not private photographs posted indiscriminately. If the problem involves a RAW handoff, include the relevant sidecars and rendered reference when sharing is authorized.
Close the investigation with a narrow statement: for example, “the specified warning no longer appears on the corrected copy, and this decoder opens it.” Do not upgrade that observation to “the file is guaranteed uncorrupted.”
Related tasks
- Lightroom Metadata Conflict: Keep the Disk or Catalog Version?
- Why Does My RAW Photo Lose Its Edits on Another Computer?
Sources and scope
- ExifTool FAQ: Grouped duplicate-tag inspection, metadata character encodings, CSV exchange and validation limits are documented; validation is not a general image-repair guarantee.
- Extra Tags: TestName is a dry-run rename tag. Validate and Warning are generated diagnostic tags, and -a is needed to see duplicate warnings.
Documentation-based guidance researched on 23 October 2026 (Asia/Shanghai). Commands and acceptance procedures are proposed examples, not reported hands-on tests. Official ExifTool documentation was readable through search-indexed page text; a direct application-documentation fetch returned HTTP 403. Historical official-forum examples, where cited, demonstrate specific questions rather than current demand frequency. ExifTool version and file-format support must be checked on the receiving system.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: 85 LENS (Ngô Hoàng Auth) / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.