Generator · pre-upload
Gemini images: metadata and SynthID
Gemini is one of the few tools using two mechanisms at once: a possible C2PA manifest in the file, and SynthID in the pixels. The first can be cleaned. The second cannot be handled at all.
On-device/No upload/Quality unchanged/No sign-up
Drop images here, or click to choose
JPG, PNG, WebP, AVIF, HEIC · 15 MB each · up to 30 per batch
You can also paste a screenshot with ⌘V / Ctrl+V
Cleaning options
Want to look first? Themetadata inspectorlists every field in the file, so you can see exactly what is there before deciding what to strip.
C2PA may be present; the pixels also carry SynthID, which cannot be removed
Different export paths can write different things. The reliable approach is to inspect one sample before batch processing.
Where it writes
| Location | Notes |
|---|---|
| C2PA | Some exports carry content credentials |
| SynthID | An invisible watermark in the pixels; not removable |
| Metadata | May name the model |
Pre-upload checklist
- 11. Check whether C2PA is present
- 22. Clean the header metadata
- 33. Go in clear-eyed that SynthID will still be there
Common traps
- Assuming it is completely clean afterwards — SynthID is still in the pixels
- Reading “clean metadata” as “cannot be detected”
If it is still flagged after cleaning
That means the trigger was never in the file metadata. It could be an invisible pixel-level watermark, the platform's own visual classifier, or history held on the platform side. None of those live in the metadata layer, and cleaning again will not change them.
The full boundaries are in thedisclaimer; if you just want to confirm the file really is clean, use thewatermark check.
Common questions
Can SynthID be removed?
No. It is fused with the pixel data; removing it means regenerating the image. No metadata tool can do that.
Does cleaning still help then?
It does. Platforms decide on an AI label mainly from file metadata, and verifying SynthID needs vendor-specific capability.
How do I know whether C2PA is present?
Scan the file with the inspector.