Open-source project
rosuH/EasyWatermark avatar
rosuH/EasyWatermark

Easy Watermark: An Offline Android App for Watermarking Sensitive Photos

Project brief: Securely, easily add a watermark to your sensitive photos. .

1,888 stars154 forksKotlinMIT

At a glance

What is it?
Easy Watermark is an open-source Android app that adds text or image watermarks to photos entirely on-device. This review covers its security model, features, installation, limitations, and alternatives.
Who is it for?
Adopt Easy Watermark if you need a simple, offline way to watermark ID photos, hand-held ID cards, or preview images before sharing, and you value no tracking or crash reporting. Do not use it if you expect protection against information leakage, since the README itself admits it only reduces the value of leaked data.
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 3 days ago.
What is it written in?
Mainly Kotlin, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on September 15, 2026, and from our analysis. They are not legal advice.

DEEP OPEN-SOURCE ANALYSIS

What Easy Watermark Solves and Who It Is For

Easy Watermark targets a narrow but real problem: adding a visible watermark to a photo before you send it somewhere. The README gives concrete examples: submitting ID card photos, hand-held ID photos, project previews, or sample images that you want to protect from misuse. The app is for individuals who need a quick way to mark an image as intended for a specific purpose, such as 'this photo is for xx for xxx purposes only.' It is not a DRM tool or an encryption layer. The developer explicitly states the limit: the app cannot prevent uploads or leaks, it can only reduce the value of the information if it leaks. So the target user is someone who wants a low-friction, offline way to add a deterrent watermark, not a guarantee of security.

Security by Design: Offline Processing and No Permissions

The core security claim is that everything happens on the device. The README says the code is fully open source, and the app is 'pure offline,' meaning no network calls are made for processing. On Android 10 (API 29) and above, the app requires no permissions at all. That is a strong statement: no storage permission means the app cannot scan your entire gallery, and it cannot upload anything. For users on API 28 and below, storage permissions are needed to access and save photos, which is a normal limitation. The app also omits any analytics, tracking, device IDs, or crash reporting. The developer notes that if you crash, you have to manually share the crash info, which is a trade-off: no telemetry means no automatic bug reports, but also no data leaving your device. This design is consistent with the project's stated goal of 'what's yours is yours.'

How Watermarking Works: Layout, Style, and Content

The app supports two types of watermark content: text and image (the latter are called stickers). The layout engine repeats the watermark across the entire photo, with configurable horizontal and vertical intervals. That means you can tile a watermark over the whole image, not just place a single label in a corner. Style options include font color, font style, transparency, font size, and rotation angle. The README suggests turning down the transparency so you do not block key information, which is a practical tip for ID photos where the text must remain legible. The mechanism is straightforward: you pick a photo, choose text or an image, set the style parameters, and the app renders the watermark onto the photo. There is no mention of batch processing or editing after export, so it is a single-photo workflow.

Getting It Running: Installation and Usage

You do not build from source unless you want to; the developer provides pre-built binaries. The README lists four developer-led channels: GitHub Releases, Google Play, F-Droid, and Coolapk. The Google Play version is paid, while the others are free; the README notes the paid version is the same code and is a way to support the developer. F-Droid is a trusted open-source repository, and GitHub Releases always has the latest version. The app is written in Kotlin, but you do not need a build command to use it. For developers who want to fork, the repository is on GitHub under the MIT license. The usage flow is: install the app, open a photo, set your watermark text or image, adjust transparency and other style options, and save. The README does not provide a command-line interface or a library API; it is a standalone Android application.

Limitations and Cases Where It Is the Wrong Tool

The most obvious limitation is that the developer openly admits the watermark is not a security guarantee. The README says, 'Even if it's (probably) useless in the end, at least you can disgust the leaker a bit.' That is a honest assessment: a determined leaker can crop, blur, or edit out a watermark. The app also requires manual setup for each photo; there is no batch mode mentioned, so watermarking a large set of images would be tedious. Another limitation is the permission requirement for older Android versions. If you run Android 9 or lower, you must grant storage permissions, which weakens the privacy stance. The app is also Android-only; there is no iOS or desktop version. If you need to watermark photos on a computer or an iPhone, this is not the tool. Finally, the design is tied to Material Design, and the UI is credited to a designer, so customization of the app's interface is not something you can do without violating design rights.

Alternatives: How They Differ in Approach

A common alternative is a desktop tool like ImageMagick, which can add text watermarks via command line. The difference is fundamental: ImageMagick is a general-purpose image processing library, not a dedicated privacy app. It runs on your computer, so it can handle batch processing and scripting, but it does not have a mobile UI and it does not make any privacy claims. Another alternative is a cloud-based watermarking service, but those require uploading your photos, which defeats the purpose of keeping sensitive images local. Easy Watermark's approach is to keep everything on-device and to offer a simple, one-tap mobile experience. The trade-off is that you lose the flexibility of a scripting tool. For a user who wants to watermark a single ID photo on their phone, Easy Watermark is more direct. For a developer or a user with a batch of images, ImageMagick or a similar tool is more efficient.

Maintenance, Licensing, and Upgrade Cost

The project is under the MIT license, which allows free use, modification, and distribution, including commercial use, with attribution. This is a permissive license, so you can fork and adapt the code without legal restrictions beyond preserving the copyright notice. The repository has recent activity: the last push was October 2025, and version 2.10.0 was released on the same day. There are also releases from August 2024 and September 2024, indicating ongoing maintenance. However, the README does not describe an upgrade mechanism or a changelog, so you have to check the release notes on GitHub for changes. The app is not a library, so upgrading means installing a new APK, not updating a dependency. The maintenance cost for a user is low: you download a new version from the same channel. For a developer who forks, the cost is the same as any Android project: you need to keep up with Android SDK changes, but the MIT license gives you freedom to do so.

Editorial conclusion

Adopt Easy Watermark if you need a simple, offline way to watermark ID photos, hand-held ID cards, or preview images before sharing, and you value no tracking or crash reporting. Do not use it if you expect protection against information leakage, since the README itself admits it only reduces the value of leaked data. Before adopting, verify the watermark rendering quality on your specific images, test the interval and rotation settings, and confirm the app is available from a trusted channel like F-Droid or GitHub Releases, not third-party mirrors.

Official sources

  1. Official README
  2. Project repository
  3. Release notes
Community notes

Community notes