A Content Credentials validator confirms a label exists, which is not the same as confirming a chain.

C2PA is the technical standard: a manifest format, assertions, hashes and signatures. Content Credentials is the name Adobe uses for the implementation, now adopted by a coalition of platforms and camera makers.

A validator is the tool that reads a manifest and reports what it says. The strength of the report depends entirely on how far the validation goes, and that distance is where most confusion lives.

Level one is presence: a manifest container exists in the file. Any byte-level scan can establish this, and it is what most browser tools report.

Level two is integrity: the manifest parses, the asset hash matches the recorded hash, and the signature is intact. This needs the manifest actually parsed rather than detected.

Level three is trust: the signing certificate chains to a party on a trust list you accept, and the assertions are within what that party is trusted to claim.

A check that reports presence and calls itself validated is the failure mode to avoid. Say which level you reached.

Presence checks are not useless. Used as an inventory across a delivery, they show which assets carry provenance and which were stripped somewhere in the pipeline.

Resizing, screenshotting, converting format and most social uploads drop embedded metadata. This is normal, not malicious, and it means absence cannot be read as concealment.

A workable policy therefore cannot run on labels alone. It needs a record kept outside the file: hash at export, manifest retained, date, tool, and the name of whoever handled it.

Where a supplier or studio provides signed output, ask them to retain the manifest alongside the delivered asset. It is the only way the label survives the pipeline.

Describe the artefact, not the conclusion. A manifest is present, it names this tool, the file is this size, and these markers are absent.

Then state the level reached, in plain words: presence checked, integrity not validated, trust chain not evaluated. That single sentence prevents most of the misreading that provenance reports attract.

For anything that turns on authenticity, hand the file and the report to a reviewer who can pursue the trust chain with the tools that do it properly.

Signing is moving into capture devices and production tools, and platforms are being pushed to preserve manifests rather than strip them. When that lands, presence becomes common and trust becomes the discriminating question.

Until then, treat a label as one input. The defensible position is a workflow that signs early, retains the original and states its level of verification without inflating it.