Google Gemini metadata, and the part nothing can remove
Gemini and Imagen attach C2PA content credentials, which this tool removes like any other. They also embed SynthID: an invisible watermark in the pixels themselves, and that is a different problem entirely.
This page exists to be straight with you about where the line falls.
writes to: C2PA + SynthID
Drop an image here
We read what is inside it first, then show you every field before anything is removed.
JPEG · PNG · WebP: up to 25.0 MB · 30 files at a time
What is in the file
What Google Gemini & Imagen writes into your image
| Field | Contents |
|---|---|
| C2PA manifest | Google-signed content credentials, removable |
| Digital source type | trainedAlgorithmicMedia, removable |
| EXIF Software | Names the Google model, removable |
| SynthID | Embedded in pixel data, not removable |
What it reveals
What someone with your file can learn
- Metadata declaring Google as the generator, which this tool strips
- A pixel-level watermark that survives cropping, resizing, compression and screenshots
Worth knowing
Google Gemini & Imagen workflow notes
- SynthID is designed to survive exactly the operations people try: screenshots, crops, re-compression, colour shifts and format conversion.
- Because this tool never modifies pixels, it cannot affect SynthID. That is a consequence of the lossless design, not an oversight we plan to fix.
- Anything advertising SynthID removal is either re-encoding your image heavily and hoping, or misleading you. Treat such claims with suspicion.
Questions
Google Gemini & Imagen metadata FAQ
›Can you remove SynthID?
No. SynthID lives in the pixels, and this tool deliberately never alters pixels. No metadata tool can remove it, and tools claiming otherwise are either degrading your image in the hope of disrupting the signal, or simply wrong.
›Then what does cleaning a Gemini image actually achieve?
It removes the C2PA manifest and metadata declarations, which is what most platform labels currently read. It will not defeat a detector that checks for SynthID specifically. That is a real limit, and worth knowing before you rely on it.
›Does a screenshot remove SynthID?
It is designed to survive that. SynthID is built to persist through screenshots, crops, resizing and compression, so a screenshot costs you quality without reliably solving the problem.
Other tools