What the manifest reveals
- The tool or model that produced the image, sometimes with its version.
- The edit chain: every application that reopened the file may append an assertion.
- Timestamps, the signing organisation and a linking identifier.
- Depending on the producer, a thumbnail of the earlier state of the image.
Where it hides in the file
The manifest is packed into a JUMBF container, itself stored in a format-specific region. In a PNG it occupies an ancillary chunk, typically caBX. In a JPEG it is spread across one or more APP11 segments. An SVG carries it in an RDF metadata block, a PDF in a dedicated stream.
Removing it cleanly therefore means understanding the format: rebuilding the PNG without the chunk and without breaking the CRC chain, or reassembling the JPEG without those segments. Blindly zeroing bytes would produce an unreadable file. A byte-level scan is only a safety net, to flag a residue the parser might have missed.
Should you actually remove it?
There are good reasons to keep it. If you are a photographer or illustrator, the manifest proves authorship and documents your edits: that is an asset, not a nuisance.
There are equally good reasons to strip it: not publishing the prompt and tool chain behind commercial work, avoiding an automatic "AI content" label on an image you heavily reworked, or simply delivering a clean file to a client. Note that most social networks already drop these blocks on upload, without asking you.
Verifying the manifest is really gone
Two independent checks. Locally: load the cleaned file back into the analyser — no C2PA finding should appear. Externally: the C2PA Verify site will tell you whether it still finds Content Credentials.
A reliable secondary signal is file size: a manifest with its thumbnail is often tens of kilobytes. A clear size drop with unchanged dimensions confirms the removal.
Watch out for the most common confusion: removing C2PA from a Gemini or Imagen image does not remove SynthID, which lives in the pixels. Both marks often coexist in the same file.
Frequently asked questions
Does removing C2PA alter the image?
No. Pixels are rewritten identically; only the metadata block is dropped. Visual quality is strictly unchanged and the file gets smaller.
Does the cryptographic signature prevent removal?
No. The signature lets you verify that a manifest which is present is authentic and untampered; it does not stop the block from being removed. An image with no manifest is simply an image with no declared provenance.
Do I have to upload the image somewhere to clean it?
No. A PNG or JPEG format parser runs perfectly well in JavaScript inside the browser: there is no reason for the file to leave your device.
Clean your file or your text
Detection and cleaning inside your browser: no upload, no account, no quota. Your files never leave your device.
Open the studio