ProvenanceGuard
← Go back

← All guides

What Is C2PA and What Does a C2PA Manifest Actually Contain?

By the Ingenious AI team · Published: November 14, 2026 · Reviewed: November 14, 2026 · 8 min read

The short answer

A C2PA manifest is a signed set of assertions embedded in a media file, usually in a JUMBF box, describing how the content was created and edited. It works well while the file is untouched, and it is commonly lost the moment a platform resizes and re-encodes the upload, which is why provenance planning cannot stop at the manifest.

Seal an image free → Recover a reposted image Pricing

Many teams discover C2PA backwards: they generate an image with a tool that marks it, publish it proudly, and only later learn the published copy carries no manifest at all.

The weakness is transport, not design. The manifest lives inside the file, and the everyday machinery of the web rewrites files. Platforms resize and re-encode uploads, messaging apps compress them, and screenshots discard the file entirely. When the bytes are rewritten, an embedded manifest is commonly dropped, and the image that arrives at the next viewer carries no credentials even though it was properly marked at creation. Compliant at creation and non-compliant at distribution is the normal outcome, not an edge case.

What is a C2PA manifest? a signed bundle of assertions about a media file, covering its creation and edits, embedded in the file in a JUMBF box so supporting software can display the content's credentials to a viewer.

The problem behind C2PA manifests

That is why a registry layer exists alongside embedded marking rather than instead of it. ProvenanceGuard detects C2PA markers during inspection and reports them truthfully, and its survival simulations show whether a C2PA manifest present in a sealed file survives a platform-style transform; in the simulated transforms it does not, while the registry fingerprint match does. The lesson is not that C2PA is useless, but that an embedded manifest alone cannot be the whole compliance plan for content that will be distributed.

C2PA is a technical specification for attaching a manifest to media: a structured, signed bundle of assertions about how the content was created and edited, typically carried in a JUMBF box inside the file. When a camera, generator or editor that implements the specification writes a manifest, and the file reaches a viewer unaltered, supporting software can read the manifest and show the content's credentials. The idea is sound and increasingly widely implemented across cameras, tools and platforms.

How ProvenanceGuard handles it

That byte-level honesty changes decisions. A file that arrives with a valid C2PA manifest needs different handling from a file whose metadata was already stripped by an earlier platform hop, and both differ from a file that was never marked at all. Checking first stops a common mistake: sealing and republishing an image while assuming its original manifest is intact, when in fact the copy in hand lost it two uploads ago. The inspection result becomes the baseline the rest of the record is built on.

Inspection also has limits worth stating. A marker being present says the bytes contain it; it does not say the claims inside it are true, and a signature check says whether a ProvenanceGuard assertion was altered, not whether the disclosure text a creator typed was accurate. Provenance records what was declared and when it was registered. Treating it as more than that, in either direction, is how teams end up both over-trusting and under-using the records they have.

What survives distribution, and what does not

Only JPEG and PNG files are supported, up to 25 MB, because those are the formats whose byte structures the inspection, embedding and fingerprinting are built and tested against. A file in another format is refused rather than guessed at. That refusal is a feature: a provenance tool that silently approximated on formats it does not understand would produce records that look solid and are not, which is worse than no record at all.

Inspection comes before sealing, because an asset may already carry signals. ProvenanceGuard reads the actual bytes of an uploaded JPEG or PNG and reports what is really there: C2PA and JUMBF markers, an XMP packet, EXIF data, PNG text chunks, any AI disclosure already present in the metadata, and any prior ProvenanceGuard assertion, including whether that assertion's signature still verifies. Nothing is inferred from the filename or the uploader's claims; every field on the inspection result is derived from the file itself.

A routine that survives busy weeks

The pattern the simulations reveal is consistent and worth internalising. Embedded metadata, including the signed assertion and any C2PA manifest, does not survive the transforms. The visible label generally does, as long as it stays in frame and legible at the reduced size. The perceptual fingerprint still matches the registry record after the transform, within the match threshold, and the registry lookup therefore survives even when everything inside the file is gone. Distribution-proof provenance is the registry plus the label; the embedded assertion is the record of origin.

Running the check before a campaign, rather than after a takedown or a complaint, turns those findings into decisions. If the label fails at a platform's width, the artwork changes. If a format conversion in the pipeline strips everything before publication, the seal is applied after that conversion instead of before it. The simulations are cheap and repeatable, so they belong in the pre-publish routine for any asset that matters, not in the post-mortem.

Survival re-checks, a Pro feature, answer the question publishing actually raises: after this platform does what it does to uploads, what is left of my marking? The check runs local simulations of documented platform transforms on the sealed and labelled copies: resize to the platform's maximum width, JPEG re-encode at its quality setting, and metadata stripped. The result is reported per platform for Instagram, TikTok, YouTube thumbnails, X and LinkedIn, and every row is labelled as a simulation, because that is what it is, not an actual upload.

Five actions to take

  1. Inspect your generator's export for C2PA markers before assuming they are there
  2. Run a survival simulation on one marked file and record what the transform removes
  3. Download and keep both copies the seal produces: the sealed copy as the record, the labelled copy for publication
  4. File the exhibit's verification URL beside the asset wherever your team keeps campaign or client records
  5. Run check-a-copy on the version you actually published, and note which checks held: hash, signature, fingerprint

A worked example: A two-person design studio preparing a product launch

They inspected their hero image before sealing it: the generator's C2PA markers were present in the export, absent after one simulated platform transform, and the studio changed its plan to seal the final export and publish the labelled copy for its 6 launch images.

The lesson generalises beyond this case. Records made at publication time are cheap, calm and complete; records reconstructed under pressure are expensive, partial and contested. Everything in this guide is in service of moving work from the second category into the first.

FAQ

Does ProvenanceGuard issue C2PA manifests?

No, and it says so everywhere. It detects C2PA markers during inspection and embeds its own HMAC-signed ProvenanceGuard assertion in XMP, labelled accurately as its own assertion, never as a C2PA manifest.

What formats and sizes are supported?

JPEG and PNG, up to 25 MB per file. Those are the formats the inspection, XMP embedding and fingerprinting are built and tested against; other formats are refused rather than approximated.

What does the free tier actually do?

The complete job on an asset: byte-level inspection, a signed assertion embedded as XMP, a visibly labelled copy, SHA-256 and perceptual fingerprints registered, and a public verification page. Paid plans add survival re-checks, evidence packs and bulk verification.

What do Pro and Team cost?

Pro is $29 a month and Team is $79 a month, as shown on the pricing page. Paid depth means per-platform survival re-checks, evidence pack export with EU, California and New York wording, and the bulk hash-verification API.

Seal an image free →