What it needs, and what it asks.
An Android phone, a photo with a repeating mark, and some patience on the first run. The rest is below.
Quick facts
| Topic | What holds |
|---|---|
| Android version | Android 8.0 (API 26) or later. |
| Photos in | Images chosen in the Android picker, or shared to the app from another app. |
| Photos out | Saved to the gallery as JPEG or PNG (on Android 10 and later in Pictures/WatermarkRemover), or shared as PNG. |
| Permissions | No access to your photo library: the app sees only the images you pick or share. It uses the network only to send reports, and makes no connection when it starts. |
| Where it runs | On the phone. Learning and removal need no connection. |
| Engine | A Hardware Test measures the phone and picks the removal engine. It is the first item in the ⋮ menu on every screen. |
| Fill model | The standard build includes the MI-GAN model on the phone; the lite build uses a classical fill instead. |
| One-photo removal (0.6.0) | Needs about 1.2 GB of free memory and the full (non-Lite) build; the Lite build does not include it. About 20 s per 12-megapixel photo on a 2025 flagship phone and about 100 s on a 2020 mid-range phone (timed on one 12-megapixel test picture). |
| Long jobs | A long removal keeps running with a notification while you use other apps. |
Which phones have run the app is on the devices page, from reports of real devices only.
Questions
Does it work offline?
Yes. Learning and removing the mark run on the phone and need no connection. A report you send while offline waits on the phone and is sent later.
Can it remove a single logo?
From 0.6.0, yes, with limits. The one-photo path uses a model on the phone to estimate the mark and undo it, and on our test set the median improvement was +6.5 dB, with some results modest (examples). It needs about 1.2 GB of free memory and the full build. Older versions, and the Lite build, cannot do this from one photo: the app learns a mark by comparing copies, and the same logo in the same place on two or more photos gives mixed results, so check the preview before saving (why).
Why does the first analysis take a while?
Before it removes anything, the app learns the mark from your photos, and that is the slow part. The app’s own estimate is about a minute on mid-range phones for the first analysis; that is an estimate, not a measured average across phones.
Why does fine detail under the mark look painted?
Where the mark hid the picture completely, nothing of the original is left to recover, so that area is filled in from its surroundings: by the MI-GAN model on the phone in the standard build, or by a classical fill in the lite build. That area is a reconstruction, not the original.
What leaves the phone?
No photo and no result. The app can send reports, each with its own switch in Settings: feedback and result ratings you choose to send (a screenshot only if you attach one), crash and memory reports (on by default), Hardware Test results (on by default), and self-test results from a check the app runs on sample images built into it, once per install and again after some app or system updates. Opening the app makes no network connection of its own. The privacy policy lists every field.
Is it free?
Yes. The core features are free and work offline.
How do I send feedback?
Tap the feedback button in the corner of the screen, or choose Send feedback in the ⋮ menu on any screen. The report attaches the technical details needed to look into a problem, and you can add a screenshot. There is no support email; the app is the channel.
Where do I get it?
On Google Play, where it is listed as Watermark Remover (Offline). It has been available to everyone there since 15 October 2026; before that it was a closed test.
Can I remove any watermark?
The app restores photos. Whether you may alter a particular photo is a question of the photographer’s or owner’s rights, which the app cannot judge for you. Use it on photos you have the right to restore.