Skip to main content
Encypher Logo

For creative agencies

C2PA 2.4 Content Credentials for your ad creative.

Sign supported ad creative with C2PA 2.4 Content Credentials. Review signer identity, source declarations and ingredient provenance against your client brief. Add watermarking where your workflow calls for it.

The request takes a name, an email, a format, and the clause your client sent. No client asset upload required. We will review the requirement and agree the next step. See Mark pricing

C2PA 2.4

the version new creative signing writes

Ingredients

references to source assets and their credentials

No upload

send the requirement before sharing client files

Identity. Ingredients. Acceptance.

Answer the clause in the brief.

When your client asks for Content Credentials, signer identity, or ingredient provenance, start with their specification. Check one deliverable before changing your production workflow.

01

Sign under your agency name

While you evaluate, signing runs under the Encypher platform identity. Your agency name appears on an eligible paid plan, once we accept your identity proof.

Start free while you evaluate
02

Show where the artwork came from

Link source assets and preserve their existing credentials. Your client can inspect the declared ingredients and actions. Missing source credentials remain a gap to resolve.

03

Test against their check

It depends on the tool your client checks with. We agree that check up front, then run your real export and delivery path.

What the client opens

One deliverable, checked by anyone.

The card below is a labeled example of the fields a check returns. Real signed creative, with the output it gives back, sits on the examples page.

Signed deliverable

Labeled example
Signer
Your agency, on a paid plan with accepted proof
Credential
C2PA 2.4, with a signing time
Ingredients
Source references and available credentials

Signing under your own agency name needs an eligible paid plan and accepted identity proof. A watermark does not replace a source declaration your client asked for.

See the signed examples

Look before you ask

Real files first. Forms later.

Open a signed image, read the source history behind it, then check the coverage table against the formats you ship.

Signed creative

One of our own images, with its credential, its signer, and its signing time.

Open the image example

Ingredient history

A composition with references to its source assets and their available credentials.

See the ingredient graph

How it works

From one clause to one accepted file.

The first pass can use your own artwork or ours. Client files move by secure transfer after the intake, and we do not host them in public by default.

  1. 01

    Send the clause

    A name, an email, a format, and the clause your client sent. No asset upload.

  2. 02

    Agree the scope

    We confirm the formats, the signer, the source inputs, and the check your client accepts.

  3. 03

    Sign and deliver one

    We sign a sample, you run your real export and delivery path, then we read the result together with the gaps named.

Proof details

Coverage and client acceptance

Encypher supports 70+ formats for signing and verification. We check the agreed technical requirements; your client decides whether to accept the deliverable.

  • C2PA 2.4 is the default signing version. Version support varies by format: 67 of the 70 formats list it today.
  • Our audio and video examples show that the credential is present and valid. They do not show that a watermark survives a transcode.
  • Our formal C2PA conformance record covers version 2.2 over 20 media types. That record is narrower, and it is not a 2.4 pass.