PrivacyTools.io
Reviewed by Gabriel Bachmann
ExifEraser logo

ExifEraser

github.com/Tommy-Geenexus/exif-eraser
2 ratings so far*

File support: JPEG, PNG and WebP.

Threat level
Covered

A covered pick. Anyone can use it as a private drop-in, with no setup or know-how. Enough for most people. Threat levels

Screenshot of the ExifEraser website
Share
Our take

Choose this when the cleaning needs to happen on the phone itself, which is where most oversharing actually occurs, right before you hit send. It’s open-source, MIT-licensed, and refreshingly simple. The limit is narrow format support, JPEG, PNG and WebP only, so it won’t touch video or other file types. As a pre-share habit on Android it does its one job cleanly, just don’t expect it to be your only metadata tool.

MIT androidandroid-appexif-removergoogle-play-store
Stars
437
+1 this week
Forks
10
4 watching
Last commit
20d ago
healthy
Latest release
v6.5.1
4mo ago, 29 total
Star history
Issues
90% closed
9
open
85
closed
+0 / -0
opened / closed, last 4 weeks
Opened vs closed, last 12 weeks
Commits, last 26 weeks
13 commits, active 7 of 26 weeks
4 contributors since Jun 2020
Languages
  • Kotlin 100%
Updated daily from the GitHub API. Star tracking since Jun 15, 2026.

ExifEraser alternatives

ExifEraser license, in plain English
MIT
Permissive

Do almost anything: use, change, and ship it, even inside closed-source products. The only condition is keeping the copyright notice.

Permits

  • Commercial use
  • Modification
  • Distribution
  • Private use

Requires

  • License and copyright notice

Does not provide

  • Liability cover
  • Warranty

Why it matters: Permissive licensing lets anyone reuse this, including inside closed products. That is freedom to build on, but no guarantee that downstream copies stay open.

Plain-language summary of the project's license, not legal advice. Read the full text for the exact terms.

* Average ratings will show on this page once the threshold of 5 ratings is reached.