{
  "question": "Someone sent us a photo that shows a valid C2PA Content Credential in a verify tool. What does that actually prove about the image: that it's real, who made it, whether AI was used? And what does it mean when a file has no credential at all?",
  "slug": "what-does-a-valid-c2pa-content-credential-prove-about-an-image-or-video",
  "url": "https://www.rightshold.com/answers/what-does-a-valid-c2pa-content-credential-prove-about-an-image-or-video",
  "short_answer": "Less than the badge suggests. A valid Content Credential (a C2PA manifest) proves that the provenance data and the content it's bound to haven't changed since a particular signer signed them, and tells you whose signing certificate was used. With a trusted time-stamp it also shows the signature was made while that certificate was valid. The C2PA's own explainer says Content Credentials make no judgment about whether the provenance data is true: they show it's well-formed, untampered, valid and signed by someone on a known trust list. So it doesn't prove the scene happened, it doesn't prove every edit was recorded (an edit in a tool that doesn't support C2PA leaves no entry), and it doesn't identify a person unless an identity extension was added. Only the assertions the signer created are attributed to the signer, and an AI origin shows up only if the generating tool recorded it, in the digitalSourceType field. Which signer counts as trusted depends on the checker: the official C2PA trust list comes from the conformance program that opened in June 2025, and the older Interim Trust List was frozen on January 1, 2026. A missing credential proves nothing either way: metadata can be stripped, and C2PA says files without credentials shouldn't automatically be distrusted.",
  "checklist": [
    "Check the file in a validator and read the result, not just the badge: is the manifest valid (hashes and signature match), and is the signer trusted?",
    "Look at who signed. The signer is the holder of the certificate the claim generator used, often a camera maker, an app or a platform, not necessarily the person who took the photo.",
    "Note which trust list the checker used. Content signed under the frozen Interim Trust List and content from conforming products on the official C2PA trust list must be shown differently by validators during the transition.",
    "Check for a trusted time-stamp. It lets a validator confirm the signature was made while the certificate was valid even after the certificate expires or is revoked.",
    "Read the actions and the digitalSourceType. A generative AI tool that records its use labels the content as AI-generated there; if the field is absent, that only means it wasn't recorded.",
    "Separate assertions the signer made (created_assertions) from ones it only gathered (gathered_assertions). Only the first set is attributed to the signer.",
    "Treat ingredient history with care. An ingredient's credential was checked when it was added; the original ingredient file usually isn't included, so you can't re-verify it yourself.",
    "If there's no credential, don't conclude the file is fake. Look for a durable credential through a watermark or fingerprint lookup where the tool supports it, ask the sender for the original file, and use other checks."
  ],
  "sections": [
    {
      "heading": "What a valid credential tells you",
      "points": [
        "A Content Credential, which the specification calls a C2PA manifest, is a set of assertions about an asset (how it was created, what actions were applied, whether AI was involved) that are hashed, bound to the content and digitally signed with an X.509 certificate. The explainer describes the combination of cryptographic hashes such as SHA-256 and a Merkle-tree-like structure as tamper-evident: any change to the asset or the provenance data breaks the match.",
        "So a valid result means three things: the provenance data hasn't been altered, the content still matches what was signed, and the signature came from the stated certificate. If the manifest includes a time-stamp from a time-stamping authority on the C2PA TSA trust list, a validator can confirm the signature was made while the certificate was valid, without checking revocation online at the time you view it.",
        "Generative AI shows up through the digitalSourceType field on the action that created the content. That's only as complete as the generating tool's implementation: the credential records what the claim generator chose to record."
      ]
    },
    {
      "heading": "What it doesn't tell you",
      "points": [
        "The C2PA explainer says it plainly: Content Credentials do not provide value judgments about whether a given set of provenance data is true, only whether it's well-formed, free from tampering, valid and trusted. Provenance alone can't tell you whether the content is true, accurate or factual.",
        "Provenance isn't always complete. The explainer's example is a crop made in a tool that doesn't support Content Credentials: nothing records it, and if the image then goes through a supporting tool, the new signer implicitly attests to the cropped version.",
        "It isn't a person's identity. The core specification focuses on the content, not on the human or organization behind it; identity claims need an extension such as the Creator Assertions Working Group's identity assertion. And the signer is only attributed with the assertions listed in created_assertions, not those in gathered_assertions.",
        "Ingredients can't be fully re-checked. When an asset is composed from others, each ingredient's credential is validated at the time it's added and that result is recorded, because the ingredient's own data usually isn't carried along.",
        "No credential isn't evidence of fakery. Adding provenance is optional and metadata can be removed. The specification's answer to stripping is durable Content Credentials: a soft binding such as an invisible watermark or a fingerprint that lets a tool find the manifest in cloud storage, with a Soft Binding Resolution API added in version 2.2."
      ]
    },
    {
      "heading": "Which trust list the checker used",
      "points": [
        "Trust in C2PA comes from the signer's certificate. The C2PA trust list is a list of certificate authorities that issue signing certificates to generator products that passed the C2PA Conformance Program, which opened in June 2025; conforming validators must check signatures against it. Conforming products are published on the C2PA Conforming Products List, and the C2PA FAQ says certificates carry the product's assurance level.",
        "The earlier Interim Trust List was frozen on January 1, 2026: nothing is added or updated, existing certificates stay valid for legacy support, and content signed while a certificate was valid is still considered valid under the legacy model. During the transition validators may consult both lists but must distinguish between them.",
        "The Content Authenticity Initiative's documentation says the C2PA Verify tool still uses the Interim Trust List, and shows the certificate owner and signing time only when the certificate is on it. So the same file can read as a known signer in one tool and an unrecognized one in another; note which tool and list you used when you record a result."
      ]
    }
  ],
  "checks": [],
  "ask_rightshold": {
    "start": "https://www.rightshold.com/start?ref=seo",
    "mcp_endpoint": "https://www.rightshold.com/mcp",
    "ask": "Fetch the signed AI run receipt we recorded when we delivered this generated image to the client, so I can hash the file they now have and check whether it's the exact file we sent, even though its Content Credential is missing.",
    "mcp_call": {
      "tool": "verify_ai_run",
      "arguments": {
        "id": "air_<20 hex characters from the receipt id>"
      }
    },
    "also": [
      "Free, no key. Calling with {id} returns the receipt and its signature, including output_sha256 and the time it was recorded. Hash the client's file with SHA-256 and compare. Call with {receipt, signature} to confirm the receipt is on record.",
      "An identical hash means it's byte-for-byte the file you recorded, embedded credential included if you hashed the file after signing it. A different hash can be an edit, a re-encode or stripped metadata: a hash comparison can't tell those apart, unlike a C2PA soft binding.",
      "To have a receipt to check later, record each delivered file with record_ai_run (API key; hashes only), putting the manifest's hash and your signing certificate's identifier in params and keeping your own copy of params."
    ],
    "scope": "Rightshold doesn't create, read or validate C2PA manifests, isn't a C2PA conforming product or on any C2PA trust list, and isn't affiliated with the C2PA or the Content Authenticity Initiative. A Rightshold receipt is a separate dated record of a file's hash; it only matches the exact bytes. Descriptions are from the C2PA explainer and documentation as checked on November 10, 2026."
  },
  "sources": [
    {
      "title": "C2PA: C2PA and Content Credentials Explainer (specification 2.4)",
      "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html"
    },
    {
      "title": "C2PA: Content Credentials technical specification 2.2 (May 2025; Soft Binding Resolution API)",
      "url": "https://spec.c2pa.org/specifications/specifications/2.2/specs/_attachments/C2PA_Specification.pdf"
    },
    {
      "title": "C2PA: Conformance Program",
      "url": "https://c2pa.org/conformance/"
    },
    {
      "title": "C2PA: FAQ (trust list, conforming products, Interim Trust List)",
      "url": "https://c2pa.org/faqs/"
    },
    {
      "title": "C2PA: Conformance Explorer (Conforming Products List, C2PA Trust List, TSA Trust List)",
      "url": "https://spec.c2pa.org/conformance-explorer/"
    },
    {
      "title": "Content Authenticity Initiative: Trust lists",
      "url": "https://opensource.contentauthenticity.org/docs/conformance/trust-lists.md"
    },
    {
      "title": "Content Credentials: Verify tool",
      "url": "https://contentcredentials.org/verify"
    }
  ],
  "related": [
    {
      "title": "Does the EU AI Act require you to watermark AI-generated content?",
      "url": "https://www.rightshold.com/answers/does-the-eu-ai-act-require-you-to-watermark-ai-generated-content-by-december-2-2026"
    },
    {
      "title": "Does California's AI Transparency Act apply to your AI image, video or audio app?",
      "url": "https://www.rightshold.com/answers/does-californias-ai-transparency-act-apply-to-your-ai-image-video-or-audio-app"
    },
    {
      "title": "How to check that an AI agent's delivered file matches the output hash recorded for its run",
      "url": "https://www.rightshold.com/answers/how-to-check-that-an-ai-agents-delivered-file-matches-the-output-hash-recorded-for-its-run"
    },
    {
      "title": "Verified AI Runs",
      "url": "https://www.rightshold.com/verified-ai-runs"
    }
  ],
  "computed_from": "Curated guidance; license verdicts computed from Rightshold's license profiles at render time. Not legal advice.",
  "updated": "2026-11-10"
}