Overview
Shows you what your photos leak. Drop in a JPEG and the tool reads its EXIF metadata — camera make and model, orientation, date taken, and GPS coordinates — entirely in the browser, then can hand you back a clean copy in PNG, JPEG or WebP with the metadata verifiably gone.
How It Works
Drag a file in or click to browse (25 MB limit, one file at a time). The metadata appears as labelled fields, GPS coordinates come with an Open GPS position on map link, and Copy as JSON hands the fields to your clipboard while Download JSON saves them as a file named after the photo. Pick a clean-copy format — PNG for graphics, or JPEG or WebP for photos, which re-encode far smaller than a PNG of the same picture — then Download clean copy (metadata removed) saves a freshly encoded file with no metadata.
Step-by-Step Usage Guide
- Drop a JPEG onto the zone, or click to browse.
- Read the fields — make, model, orientation, date, and GPS where present.
- Open the map link if the coordinates matter, or Copy or Download the JSON for records.
- Pick PNG, JPEG or WebP for the clean copy and download it.
Technical Specifications & Standards
The EXIF reader is a hand-rolled binary parser that walks the JPEG's marker structure into the TIFF header and its IFDs — no third-party EXIF library. Metadata removal works by re-encoding: the image is drawn to a canvas (which applies the EXIF rotation flag, so the clean copy keeps the photo upright with no orientation flag left to misinterpret) and exported in your chosen format. The claim is then verified against the produced bytes: for JPEG output the tool re-parses the file and confirms no APP1 EXIF segment survived, and the download is named by the format the bytes actually carry, not the one requested — a browser without the requested encoder produces a PNG-fallback that would otherwise be mislabelled. Files never leave the browser; parsing, previewing, and re-encoding all happen locally.
Targeted Use Cases
- Checking what location data a photo carries before posting it publicly.
- Auditing images a client is about to publish for embedded camera data.
- Producing stripped, photo-sized JPEG copies instead of bloated PNGs.
- Verifying that an image is really clean — the tool re-parses its own output.
Notes & Gotchas
- EXIF is read from JPEG files only; PNG and WebP inputs are always reported as metadata-free because the parser does not read those containers.
- Choose JPEG for photographs — a stripped PNG of a photo can be ten times larger; WebP is smaller still.
- The field set is deliberately small: make, model, orientation, date taken, date modified, and GPS. Exposure, ISO, and lens data are not parsed, so do not rely on them appearing.
- The map link opens Google Maps with the coordinates in the URL — that lookup leaves the browser, but only when you choose to click it.
Frequently Asked Questions
Does the image leave my device?
No. Reading, previewing, and re-encoding happen in the browser; the only optional network call is the map link you click yourself.
How is metadata removed?
By re-encoding through a canvas. The tool then re-parses the output bytes to confirm no EXIF segment remains, so the clean claim is checked, not assumed.
Which clean-copy format should I pick?
PNG for screenshots and graphics, JPEG for photographs, WebP where size matters most and your browser has the encoder. Availability is probed by inspecting real encoder output.
Does the clean copy stay upright?
Yes — the rotation flag is applied during decode, so rotated phone photos come out upright with no orientation flag left to double-rotate them in other software.
Is there a size limit?
Yes, 25 MB per file and one file at a time — it is an inspection tool, not a batch pipeline.