Does Google Gemini image models, Imagen and Veo add Content Credentials?

If you publish Google Gemini image models, Imagen and Veo output in the EU

Marking outputs in a machine-readable way is the duty of the tool’s provider under Article 50(2) of the AI Act. If you use the output for work and it is a deepfake, the visible disclosure is yours (Article 50(4)), whatever Google adds to the file. What that means for your content: AI images and AI video.

Scope and limits

• The Vertex AI list of C2PA-signed models names Gemini image models, Veo versions and others. Imagen is not in that list, so C2PA for Imagen specifically is not documented there.
• The quote under “edits” is about modifying a signed file with a non-C2PA tool, which Google says results in a validation failure. It is not a statement about metadata being removed.
• Google’s pages describe SynthID for images, video, audio and Gemini-app text; this page covers the image and video models above.

If the credentials are removed

C2PA data travels inside the file, so a re-encode, screenshot or upload that does not carry it across leaves an image with no credentials. A watermark or fingerprint can help find a record again, if one was stored (see the C2PA specification’s soft bindings). Proofcan is independent of Google: for images you mark with Proofcan it writes a C2PA manifest, an invisible watermark and a registry record. It does not change or vouch for how Google marks its own outputs.

Check a file yourself

The Content Credentials checker reads the C2PA data in an image in your browser and shows who signed it, the generating tool and whether the signature still matches. It reads what a file declares; it does not detect AI from pixels, and a file with no credentials proves nothing either way. See why metadata gets stripped.