Is C2PA a watermark?

No. C2PA is metadata — a signed manifest wrapped around a file, recording what created it and what has edited it since. A watermark changes the content itself. If you searched for "metadata watermark", that phrase is the confusion in miniature: metadata sits beside the pixels, a watermark sits inside them.

Two different mechanisms

A C2PA manifest is bound to its file by a cryptographic hash of the bytes. That is what makes it verifiable — alter a pixel and the signature no longer matches — and also what makes it fragile. Anything that re-encodes or re-captures the file tends to drop the manifest rather than break it. What strips content credentials goes through which operations do that.

A watermark makes no claim about bytes. It perturbs the content — pixel values, or word choices in text — so copying the content copies the mark. It survives handling that a manifest does not, and in most cases you can't read it without the vendor's own detector.

So why do people say "C2PA watermarking"?

Because the spec does mention watermarks, in a narrow role. C2PA defines soft bindings: an assertion carrying a fingerprint or an invisible watermark identifier, used to match a file back to a manifest held somewhere else even when the bytes have changed. The watermark is a pointer to the record, not the record. The provenance claim still lives in the signed manifest, and the match only works if that store is reachable.

Google Content Credentials

Same standard, under Google's name for it. Pixel 10 cameras write C2PA credentials into photos, and Google added Content Credentials verification to the Gemini app after announcing it in May 2026, with Search and Chrome rolling out since. Google's watermark is SynthID, a separate signal that lives in the pixels. A file can carry both, either, or neither.

Neither signal tells you who wrote something. A valid credential tells you which tool produced that exact file; a missing one tells you almost nothing, because most honest files have never had one. To see which a file actually carries, run it through the metadata detector.