EXIF is closer to a label
EXIF stores camera model, exposure, GPS, date, orientation and sometimes software. XMP and IPTC add descriptions, authorship and workflow fields. Most values can be rewritten without built-in proof of who changed them, so a traditional cleaner looks for known sections and removes them.
That is useful for privacy but weak evidence of provenance. A capture date can be accurate, wrong or edited. Screenshots, messenger downloads and genuine photographs can all have no EXIF at all.
C2PA is closer to a sealed log
A C2PA manifest carries a claim: assertions about content that may include editing actions, ingredients, thumbnails and the application involved. The claim is digitally signed, and a hard binding connects it to the asset through cryptographic hashes or another permitted mechanism.
A validator checks separate properties: claim signature, asset binding, algorithm support and signer credential trust. A green result therefore means the technical claim validated — not that every depicted event is true.
Why an EXIF-only tool misses the point
C2PA is not simply another familiar EXIF field. Different media containers use appropriate structures, including JUMBF, and a history may reference ingredients and other manifests. A tool that only understands classic JPEG APP1 data can report empty EXIF while failing to explain available Content Credentials.
- You need a container parser, not a search for two text tags.
- You need cryptographic validation, not just a JSON viewer.
- Absent, unsupported, invalid and valid are different outcomes.
What cleaning actually does
A full pixel re-encode can create a new file without the attached manifest, and a specialist tool may remove a known block. The result is missing history, not a corrected signature. To produce an honest new derivative, software must create a new claim, describe the original as an ingredient and sign with its own credential.
That is why inspection comes first. Blind cleaning may remove GPS for good privacy reasons while also discarding useful provenance evidence.
FAQ: does an ordinary EXIF cleaner remove C2PA?
Not necessarily. A utility that only deletes JPEG APP1/EXIF may never recognize C2PA in APP11/JUMBF, a PNG caBX chunk or another container structure. A full image re-export may drop the manifest as a side effect, but that is different from finding, validating and selectively removing the provenance layer.
Inspect the result. “C2PA not found” means only that no accessible manifest was found in the new copy; it does not prove human authorship or create a replacement signed history.