The short answer
No. This tool cannot erase SynthID, Content Credentials, stock-photo or agency watermarks, TikTok or Sora overlays, or any watermark it has not specifically been built to recognize. It removes exactly one thing: the documented visible Gemini and Veo corner mark, matched against the measured size catalog. Everything else is out of scope on purpose, not a missing feature waiting on a future release.
What is actually covered, and what is not
| Watermark type | Status | What to expect |
|---|---|---|
| Visible Gemini / Nano Banana / Veo corner mark | Supported | The one thing this project is built for: a documented mark matched against a measured catalog of sizes, margins, and anchor positions. |
| SynthID | Not supported | A distributed signal learned into the pixels across the whole image, not a fixed overlay in one corner. There is no local region to erase. |
| Content Credentials / C2PA metadata | Not supported | A signed provenance record, not a visual overlay. Stripping it would misrepresent an image's origin, so it is refused on principle. |
| Stock photo or agency watermarks | Not supported | Different geometry, different rendering rules, and not in the catalog. The detector requires a verified match before it changes any pixel. |
| TikTok, Sora, or other platform overlays | Not supported | Built for a different renderer with a different mark entirely. Out of scope for the same reason as any other undocumented pattern. |
| Arbitrary custom overlays, text, or logos | Not supported | The engine matches specific catalog entries. It has no generic "remove whatever is in this rectangle" mode to fall back to. |
Why "fail closed" is a guarantee, not an apology
When the detector cannot confirm a supported mark on a given file, it leaves the file untouched and reports why. It does not fall back to a generic inpaint over a guessed region. A guessed edit would be worse than doing nothing: it degrades real image content without confirming it fixed anything, and it creates the impression that the file was checked when it was not.
That is also the entire reason SynthID is refused rather than attempted. SynthID is designed to keep working after the kind of cropping, filtering, frame-rate changes, and lossy recompression that would defeat a naive pixel-level removal attempt. A tool that claimed to strip it would either be lying about the result or actively degrading the image while failing to touch the actual signal. Because the engine only recognizes documented Gemini and Veo geometry, it is not merely unwilling to behave like a general watermark stripper; it is technically incapable of it. There is no generic edit mode hiding behind a setting, and no plan to add one.
Removing a visible mark does not touch a disclosure duty
Removing a visible watermark changes pixels. It does not change legal or platform obligations that existed before the edit. If a jurisdiction's AI-content disclosure rule, or a platform's own labeling policy, required marking a piece of media as AI-generated before this tool touched it, that requirement is still there afterward. Nothing about "the visible mark is gone" implies "the content is now unrestricted to publish however you like," and this page is written partly to make sure nobody reads it that way. The responsible use guide goes deeper on that distinction, and the Gemini watermark vs SynthID guide covers how the two signals differ technically in more depth than a scope page like this one should try to.
If you actually need one of the things above
Sometimes the honest answer is that this is not the right tool, and that is worth saying plainly rather than leaving a visitor to find out by trying and failing.
- Checking for SynthID, rather than removing it, is a different task from anything this project does. Google's own in-app verification tooling is the relevant path, not a third-party pixel editor, precisely because SynthID is not something a pixel editor can see.
- Verifying Content Credentials on a file is a provenance question, answered by a C2PA-aware viewer, not by any watermark remover.
- A platform-specific overlay, such as a TikTok stamp, a Sora corner tag, or a stock-agency mark, needs a tool built against that platform's own rendering rules. Pointing this engine at a mark it was never calibrated for either does nothing, because it fails closed by design, or, if a safety check that does not exist here were somehow bypassed, would damage a file for no confirmed benefit.
- Outputs from Google AI Studio or the Gemini API may not carry the visible mark at all on some tiers; that page explains which tiers do and do not, so you can check before assuming you need a remover.
- Gemini Omni outputs are new enough that this project has not verified their visible-mark behavior against real samples yet, so no removal claim is made there either.
The catalog is how this boundary stays honest
The reason this page can state its limits this precisely is the same reason the size catalog exists: every claim about what is supported traces back to a measured, checked entry, not a description of a general pattern. If a new Gemini or Veo output ever ships a visible mark this project has not verified, the correct fix is adding that evidence to the catalog, the same way the current entries were added, not loosening what "supported" means. Anyone who wants to check that this is really how the detector behaves, rather than take this page's word for it, can read the open-source engine directly, or run a file through the browser eraser and read the exact skip reason it reports.
Last updated 2026-07-31