Why Is My Batch EXIF Removal Still Showing Location? (Fix Without Uploading)

You ran a batch strip, checked the file, and the GPS pin is still there. Or the photo opened fine on your laptop but Instagram still guessed your neighborhood. If that sounds familiar, the problem usually isn't the tool — it's which copy of the file you're inspecting, or which metadata channel survived the pass.

This is a troubleshooting walkthrough for anyone cleaning a folder of photos before sending them to a client, posting them, or handing off a drive. The goal is simple: batch remove EXIF without uploading anything to a server, and actually confirm it worked.

Why metadata survives a "successful" strip

There are three common culprits, and they look identical from the outside.

1. You're checking the original, not the export. Most browser tools — including EXIF Remover — leave your source file untouched on disk. The cleaned version is a new download. If you re-open the same file from your camera roll or Downloads folder, you're looking at the original. This is the single most common reason people think the strip failed.

2. The format didn't get re-encoded the way you assumed. EXIF removal by re-encoding (drawing the pixels to a canvas and exporting a fresh blob) works reliably for JPG, PNG, and WebP. HEIC is conditional — it only works if your browser can decode HEIC in the first place. On browsers that can't, the file may not process at all, or may fail silently in a batch. That's not a bug in the strip logic; it's a decode limitation.

3. Something downstream re-added metadata. Some editors, cloud sync clients, and social upload flows write their own metadata fields. If you strip, then open the image in a photo editor and re-save, you may reintroduce software tags or a new timestamp. Strip last, or strip again after any re-save.

Diagnose before you strip: read the table first

Don't strip blind. The fastest way to know whether you have a real problem is to look at what's actually in the file.

Drop one representative photo into the EXIF Remover and read the grouped table. You'll typically see:

GPS — latitude/longitude, sometimes altitude and direction
Camera — make, model, lens
Capture — timestamp, ISO, exposure
Software — the app or OS that last wrote the file

If GPS is present here, it will be present in the file you share. If it's absent here, your earlier strip probably worked and you were inspecting the wrong copy.

For a folder, spot-check two or three images rather than all of them. Cameras and phones write consistently, so if one has GPS, the batch almost certainly does.

The fix: batch strip without uploading

Here's the workflow that avoids the confusion above.

Collect the originals in one folder and don't touch them. Treat them as read-only.
Open the tool at toolkite.net/exif-remover and drag your files in — JPG, PNG, WebP, or HEIC (HEIC only if your browser can decode it). Nothing is uploaded; the reading and stripping happen in your browser.
Review the table on at least one file so you know what's being removed.
Hit Strip EXIF. The tool re-encodes the image via Canvas and produces a clean blob.
Download the cleaned files into a separate folder — name it something like clean/ so you never mix it up with the originals.
Verify. Re-open one cleaned file in the tool and confirm the GPS and camera rows are gone.

On the free tier you can process up to 10 photos per run. If you're cleaning a shoot, the optional Pro license raises that to 50+ per run and adds a privacy risk report with a score, plus CSV/JSON export of the metadata you found. That export is genuinely useful if you need to log what was in a batch before deleting it — for example, keeping a record of capture timestamps for a client while removing the location.

One honest caveat: because JPEG is re-encoded (quality around 0.92), the output is not bit-identical to the input. Visually it's fine for social, web, and client previews, but if you need pixel-perfect archival copies, keep the originals and treat the cleaned files as derivatives.

Prevention: stop the problem before it starts

A few habits make batch EXIF removal boring, which is what you want.

Strip at the end of your edit chain. Any re-save after stripping can reintroduce software tags.
Keep originals and cleaned files in separate folders. Most "it didn't work" reports are folder mix-ups.
Check HEIC before a big batch. Test one HEIC file first; if your browser can't decode it, convert to JPG beforehand rather than discovering it mid-run.
Don't assume selective removal. The tool strips all metadata in one pass — there's no GPS-only or keep-the-lens-info mode. If you need to preserve some fields, that's a job for a different tool.
Re-check after any third-party app touches the file. Editors and upload pipelines can write new metadata.

If your batch is part of a broader publishing workflow, it's worth pairing this with a watermark pass so branding and metadata cleanup happen in the same sitting. Watermark runs in the browser too, so the same no-upload rule applies.

When a browser tool isn't the right fit

Be honest about the limits. A browser-based stripper is excellent for social posts, client previews, and quick batches. It is not a forensic tool, and it doesn't claim to be.

If you need to inspect or remove metadata at a deeper level — obscure formats, scripted pipelines, or field-by-field control — command-line tools like ExifTool are the right call. They're slower to set up and less friendly, but they give you granular control this tool deliberately doesn't offer. Use the browser tool for the 90% case and reach for the CLI when you genuinely need surgical precision.

For anything involving sensitive files, remember the privacy angle: with a browser tool, the image never leaves your machine. That's the whole point. You can read more about how Toolkite handles data on the privacy page.

FAQ

Why does my photo still show GPS after I batch removed EXIF?

In most cases you're inspecting the original file, not the cleaned export. Browser tools leave the source untouched and produce a new download, so re-opening the file from your camera roll or Downloads folder shows the original metadata. Open the cleaned copy from your separate output folder instead, and re-check it in the tool.

How come some photos in my batch didn't get stripped at all?

Format is the usual reason. JPG, PNG, and WebP re-encode reliably, but HEIC only works if your browser can decode it. If a HEIC file can't be decoded, it may fail or be skipped in the batch. Test one HEIC file before running a large set, and convert to JPG first if needed.

What if I strip EXIF and then edit the photo again?

Re-saving in an editor or syncing through certain apps can write new metadata fields, including software tags and fresh timestamps. Strip as the last step in your workflow, or strip again after any re-save. Keeping originals and cleaned files in separate folders makes this easy to manage.

Does batch EXIF removal without uploading mean nothing leaves my device?

Yes — with a browser-based tool the file is read and re-encoded locally, and nothing is sent to a server. That's the core advantage over upload-based converters. You can read more about how data is handled on the Toolkite privacy page.

Is the cleaned image identical to the original?

Not bit-for-bit. JPEG output is re-encoded at roughly 0.92 quality, so there's slight recompression. It looks fine for social media, web, and client previews, but if you need pixel-perfect archival copies, keep the originals and treat the cleaned files as derivatives.

Can I remove only GPS and keep the camera info?

No — the tool strips all metadata in a single pass, so there's no GPS-only or keep-the-lens mode. If you need field-by-field control, a command-line tool like ExifTool is the better fit. The browser tool is built for quick, private, whole-file cleanup.