A clip goes through this tool by holding one box over the visible Gemini badge for the whole run, not by finding the mark again on each frame. That is the single decision the whole method rests on, and it is what makes a badge that stays put come off cleanly and a mark that travels with the shot impossible to take.
The output is a re-encoded file rather than your original with a patch on it. There is no byte to replace on a clip: the frames come out of the decoder, the box is rewritten on each one, and they go back through an encoder. Video encoding is lossy, so the recompression covers the whole frame rather than the box. What comes back is a clean clip, not a bit-identical one.
What the tool is looking for is narrow: the visible Gemini mark, in one of the two geometries this site was calibrated against. It does not touch SynthID, the invisible signal written into the pixels, and it does not repair a mark that changes position as the shot moves.
Why one box, and not one box per frame
It is tempting to assume the better method is to re-locate the badge on every frame and repair each one exactly. In practice that is the method that fails visibly. A locator that lands exactly on the first frame and drifts a few pixels by the second does not look like a slightly softer repair. It looks like the mark, pulsing. The eye is far more sensitive to that shimmer than to a slightly soft patch.
So the box is placed once, from the corner geometry the template records, and reused across the run. The price of that choice is stated plainly: it only suits a badge that holds one position. A mark that tracks a subject, or drifts with a camera move, is a tracking problem, and tracking is a different instrument.
How to run it
If you searched for how to remove a Gemini watermark from a video, the steps below are the answer — with one boundary that decides whether they work at all. The steps are short, and the two checks worth doing before you start are shorter.
- Check that the badge holds still. Scrub the clip and watch the corner. If the mark stays at the same coordinates, the box method is the right one. If it moves, stop here.
- Drop the clip in. MP4, WebM or MOV, decoded in the tab you already have open. Nothing is uploaded, and no account is asked for.
- Let it align, then run. The tool scores both watermark geometries against the frame and keeps the one that lines up better. You can nudge the box by hand if the automatic choice is close but not exact.
- Download and check the result. The clip comes back re-encoded. The check below is the one that tells you whether the visible badge is actually gone.
What it cannot do
- A mark that moves. The box is fixed for the run. A travelling mark needs per-frame tracking, and this tool does not track.
- SynthID. The invisible signal is written into the pixel values and is designed to survive re-encoding. No setting here alters that.
- A mark that is not Gemini's. The tool is a template matcher for two known geometries. A platform badge, a stock overlay or a camera stamp is a different shape, and the template will not line up with it.
The check you can run on the result
There is no public check for a still that tells you whether an invisible mark made it through an edit. A clip has a check of its own, and it lives inside Google's own app. Gemini's verification tool takes images, video and audio from signed-in users: one file at a time, 100 MB or less, and video under 90 seconds.
The answer is not a yes or a no. If a SynthID watermark is detected, Google's help page says all or part of the video was created or edited by its models. If none is detected, the file was not made by Google AI, but it could have been made by another system. And for video specifically, the result names which parts of the clip a mark was detected in — a detection inside a segment does not extend to the whole of it.
That last line is the practical one. A clip's verdict arrives in parts, so “clean” is not a single fact about the file. It can be true of one stretch and false of the next.
The short version
If the visible badge sits in one place for the whole clip, this tool holds one box over it and rewrites that box on every frame, then re-encodes the result. If the mark moves, it is the wrong tool, and no setting on this page changes that. The invisible layer is not touched either way. What the mark is, and how to stop it being added before you generate, is the subject of the main Gemini page.
Sources
- Google, Video generation in the Gemini API — Veo, limitations section — ai.google.dev/gemini-api/docs/veo. Source of the statement that videos created by Veo are watermarked using SynthID.
- Google DeepMind, SynthID — deepmind.google/technologies/synthid/. Source of the wording that the watermark is designed to withstand changing frame rates and lossy compression.
- Google, Verify AI-generated images, videos, and audio, Gemini Apps Help — support.google.com/gemini/answer/16722517. Source of the file limits, the three possible results, the statement that a video result names which parts were detected, and the limitation that the check recognises Google AI tools only.
- Our own tool's behaviour, measured on this site: a clip in MP4, WebM or MOV is taken, one box is held for the whole run, the output is re-encoded, and audio is carried across rather than dropped.