Images from Gemini — the model everyone calls Nano Banana — come out with a small sparkle stamped into one corner. It is composited over the finished picture rather than drawn into it, which is what makes it removable: the badge is a lid, and the photograph underneath it is still a photograph. This page finds where that lid sits, discards those few thousand pixels, and rebuilds the area from the picture surrounding it. Everything happens in this browser, and every image you drop in is processed, not just the first.
A badge that is composited onto a finished image is a different problem from one that is drawn into it. Gemini writes its sparkle over the picture as a partly transparent layer, so the pixels underneath were once a real photograph and the question is only how to get them back. Knowing the glyph exactly would let you invert the blend and recover the original arithmetically; not knowing it means treating the badge as a hole and rebuilding it from its surroundings instead. The second approach is less exact and far more robust, because it does not depend on which version of the glyph was used, what size it was rendered at, or whether the file was re-encoded afterwards and the original alpha no longer holds.
Finding the badge is the harder half, and a fixed coordinate does not do it. The inset has moved between model versions and the newer ones calibrate it per aspect ratio, so a page that assumes a position will confidently repair empty sky on a portrait crop. What identifies a glyph reliably is that it is bright and thin at once: a morphological top-hat keeps small bright structures and discards large ones, which separates a stamped mark from an overexposed sky that a brightness threshold would flag just as loudly. Judging what survives on how far it stands out from the rest of the corner, rather than on how bright it is, is also what lets a white badge on a pale background be found at all — its absolute lift is barely ten levels, and against a backdrop that varies by almost nothing that is still unmistakable.
Doing this in the page rather than on a server changes what the tool is for. Generated images are often drafts nobody intends to publish — a mock-up for a client, a character sheet, something with a face in it — and a free web service that takes an upload has a retention policy most people have not read. Here the files never leave the tab, which also sets the real limit: a batch is bounded by the memory of the device rather than by an upload quota, and images are decoded one at a time because decoding a dozen large ones at once is the quickest way to have a browser tab killed outright.
The visible one: the small sparkle badge that Gemini and Nano Banana composite into a corner of a generated image. The figure usually quoted is 48 pixels square inset 32 pixels on images up to 1024 across, and roughly double that above it — and no picture measured here matches it. Averaging 56 Gemini pictures over a window pinned to the bottom-right corner leaves the badge standing while everything else averages away, and what is left is a four-pointed star about 42 pixels across whose centre sits 98 pixels in from both edges of a 687x1024 original. Two pictures in the set at a different size carry it 103 pixels in, which is the same figure scaled by the size of the picture. That measured offset is what the page looks at, and it turned out to be far more dependable than searching the corner for anything bright and thin.
No, and it does not try to. SynthID is a second, invisible watermark that Google spreads across the whole image in the frequency domain rather than placing in a corner. Nothing here touches it, so an image processed on this page is still identifiable as AI-generated by a detector that looks for it. Removing the visible badge and removing the provenance signal are different things, and only the first one is what this tool does.
No. Two steps, both arithmetic. First the page looks for a patch elsewhere in the same image whose surroundings most closely match the surroundings of the badge, so a repair over brickwork is made of that brickwork and a repair over sky is made of that sky. Then it solves a Poisson equation across the hole: the copied patch supplies the texture, and the real pixels bordering the hole supply the colour, so the edge of the repair equals the pixels it abuts exactly. There is no seam to feather because there is no seam. Where nothing nearby is a good enough match it falls back to the smoothest surface that meets the boundary, which is right for a plain background and a soft blur on a busy one.
Not one pixel, as long as you save as PNG. The repair writes only inside the box shown on the card, and PNG stores what it is given. Choosing JPEG or WebP re-encodes the whole image, which is a small loss everywhere rather than a large one anywhere — usually invisible at 95, and the right choice if the original was already a JPEG, since re-saving a photograph as PNG can multiply the file size several times over.
Yes — that is what Remove from all does. Select any number of files in the picker, or drag them in together, and each one is detected and repaired in turn with a count showing progress. They are processed one at a time on purpose: decoding a dozen large images simultaneously is the fastest way to have a browser tab killed for running out of memory. Download ZIP then packages every finished image into one archive.
Because it would rather say so than claim a find it cannot support. Detection matches a model of the glyph — a four-pointed star drawn from a formula, not a copy of Google's artwork — against the place the badge is measured to sit, then scores how well the shape fits and how far it lifts the whiteness of the picture. What defeats it is contrast rather than clutter: a half-transparent white sparkle over a bright spray of water or a near-white sky leaves almost nothing to match, and two of the 56 pictures measured came out exactly that way. The page still repairs the measured position and labels the card, so "not found" is an instruction to look at the two magnified squares rather than a refusal. Setting the corner by hand is what a picture from a different generator needs.
Try three things in order. Raise the Margin slider by a few pixels, since a leftover outline is usually compression spill just outside the detected box. Then check what the badge is sitting on — a repair reads as a smudge mainly where it crosses a hard edge, so a badge over a doorframe or a horizon is the hard case. If it still shows, switch to Crop the strip off, which cannot go wrong in that way.
For your own generated images, generally yes — and it is worth reading the terms attached to whichever model produced them, because they differ and they change. What is not all right is running someone else’s work through it: a watermark on a stock photograph, a photographer’s signature or a studio’s mark is there to assert ownership, and removing it does not transfer any. The invisible provenance mark on an AI image is also untouched here, which is deliberate.