
An ImageKit Content Credentials request can fail before signing, fail because of its output format, or deliver a signed image whose certificate is not recognized by a verifier's trust list. Check these stages separately. A 403, a 400 and an “unknown signer” result do not describe the same problem.
Key Takeaways
c2pa-truerequires the account's signing add-on to be enabled.- Unsupported explicit output formats cause a different failure.
- Verifier trust status and cryptographic integrity need separate interpretation.
Read the response before interpreting provenance
Official ImageKit Content Credentials documentation states that requests including c2pa return 403 Forbidden when the paid signing add-on is not enabled. It separately documents a 400 Bad Request when c2pa-true is combined with an explicit unsupported output format. Animated PNG output cannot be signed.
The page describes an untrusted or unknown signer warning, including signingCredential.untrusted, when its signing certificate is not recognized by the C2PA trust list. That explanation reflects the captured documentation, not a promise that certificate or trust-list status will remain unchanged.
Use a three-stage worksheet
| Observation | First question | Next evidence |
|---|---|---|
| 403 with signing requested | Is signing enabled for this account? | Account feature confirmation |
| 400 after specifying a format | Is the explicit output supported? | Exact transformation and format |
| Image delivered, signer warning | What does the verifier report separately? | Issuer, integrity and trust results |
- Save the response status and exact non-sensitive transformation settings.
- Confirm add-on availability with the authorized account owner.
- Choose a currently supported output format for the sample.
- Download the delivered image rather than inspecting a source preview.
- Open it in a C2PA verifier and record the issuer, listed actions and any warning independently.
Do not purchase an add-on or change account settings merely to silence a diagnostic without the owner's decision.
A hypothetical edited portrait
A studio proposes a resize followed by credential signing. Its acceptance record should identify the delivered file, the expected ImageKit issuer and the edits actually displayed by the verifier. If AI-assisted operations were applied, inspect the corresponding disclosure rather than inventing an assertion from the image's appearance.
ImageKit documents retaining an input C2PA record as a parent ingredient when present. That does not justify claiming that every source file already contains credentials.
Acceptance and limits
Accept only a decodable delivered file with a truthful report of the observed verifier state. Do not rewrite “unknown signer” as “no credential,” or call a signed edit history proof that the depicted event occurred.
The provenance-preservation guide covers keeping evidence through successive exports. This guide addresses a specific provider's signing errors and verifier-state interpretation. No account request or signing test is claimed here.
Related tasks
- How Do I Keep AI Image Provenance Metadata Through Editing and Delivery?
- Lightroom Content Credentials: Attach Privately or Publish to the Cloud?
- How Do I Check a Photo for Location Metadata Before Sharing It?
Sources and scope
- ImageKit: Content Credentials (C2PA): c2pa add-on enablement and 403 response, unsupported explicit output format 400, APNG signing exclusion, issuer/actions/parent history, and documented trust-list warning interpretation.
Documentation-based editorial guidance. All scenarios, worksheets and acceptance checks are hypothetical or proposed. No hands-on test, account operation, benchmark, measured search demand, AI-citation rate or platform acceptance is claimed.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.