Read the provenance embedded in a file
Content Credentials use the C2PA standard to carry signed claims about an asset’s origin and changes. This reader uses the official Content Authenticity Initiative web SDK to inspect embedded manifests, creator assertions, edit actions, ingredients, signature details and thumbnail metadata.
The SDK performs local signature and integrity checks. This page reports its validation details without fetching external manifests, trust lists or certificate revocation information. Publisher certificate trust is therefore not established here. A manifest can describe only part of a file’s history.
What a result can tell you
A missing manifest does not establish whether a file was created with AI. Credentials can be absent, removed, unsupported or stored remotely. A present signature can help bind claims to a file, but it cannot establish that the depicted event happened or that every claim is true. Read the reported validation details and compare them with other evidence.