Content credentials, a manifest with a signature
Content credentials are a signed record stored alongside an asset rather than inside it. They can carry structure, they can be verified against a key, and they disappear silently whenever something rewrites the file. As of 2026-09-12.
| Property | Consequence for a reader |
|---|---|
| Stored beside the content | Nothing about the picture or sound changes |
| Signed | Tampering is detectable; the signer is named |
| Structured | Can hold a chain rather than a single claim |
| Optional to copy | Any rebuild that skips it drops the whole record |
Inclusion rule. Properties common to attached, signed provenance records as their specifications describe them. Order. From the defining property to the practical consequence.
1The strongest available mark, and the most fragile
Because the record sits outside the content, it can be long, structured and signed. Because it sits outside the content, anything that builds a new container without copying it loses everything it held.
Those two sentences are the same fact read twice. No amount of engineering reconciles them, which is why some products apply a second mechanism inside the content as well.
2What arrives is not what was written
Platforms re-encode on upload and generate derivatives afterwards. Each step is a chance for the record to be left behind, and nothing notifies anybody when it is.
So a claim that outputs carry credentials describes what leaves a vendor. Whether an audience's copy carries them is a property of the route, and routes are testable in an afternoon.
3Reading one is easy when a public reader exists
Because the format is published, anybody can implement a reader, and several parties have. That is what makes the mechanism useful to somebody with no relationship to whoever made the file.
A vendor naming a public place to inspect a record is doing something small and consequential: turning a stated property into a check a person can attempt in a minute.
4Scope is the field to look for
A vendor can attach credentials to everything, to one product area, or from one version onward. Each of those is a different claim, and only the narrow ones can be matched against a reader's own files.
A headline sentence rarely carries the scope. It is usually one clause further down, and it is the clause that decides whether the claim is usable at all.
5Published material behind this entry
A term in this record: what it means, and what the published material says about it, each figure read on 2026-09-12. Related: Watermark, Deepfake.