On the results page for this term, almost every entry says the same three things: free, private, and runs in your browser. Almost none of them says what “free” costs you, or what the tool does not remove.
“Free” here describes a business model, not a feature. There are four common kinds, and each is paid for somewhere: your file leaves your device; your output is capped; the free tier is a funnel to a paid one; or the work genuinely runs in your own browser and nothing is taken. The word on the page looks identical in all four cases.
The one thing no price buys is SynthID removal. Google's own documentation describes detection as probabilistic and the signal as written into the pixels, so “free” and “guaranteed clean” cannot both be true. Our own position, in the same terms: free, in your browser, no account, no upload — and we remove the visible badge only. We do not remove SynthID, and we say so before you drop a file in.
What the results for this term have in common
We looked at the results for this term on 30 September 2026, and the shape of the page is worth describing before anything else, because it is not a list of different answers. It is a list of the same answer repeated: a tool page, a short promise, and a button.
Three claims recur almost everywhere: that it is free, that it is private, and that it runs in your browser. All three are cheap to write and expensive to check. Then there is a fourth claim that almost none of them makes, and it is the opposite kind of claim: a plain statement of what the tool does not remove.
To be clear about what we are and are not saying: we are not calling those pages dishonest, and we are not going to characterise their motives. Several of them are probably doing exactly what they say. The point is narrower and more useful — of those four claims, three can be tested by you in under a minute, and the fourth one is the only one that tells you whether the page is being straight with you.
Four kinds of “free”, and what each one costs
When a tool is free to use, something else is being paid. These are the four patterns we see most often on this term. The tell is always in the tool's own instructions, not in its marketing copy.
- Free, but your file leaves your device. The tell: the page asks you to upload your image before anything happens. The cost: your picture now sits on someone else's disk, under a retention policy you would have to go and read. A second consequence is easy to miss — a tool that needs the file on a server also cannot work offline, and cannot work if you would rather not send that particular image anywhere.
- Free, but the output is capped. The tell: the free tier limits resolution, file size, or how many images you get per day — or the download comes back with the tool's own mark on it. The cost: you take one company's badge off and get another company's badge instead. A mark you did not ask for is not the same thing as a clean image, whichever logo it carries.
- Free to try. The tell: credits, a sign-up wall before the result appears, or a preview you cannot download. The cost: your time and an email address, for a result you may not get to keep. This is a legitimate business model; it is just not what the word “free” led you to expect.
- Free and local. The tell: the work happens in the tab you already have open, and no request leaves the page. The cost: nothing for the file. But read the tool's stated limits anyway, because “local” says nothing at all about what a tool can remove — a local tool can still be a local tool that does not do what you need.
Only the fourth kind makes a claim you can verify in ten seconds. The first three ask you to take something on trust about a process you cannot see. The fourth one asks you to open your browser's network panel and watch nothing happen. That difference is the whole reason this page exists.
Five questions to ask before you drop a file in
This is the part we would want if we were searching for this term. Every question below is answerable from the tool's own page, and none of them requires you to know anything about image processing.
- 1. Does it ask you to upload? If it does, the price is your file. That may be a price you are happy to pay — the point is that it is a price, and it should be named.
- 2. Does it make you create an account before it shows you the result? If so, the price is your identity, and the result is being held until you pay it.
- 3. Does the output keep your original resolution and dimensions? A “clean” result that came back smaller is a different product from the file you put in. Check the pixel dimensions of what you downloaded against what you uploaded.
- 4. Does the output carry the tool's own watermark or branding? Swapping one mark for another is not removal, and a free tier is where this shows up most.
- 5. Does the page state plainly what it does not remove? This is the only question that cannot be answered by good copywriting. Anyone can write “free” and “private”; describing your own limits costs you a selling point.
Questions one to four you can answer yourself, by testing the tool. Question five you cannot test — you can only read the answer and notice whether it is there at all.
Why a free tool can remove the visible mark at all
There is a technical reason the visible badge is the one thing a small free tool can genuinely do, and it is worth knowing because it explains the whole price structure of this niche.
The visible mark is not a model output. It is ordinary pixels composited over your picture — a corner logo placed with a known position and a known transparency template. Because the geometry and the template are known, the original pixels underneath can be recovered arithmetically, by reversing the blend. That is arithmetic, not inference: it needs no server, no model, no dataset and no per-image cost, which is exactly why it can be given away.
SynthID is the opposite case in every respect. Google DeepMind's documentation states that the system embeds digital watermarks directly into AI-generated images — into the pixels themselves, spread across the whole picture rather than sitting in one location. There is no single component to isolate and rewrite, and no known template to reverse. A free tool has no revenue to fund that work, and on Google's own account of how detection behaves, the work does not have a guaranteed end state anyway.
The claim that cannot be made honestly, at any price
Google's SynthID documentation says detection is probabilistic, and lists three possible outcomes rather than two: watermarked, not watermarked, and uncertain. That third state is the one that settles this section. If the detector's own answer can be “uncertain”, then no one — free or paid, us or anyone else — can hand you a guarantee about an invisible signal.
So when a page promises a free, complete, guaranteed clean-up, the problem is not the word “free”. The problem is the word “guaranteed”: it is a claim about a measurement neither the page nor you can run. A price of zero does not make that claim any more available. It makes it less available, because verifying it is the expensive part.
One precision note, because it matters and almost nobody bothers with it: Google's documentation also describes the technique as robust to some transformations but subject to limitations, and says it is not designed to directly stop motivated adversaries from causing harm. Those sentences are written about SynthID Text, not about images. We are quoting them as evidence of how Google characterises its own technology, not claiming they describe your JPEG. We went through that distinction in full on whether SynthID can be removed.
The same five questions, asked of this site
It would be a poor checklist if we did not run it on ourselves. So, in order:
- 1. Does it ask you to upload? No. The file is read by your browser and the cleaned image is written by your browser. Nothing is sent anywhere, and there is no server-side step that could receive it.
- 2. Does it make you create an account? No. No account, no sign-up, no login, no email.
- 3. Does the output keep your original resolution? Yes. It rewrites only the pixels inside the watermark box and copies everything else from your file untouched. You get the same dimensions back.
- 4. Does the output carry our branding? No. There is no mark added, no price on the page, and no limit on how many images you clean.
- 5. Does it state what it does not remove? Yes, and this is the one we would be embarrassed to get wrong: it does not remove SynthID, and it does not strip C2PA metadata. It removes the visible badge, and that is all it removes.
The limits we will write down in the same place as the checklist: one image at a time; PNG, JPEG or WebP; up to 60 megapixels, with no file-size cap. And one we found by testing rather than by hoping — at the 1K output size that Nano Banana models default to, this tool failed to locate the watermark correctly. We published the measured numbers and the cause on the Nano Banana page, and the fix is not in yet. A page that will not put its own failures next to its own promises has already answered question five.
If “free” is the actual requirement
Then here is the honest summary of what you can get for nothing:
- The visible badge: free, and free here. It is arithmetic on a known template, which is why it does not need to cost anything. Run it on an image and compare the result against your original yourself.
- SynthID: not available at any price. Not from us, and — given that detection is probabilistic and the signal is distributed across the pixels — not from anyone selling certainty. If a page tells you otherwise for free, ask what it would charge to prove it.
- Disclosure: free, and it solves the problem most people actually have. If the reason you want the mark gone is that the image is going somewhere that requires AI content to be labelled, then labelling it is the complete solution, not a compromise. We wrote up what the rules actually target separately, and Google's own policy pages are quoted in full on what Google's rules and forum say.
And if you have not generated the image yet, the cheapest answer of all is upstream of every tool on that results page: the setting that stops the mark being added. Free, permanent, and it works on the first try.
Sources
- Google, Generative AI Prohibited Use Policy (last modified 17 December 2024) — policies.google.com/terms/generative-ai/use-policy. Source of the quoted clause on misrepresenting the provenance of generated content.
- Google, Generative AI Additional Terms of Service (last modified 9 August 2023) — policies.google.com/terms/generative-ai. Source of the quoted wording on not attempting to bypass protective measures.
- Google DeepMind, SynthID documentation — ai.google.dev/responsible/docs/safeguards/synthid. Source of the quoted wording on embedding watermarks directly into generated content, the probabilistic nature of detection, and the three detection states. The robustness and limitations statements quoted above concern SynthID Text, not images.
- Our own observation of the results returned for this term, checked 30 September 2026. Described as a pattern only: no site is named, no ranking position is claimed, and no page's wording is reproduced. The claims attributed to “the pages shown” above are the claims those pages make about themselves.
- Our own tool's behaviour, measured on this site: only the pixels inside the watermark box are rewritten; the original dimensions are preserved; SynthID and C2PA metadata are left untouched. The 1K Nano Banana failure is documented with its measured numbers on the Nano Banana page.