Two jobs, one pass
The usual routine is clumsy: convert HEIC to JPG with one tool, then run the JPGs through an EXIF remover, then hope you didn’t upload the wrong folder. This page folds both into one. Each photo is decoded, converted and written out as a fresh JPG with no metadata block at all.
Because a new JPG is being created anyway, nothing has to be “deleted” from it. The fields simply never get written.
What’s removed and what stays
| Data | In the JPG? |
|---|---|
| GPS location | No |
| Date and time taken | No |
| Phone model, lens, exposure | No |
| Other EXIF fields | No |
| Colour profile (Display P3) | Yes, so colours stay accurate |
The colour profile isn’t about you, it’s about the image. Dropping it would make iPhone photos look dull on some screens, so it stays. If you’d rather have a plain sRGB file, switch the Colour option.
When a clean JPG is the right call
- Listing items for sale. Buyers see the photo, not your street.
- Posting to forums, community sites or your own blog, where files are often served as uploaded.
- Sending photos to people you don’t know well, such as landlords, insurers or customer support.
- Publishing on behalf of someone else, where their device or schedule shouldn’t be visible.
A heads-up about dates
Removing timestamps means photo apps can’t sort these JPGs by when they were taken. They’ll fall back to the file date, which is today. That’s fine for one-off sharing but annoying in an archive. For your own library, use HEIC to JPG, which keeps the date and drops only the location.
Prefer to stay in HEIC? Remove HEIC metadata cleans the original losslessly without converting. And to double-check any file, open it in the HEIC metadata viewer.
Quietly local
You’re removing metadata for privacy, so a tool that uploads first would defeat the point. Here, the WebAssembly decoder runs in your tab and writes the clean files straight to your downloads. Close the tab and the photos are gone from memory.