If you arrived here hoping to run a video through the tool on this site, it will not work — and we would rather say that on the first line than after you have picked a file. The tool reads PNG, JPEG and WebP images, one image at a time. There is no video path in it, no frame extraction, no audio handling, and no setting that turns any of those on.
The phrase is also not one problem. A mark on a clip can be a logo burned into every frame, a mark that moves with the shot, an overlay on a still inside a slideshow, or — the case that matters most for AI-generated footage — an invisible pattern written into the pixel values. Those need different tools. For the last one, Google's own documentation says the mark is designed to survive the very operations video editing consists of: changing frame rates and lossy compression.
So this page does something else. It sets out how to work out which of the four you have, what each one actually requires, and the check you can run on a finished clip that the pages on this term generally leave out. If what you have is a still image with a visible badge on it, that is what this site does, and the tool is the first item in the navigation above. If you have a clip, this page is the end of the road, and it is better to know that now.
A watermark on a clip is not one thing
Pages offering to remove a watermark from your video tend to describe a single job. In practice the phrase covers at least four situations, and the tool that suits one is usually the wrong tool for the next.
- A visible overlay, identical in every frame. A logo, a platform badge, a camera date stamp. It sits at the same coordinates at the same size for the whole clip. This is the case frame-by-frame repair is aimed at, and the only one where the word “remove” means what people assume it means.
- A visible overlay that moves. The mark changes position, and sometimes size, as the shot moves; it may track a subject. Repairing it needs tracking across frames, and a tracker that is right on one frame and marginally off on the next does not give you a clean clip. It gives you a mark-shaped shimmer.
- A mark on AI-generated footage, which is two layers rather than one. Google's developer documentation states plainly that Videos created by Veo are watermarked using SynthID. That is the invisible layer, written into the pixel values and spread across the frame. A generated clip can also carry a visible badge, which is a separate thing in a separate place and fails in a completely different way.
- A still image's mark inside a slideshow. If your “video” is a still, or a sequence of stills, you do not have a video problem at all — you have the still-image problem, repeated. That part we can help with: the frames themselves are ordinary images, and the tool handles them one at a time.
The results for this term present all four as one job. That is why a page can be entirely accurate about what it does and still not be the page you needed — and why the four questions further down are worth asking before you hand over a file.
The layer you cannot see is specified to survive the video pipeline
The single most useful sentence about video watermarks is in Google DeepMind's own description of SynthID. It says the mark is:
designed to stand up to modifications like cropping, adding filters, changing frame rates, or lossy compression
Read that list again, because two of the four items are not edge cases in video — they are the pipeline. Changing the frame rate is what happens when a clip is conformed to a different timeline. Lossy compression is what every delivery format does, and it happens again every time the file is uploaded to a platform and downloaded from it.
So for AI-generated footage, the invisible layer is explicitly specified to come through the operations that video editing consists of. That is the ceiling on this term: “remove watermark from video” can, at most, mean the visible layer. A page that lists AI video watermarks among the things it erases, and says nothing about the other layer, is describing half a job under a whole name — and the half it is silent about is the one the platform you post to is able to check.
The visible layer is worth one paragraph of its own, because it changed recently. Google made the visible mark optional in August 2026, and the same change covered its video editor. If the clip has not been generated yet, that switch sits upstream of every tool on this term; the details, with the source, are in the official setting.
The check you can run on a clip — and why it comes back in parts
For a still image there is no public way to test whether an invisible mark survived an edit; you can compare pixels, and that is the end of it. For video there is a check, and it is built into Google's own app.
Gemini's verification tool is available to signed-in users and covers images, videos and audio. The constraints that matter for a clip: one file at a time, 100 MB or less, and videos under 90 seconds. You upload the file and ask a question such as Was this video created or edited by Google AI?
What comes back is worth reading carefully, because it is not a yes or a no:
- If a SynthID watermark is detected, Google's help page says this means all or part of the image or video was created or edited by Google's AI models.
- If one is not detected, the file wasn't created or edited by Google AI, but it could have been created by other AI systems.
- And for video specifically: Gemini will state which parts of the video a SynthID watermark was detected. This doesn't mean it was detected in all parts of that portion of the video.
That third line is the one to sit with. A video verdict is reported in segments, and a detection inside a segment does not extend to the whole of it. So “clean” is not a single fact about a clip — it can be true of one stretch and false of the next. If you are checking whether an edit worked, that is the measurement, and it is a partial one by design.
Two further limits come from the same page. The check can currently only recognize content created by Google AI tools, even though other companies have begun adopting SynthID. And some files come back unclear, for stated reasons such as Not enough details to watermark or Likely too small an edit.
Why this tool stays out of it
Our scope is measured rather than aspirational. The tool reads PNG, JPEG and WebP images, one at a time, up to 60 megapixels, in the browser tab you already have open. It does not open video, it does not touch audio, and it does not remove SynthID.
The method is reverse alpha blending: recover the pixels under a known overlay by solving the compositing equation backwards. What that method needs is the frame as the generator wrote it — the picture with the mark composited on top, at full precision. The rest of this paragraph is reasoning rather than a measurement, and we will label it as such. A frame decoded out of a delivered video is not that picture. Video codecs store most frames as a prediction from other frames plus a lossy correction, so the values you get back are the output of that process rather than the pristine layer the blend was applied to. Reverse the blend on those and you are solving an equation with an input that has already been altered.
There is a second reason, and it is the one that decides whether the result is usable. A still-image repair is judged on one frame. A video repair is judged on the difference between consecutive frames. A method that is right on frame one and marginally different on frame two does not read as a slightly worse repair — it reads as the mark, flickering. We have not tested this tool against any video pipeline, and we are not going to write a page that implies we have.
If you are holding a clip, what actually helps
- Not generated yet. Use the generator's own setting if it has one. That is upstream of every editor on this term, it is free, and it is lossless. For Google's models, see the official setting.
- Generated, the mark is visible, and it sits in a corner you were going to trim anyway. Cropping or reframing is the simplest thing that works, and it is honest about its cost: you lose part of the picture and you change the framing. Covering the mark with an element of your own is the same trade in a different shape.
- Generated, the mark is visible, and the framing matters. You need a tool that states it handles video and does the repair across frames rather than on one of them. Ask it the questions in the next section before you hand over the file.
- The layer you cannot see. Nothing on this term changes it. If provenance is what you actually care about, the answer is not an editor — it is disclosure, which is what Google's own community answer recommends as best practice. We collected that answer, and kept it clearly separate from Google's policy text, in what Google's rules and forum say.
Four questions for any page that offers to take a watermark off your video
Only the first of these can be answered in ten seconds. The other three you can only read, and they are the ones that decide whether the word “removed” means anything at all.
- Does it accept the file, or does it want a link? A tool that asks for a link is not editing your file. It is editing a copy it fetched, at whatever resolution the platform chose to serve, so the clip can come back at a different size than the one you uploaded.
- Does it say which of the four kinds it handles? “Watermarks, logos and text” is a list of things, not a statement of method — and the four situations above are not equally hard.
- Does it say anything at all about the invisible layer? Silence is the most common answer on this term. What that layer actually is, and why it behaves differently from a logo, is on whether SynthID can be removed.
- Does it tell you how to check the result? This is the one that matters. A check for video exists, it is described above, and a page offering to clean a clip without mentioning it is asking you to take the outcome on faith.
The short version
If the mark you want gone is on a clip, this site cannot help you, and the honest routing is: use the generator's own setting before the clip is created; if the clip already exists, use a tool that says it handles video and repairs across frames rather than on one of them; and before you publish, run the check on the result, because for video that check exists and it reports in parts. If what you actually have is a still image with a visible badge in the corner, that is the job this site does, and the tool is the first item in the navigation at the top of this page.
Sources
- Google, Video generation in the Gemini API — Veo, limitations section — ai.google.dev/gemini-api/docs/veo. Source of the quoted statement that videos created by Veo are watermarked using SynthID, quoted from the model documentation's watermarking note. (The quote now lives on the Veo model page; the parent Video generation page at /docs/video was reindexed to list the video models and no longer carries the watermarking note. Re-checked 1 October 2026.)
- Google DeepMind, SynthID — deepmind.google/technologies/synthid/. Source of the quoted wording on what the watermark is designed to withstand, including changing frame rates and lossy compression, and of the statement that SynthID embeds watermarks directly into AI-generated images, audio, text or video.
- Google, Verify AI-generated images, videos, and audio, Gemini Apps Help — support.google.com/gemini/answer/16722517. Source of the quoted wording on the verification tool, the file limits for video, the three possible results, the statement that a video result names which parts of the video were detected, and the stated limitation that the check recognises Google AI tools only.
- Our own observation of the results returned for this term, checked 1 October 2026. Described as a pattern only: no site is named, no ranking position is claimed, and no page's wording is reproduced.
- Our own tool's behaviour, measured on this site: PNG, JPEG and WebP images are accepted one at a time, up to 60 megapixels, and video files are not accepted. The section on why the method does not extend to decoded video frames is labelled in the text as reasoning, not as a measurement.