EXIF Viewer & Stripper
Inspect or remove camera metadata (including GPS coordinates) from JPG and HEIC photos
Drop a photo here — JPG, PNG, HEIC, WebP. EXIF data stays in your browser.
Max file size: 50MB
How to EXIF Viewer & Stripper Online
Inspect and strip EXIF metadata (camera info, GPS coordinates, timestamps) from JPG, PNG, HEIC, and WebP images.
- Drag a photo into the drop zone, or click to choose one. JPG, PNG, HEIC, and WebP all work.
- The tool reads the metadata client-side and groups it by category: Camera, Exposure, Time, GPS, Attribution.
- If the photo contains GPS coordinates, a red warning banner shows up at the top with the exact lat/lon and a one-click link to view the location on OpenStreetMap.
- Click 'Strip metadata & download' to get a metadata-free copy of the image — pixels preserved exactly, all EXIF / IPTC / XMP tags removed.
- Verify by dropping the downloaded file back in: it should show 'No EXIF metadata found'.
About EXIF Viewer & Stripper
If you have a smartphone and your camera roll's "Location Services" toggle is on, every single photo you've ever taken on that phone is geotagged. The latitude and longitude where you stood when you pressed the shutter sit inside the file, accurate to within a few meters, ready to read by anyone with a copy of the photo. This has been true since the iPhone 3GS in 2009. The privacy implications are real: your home, your workplace, your favorite coffee shop, your child's school, every restaurant you photograph the menu of — all of it is in the file, all of it transmits anywhere you share the photo, unless something along the way strips it.
This tool exists for two related jobs.
**Job 1: see what's in your photos.** The display reads every EXIF tag the `exifr` library can extract and groups them into meaningful sections. Camera shows the make, model, and lens. Exposure shows the aperture, shutter speed, ISO, and focal length — useful for learning from your own shots or someone else's. Time shows when the photo was captured and when the file was created (sometimes different, especially after editing). And GPS — when present — shows latitude and longitude with the precision they were captured at, plus altitude when available. The GPS section is intentionally styled red with a OpenStreetMap link because it's the one piece of metadata most people are surprised to learn is there.
**Job 2: strip the metadata before you share.** Click the button at the bottom and the tool re-encodes the image through the browser's canvas, which is the standard technique for washing all sidecar metadata. The output is a JPG (or PNG, matching the input) with pixels identical to what you uploaded but with no EXIF, no IPTC, no XMP, no thumbnail, no ICC profile, no vendor blobs. Drop the result back in to confirm — the display reads "No EXIF metadata found" and you have a file safe to share anywhere.
**What about social-media stripping?** It varies enough to be unreliable. The major Western social platforms (Facebook, Instagram, Twitter/X) generally strip GPS but keep camera info; LinkedIn and Discord strip almost everything; smaller platforms keep everything; direct shares (email, AirDrop, Signal, iMessage) preserve everything; cloud backups preserve everything. If you care about not leaking location data, the only safe assumption is "the file I'm about to share carries my full metadata unless I personally stripped it." This tool gives you that personal stripping step.
A subtle point about **modern phone formats**: iPhones since 2017 default to HEIC (High Efficiency Image Format). HEIC has the same EXIF + GPS structure as JPG and the same privacy issues. The `exifr` library reads HEIC metadata fine; stripping requires converting to JPG first (which the tool does automatically since canvas can decode HEIC on modern browsers). Android phones using HEIF behave the same way.
**RAW formats** are out of scope for stripping. CR2 (Canon), NEF (Nikon), ARW (Sony), DNG, and other RAW formats are read-only for metadata — they exist precisely to preserve every capture parameter for editing flexibility, and re-encoding RAW to JPG loses the very thing that makes RAW worth shooting. For RAW workflows, do your stripping in Lightroom / Capture One / Affinity Photo at export time. For developed JPGs, this tool is the right destination.
Everything runs in your browser. The `exifr` library (~15 KB compressed) is bundled with the page. Parsing and stripping happen client-side; the image, its location data, and any other sensitive metadata never leave your tab. Verify in DevTools — the only network request during use is the page itself and the parser library, both from the site's own origin.
Related Tools
Frequently Asked Questions
What is EXIF and why should I care?
EXIF (Exchangeable Image File Format) is metadata your camera embeds inside every photo. It includes the make and model of your camera or phone, the lens, the exact aperture and shutter speed, the date and time you took the shot, and — most often the privacy issue — the **GPS coordinates of the location**. Every photo you take with location services on contains the latitude and longitude precise to a meter. Every time you upload that photo somewhere without stripping the EXIF, you may be telling the world exactly where you live, work, or where your children's school is.
Do social networks strip EXIF automatically?
It varies. Facebook, Instagram, and Twitter/X strip GPS coordinates on upload (most camera metadata stays). LinkedIn and Discord strip almost everything. Reddit strips depending on which CDN serves your image. WhatsApp keeps most metadata but strips GPS. Direct shares (email, AirDrop, SMS) preserve everything. Cloud backups (iCloud, Google Photos, OneDrive) preserve everything. The safe assumption: anywhere except major Western social-media platforms, your full EXIF travels with the photo. This tool gives you ground truth — paste in any photo and see exactly what's in it.
How does 'Strip metadata' work?
The tool decodes the image into a canvas, then re-encodes the pixel data back to JPG or PNG. Canvas re-encoding is the standard 'wash' for image metadata — the spec defines no way to carry EXIF / IPTC / XMP through canvas pixel operations, so the output file is guaranteed metadata-free. The visible pixels are preserved exactly (no quality loss for PNG; ~95% quality for JPG by default).
Are GPS coordinates really that precise?
Yes. Modern phone GPS on a clear day is accurate to about 3 meters horizontally. The EXIF `GPSLatitude` and `GPSLongitude` tags store coordinates with sub-meter precision (often 6 decimal places of degrees, which is roughly 10 cm). The tool surfaces these as a red warning banner with a one-click link to OpenStreetMap so you can see exactly what's encoded.
What about RAW files (CR2, NEF, ARW, DNG)?
RAW formats are read-only for EXIF in this tool. The `exifr` library reads them, but stripping requires re-encoding to a different format — RAW is by design a one-way capture format and you'd lose the editing latitude that makes RAW worth shooting. If you need to share a RAW file's pixels without metadata, develop it to JPG in your editor (Lightroom, Capture One, Affinity Photo) with the 'do not include metadata' option, or run the JPG export through this tool.
Does this tool also strip XMP and IPTC?
Yes — canvas re-encoding strips all three sidecar metadata standards (EXIF, IPTC, XMP) plus thumbnail previews, ICC color profiles, and any vendor-specific tags. The output is metadata-free. The trade-off is that ICC profiles also get dropped — for photos that depend on a specific color profile (display-P3 wide gamut, Adobe RGB), the appearance may shift slightly when viewed on color-managed monitors. For typical sRGB phone photos this is not noticeable.
Is the image sent to a server?
No. EXIF parsing runs in your browser via the `exifr` library (~15 KB compressed). Re-encoding uses the browser's built-in canvas. The image, its metadata, and any GPS coordinates inside it never leave your tab. You can verify in DevTools — the only network request is loading this page's JavaScript bundle.