Does this actually remove the SynthID watermark?

No, and it would be worth doubting anyone who says their free web tool does. SynthID is written into the pixel values, not into the file's metadata, so a tool that edits metadata cannot reach it. What this removes is the C2PA Content Credential and the other metadata Google attaches, which is a real mark and a real removal, just not that one.

Then why do other sites say they remove it?

Read their own FAQs and several of them agree with this page. One states plainly that it is not guaranteed to work and is provided for demonstration purposes; another says no tool, theirs or anyone else's, guarantees complete removal. The claim on the landing page and the claim in the FAQ are not the same claim.

How would I know if an image still carries SynthID?

You cannot check it here, and neither can any third party, because detection needs Google's own model and the public detector is still behind a waitlist. What you can check here is the metadata side: the C2PA checker on this site reads whatever provenance record a file carries and shows it to you.

Is anything uploaded when I use this?

No. The work happens on bytes already in the tab, and there is no request to check. Open the network panel in your browser's developer tools, drop a file in, and watch it stay empty. That is a claim you should test rather than take from us, particularly in this category.

If the pixel watermark stays, what is the point of running this?

Two things come off that people actually care about. The C2PA manifest is what a checker reads to say 'this image was made by Gemini', and stripping it removes that machine-readable claim. The EXIF and XMP alongside it can carry a prompt, an account identifier or a timestamp. Neither of those is the pixel watermark, and this page will not pretend otherwise, but they are the parts that get read in practice.

Will an image still be detectable as AI generated after this?

By a tool that examines the pixels, very likely yes. By a tool that reads the file's metadata, no, because that record is gone. The two questions get conflated constantly and they have different answers, which is the single most important thing to understand before relying on any page that offers this. If your reason for stripping is that a platform rejected the upload after reading its Content Credentials, this addresses that. If your reason is to pass a pixel-level detector, nothing here does that.

Does stripping the manifest change the image itself?

Not by a single pixel. The manifest lives in a container block alongside the image data rather than inside it, and removing that block leaves the encoded pixels exactly as they were. That is different from re-encoding an image, which does change pixels and is what most 'remove watermark' workflows quietly do to you.

When is a SynthID remover the right tool, and when is it not?

It is the right tool when a platform or a checker has read the Content Credentials attached to your image and acted on them, because that record is exactly what comes off here. It is the wrong tool if you believe removing it makes the image indistinguishable from a photograph, because the pixel watermark Google embeds is untouched and is not readable or removable from a page like this one. Every SynthID remover on the web faces that same boundary; the ones that do not say so are the ones to be careful with.

Does it work on images from tools other than Gemini?

Yes, because what it strips is a standard container rather than anything specific to one vendor. Any image carrying a C2PA manifest is handled the same way, and several image generators now sign their output the same way Google does. It also clears ordinary EXIF and XMP, so a photograph with GPS coordinates is cleaned by the same pass.

MetadataNothing leaves this tab

SynthID remover

Google puts two marks on a generated image. This takes off the one that is a file record, byte for byte, and leaves your pixels alone. The other one lives in the pixels and does not come off here.

Found

What this looks for

Add a PNG, JPEG or WebP and every metadata block in it is listed here by name and byte count, before anything is removed. It looks for EXIF, XMP, IPTC and Photoshop resource blocks, free-text comments, modification timestamps, and C2PA Content Credentials. The colour profile is left alone on purpose, because deleting it changes how the image looks and it says nothing about you.

A watermark encoded into the pixels themselves, such as SynthID, is a different mechanism and is not something this or any metadata tool can remove.

1Files

Drag images in, paste, or click to choose

A whole folder works too · Ctrl/Cmd+V pastes · on phone this opens your photo library · up to 60 MB per file

No files added yet.

Mechanism

What a SynthID remover can and cannot reach

