Why does every Google Omni clip carry a watermark?
Google Omni — the AI video model exposed through Gemini and AI Studio — bakes a small sparkle watermark into the bottom-right corner of every clip it generates as a visible provenance signal. It is visible, intentional, and survives most naive edits like re-uploading to a video editor. This guide walks you through removing the Google Omni watermark cleanly, without re-shooting, without re-encoding manually, and without losing the audio track.
What does the Google Omni watermark look like?
On a 1280×720 clip the mark is roughly 96×96 pixels, anchored about 64 pixels from the right and bottom edges. It uses a semi-transparent white logo composited onto the rendered video frame with alpha blending. Larger renders use a proportionally larger mark; the underlying overlay shape matches the standard Gemini image watermark, just applied to every frame of the video.
Why can't you just crop the watermark out?
Cropping breaks aspect ratios — your 16:9 clip becomes a non-standard frame that no marketplace, ad network, or social platform accepts cleanly. Re-encoding through a video editor with a black box covering the mark is uglier still: viewers immediately notice the patch, and the censor look damages credibility for ads, product demos, and portfolio reels.
How does per-frame reverse alpha-blending remove the watermark?
Erasio reverses the alpha-compositing math that put the watermark there. For every frame of the clip it computes original = (frame − α × overlay) / (1 − α), which restores the underlying pixels the watermark was hiding. The audio track is copied across untouched, and the output is re-wrapped as a clean MP4 with the original duration and resolution preserved.
Method 1: How do you remove a Google Omni watermark automatically with the Chrome Extension?
If you generate Google Omni clips on Gemini regularly, install the Erasio Chrome Extension. It hooks into the Gemini video download flow and strips the watermark before the file lands in your Downloads folder — so every clip you save is already clean.
- Install Erasio from the Chrome Web Store
- Open gemini.google.com and generate or open any Google Omni video
- Click the download button
- The MP4 saves clean — no watermark, original audio, same resolution
Method 2: How do you clean an already-saved Google Omni MP4 with the online tool?
Already saved a watermarked Google Omni clip? Use the Erasio Online Tool to clean it after the fact. Everything runs in your browser via WebCodecs — the file never leaves your device.
- Open the Erasio Online Tool
- Drop your watermarked MP4 onto the upload area
- Wait for the per-frame processing to finish (typically a few seconds per second of video)
- Download the clean MP4
Does removing the watermark reduce video quality or strip the audio?
No. The output is re-encoded at a high bitrate so visual quality stays effectively the same, and the original audio track is copied verbatim — no transcoding, no perceptible loss. The only thing missing from the output is the watermark itself.
FAQ
Does it work on all Google Omni clips?
Yes — Erasio supports every Google Omni resolution and the standard Gemini sparkle pattern. If Google changes the watermark in a future update, Erasio ships a matching update at no extra cost.
Is it private?
Yes. All processing runs locally in your browser. No video file is uploaded to any server. Pre-launch product demos and embargoed campaign creative stay on your machine.
Can I do this on mobile?
The online tool works on mobile browsers, but video processing is fastest on desktop where modern WebCodecs APIs perform best.
What happens inside the file when you remove the watermark
An MP4 is a container, not a single stream. It holds encoded video and encoded audio side by side, plus timing metadata that keeps them in sync. Understanding that structure explains why some tools wreck your audio and others do not.
Erasio demuxes the container first, separating the two streams. The audio is set aside immediately and never decoded — it is copied into the output exactly as it arrived, which is why there is no generational loss on the sound no matter how many times you process a clip.
The video stream is decoded frame by frame through WebCodecs. Each frame gets the same inverse alpha transform applied to the watermark region, because the mark sits in the same place on every frame. A 10-second clip at 24fps means 240 individual patches, all computed on your own machine.
Then the patched frames are re-encoded and re-muxed with the untouched audio into a new MP4. Re-encoding the picture is genuinely unavoidable here — every frame changed, so the compressed representation has to be rebuilt.
How to judge whether a watermark remover degraded your clip
Since the video stream must be re-encoded, the question is not whether re-encoding happened but whether it was done well. Three things separate a good result from a bad one, and you can check all of them yourself.
First, compare file sizes. If your 40 MB source came back as 6 MB, it was re-encoded at a fraction of the original bitrate and detail has been thrown away across the entire frame — not just where the watermark was. Erasio derives the output bitrate from the source with headroom rather than applying a fixed formula, so sizes stay in the same neighbourhood.
Second, check the resolution and frame rate in your player's file info. Some tools silently downscale to speed processing up. Erasio passes source width, height and frame rate straight through to the encoder; there is no downscaling step anywhere in the pipeline.
Third, scrub through the clip rather than pausing on one frame. The most common failure with per-frame detection is drift: the mark disappears on most frames and flickers back on others. That shimmer is far more visible to a viewer than a single imperfect frame, and it is the artefact worth looking for.
What removal does not change
A cleaned clip loses the visible sparkle and keeps everything else — resolution, frame rate, duration, audio. What it does not lose is provenance. Google embeds SynthID across generated frames as an invisible signal, it survives re-encoding, and Erasio does not target it. Your clip still identifies as AI-generated to anything that reads for SynthID.
That boundary is deliberate rather than a limitation we are working around. The visible mark interferes with legitimate use of video you generated and own — ad platforms reject watermarked creative, clients notice it in previz reels. The provenance signal serves a different purpose, and removing it is not what this tool is for.
