How to remove gps geotags from iphone photos locally
- Step 1Open the tool and follow the redirect — The GPS / Geotag Remover is a cross-suite shortcut. Selecting it sends you to the EXIF Scrubber at /image-tools/exif-scrubber — that is where the file is processed. If you ever see an error like 'GPS / Geotag Remover is a cross-suite tool', it means a file was sent to the security processor directly; just open the EXIF Scrubber page instead.
- Step 2Get the photo off your iPhone as a JPEG — If you AirDrop, email, or sync to a Mac/PC, the photo is usually already a
.jpg. If your Camera setting is High Efficiency, the original is HEIC — browsers generally can't decode HEIC on a Canvas, so convert it first with /image-tools/heic-to-jpg. To make iPhone capture JPEG natively, set Settings → Camera → Formats → Most Compatible. - Step 3Drop the photo onto the scrubber — Drag a JPEG (or PNG/WebP/BMP/GIF) into the upload area. Nothing is sent to a server — the image is read into browser memory and decoded into an
<img>element locally. The free tier handles one file up to 10 MB; paid tiers raise both the size cap and the batch count. - Step 4Run the scrub — The tool paints the decoded image onto an HTML Canvas at its native pixel dimensions and exports a new blob. Because the export is a fresh encode, the result file simply has no metadata block to carry GPS — there is no per-tag toggle and no options panel; the scrubber takes no settings.
- Step 5Download the clean copy — Save the file. For a single image the download is named
clean.pngregardless of the source format; a single JPEG input still produces JPEG bytes (the extension in the name is cosmetic — rename to.jpgif a strict viewer rejects the mismatch). A multi-file batch returns each cleaned image for download. - Step 6Verify the result is actually clean — Re-open the downloaded file in the EXIF Map Previewer — it should report 'no location data'. Or load it in an image-metadata viewer such as /image-tools/exif-viewer; a scrubbed file shows no GPS, no camera, no timestamp tags.
What the EXIF Scrubber actually does, by input format
The redirect target decodes the image and re-exports it through an HTML Canvas at quality 0.95. JPEG input re-encodes as JPEG; every other format exports as PNG. The Canvas export carries no metadata, so all of it is removed regardless of format.
| Input format | Output format / filename | GPS & all EXIF/IPTC/XMP | Pixel fidelity |
|---|---|---|---|
| JPEG (.jpg/.jpeg) — the usual iPhone share format | JPEG bytes, named clean.png for a single file | Removed entirely (fresh encode has no metadata block) | Re-encoded at quality 0.95 — visually identical, but not byte-identical pixels (a second lossy JPEG pass) |
| PNG (.png) | PNG, named clean.png | Removed entirely (PNG rarely carries GPS anyway) | Lossless re-encode of the decoded pixels |
| WebP / BMP / GIF | PNG (re-encoded), named clean.png | Removed entirely | Re-encoded to PNG; first GIF frame only (animation is lost) |
| HEIC / HEIF (iPhone High-Efficiency) | Fails to load on most browsers | n/a — file never decodes | Convert to JPEG first via /image-tools/heic-to-jpg |
iPhone EXIF fields and where they end up
What an iPhone bakes into a JPEG and whether a Canvas re-encode keeps it. The whole metadata container is dropped, so every row here is removed in one pass — there is no GPS-only mode.
| iPhone metadata field | What it leaks | After scrubbing |
|---|---|---|
| GPS Latitude / Longitude | Exact spot the photo was taken (~5 m) | Removed |
| GPS Altitude / Img Direction | Elevation and compass heading | Removed |
| GPS / SubSec timestamps | When the photo was captured, to the second | Removed |
Make / Model (Apple, iPhone 15 Pro) | Which device took it | Removed |
| Lens Make/Model, focal length, aperture | Camera fingerprint | Removed |
Software (17.4.1) | iOS version on the device | Removed |
| IPTC / XMP (edits, keywords, Apple AI labels) | App edit history, captions, tags | Removed |
| Pixel data (the actual photo) | The image itself | Preserved (re-encoded for JPEG) |
Tier limits for the image-tools EXIF Scrubber
The scrubber runs in the image tool family, so it uses image-family limits — not the security-family ones. All processing is local; limits are guardrails on browser memory.
| Tier | Max file size | Files per batch |
|---|---|---|
| Free | 10 MB | 1 |
| Pro | 100 MB | 10 |
| Pro-media | 2 GB | 50 |
| Developer | 2 GB | Unlimited |
Cookbook
Concrete iPhone-photo scenarios with what goes in and what comes out. 'before' rows are the metadata an EXIF reader shows on the original; 'after' rows are what it shows on the downloaded file.
Strip GPS from a single beach photo before posting
A JPEG straight off an iPhone carries a full GPS block. After the scrubber, an EXIF reader finds nothing — not just GPS gone, the camera and timestamp tags are gone too, because the re-encode produces a file with no metadata container.
Before (exiftool on IMG_4821.jpg): GPS Latitude : 25 deg 47' 24.12" N GPS Longitude : 80 deg 7' 48.36" W Make : Apple Camera Model : iPhone 15 Pro Date/Time : 2026:05:18 14:22:07 Software : 17.4.1 Action: drop onto EXIF Scrubber -> download clean.png After (exiftool on the download): (no EXIF / IPTC / XMP tags found) -> rename to .jpg if a strict viewer dislikes the name
Confirm what a photo leaks, then scrub it
Before trusting the scrubber, verify the original actually carries GPS using the EXIF Map Previewer (it plots the coordinates on a map). Scrub, then re-check — it should now say no location data. This is the verify-scrub-verify loop privacy-conscious users want.
Step 1 EXIF Map Previewer on original
-> marker drops on 1600 Amphitheatre Pkwy
Step 2 EXIF Scrubber on the same file
-> download clean.png
Step 3 EXIF Map Previewer on clean.png
-> 'no location data' (= geotag-clean)iPhone HEIC photo that won't load
If your Camera is set to High Efficiency, the file is HEIC. Browsers can't paint HEIC onto a Canvas, so the scrubber can't decode it. Convert first, then scrub the resulting JPEG.
Drop IMG_4900.HEIC onto EXIF Scrubber -> image fails to load (no clean output) Fix: 1. /image-tools/heic-to-jpg -> IMG_4900.jpg 2. EXIF Scrubber on IMG_4900.jpg -> clean.png (or set iPhone Camera Formats to 'Most Compatible')
Batch-clean a folder of listing photos (Pro)
Selling a car or apartment online means uploading many photos, each geotagged to where you live. On a paid tier the EXIF Scrubber takes a multi-file selection and returns a cleaned copy of each. Free tier is one file at a time.
Free tier : 1 file <= 10 MB per run Pro : up to 10 files, <= 100 MB each Pro-media : up to 50 files, <= 2 GB each Drop 8 listing JPEGs (Pro) -> 8 clean images, each with the GPS + camera fingerprint removed.
Screenshot vs. camera photo — when there's nothing to strip
iPhone screenshots are PNGs with little to no metadata, and photos taken with Location Services off carry no GPS. The scrubber still works (it just produces a metadata-free re-encode), but there was nothing private to remove in the first place. Use the Map Previewer to tell the difference.
Screenshot.PNG EXIF reader: no GPS, no camera tags Scrub anyway -> clean.png (metadata-free, same pixels) Photo with Location Services OFF EXIF reader: camera tags present, NO GPS Scrub -> removes camera tags too (full re-encode)
Edge cases and what actually happens
It strips everything, not just GPS
By designThere is no 'GPS only' switch. The scrubber decodes the image and re-exports it through a Canvas, and a Canvas export has no metadata container at all — so EXIF, IPTC, XMP, camera make/model, lens, software version, and timestamps are all removed in the same pass. This is more thorough than a tag-by-tag delete. If you specifically need to keep, say, the capture date while dropping GPS, this tool can't do that — it is all-or-nothing.
JPEG output is re-compressed, not a byte-copy
ExpectedA common misconception is that the pixels come through bit-identical. They don't for JPEG: the file is re-encoded at quality 0.95, which is a second lossy pass. The result is visually indistinguishable in normal use, but it is not the same byte stream, and file size usually drops. PNG and other formats export as a lossless PNG of the decoded pixels.
HEIC / HEIF input fails to load
Unsupported inputiPhones in High Efficiency mode save HEIC. Most browsers cannot decode HEIC onto a Canvas, so the image never loads and you get no output. Convert to JPEG first with /image-tools/heic-to-jpg, or switch Settings -> Camera -> Formats to 'Most Compatible' so the iPhone captures JPEG directly.
Output is named clean.png even for a JPEG
Cosmetic mismatchA single-file run always downloads as clean.png. For JPEG input the bytes are real JPEG despite the .png name. Most viewers sniff the content and open it fine; a strict tool that trusts the extension may complain. Just rename to .jpg. This is a naming quirk, not a corruption.
Animated GIF loses its animation
Lossy by designA GIF is decoded as a single frame and re-exported as PNG, so only the first frame survives and the animation is gone. The scrubber is built for still photos; don't use it to clean metadata from animated GIFs you want to keep moving.
Reached the security processor directly
ErrorThe GPS / Geotag Remover is a cross-suite tool that redirects to the EXIF Scrubber. If a file somehow hits the security processor for this slug, it throws: 'GPS / Geotag Remover is a cross-suite tool. Open it at /image-tools/exif-scrubber to process files.' Just use the EXIF Scrubber page.
File over the tier size limit
RejectedThe free tier caps a single file at 10 MB (a typical iPhone JPEG is 2-5 MB, so most fit). A 48 MP ProRAW or a very large panorama can exceed it. Pro raises the cap to 100 MB and Pro-media/Developer to 2 GB. Very large dimensions can also hit browser Canvas size ceilings independent of the byte limit.
Photo had no GPS to begin with
PreservedScreenshots, photos taken with Location Services off, and many downloaded images carry no GPS. The scrubber still runs and produces a metadata-free copy, but there was nothing location-sensitive to remove. Use the EXIF Map Previewer first if you want to know whether a photo is actually leaking a location.
LSB-hidden data survives a PNG round-trip
Out of scopeStripping metadata does not touch the pixels' least-significant bits. If someone embedded data via LSB steganography in a PNG, a lossless PNG re-encode can leave it intact. Metadata scrubbing and steganography are different problems — detect hidden payloads with the Steganography Decoder. (Re-encoding a JPEG does tend to destroy LSB data, since JPEG is lossy.)
Free tier is single-file only
Tier limitOn the free tier you scrub one photo per run. To clean a whole camera roll or a set of marketplace photos in one go, the multi-file batch needs Pro (10 files), Pro-media (50), or Developer (unlimited). The per-file privacy result is identical across tiers — only throughput differs.
Frequently asked questions
Does my photo get uploaded anywhere?
No. The GPS / Geotag Remover redirects to the EXIF Scrubber, which runs entirely in your browser using an HTML Canvas. The photo is read into memory, decoded, and re-encoded locally — no bytes leave your device. You can verify this by opening your browser's Network tab while you scrub: there are no upload requests.
Does this strip every EXIF tag, or just GPS?
Every tag. The scrubber re-encodes the image through a Canvas, and the resulting file has no metadata container at all — so GPS, camera make/model, lens, software version, timestamps, IPTC, and XMP are all removed together. There is no GPS-only mode. If you need to keep some metadata (like the capture date) while dropping GPS, this tool can't do selective removal.
Will the photo look different after scrubbing?
Visually, no. The dimensions and content are preserved. The one technical caveat: JPEG input is re-encoded at quality 0.95, which is a second lossy pass — so it is visually identical but not byte-for-byte the same pixels. PNG and other inputs are re-encoded losslessly to PNG. For normal sharing this is imperceptible.
Is HEIC supported?
Not directly. Most browsers can't decode HEIC onto a Canvas, so a HEIC file won't load. Convert it to JPEG first with /image-tools/heic-to-jpg, then scrub the JPEG. To avoid HEIC entirely, set your iPhone to Settings -> Camera -> Formats -> 'Most Compatible' so it captures JPEG.
Why is the download called clean.png when I gave it a JPEG?
A single-file run is always named clean.png. For JPEG input the bytes are still real JPEG — the name is cosmetic. Most apps detect the actual format and open it fine; if a strict viewer rejects it, rename the file to .jpg.
How do I confirm the GPS is actually gone?
Re-check the downloaded file. Drop it into the EXIF Map Previewer — a clean file reports 'no location data'. Or open it in /image-tools/exif-viewer, which lists all metadata and will show no GPS, no camera, and no timestamp tags on a scrubbed image.
Can I clean a whole batch of photos at once?
Yes, on a paid tier. The EXIF Scrubber accepts multiple files: up to 10 on Pro, 50 on Pro-media, and unlimited on Developer. The free tier processes one file per run. Each photo gets the same full-metadata removal regardless of tier.
What's the largest file I can scrub for free?
10 MB on the free tier, which comfortably covers a typical iPhone JPEG (2-5 MB). High-resolution ProRAW or stitched panoramas can exceed it — Pro raises the cap to 100 MB and Pro-media/Developer to 2 GB. Note these are image-family limits, since the scrubber lives in the image suite.
Does removing metadata reduce the file size a lot?
Usually a little. The metadata block on an iPhone JPEG is typically a few KB to a few dozen KB, so removing it shaves that off. The JPEG re-encode at quality 0.95 can change the size more noticeably in either direction, but the visible quality is unchanged.
Will this remove data someone hid in the pixels (steganography)?
No. Metadata scrubbing doesn't touch the pixel values' least-significant bits, so LSB-hidden data in a PNG can survive a lossless re-encode. That's a separate problem — use the Steganography Decoder to detect hidden payloads. (Re-encoding a JPEG does tend to destroy LSB data because JPEG is lossy.)
How is this different from the office or audio metadata tools?
Same goal — removing identifying metadata before sharing — different file types. For documents use the Office Doc Property Wiper (strips author/comments from .docx/.xlsx/.pptx); for music use the Audio ID3 Ghoster (removes ID3 tags and album art). For finding redundant embedded preview thumbnails, see the Hidden Thumbnail Extractor.
Can I also scrub names, emails, or phone numbers visible in a photo?
Not with this tool — it removes file metadata, not content. If your privacy concern is text content (e.g. a CSV or document containing personal data), the Email & Phone Scrubber redacts PII patterns like emails, phone numbers, and card numbers. For burning a region of a scanned signature out of an image, see the dedicated signature tool in the security suite.
Privacy first
Every JAD Security operation runs entirely in your browser. Files, passwords, and PGP private keys never leave your device — verified by zero outbound network requests during processing.