An image out of Gemini or Imagen carries a C2PA manifest, a signed record naming the tool that made it, and it usually carries EXIF and XMP alongside. Those are container blocks: a caBX chunk in PNG, an APP11 segment in JPEG, a C2PA chunk in WebP. This tool walks the container, drops those blocks, and copies the pixel data across untouched, which is why the result is byte-identical in the picture itself and carries no provenance record. The SynthID signal is different in kind. It is a pattern the model wrote into the pixel values, so no amount of editing the file's metadata reaches it, and removing it would mean changing the picture.

Limits

Where a SynthID remover falls short

The SynthID watermark itself is not removed. It is encoded in the pixels, and the only published attack with verified results, UnMarker from IEEE S&P 2025, needs a GPU with 32GB of memory. Nothing running in a browser tab does this.
Sites that claim otherwise are worth checking. Several of the best-ranked ones state in their own FAQ that removal is not guaranteed, and three of them send your file to a server while the page says processing is local. Open your browser's network panel and watch.
Removing the C2PA record does not make an image undetectable. Detection of SynthID is done on the pixels by Google's own model, and it does not consult the metadata at all.
Cropping, filters, screenshots and re-compression do not defeat SynthID either. Google's own paper reports 98.06% detection after the worst combination of thirty ordinary transformations.

Questions

Questions about SynthID removal

Does this actually remove the SynthID watermark?: No, and it would be worth doubting anyone who says their free web tool does. SynthID is written into the pixel values, not into the file's metadata, so a tool that edits metadata cannot reach it. What this removes is the C2PA Content Credential and the other metadata Google attaches, which is a real mark and a real removal, just not that one.
Then why do other sites say they remove it?: Read their own FAQs and several of them agree with this page. One states plainly that it is not guaranteed to work and is provided for demonstration purposes; another says no tool, theirs or anyone else's, guarantees complete removal. The claim on the landing page and the claim in the FAQ are not the same claim.
How would I know if an image still carries SynthID?: You cannot check it here, and neither can any third party, because detection needs Google's own model and the public detector is still behind a waitlist. What you can check here is the metadata side: the C2PA checker on this site reads whatever provenance record a file carries and shows it to you.
Is anything uploaded when I use this?: No. The work happens on bytes already in the tab, and there is no request to check. Open the network panel in your browser's developer tools, drop a file in, and watch it stay empty. That is a claim you should test rather than take from us, particularly in this category.
If the pixel watermark stays, what is the point of running this?: Two things come off that people actually care about. The C2PA manifest is what a checker reads to say 'this image was made by Gemini', and stripping it removes that machine-readable claim. The EXIF and XMP alongside it can carry a prompt, an account identifier or a timestamp. Neither of those is the pixel watermark, and this page will not pretend otherwise, but they are the parts that get read in practice.
Will an image still be detectable as AI generated after this?: By a tool that examines the pixels, very likely yes. By a tool that reads the file's metadata, no, because that record is gone. The two questions get conflated constantly and they have different answers, which is the single most important thing to understand before relying on any page that offers this. If your reason for stripping is that a platform rejected the upload after reading its Content Credentials, this addresses that. If your reason is to pass a pixel-level detector, nothing here does that.
Does stripping the manifest change the image itself?: Not by a single pixel. The manifest lives in a container block alongside the image data rather than inside it, and removing that block leaves the encoded pixels exactly as they were. That is different from re-encoding an image, which does change pixels and is what most 'remove watermark' workflows quietly do to you.
When is a SynthID remover the right tool, and when is it not?: It is the right tool when a platform or a checker has read the Content Credentials attached to your image and acted on them, because that record is exactly what comes off here. It is the wrong tool if you believe removing it makes the image indistinguishable from a photograph, because the pixel watermark Google embeds is untouched and is not readable or removable from a page like this one. Every SynthID remover on the web faces that same boundary; the ones that do not say so are the ones to be careful with.
Does it work on images from tools other than Gemini?: Yes, because what it strips is a standard container rather than anything specific to one vendor. Any image carrying a C2PA manifest is handled the same way, and several image generators now sign their output the same way Google does. It also clears ordinary EXIF and XMP, so a photograph with GPS coordinates is cleaned by the same pass.