01

Useful clues to inspect

Software, creator tool, modification date, XMP history and thumbnail mismatches can be relevant clues. Read them together with file structure and known copies rather than relying on one tag.

Key points
  • Software or creator-tool fields
  • Modify dates and timezone context
  • XMP history when present
  • Dimensions and encoding changes
  • C2PA actions when signed credentials exist
02

Why absence proves very little

A clean export may remove every software tag. A screenshot creates a new file. A social platform may rewrite the image. Someone can also edit ordinary metadata directly. No supported edit tag is therefore a neutral result.

03

Use stronger evidence when stakes are high

Keep trusted originals, compare cryptographic hashes when you have known copies, inspect signed provenance where available, and use qualified forensic review for consequential decisions.

04

Define what “edited” means first

Rotation, cropping, color correction, resizing, metadata cleaning and platform recompression all change a file. That is different from altering the depicted scene. A useful analysis states which technical change it observed instead of using one emotionally loaded label.

Even an untouched camera image may receive software or timestamp changes during import. Conversely, a carefully manipulated image can have metadata copied from another file or removed entirely.

Key points
  • File changed
  • Pixels re-encoded
  • Dimensions changed
  • Scene content altered
  • Metadata-only change
05

How the ambiguity test limits overclaiming

Each of the five patterns had more than one plausible history. The rules therefore returned workflow clue, image changed, absence only, time clue or review needed. None was converted into a probability of manipulation.

This is intentional. Percent confidence looks precise but would require a validated model, representative corpus and known ground truth. Ordinary editable metadata does not provide that foundation.

06

Use stronger evidence for consequential questions

Compare with a trusted original, examine signed provenance where present and preserve hashes. Pixel-level forensic methods may help specialists, but they also have limitations and should be interpreted by qualified practitioners.

For everyday use, metadata is excellent for explaining format, dimensions, capture settings and workflow changes. Keep the conclusion within those strengths.

What this does not prove

A metadata result describes the fields and structures that the supported parser could read. It does not, by itself, prove authenticity, intent, authorship or the truth of the visible scene.

Sources