Geotagging means embedding latitude, longitude, and often altitude or heading into a photo’s metadata—usually inside EXIF—so software can sort albums by place, plot trips on a map, or suggest location-based captions. Modern smartphones enable GPS by default for the camera app, which is convenient when you want to remember where a picture was taken. The same convenience becomes a liability when you share that file online: the pixels may look harmless while the metadata quietly reveals a home address, a child’s school route, a protest or clinic visit, or the interior layout of a secure facility inferred from precise coordinates plus time-of-day.
SynthQuery’s Geotag Remover is a free, browser-based utility that focuses narrowly on that risk. You upload one or many images in common formats—JPEG, PNG, WebP, TIFF, or Apple HEIC/HEIF—and the page reads embedded EXIF locally to see whether GPS tags are present. When they are, you get a short human-readable summary (coordinates and, when available, a reverse-geocoded address via OpenStreetMap’s Nominatim service) plus an embedded map preview so you can visually confirm what the file would have disclosed. One action then rewrites metadata so GPS sub-IFDs and pointers are removed while other EXIF fields—camera make and model, lens information, exposure settings, timestamps, copyright strings, and similar descriptive tags—are preserved wherever the file format allows. Downloads can be taken per image or packaged into a ZIP, and nothing in that pipeline is uploaded to SynthQuery’s application servers for processing: decoding, EXIF surgery, and re-muxing stay inside your tab.
This workflow complements broader SynthQuery capabilities. When you are ready to publish long-form copy next to cleaned imagery, the AI Detector and Humanizer help you review AI-assisted text responsibly. The Free tools hub at /free-tools lists lightweight utilities in one place, and the full product catalog remains available from https://synthquery.com/tools when you need calculators, resizers, converters, or enterprise-grade content analysis beyond quick privacy fixes.
Why GPS metadata is different from other EXIF
Camera settings rarely pinpoint a bedroom window; GPS often does, especially when accuracy is good and the capture happens indoors with Wi‑Fi/cell assistance. Removing only GPS reduces the sensitive surface area while keeping technical provenance that photographers, archivists, and DAM workflows still value.
Not a substitute for holistic operational security
Stripping geotags does not remove faces, license plates, unique architecture, or text in the frame. Journalists, activists, and parents should combine metadata hygiene with cropping, blurring, consent practices, and organizational policies. This tool removes one common leak vector—not every leak vector.
What this tool does
The feature set is deliberately narrow: privacy-first GPS removal with verification, not a full DAM replacement. JPEG handling walks APP1 “Exif ” segments with piexifjs after exifr has identified coordinates for the UI—GPS dictionaries and IFD0 pointers such as tag 34853 (GPS IFD offset) are dropped, then the remaining EXIF is re-inserted so camera-oriented tags survive when still structurally valid. PNG and WebP follow the same philosophy on their respective EXIF containers: PNG’s eXIf ancillary chunk and WebP’s EXIF RIFF chunk carry TIFF-encoded EXIF payloads; those payloads are parsed, GPS subtrees removed, and the chunk is rewritten or omitted if nothing remains besides the removed location data.
Map previews use OpenStreetMap’s embed endpoint; attribution appears under each iframe because open data still requires credit. Batch mode applies the same rules file-by-file so mixed sets of JPEG screenshots and HEIC phone photos can be processed in one sitting without mixing bytes between clients. ZIP packaging relies on the same JSZip dependency used elsewhere on SynthQuery so power users recognize the behavior. Quality is not re-touched for raster formats that only need metadata edits; HEIC→JPEG and TIFF→PNG paths necessarily re-encode because the browser stack cannot always round-trip those containers with arbitrary vendor extensions.
SynthQuery also hosts a broader Remove EXIF/Metadata utility when you need aggressive stripping presets across more tag categories. Pair this geotag-focused page when your reviewers insist on keeping lens and timestamp fields for authenticity but refuse to ship latitude/longitude to social networks, marketplaces, or public bug trackers.
Why ZIP and per-file downloads both exist
Some browsers throttle multiple download prompts; a single archive is calmer for recipients. Individual downloads help when only one asset from a batch failed ZIP expectations or when you want to inspect a single cleaned byte range before emailing the rest.
Technical details
EXIF stores GPS as a dedicated sub-IFD referenced from the zeroth IFD via tag 34853 (0x8825). Inside the GPS IFD, latitude and longitude appear as arrays of unsigned rational pairs (degrees, minutes, seconds components) plus ASCII reference tags (“N”/“S”, “E”/“W”). Optional tags cover altitude, timestamp, satellites, measure mode, differential correction, and more—SynthQuery’s removal path clears the GPS dictionary rather than zeroing individual rationals piecemeal, which avoids leaving half-valid location stubs that confuse downstream parsers.
Selective removal matters because many other tags live in separate IFDs: Exif IFD (34865) holds DateTimeOriginal, lens metadata, flash bitmask, and user comment pointers; interoperability IFDs may exist for flash-related notes. Piexifjs rebuilds a compact TIFF payload for JPEG APP1 and PNG/WebP EXIF chunks after GPS deletion, so pointers remain internally consistent. Phone GPS accuracy varies with sky view, multipath, and assisted modes—five-metre-class fixes are common outdoors, while indoor Wi‑Fi fixes might jump tens of metres. Embedded coordinates therefore reflect device confidence at capture time, not survey-grade truth.
HEIC containers wrap HEVC-coded images and auxiliary metadata; browsers decode through WASM helpers such as heic2any, producing a JPEG intermediate. EXIF is re-derived via exifr from the original HEIC bytes and re-embedded without latitude or longitude when possible. TIFF is a native IFD-linked format; rewriting arbitrary compressed strips in-browser is fragile, so the tool rasterizes page one and attaches rebuilt EXIF into PNG’s eXIf chunk—archivists should keep lossless TIFF masters offline.
Verification after cleaning
Re-open a cleaned file in any reputable EXIF viewer (or re-upload into this page) to confirm GPS tags are absent. Some social networks strip metadata on ingest anyway; keeping a local cleaned copy ensures you control what leaves your device, independent of platform behavior.
Use cases
Parents posting playground photos often want grandparents to see smiles without advertising which gate or trailhead their routine follows—GPS removal keeps the joy while blunting stalking-adjacent precision. Real-estate agents marketing occupied homes can strip shoot coordinates from exterior twilight photos so listing JPEGs do not double as a parcel pin drop, while still retaining camera EXIF that proves the image was not wildly re-touched in software timestamps. Journalists and human-rights documenters routinely scrub location before syndication even when the capture device logged accurate coordinates for their own notes; this tool offers a fast browser option when newsroom desktop suites are unavailable.
Dating-app profile pictures, marketplace listings for high-value collectibles, and teacher blog posts with student events are three more contexts where viewers infer too much from a pin on a map. Child-safety guides increasingly mention metadata because young subjects cannot consent to invisible data trails. Teams that mix marketing imagery with AI-generated copy can run SynthQuery’s AI Detector on captions while running this remover on the raster attachments, keeping two different risk classes separated. When TIFF archives must enter a web workflow, converting only the first page to PNG with rebuilt non-GPS EXIF is a pragmatic compromise compared with emailing multi-hundred-megabyte masters through insecure channels.
Whenever you need broader EXIF removal—including IPTC-like fields, comments, or serial-like software strings—visit the Remove EXIF/Metadata tool and choose a preset that matches your policy. When you only need coordinates gone, stay on this page to minimize collateral loss of camera science data.
Marketplace and classified safety
Even when you never mention your suburb in the description, a geotagged phone photo of a laptop on a kitchen bench can place you within tens of metres. Stripping GPS before upload closes that gap; still avoid identifiable backgrounds if threat model demands it.
How SynthQuery compares
Full metadata strippers—whether desktop batch apps or all-in-one “privacy scrubbers”—often delete every EXIF, IPTC, and XMP field to maximize anonymity. That is appropriate for whistleblower pipelines or stock redistribution, but destructive for photographers who rely on lens serials, copyright blocks, or synchronized capture times across bodies. SynthQuery’s Geotag Remover targets a middle policy: eliminate geolocation while preserving as much technical and rights metadata as the encoder stack allows, with explicit UI copy when HEIC or TIFF forces a format conversion.
Compared with screenshotting a photo (which nukes nearly all metadata) or re-saving through a random “compressor” site of unknown trust, this page documents behavior, runs locally, and shows a map-backed confirmation step so you are not guessing whether GPS existed. It is free at point of use like other SynthQuery utilities, which matters when volunteers process hundreds of community event photos after a single afternoon shoot.
Aspect
SynthQuery
Typical alternatives
Metadata scope
Removes GPS IFD data and pointers; keeps other EXIF fields when structures remain valid after editing.
Many “strip metadata” buttons delete the entire EXIF segment or re-encode without explanation.
Confirmation UX
Shows coordinates, optional reverse geocode, and an OpenStreetMap embed before you export.
CLI tools are powerful but opaque; some web uploaders hide what they removed.
Privacy architecture
Processing uses FileReader/Blob APIs in your browser tab; routine analytics may log page views but not your image bytes.
Server-side scrubbers require trust in transit and retention policies.
Batch ergonomics
Per-file downloads plus ZIP packaging with JSZip, aligned with other SynthQuery image utilities.
Desktop DAM suites excel at huge archives but may be blocked on locked-down laptops.
How to use this tool effectively
Start from the originals your phone or camera exported—avoid lossy “export for social” paths that may have already recompressed pixels unless that is intentional. Open the Geotag Remover page and use either drag-and-drop or the file picker; you can queue many files at once within the stated per-file size and count limits shown in the interface. After each file is added, the tool automatically scans EXIF for latitude and longitude. Rows update with a status line such as “Location found” plus decimal degrees, and when reverse geocoding succeeds you will also see a plain-language place description appended for context.
Each image that contains coordinates shows an embedded OpenStreetMap preview bounded around the point so you can sanity-check the reading before you distribute the file. When you are satisfied, press “Strip GPS & prepare downloads.” The implementation removes GPS IFD data and pointers while attempting to retain unrelated EXIF. Individual “Download cleaned” buttons appear per row once processing completes, and “Download all as ZIP” bundles every successful output for email attachments or ticket uploads. HEIC sources are converted to JPEG in-browser because browsers cannot natively re-save HEIC; non-GPS EXIF is copied when exifr and piexif can express those fields. TIFF inputs are decoded to a first-page PNG with an optional eXIf chunk rebuilt from the same tag harvest—multi-page TIFF beyond page one is outside this page’s scope, so keep archival masters elsewhere if you need every page untouched.
If a file never contained GPS, the status line explains that no GPS metadata was detected; you still receive a consistent “clean” export path so batch workflows do not need special cases. Errors—corrupt metadata, exotic compression, or decoder limits—surface inline per file rather than failing the entire queue silently. After downloads, clear the queue before working on a different shoot so blob preview URLs are revoked and memory stays predictable on long sessions.
Rate limits on address lookup
Reverse geocoding uses the public Nominatim API with a polite User-Agent string and a staggered delay between requests so small batches stay within community guidelines. Very large queues may take noticeable wall-clock time; coordinates still display immediately even if an address line arrives later.
Limitations and best practices
Browser memory caps still apply: extremely wide panoramas or deep TIFF stacks may fail to decode on low-RAM phones—resize or split assets first using SynthQuery’s Image Resizer or TIFF-oriented converters if you hit errors. Nominatim reverse geocoding is a courtesy public service; do not hammer it with automation beyond casual human pacing, and treat addresses as hints rather than legal land titles. Map iframes load third-party cartographic tiles under OpenStreetMap policies; if your compliance regime forbids any external network access, disconnect before opening embeds or use an air-gapped EXIF editor instead.
This page does not attempt to parse every vendor MakerNote or proprietary depth-map sidecar; those blobs may still contain coarse location in exotic devices—verify with manufacturer tooling if your threat model includes nation-state adversaries. Animated WebP and multi-frame HEIC sequences are outside the happy path; export a still frame first. Always retain uncompressed archival masters with a documented chain of custody when legal evidence matters; stripped derivatives should be labeled as distribution copies.
When TIFF conversion to PNG is unacceptable, keep TIFF masters offline and run desktop exiftool-style workflows for in-place IFD surgery. Link workflows to the Free tools hub (/free-tools) for discoverability, and send teammates who need AI text review to /detect and /humanizer when campaigns mix imagery with generative prose.
Soften machine-like prose that accompanies cleaned photos in blogs, listings, or press releases.
Frequently asked questions
Latitude and longitude describe where the device thought it was when the shutter fired—often within a few metres outdoors. Combined with DateTimeOriginal, that pin can imply routine (same corner every school morning), travel history, or sensitive venues. Altitude, heading, and speed tags sometimes appear too, tightening inference further. Removing GPS does not erase visual clues in the pixels, but it stops mapping software and many forensic scripts from reading a precise coordinate pair straight out of the file header.
Default camera apps on iOS and Android typically record GPS when location services are enabled for the camera. Third-party social apps may attach coordinates on capture or preserve them through edits depending on settings. Scanners, drones, and some action cameras also write GPS IFDs. Desktop exports from Lightroom or Capture One follow whatever sync metadata preset you choose. If you are unsure, upload a test image into this tool’s scanner—the preview and map confirm whether coordinates exist before you share publicly.
Major social platforms often strip or rewrite location metadata on upload, but policies change and implementation details differ for stories versus DMs versus original-quality backups. You should not rely on a network you do not control as your only privacy layer—downloaders, email forwards, and “save image” paths can still propagate originals. Cleaning files locally guarantees the asset you attach to a ticket, forum, or cloud folder starts without GPS even if the next hop recompresses.
Consumer phones mix true GNSS fixes with Wi‑Fi and cellular assistance. Rural open-sky shots might land within a few metres; indoor shots might drift tens of metres or snap to the wrong venue POI. That uncertainty does not make coordinates harmless—attackers combine coarse pins with other OSINT—but it explains why map previews sometimes look slightly offset from where you remember standing. SynthQuery shows what the file literally contains so you can judge risk.
Download the cleaned file and open it in any EXIF inspector, or drag it back into this page: the scanner should report that no GPS metadata was detected. On macOS, Preview’s Inspector shows location when present; Windows Properties → Details may surface GPS; exiftool on desktop remains the gold standard for scripts. If a tool still shows GPS after using this page, ensure you are inspecting the exported “-geoclean” derivative rather than the original in Downloads.
For JPEG, PNG, and WebP paths that only adjust metadata segments, pixels are untouched—no recompression occurs. HEIC inputs convert to JPEG because browsers cannot natively write HEIC; that step can change generational quality slightly, so keep originals elsewhere when archival fidelity matters. TIFF inputs become PNG for page one with optional rebuilt EXIF in an eXIf chunk; that is a lossless PNG encode of decoded pixels but not a byte-identical TIFF round-trip.
No. The remover uses client-side APIs (FileReader, Blob, typed arrays, dynamic imports of exifr, piexifjs, heic2any, utif helpers, and JSZip) so bytes stay in your browser process. Network calls you may notice include loading the SynthQuery web app, fetching map tiles/embeds, and optional Nominatim reverse lookups that send only coordinates—not your image file. Corporate proxies or DNS still see domain names; if that is sensitive, work offline after the bundle loads or use an air-gapped workstation tool.
This page deletes GPS-focused structures while trying to leave camera, timestamp, and rights-related EXIF intact. SynthQuery’s Remove EXIF/Metadata tool targets broader categories—useful when you want minimal metadata for stock redistribution or compliance sweeps. Pick Geotag Remover when stakeholders explicitly want lens and datetime fields for authenticity but refuse to leak coordinates; pick full removal when policy says “no embedded metadata at all.”
Yes. HEIC/HEIF uploads decode to JPEG with best-effort non-GPS EXIF reinsertion. TIFF uploads decode the first image directory to PNG with optional eXIf embedding rebuilt from exifr’s tag harvest—multi-page documents should be split externally if every page must be preserved. For heavy TIFF batches, consider converting with the TIFF to JPG or TIFF to PNG utilities first, then run geotag removal on the raster outputs if that matches your DAM policy.
Coordinates display whenever EXIF includes latitude and longitude. Reverse-geocoded addresses appear when Nominatim returns a display name; network errors, rate limits, or remote locales may leave coordinates only. Map iframes require connectivity to OpenStreetMap infrastructure. If either dependency fails, you can still strip GPS using the primary action—the confirmation helpers are supplementary, not gatekeeping.
Geotag Remover - Free Online Image Utilities Tool
Strip GPS only · Keep camera EXIF · Map preview · Batch + ZIP · JPG, PNG, WebP, TIFF, HEIC — 100% client-side (UTIL-004)
Drag and drop images here or browse. Accepts JPG, PNG, WebP, TIFF, and HEIC. Up to 20 files, 50.00 MB each. Everything runs in your browser — files are not uploaded to SynthQuery.