Back to blog
GuidesApril 20, 20265 min readKonvrt Team

Strip EXIF and GPS Metadata Before Sharing: 2026 Guide

What each EXIF field leaks, which platforms strip metadata and which do not, and how to clean a folder of photos in one pass.

Strip EXIF and GPS Metadata Before Sharing: 2026 Guide

Every JPEG your phone takes has a second file riding inside it. Not a hidden file exactly, just a block of structured data that sits alongside the pixels. That block is EXIF, and on a modern iPhone or Pixel it typically holds about 80 to 120 fields. Most are harmless. A handful are not.

The ones that actually matter, in rough order of how much they leak:

Tag Leaks Typical value
GPSLatitude, GPSLongitude Exact location 37.7749, -122.4194
GPSAltitude Elevation in meters 52.3 m
DateTimeOriginal Timestamp to the second 2026:04:18 14:32:07
Make, Model Device fingerprint Apple, iPhone 17 Pro
LensModel More device detail iPhone 17 Pro back triple camera 6.86mm f/1.78
Software OS version 19.2.1
OwnerName, Artist Set in camera settings J. Smith
SerialNumber, LensSerialNumber Uniquely identifies device DNPXXXXXXXXX

GPS is the obvious one. A photo of a hot meal posted to a public forum will, by default, include the coordinates of the restaurant, and if that restaurant is your house, the coordinates of your house. Exact to within 5 meters on a phone with a clear sky view.

The less obvious ones are the device fingerprint and serial numbers. Camera serial numbers are stable across the life of the device and have been used in court to tie an anonymous image back to a specific camera body.

Which platforms strip metadata automatically

This changes periodically. As of early 2026:

  • Twitter/X: strips EXIF on upload, including GPS.
  • Facebook, Instagram: strip EXIF on upload, including GPS.
  • WhatsApp: strips EXIF in chat, but "original quality" mode in some versions preserves it.
  • Discord: preserves EXIF in attachments. GPS included.
  • Slack: preserves EXIF.
  • iMessage: preserves EXIF, including GPS. Confirmed with a 2025 test.
  • Signal: strips EXIF.
  • Email (most clients): preserves EXIF untouched.
  • Direct uploads to your own website, S3, etc: preserves EXIF.
  • GitHub issues, GitLab issues: strip EXIF from image attachments.
  • Reddit (new.reddit): strips EXIF on the image host, but if you link an external image it is up to that host.

If you are posting through any channel that might preserve metadata, strip it first.

The platforms that do strip are not universally safe either. Instagram strips the EXIF block but adds their own metadata. Facebook fingerprints uploads with an invisible watermark, unrelated to EXIF, that ties the image back to the uploader's account. EXIF stripping solves the first-party leak, not the platform-inflicted one.

What happens when you "remove metadata" in Finder or Explorer

Windows "Remove Properties" (right-click, Properties, Details, "Remove Properties and Personal Information") strips most EXIF but leaves XMP and IPTC fields in place. It also sometimes misses GPS on files produced by non-Microsoft software. Run ExifTool against a file you thought you cleaned and you will often find remnants.

macOS Preview does a similar partial job. The Preview-exported JPEG loses most EXIF but preserves color profile data and may leave ICC tags containing device-specific information.

If you want a clean file, use a tool that actually parses the full metadata tree (EXIF, XMP, IPTC, makernotes, thumbnail embedded EXIF) and rewrites the file without them. Half-measures leave fingerprints.

The thumbnail trap

One EXIF field worth knowing about specifically: ExifThumbnail. It is a small JPEG preview embedded inside the main JPEG. On older phones and some cameras, this thumbnail was generated before cropping, so the thumbnail could still show the part of the image you cropped out. This bit several public figures in the early 2010s. Modern phones re-generate the thumbnail to match the final image, but scanned or processed files still sometimes carry stale thumbnails. A full metadata strip removes the embedded thumbnail along with everything else.

Batch cleaning a folder locally

Doing one file at a time is fine. Doing 800 vacation photos that way is not. Two ways to batch:

ExifTool from the command line:

# Remove all metadata, keep originals as .jpg_original
exiftool -all= -overwrite_original_in_place *.jpg

# Remove only GPS, keep the rest
exiftool -gps:all= -overwrite_original_in_place *.jpg

Or in a browser, without installing anything and without uploading photos to a server: drop the folder onto /batch. Konvrt processes each file locally via WebAssembly, strips the metadata block you specify, and gives you a zip back. Nothing leaves the tab. For a single file or a format conversion that also happens to strip metadata, /convert is the same thing for one image.

A useful middle ground: strip everything except the copyright field and the color profile. Copyright is often the one metadata field you actually want preserved for your own photos. Color profile is what makes the image look right on different screens. Most tools let you whitelist specific tags.

One last field to watch

HEIC files from iPhones do not use EXIF. They use a different metadata container called mdat boxes with extended metadata, and many EXIF-stripping tools built for JPEG do not touch it. If your source is HEIC, either convert to JPEG with metadata stripping in the same pass, or use a HEIC-aware stripper. A HEIC posted publicly with "stripped EXIF" by a JPEG-only tool still has every field it started with.

The shortest useful takeaway: if a photo is leaving your device for any audience wider than close family, assume the metadata goes with it, and strip in the same step as whatever else you are doing to the file.

Built for fast file workflows

Convert, optimize, and ship files without sending them away first.

Konvrt keeps the experience simple: local-first processing when possible, clear pricing, strong privacy defaults, and focused tools for repetitive file work.

Local-first

Files stay on your device for supported browser workflows.

Fast answers

Use FAQ, docs, and contact paths without hunting around the site.

Clear upgrades

Move from free workflows to paid access without confusing plan language.