MetaPurge

About MetaPurge

A metadata remover should not require handing your files to a stranger. MetaPurge reads the container format in the browser, rewrites it there, and verifies its own output.

Why it exists

Search for "remove EXIF online" and most results ask you to upload the image. That is a reasonable engineering shortcut and a poor privacy decision: the file you are trying to sanitise is copied to a server you do not control, together with the coordinates you were trying to remove.

Browsers have had everything needed to do this locally for years — typed arrays, Blob URLs, File APIs, a canvas for the awkward formats. MetaPurge exists to show that the upload step was never necessary.

How it works

The app sniffs the real format from the file's magic bytes rather than trusting the extension, then hands it to a container-specific editor. JPEG segments, PNG chunks, WebP RIFF chunks and GIF blocks are parsed into a common field model, which is what the dashboard renders.

When you purge, the selected fields are removed at the container level and the compressed image data is copied across untouched — so a lossless format stays lossless. The output is then parsed again: no selected field may survive, GPS must be gone, and the compressed pixel payload must hash identically to the input.

Full technical detail, including the exact segments removed per format, is in the verification guide and the project README.

Who builds it

MetaPurge is built and maintained by Rajat Malik, a frontend architect based in Gurgaon, India. He works on large web products by day and publishes open-source tools, including browser extensions and npm libraries, under the same standards used here: no unnecessary dependencies, accessible interfaces, and measurable outcomes.

Editorial standards

The guides are written to be checkable. That means:

  • Tag names and numbers come from the published EXIF and IPTC specifications, not from memory of a blog post.
  • Claims about third-party platforms are phrased as behaviour observed at the time of writing, because those platforms change without notice.
  • No statistics are invented. Where a number would be useful but unknown, the guide says so instead of guessing.
  • Pages carry a visible last-updated date, and are revised when the underlying behaviour changes.

Independence

MetaPurge is not affiliated with, endorsed by, or operated by Google. Google AdSense is used to serve advertising alongside the content, and Google Analytics is used to count visits. Neither service receives your images: files are processed in the browser and are never sent to an ad or analytics endpoint. The privacy policy explains exactly what is collected.

Contact

Bug reports, corrections and questions all go to the same place: contact@rajatmalik.dev. The contact page explains what to include so a report can be reproduced.