How to remove exif gps before you post a photo online
- 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 page does the processing. If you see 'GPS / Geotag Remover is a cross-suite tool', a file was sent to the security processor directly; open the EXIF Scrubber page instead.
- Step 2Get the photo ready as a standard image — Use a JPEG or PNG. If it's an iPhone HEIC or a Galaxy HEIF, convert to JPEG first with /image-tools/heic-to-jpg — browsers can't decode those onto a Canvas. Screenshots are usually PNGs and carry little metadata, but you can scrub them too.
- Step 3Check what it's leaking (optional but smart) — Before scrubbing, drop the photo into the EXIF Map Previewer. If it plots a marker, the photo carries GPS that a downloader could read. If it says 'no location data', the photo is already geotag-clean and you may not need to scrub for location (though the scrubber still removes camera/timestamp tags).
- Step 4Scrub the photo — Drop the image onto the EXIF Scrubber. It paints the decoded photo onto an HTML Canvas at native dimensions and exports a fresh blob — the result has no metadata block to carry GPS. There is no per-tag toggle and no options panel; the scrubber takes no settings. Free tier is one file up to 10 MB.
- Step 5Download the post-ready file — Save it. A single image downloads as
clean.png; JPEG input is still real JPEG (the.pngname is cosmetic — rename to.jpgif an uploader is picky). This is the file to post — upload it instead of the original, whether to a feed, a DM, a forum, or as a 'document'. - Step 6Verify it's clean, then post — Re-open the download in the EXIF Map Previewer — a clean file reports 'no location data'. Or load it in /image-tools/exif-viewer to confirm no GPS, no camera, no timestamp. Now it's safe to post however you like.
Why scrubbing first beats trusting the platform
Platform EXIF handling varies and changes; the only path you fully control is the file you upload. This compares relying on the destination vs. scrubbing the file yourself first.
| Upload path | Does the platform strip EXIF? | If you scrub first |
|---|---|---|
| Photo to a feed (web upload, re-encoded) | Often yes — but varies by site and changes over time | Guaranteed clean, regardless of the platform |
| DM / chat attachment | Sometimes kept, especially 'send as file' | Clean — the file itself has no metadata |
| Forum / marketplace 'upload file' | Frequently kept as-is | Clean — nothing to leak in the upload |
| 'Send as document' (bypasses image pipeline) | Almost always kept | Clean — you scrubbed before attaching |
What's removed before you post, by metadata field
A typical phone JPEG's EXIF and whether a Canvas re-encode keeps it. The whole container is dropped, so every field is removed in one pass — there is no GPS-only mode.
| Field | What it tells a downloader | After scrubbing |
|---|---|---|
| GPS Latitude / Longitude | Where the photo was taken (~5 m) | Removed |
| Date/Time + SubSec | Exactly when you were there | Removed |
| Make / Model / Software | Your device and OS version | Removed |
| Lens / aperture / focal length | Camera fingerprint | Removed |
| IPTC / XMP (edits, captions) | Edit app, keywords, captions | Removed |
| Pixel data (the photo) | The image itself | Preserved (re-encoded for JPEG) |
Tier limits for the image-tools EXIF Scrubber
The scrubber lives in the image tool family, so it uses image-family limits. All processing is local; limits guard 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
Posting 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 file you upload.
Scrub a photo before DMing it as a file
Sending an image as a chat attachment or 'send as file' often keeps the EXIF, even on platforms that strip feed uploads. Scrub first so the file you send is clean no matter how it's delivered.
Before (exiftool on IMG_2207.jpg): GPS Latitude : 51 deg 30' 26.0" N GPS Longitude : 0 deg 7' 39.0" W Date/Time : 2026:06:02 19:44:10 Make / Model : Apple / iPhone 14 Action: EXIF Scrubber -> download clean.png -> rename clean.jpg After (exiftool on the file you send): (no EXIF / IPTC / XMP tags found)
Check, scrub, re-check before going public
The privacy loop: plot the original to prove it's leaking, scrub it, then confirm the upload-ready copy says no location.
Step 1 EXIF Map Previewer on original
-> marker on your current neighbourhood
Step 2 EXIF Scrubber on the same file
-> download clean.png
Step 3 EXIF Map Previewer on clean.png
-> 'no location data' (safe to post)Screenshot vs. camera photo — know what you're posting
Screenshots are PNGs with little metadata; camera photos carry GPS and device tags. The scrubber works on both, but only the camera photo had something private to remove.
Screenshot.png EXIF reader: no GPS, no camera tags Scrub -> clean.png (metadata-free, same pixels) Camera photo.jpg EXIF reader: GPS + device + timestamp present Scrub -> clean.png (all metadata removed)
HEIC selfie that won't load
An iPhone HEIC won't decode on a Canvas. Convert to JPEG first, then scrub before posting.
Drop IMG_5102.HEIC onto EXIF Scrubber -> fails to load (no output) Fix: 1. /image-tools/heic-to-jpg -> IMG_5102.jpg 2. EXIF Scrubber on the .jpg -> clean.png -> post the clean copy
One quick scrub before a marketplace listing photo
Marketplace and forum uploads frequently keep EXIF as-is. Even a single photo of an item for sale can geotag your home. Scrub it before uploading; for multiple photos use a paid tier batch.
item_for_sale.jpg Before: GPS = your home address, timestamp, device Scrub -> clean.png -> upload to the listing After: no GPS, nothing to dox you with (Free = 1 file/run; Pro+ batches the whole set)
Edge cases and what actually happens
It strips everything, not just GPS
By designThere is no 'GPS only' switch. The scrubber re-exports the image through a Canvas, which has no metadata container — so GPS, timestamp, device make/model, software, lens info, IPTC, and XMP all go in one pass. For posting that's ideal: the timestamp and device fingerprint are worth removing too. But it can't keep some tags while dropping location; it is all-or-nothing.
Don't assume the platform stripped it for you
Why scrub firstPlatform EXIF handling is inconsistent: many strip feed uploads but keep metadata on DM attachments, forum uploads, or 'send as file', and behaviour changes over time. Scrubbing the file before you post removes the dependency entirely — the upload is clean no matter what the destination does.
JPEG output is re-compressed, not a byte-copy
ExpectedJPEG input re-encodes at quality 0.95, a second lossy pass. It's visually identical and, since most platforms re-compress on upload anyway, the difference is moot for posting. It is not a byte-for-byte copy — keep your original if you want a pristine master.
HEIC / HEIF input fails to load
Unsupported inputiPhone High Efficiency and Galaxy HEIF photos won't decode on most browser Canvases, so they don't load. Convert to JPEG first with /image-tools/heic-to-jpg, or set your phone to capture JPEG (iPhone: 'Most Compatible').
Output is named clean.png even for a JPEG
Cosmetic mismatchA single-file run downloads as clean.png. For JPEG input the bytes are real JPEG despite the name. Most uploaders sniff the content and accept it; a strict one may complain — rename to .jpg. A naming quirk, not corruption.
Visible info in the photo isn't touched
Out of scopeScrubbing removes file metadata, not pixels. A street sign, house number, reflection, or document visible in the shot stays visible. This tool protects against the GPS-in-EXIF leak, not against what's literally shown in the image — crop or blur those separately.
Reached the security processor directly
ErrorThe GPS / Geotag Remover is a cross-suite tool that redirects to the EXIF Scrubber. If a file 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.' Use the EXIF Scrubber page.
File over the tier size limit
RejectedThe free tier caps a single file at 10 MB, which covers a typical phone JPEG (2-6 MB). A very large export 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.
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. Don't run a meme/reaction GIF you want to keep animated through this — it's for still photos.
Photo had no GPS to begin with
PreservedScreenshots and photos taken with location off carry no GPS. The scrubber still produces a metadata-free copy, but there was nothing location-sensitive to remove. Use the EXIF Map Previewer first to know whether a photo actually leaks a location before you bother.
Frequently asked questions
Don't social platforms already strip EXIF on upload?
Many do for feed uploads, but it's inconsistent — DM attachments, forum uploads, marketplace listings, and 'send as file' frequently keep metadata, and platform behaviour changes over time. Scrubbing the file before you post removes the dependency: the file you upload is clean no matter what the destination does.
Does the scrub itself upload my photo?
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. Open the Network tab while scrubbing to confirm no upload requests.
Does it strip just GPS, or all metadata?
All of it. The Canvas re-encode yields a file with no metadata container, so GPS, capture time, device make/model, software, lens info, IPTC, and XMP all go together. There is no GPS-only mode — which is good for posting, since the timestamp and device fingerprint are worth removing too.
Will my photo look different after scrubbing?
Visually, no. Dimensions and content are preserved. JPEG input re-encodes at quality 0.95 (a second lossy pass), but it's visually identical and most platforms re-compress on upload anyway. PNG and other inputs re-encode losslessly to PNG.
What about 'send as document' or DM file attachments?
That's exactly where scrubbing first matters most. Sending an image as a raw file or document usually bypasses the platform's image pipeline, so any EXIF rides along. If you scrub before attaching, the file itself is already metadata-free regardless of how it's sent.
How do I confirm the location is gone before I post?
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 to confirm no GPS, camera, or timestamp tags remain.
Does this protect against people seeing my location in the photo itself?
No — it only removes file metadata. A street sign, house number, or recognisable landmark visible in the image is part of the pixels and stays. Crop or blur those separately; this tool stops the invisible GPS-in-EXIF leak.
Can I scrub an iPhone HEIC photo before posting?
Not directly. Most browsers can't decode HEIC onto a Canvas, so it won't load. Convert to JPEG first with /image-tools/heic-to-jpg, then scrub. To avoid HEIC, set your iPhone to 'Most Compatible' so it captures JPEG.
Why is the download called clean.png when I uploaded 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 uploaders detect the actual format and accept it; if one rejects it, rename to .jpg.
Can I scrub several photos before a multi-photo post?
Yes, on a paid tier. The EXIF Scrubber accepts multiple files: up to 10 on Pro, 50 on Pro-media, unlimited on Developer. The free tier is one file per run. Each photo gets the same full-metadata removal.
Will this remove something hidden in the pixels (steganography)?
No. Metadata scrubbing doesn't touch the pixels' 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, since JPEG is lossy.)
Is scrubbing before posting overkill if I have location off?
If location is off, photos carry no GPS, so there's nothing location-sensitive to strip. But the scrubber still removes device model, software version, and timestamps, which some people prefer not to share. Use the EXIF Map Previewer to check whether a photo actually has a location before deciding.
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.