ProvSeal
Free extension FREN Pilot programBeta

A verifiable history, written into the file.

At every production step, ProvSeal adds what happened to the file’s C2PA manifest, then seals it with your organisation’s identity. Anyone can then trace the thread back.

Scroll, the story writes itself

Creation

The origin is declared from the moment the content is born: the camera, the software or the AI model that produced it.

c2pa.created · digitalSourceType: digitalCapture

Editing

Every change becomes a recorded action, with the source files as ingredients. Nothing is rewritten, everything is added.

c2pa.color_adjustments · ingredient: original.jpg

AI element

A generated element is declared as such, automatically, by your organisation’s policy. No exceptions, nothing forgotten.

c2pa.placed · trainedAlgorithmicMedia

Seal

The manifest is signed with your organisation’s identity, from your workstation, your token or your HSM, and bound to the exact bytes of the file.

c2pa.published · sha256 · organisation signature
✓ Trusted

One file. Its whole history.

The layers close up. What remains is a file that looks identical, carrying every step and your organisation’s signature. It can travel: its history travels with it.

1 file · 4 steps · 1 signature

Under the hood.

What a file signed by ProvSeal actually contains. An open format, the C2PA standard, readable by every compatible verifier.

manifest.jsonC2PA
{
1"claim_generator": "ProvSeal Desktop",
"title": "spring_campaign.jpg",
2"c2pa.actions": [
"c2pa.created",
"c2pa.color_adjustments",
"c2pa.placed",
"c2pa.published"
],
3"ingredients": ["original.jpg"],
4"hash": "sha256:9f2c4e81…7b9e30",
5"signature": {
"issuer": "Your organisation",
"key": "HSM"
}
}
  1. 1The softwareThe tool that produced the manifest, and its version.
  2. 2The stepsEvery action, from creation to publication, in order.
  3. 3The sourcesThe original files, themselves verifiable.
  4. 4The fingerprintBound to the exact bytes of the file: change a single byte and it breaks.
  5. 5The signatureMade with your organisation’s key, in your HSM.

What the recipient sees.

The verifier reads the manifest and checks the signature, then shows one of four statuses.

The file is
Trusted.Signed, not recognised.Invalid.No information.

Signed by an identity recognised by the C2PA trust list.The signature is valid, but the identity is not on the trust list.The file or its manifest was modified after signing.No Content Credentials. That does not mean the content is fake.

Trusted Not recognised Invalid No information
  • ProvSeal guesses nothing: it reads what the file declares and verifies the signature.

Questions
that matter.

Straight answers about C2PA provenance.

Can the metadata disappear?

Yes, a screenshot or some social networks remove it. The content then appears with no information, not as tampered with. IMATAG’s invisible watermark makes it possible to recover the origin in that case.

Can a signed file be modified?

Yes, but any undeclared change invalidates the signature. A legitimate change adds a new step, signed in turn, that references the previous version.

Does ProvSeal invent its own format?

No. ProvSeal follows the C2PA specification, readable by every compatible verifier.

Your turn to write
the first line.

ProvSeal is in beta. Join the pilot program and sign your first batch, on your infrastructure.

Join the pilot program