gemini-watermark-remover: Reverse Alpha Blending Instead of AI Inpainting
A high-performance, 100% client-side tool for removing Gemini AI image and video watermarks, built with pure JavaScript using mathematically precise reverse alpha blending.
At a glance
- What is it?
- A JavaScript tool that strips Gemini watermarks locally by inverting the alpha blend that put them there. It ships as a web app, Chrome extension, userscript, CLI and an agent Skill, and the README is candid about what it cannot fix.
- Who is it for?
- Adopt it if you have Gemini-generated images or videos with the standard watermark and you want the processing to stay on your machine; the Chrome extension and userscript cover the browser path, and the gwr CLI plus the packaged Skill cover automation. Do not adopt it if your watermark was added by a different tool, or if you need a guarantee about the legal status of removing a provenance mark, which the README does not address at all.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 20 days ago.
- What is it written in?
- Mainly JavaScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- GargantuaX/gemini-watermark-remover5,750 ★ · +156
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| GargantuaX/gemini-watermark-remover | 5.6k | 5.8k |
156 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The problem: a watermark that is a blend, not an overlay
Gemini stamps a visible mark onto generated images and videos. The usual way to remove a mark is inpainting: an AI model guesses what pixels should have been there and paints over the region. That guess is a fabrication, and it shows on textured or high-frequency areas. This project takes the opposite route. The README describes the engine as using a mathematically exact Reverse Alpha Blending algorithm rather than unpredictable AI inpainting. If the watermark was composited onto the image with a known alpha value and a known colour, the original pixel can be recovered by algebra instead of by a model. The audience is therefore narrow and specific: people who have Gemini output, who know the watermark is the standard one, and who would rather run a deterministic calculation than a generative one. It is not a general-purpose object remover, and the README itself points elsewhere for that, to pilio.ai/image-watermark-remover, for watermarks the tool cannot handle. That self-limitation is the most useful thing in the document.
Reverse Alpha Blending and the local anchor search
The mechanism has two halves. The first is the blend inversion, which needs to know the watermark's size, its position, and the alpha and colour values used to composite it. The second half is finding those parameters. The README states that the tool automatically identifies watermark size and position using Gemini's known output catalog and local anchor search. So the parameters are not derived from the image alone; they come from a catalog of known Gemini output configurations, refined by searching locally for an anchor. This is why the approach is fast and why it is brittle in a specific way: it depends on the watermark matching something in that catalog. Everything runs client-side. The README states that all image processing happens locally in your browser or on your machine and that nothing is uploaded. The package layout supports that claim: package.json lists src/core/, src/runtime/, src/sdk/, src/cli/ and src/userscript/ among the published files, and the video path ships ONNX models (allenk-fdncnn variants at 86x74, 104 and 200) together with onnxruntime WebAssembly builds. So the still-image path is arithmetic, while the video path carries a neural model inside the client. That split is worth noticing, because the project's headline claim about not hallucinating applies most cleanly to images.
Installing the Chrome extension, the userscript, or the gwr CLI
There are four delivery paths and they are not interchangeable. The fastest is the hosted tool, which the README labels the recommended route: open geminiwatermarkremover.io, drag or click to select a Gemini-generated image, let the engine process it, then download. Nothing is installed and nothing leaves the browser.
The Chrome extension is for people who want Gemini pages handled automatically. The README gives this sequence: open the Chrome Web Store listing, click Add to Chrome and confirm, then open Gemini and let the extension process supported images. There is a popup toggle named Enable on Gemini, and the README says to turn it off and refresh Gemini if the page becomes slow or misbehaves. If the Web Store is unreachable, the README says the matching verified zip, named gemini-watermark-remover-extension-v*.zip, is available from GitHub Releases for manual unpacked installation. Chrome Web Store installs update automatically; a manually loaded unpacked copy does not, so you own that update path yourself.
The userscript needs a manager such as Tampermonkey or Greasemonkey. The README says opening the .user.js URL installs it automatically, and that eligible Gemini preview images are replaced in place, with Gemini's native Copy Image and Download Image actions returning processed results. The documented boundaries are explicit: no injected per-image controls, no popup UI, no bulk actions, and if preview processing fails the original page image stays visible and usable.
For automation, the package is published as @pilio/gemini-watermark-remover with a binary named gwr. The README shows the Skill being installed through skills.sh:
pnpm dlx skills add GargantuaX/gemini-watermark-remover --skill gemini-watermark-removerThat command fetches the packaged Skill from skills/gemini-watermark-remover/ so an AI coding agent can discover and invoke it; the README notes you should add flags like --agent, --yes or --copy only if your local setup needs them. The repository also carries a .env.example for optional research and benchmark scripts, with keys GWR_ALLENK_ROOT, GWR_SAMPLE_ROOT, GWR_VIDEO_SAMPLE_ROOT and GWR_DOWNLOAD_SAMPLE_ROOT pointing at local sample directories. Those are for local benchmarking, not for normal use. The npm package also exposes subpath exports including ./browser, ./node, ./video and ./image-data, so the engine can be called from a Node script or from page code without the extension.
Where the approach breaks down
The disclaimer is unusually direct, and it should be read before the feature list. It warns that unexpected results may occur due to variations in Gemini's watermark implementation, corrupted or unusual image formats, and edge cases not covered by testing, and states that the author assumes no responsibility for data loss, image corruption or unintended modifications. Translated into practical terms: if Gemini changes how it composites the mark, the catalog lookup and anchor search can miss, and the output may be wrong rather than merely unprocessed. Keep originals.
There is also a documented environment conflict. A note links to issue 3 and says to disable fingerprint defender extensions such as Canvas Fingerprint Defender, because they cause processing errors. That is not a bug in the tool so much as a collision between two things that both want to touch canvas pixel data. If your browser setup includes canvas spoofing for privacy, this tool and that setup are at odds.
Finally, the wrong-tool case. This removes the Gemini watermark specifically. It is not a general watermark remover, it does not handle marks from other generators, and the README routes those users to a separate product.
How it differs from an inpainting-based remover
The natural alternative is a generative watermark remover, which is exactly what the README positions itself against, and the difference is not cosmetic. An inpainting model reconstructs the region from surrounding context. It will handle watermarks it has never seen, arbitrary positions, and marks from tools other than Gemini, which is why the README can point users with unusual watermarks to pilio.ai/image-watermark-remover. The cost is that the reconstructed pixels are invented. On a gradient or a flat sky nobody notices; on fine texture, hair, or text the model's guess is visible as smearing or as plausible but wrong detail.
Reverse Alpha Blending has the inverse profile. When the watermark matches a known configuration, the recovered pixels are the original ones, not a reconstruction, so there is no invented detail. That is a narrower contract, and for archival or print work it is the better one. For a one-off image with an odd watermark, the generative route is simply more likely to produce something usable. Choosing between them is choosing between fidelity on known inputs and coverage on unknown ones.
Maintenance, releases and what the MIT licence does and does not cover
The repository is not archived and the last push was on 2026-10-26. The latest release is v1.0.46 from 2026-10-02, and the preceding releases, v1.0.45 and v1.0.44, both landed on 2026-09-22, so the release cadence is dense. For an extension and userscript, that matters more than it does for a library: the Chrome Web Store path updates itself, while the unpacked zip and the userscript URL are things you re-fetch. The userscript is served from the project's own domain, so it is not covered by any store's review process.
The licence is MIT, which is permissive and permits commercial use and modification. Two boundaries are worth stating plainly without giving legal advice. First, MIT covers the code, not the output: nothing in the licence speaks to whether removing a watermark from a given image is permissible in your jurisdiction or under the terms of the service that produced it. Second, the package bundles third-party components, including ONNX Runtime WebAssembly builds and the allenk-fdncnn ONNX models listed in package.json, and the MIT file at the repository root does not by itself tell you the terms those carry. If you redistribute the package rather than just use it, read the licences of those bundled files.
Editorial conclusion
Adopt it if you have Gemini-generated images or videos with the standard watermark and you want the processing to stay on your machine; the Chrome extension and userscript cover the browser path, and the gwr CLI plus the packaged Skill cover automation. Do not adopt it if your watermark was added by a different tool, or if you need a guarantee about the legal status of removing a provenance mark, which the README does not address at all. Before relying on it, verify two things on your own files: that auto-detection finds the watermark without manual adjustment, and that the output survives your later editing steps, since the README warns that variations in Gemini's watermark implementation and unusual image formats can produce unexpected results.
Frequently asked questions
How can I remove the Gemini watermark for free?
The README's recommended route is the hosted tool at geminiwatermarkremover.io: open the page, drag or click to select your Gemini-generated image, let the engine process it, and download the result. The Chrome extension and the userscript are also free and run locally in your browser.
How do I use gemini-watermark-remover?
Pick a delivery path: the online tool for a one-off image, the Chrome extension or userscript for automatic handling on Gemini pages, or the gwr CLI and the packaged Skill for scripting and agent workflows. The README states that the extension adds an Enable on Gemini toggle, and that the userscript processes eligible preview images in place plus Gemini's native copy and download actions.
Is gemini-watermark-remover free?
The code is MIT licensed and the README presents the online tool, Chrome extension and userscript as free to use. The README also promotes other pilio.ai products on the same page, which are separate from this tool.
How can I download Gemini videos without a watermark?
The README documents a video path at geminiwatermarkremover.io/video: upload or drag-and-drop a Gemini-generated video, let the tool detect and remove the watermark, then download the cleaned video. It states that video removal runs entirely in your browser and that no files are uploaded to a server.
Is it illegal to use AI to remove watermarks?
The repository does not address the legality of removing watermarks. Its disclaimer only covers technical risk, warning that unexpected results may occur and that the author assumes no responsibility for data loss, image corruption or unintended modifications.
Why does Gemini add a watermark?
The README does not explain Gemini's reasons for adding the watermark. It only describes the mark as something the tool removes, and notes that Gemini's watermark implementation can vary.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/gargantuax-gemini-watermark-remover)Star history chart for your README
[](https://hysenlabs.com/projects/gargantuax-gemini-watermark-remover)Was this useful?