METADATA
ЗАГРУЗИТЬ
ФАЙЛ
ПЕРЕТАЩИТЕ КАРТИНКУ ИЛИ НАЖМИТЕ
ПЕРЕТАЩИТЕ КАРТИНКУ ИЛИ НАЖМИТЕ
Tool guide
A phone photo carries far more than the picture: GPS coordinates, camera model, serial number, and a timestamp down to the second. Post that file on a marketplace listing or a public forum and your home address is two clicks away. This tool takes JPEG and PNG, parses the EXIF block on your own device, shows which fields were actually present, and rebuilds a clean copy from the pixels alone. See also: fit the stripped photo under a size limit, change the width and height of the shot, erase the background behind the subject.
On Windows, open the file properties, go to Details and look at the GPS section. On macOS, use Get Info and the More Info tab. Empty latitude and longitude rows mean the geotag is gone. The tool shows the same fields in the browser before cleaning, so you can compare source and result without leaving the page.
They drop EXIF when the picture travels as a compressed photo, but sending it as a document carries every tag through untouched. Email attachments, cloud drives and marketplace uploads keep the original as-is too. Cleaning the file yourself before sending is the only reliable path.
The copy is rebuilt from decoded pixels, so a JPEG is re-encoded once — visually indistinguishable, but not a byte-identical file. PNG is lossless, so those pixels match exactly. If you need the untouched original for archiving or for a print lab, keep a separate copy before you clean it.
The file input is limited to JPEG and PNG. HEIC from an iPhone, camera RAW, TIFF and WebP will not open here. The simplest route for iPhone shots is to switch the phone to Most Compatible capture under Settings, Camera, Formats, or re-save as JPEG first, then clean the result.
No — the page handles one file per pass: load, strip, then clear it with RESET PROCESS. That gets tedious past a dozen images, and it is fairer to say so than to pretend otherwise. For bulk work a desktop utility such as exiftool is the right tool.
Yes. Parsing and re-encoding run in the browser rather than on a server, so mobile Chrome and Safari handle it. Memory is the real limit: a 40–50 megapixel shot can stall the tab on an older handset, and those files are easier to process on a laptop.
No. The parsing and rebuilding happen in your own tab, and the page makes no network request carrying the image. You can verify it yourself: open the Network panel in developer tools and run a clean — no upload appears.
Before: IMG_4417.JPG, 4.1 MB. EXIF: GPS 55.7539 / 37.6208, Apple iPhone 14 Pro, 2026:08:12 19:04:33, ISO 400
After: IMG_4417-clean.jpg, 4.0 MB. No EXIF block; resolution and colour untouched
Before: screen.png carrying a Software tag and the author's working directory path
After: screen.png with the text chunks gone, pixels identical
Your rating and feedback help decide what to improve next.