jpeg.id
  1. jpeg.id
  2. C2PA Validation Statuses

Published 31 July 2026 · jpeg.id

Integrity · trust · unknowns

Four statuses. No fake certainty.

jpeg.id reports exactly what C2PA validation establishes: trusted, signer unrecognized, invalid, or absent.

Check an image Learn C2PA basics

The four Content Credential results

  1. Trusted
    The credential integrity and asset binding pass. The signer chains to the bundled official trust snapshot. This establishes a trusted signed claim—not the objective truth of every claim or the depicted event.
  2. Signer unrecognized
    Credential integrity and asset binding pass, but jpeg.id cannot establish the signer through its bundled trust snapshot. A test, private, expired, or simply unknown certificate can produce this result.
  3. Invalid
    A hard validation check failed—for example signature integrity or the binding between the credential and containing asset. Read the technical reasons before drawing conclusions about how the failure occurred.
  4. Absent
    The supported image parsed, but no supported embedded credential was found. The file may never have had one, or a later transformation may have removed it.

Integrity and trust answer different questions

Signature validity asks whether a signed claim has maintained its cryptographic integrity. Signer trust asks whether the verifier recognizes the certificate chain under a particular trust policy. A valid signature from an unrecognized signer is not the same as a broken signature, so jpeg.id gives it a separate status.

Timestamp trust is also reported separately. A timestamp can help establish when a credential existed, subject to the timestamp authority and validation result. It does not establish when the depicted event occurred unless an independently trusted workflow justifies that inference.

Why “absent” means unknown

C2PA adoption is not universal, and embedded data can be removed. Re-encoding, screenshots, messaging systems, publishing pipelines, or deliberate stripping may produce a file without its earlier credential. Conversely, merely attaching a credential does not make an image truthful.

No real/fake or human/AI shortcut

Creation-method declarations are displayed when present, but they never change validation status. jpeg.id does not infer AI generation from missing evidence or calculate a probability from pixels.

Use technical reasons for context

Every completed report retains normalized validation reasons and a bounded raw manifest view. These details can explain which check failed or which ingredient produced a warning. Ingredient failures do not automatically override the status of the containing asset.

See how jpeg.id normalizes evidence or start with the step-by-step credential checker guide.