About the Handiwork Image Metadata Remover
Most phone and camera photos carry a hidden layer of data alongside the picture itself: the device make and model, the exact date and time a photo was taken, the software that last touched the file, and — often — the precise GPS coordinates of where it was shot. The Image Metadata Remover reads that EXIF, IPTC, and XMP data from a JPG, PNG, or WebP file, shows you exactly what it found, and then produces a cleaned copy with that data stripped out. Everything happens locally in your browser; the photo is never uploaded.
How to use the Handiwork Image Metadata Remover
- Add one or more JPG, PNG, or WebP photos by dragging them in or choosing files.
- Review the metadata found for each photo, including camera details and any GPS coordinates.
- Adjust the JPG/WebP output quality if needed, then remove metadata to produce cleaned copies.
- Download each cleaned photo individually, or download all of them as one ZIP file.
Why photos carry GPS coordinates and device details
Most smartphones and many cameras embed EXIF (Exchangeable Image File Format) data in every photo by default. Alongside technical details like exposure and lens, this can include GPSLatitude and GPSLongitude tags — the exact spot the photo was taken, often accurate to a few meters — plus the device make, model, and a timestamp. This data is genuinely useful for photo apps that sort by location or date, but it travels with the file wherever it goes: email attachments, uploads to marketplaces, and file-sharing links can all carry it forward unless something strips it first.
What this tool reads and displays
For each photo, the tool parses the EXIF IFD0 and Exif sub-IFD for camera make, model, lens, software tag, capture date, and orientation, and the GPS IFD for latitude and longitude (converted to decimal degrees with a link to view the location on a map). For JPGs, it also reads the Photoshop IPTC-IIM block for a title, caption, byline, credit, and keywords when present, and detects embedded XMP packets in JPG, PNG, and WebP files, extracting a handful of common XMP fields such as creator and creation date on a best-effort basis. Fields the parser did not find are shown as a dash — that means nothing was found in that specific tag, not that the file is provably free of every other identifying detail.
How the cleaning actually works
Removal does not edit the EXIF/IPTC/XMP blocks in place. Instead, the tool decodes the image and redraws it onto an in-memory canvas at its original pixel dimensions, then exports a new file with canvas.toBlob(). Canvas export only knows about pixel data — it has no mechanism to carry EXIF, IPTC, or XMP segments into the output — so the new file is metadata-free by construction rather than by selectively deleting known tags. This is the same canvas behavior the Image Resizer tool documents and relies on for its own output.
What can change visually after cleaning
Current versions of Chrome, Firefox, Safari, and Edge decode JPEG orientation automatically before drawing, so a photo that displayed right-side-up because of its EXIF Orientation tag will typically still display right-side-up after cleaning, even though the tag itself is gone. This is a browser decoding behavior, not a guarantee this tool makes — very old browsers handled orientation differently, so always check the downloaded file. Re-encoding a JPG or WebP is also lossy: some pixel-level detail is discarded at the chosen quality setting, the same trade-off any JPG/WebP re-save makes. PNG re-export is lossless. Pixel dimensions are always preserved exactly; this tool never downscales your photo to remove metadata.
A convenience tool, not a forensic anonymizer
This tool targets the metadata formats that commonly appear in consumer photos — EXIF, IPTC-IIM, and XMP — and clears them by re-encoding the pixels. It cannot prove a file has zero residual metadata in every possible proprietary or vendor-specific format, and it has no way to know or control what a destination service does after you upload the cleaned copy (some platforms re-add their own metadata, watermarks, or tracking identifiers on upload). Treat this as a strong default privacy pass for sharing casual photos, not a substitute for a dedicated forensic sanitization workflow when the stakes are high.
How this page was reviewed
The parser was tested against JPG, PNG, and WebP files carrying real-world EXIF GPS coordinates, camera make/model tags, IPTC captions and keywords, and embedded XMP packets, confirming the fields displayed match the source data and that the cleaned output no longer contains the original EXIF, IPTC, or XMP segments when re-inspected. The review also confirmed output pixel dimensions match the source exactly and documented where canvas re-encoding introduces unavoidable JPG/WebP quality loss.
Assumptions and limitations
- JPG and WebP output is re-encoded and therefore lossy; PNG output is re-encoded losslessly. Pixel dimensions are always preserved.
- The displayed fields are a common, best-effort subset. Proprietary maker notes, embedded ICC color profiles, and every possible custom XMP or IPTC field are not individually parsed or listed.
- Animated PNG (APNG) and animated WebP files are flattened to a single static frame, since canvas rendering only captures one frame.
- This tool cannot prove a cleaned file has zero residual metadata, and it has no control over metadata a destination site or app may add after you upload the cleaned copy.
- Very large photos or large batches can be slow or hit browser memory limits on lower-end devices, since decoding, redrawing, and re-encoding all happen on-device.
- Corrupted, unusually structured, or encrypted image files may fail to parse or decode; the tool reports which files failed rather than guessing at their contents.
Sources and standards
These authoritative references were used to verify the method and guidance on this page.
- Exchangeable image file format for digital still cameras: Exif Version 2.32 — CIPA (Camera & Imaging Products Association)
- IPTC Photo Metadata Standard — IPTC
- XMP Specification Part 1: Data Model, Serialization, and Core Properties — Adobe
- Portable Network Graphics (PNG) Specification (Third Edition) — W3C
- WebP Container Specification — Google Developers
- HTMLCanvasElement: toBlob() method — MDN Web Docs
Frequently asked questions
Does this remove GPS location data from my photos?
Yes. GPS coordinates live in the EXIF GPS IFD, and canvas re-encoding does not carry that block — or any other EXIF, IPTC, or XMP data — into the cleaned file. The tool shows you the decoded coordinates first so you can see exactly what was embedded before it is removed.
Will cleaning my photo reduce its quality?
PNG output is re-encoded losslessly. JPG and WebP are lossy formats, so re-encoding at the chosen quality setting can discard some fine detail — the same trade-off any JPG/WebP re-save makes. Pixel dimensions are always kept exactly as they were; nothing is downscaled.
Can I clean more than one photo at a time?
Yes. Add up to 20 photos in one batch, review each one’s metadata, then remove metadata from all of them and download each file individually or as a single ZIP.
Does this work on PNG and WebP files, or only JPG?
All three. JPG carries EXIF, IPTC, and XMP; PNG can carry an eXIf chunk and XMP inside a text chunk; WebP can carry EXIF and XMP chunks in its container. The tool reads and removes metadata from all three formats.
Is my photo uploaded to a server?
No. Reading the metadata and producing the cleaned copy both happen in your browser using the Canvas API. The file is never sent to Handiwork.
Why does my cleaned photo look correctly oriented even though the Orientation tag is gone?
Current versions of Chrome, Firefox, Safari, and Edge apply EXIF orientation automatically while decoding a JPEG, before the pixels ever reach the canvas — so the visual rotation is usually preserved even though the Orientation tag itself is stripped from the output. This is standard browser decoding behavior, not something this tool guarantees on every browser version.
Does a clean result mean the photo has zero metadata?
It means the common EXIF, IPTC, and XMP data this tool can detect is gone from the output, and canvas export does not carry those blocks forward. It is not a forensic guarantee against every possible proprietary tag, and it cannot control what a destination site does with the file after you upload it.
What happens to an animated WebP or APNG file?
Only the first frame is kept. Canvas rendering captures a single still frame, so animated PNG and WebP inputs are flattened to one static image in the cleaned output.