Strip every trace before you share.
Remove or randomize GPS, camera, and timestamp data from your JPEG photos. Everything happens locally in your browser — your files never touch a server.
Drop JPEG photos here
or browse your files — .jpg and .jpeg, any number at once
No files selected yet.
Three steps, no waiting on an upload.
Because your files never leave the browser, there's no queue, no progress bar for a network transfer — just local processing that finishes in milliseconds.
Add your photos
Drag JPEGs into the tool or pick them from a folder. Process one photo or a few hundred in the same batch.
Choose remove or randomize
Strip every Exif tag outright, or keep the file structure intact and swap the real values for plausible fake ones.
Download your files
Save a single photo directly, or grab everything at once as a ZIP archive — packaged locally, downloaded instantly.
Every photo carries more than the picture.
Modern cameras and phones quietly embed a surprising amount of detail into the Exif block of every JPEG. Here's what Metadata Erase clears out.
Pick the approach that fits.
Delete metadata outright
The most direct option. Every Exif tag is stripped from the file, leaving the image data untouched and the metadata block empty.
- Smallest possible file size
- No trace of the original camera or location
- Best default for sharing publicly
Swap in decoy data
Keeps an Exif block present — useful if a platform expects one — but every value is replaced with unrelated, made-up data.
- Fake camera make, model, and lens
- Randomized GPS coordinates and timestamp
- Your real data is discarded either way — nothing is reused
Supported format: JPEG
Metadata Erase currently supports .jpg and .jpeg files (uppercase or lowercase extensions both work) — the format that carries the overwhelming majority of Exif metadata from cameras, phones, and photo editors. PNG, WebP, and HEIC support may follow.
Common questions
Your photos are never uploaded. The moment you drop a file into the tool, it's read straight into your browser's memory with the File API and processed there. There is no server-side component to this tool that ever receives your image data — we couldn't see your photos even if we wanted to.
Exif (Exchangeable Image File Format) is a small block of structured data that cameras and phones write into a photo alongside the pixels — things like GPS coordinates, camera make and model, lens details, and the exact date and time the photo was taken. It's invisible when you look at the image, but it travels with the file wherever it goes.
Removing is the simpler, more common choice — it leaves a clean file with no Exif block at all. Randomizing is useful in the rare case where a platform or workflow expects some metadata to be present; it fills that block with unrelated, made-up values instead of leaving it empty.
Not yet. The current version supports JPEG (.jpg / .jpeg) files, which is where the vast majority of camera and phone metadata lives. Broader format support is on the roadmap.
No. Only the metadata block is touched — the actual image data (the pixels you see) is copied through unchanged, so there's no re-compression or quality loss.
No account and no daily limit. The practical ceiling is your device's memory, since everything runs locally — most laptops and phones handle a batch of a few hundred photos without issue.