WEBP Geotag Remover

Check whether a photo carries GPS coordinates and strip them from JPEG, PNG and TIFF files at the byte level, in batches, with no upload.

How to Check and Remove Location Data

Load a batch, run the check, and read per file whether coordinates were removed, never existed, or could not be stripped from that format.

Step 1

Upload your images

Drop in one file or a whole batch. The upload accepts common photo formats including WEBP.

Step 2

Run the GPS check

Press the button and each file is scanned for stored coordinates, then cleaned where the format allows it.

Step 3

Read the result

Every file reports removed, already clean, or unsupported, so you always know what actually happened.

Why Location Data Deserves Its Own Check Before Every Publish

Of everything a photograph can carry, coordinates are the most sensitive by a comfortable margin. A camera model tells someone what you own, a timestamp tells them when, but a latitude and longitude pair tells them where you were, often to within a few metres. Photographs taken at home, at a child’s school, or at a client’s premises leak exactly the kind of detail nobody intends to publish, and they leak it invisibly, because nothing about the image looks different.

That is why checking deserves to be its own step rather than an assumption. Most people believe their files are clean because a social network strips location on upload, but the file on your disk is a different object from the copy a platform stores. The original still has its coordinates, and the original is what gets emailed, dropped into a press kit, attached to a listing or handed to a printer. Running a check takes seconds and replaces a belief with a fact.

The cleaning itself is done properly where the format allows it, which means at the byte level rather than by re-saving. The file is parsed, the location entries inside its metadata structure are zeroed in place, and everything else, including the compressed image data, is left exactly where it was. Nothing is decoded and recompressed, so a photograph emerges from the process with its quality untouched, which is the whole point of treating metadata as a separate concern from the picture.

Each supported container needs its own handling, and this matters more than it might sound. JPEG carries metadata in application segments, PNG carries it in a dedicated chunk, and TIFF stores it in a directory of entries that reference each other. In each case the location values are located within that structure and cleared, and in each case the rest of the file is left alone rather than rewritten around them.

Honesty about scope is the part most tools skip, so here it is plainly. Stripping at the byte level is implemented for JPEG, PNG and TIFF. A WEBP file is scanned and, if coordinates are found in it, the file is reported as unsupported rather than quietly passed through as though it had been cleaned. That distinction is deliberate: a tool that claimed success while leaving coordinates in place would be worse than no tool at all. When a WEBP file genuinely needs every trace of metadata gone, the metadata remover handles it by re-encoding, which drops all metadata rather than only the location.

The reporting is what makes the tool usable on real batches. Every file ends in one of three states: coordinates removed, no location data present, or unsupported for that format. Nothing is silently skipped, and a file that never had coordinates is labelled as such instead of being counted as a success. Whole batches can be collected afterwards in a single archive, and all of it happens in your browser, so the photographs never leave your device.

Scans Every File

Each uploaded photo is parsed for stored latitude and longitude, so you learn what is actually present.

Byte Level Cleaning

Supported files have their location entries zeroed in place, leaving the compressed image data untouched.

Three Clear Outcomes

Every file reports removed, already clean or unsupported, so nothing is silently skipped or overclaimed.

Whole Batches at Once

Load as many images as you like and collect the cleaned set afterwards in a single downloadable archive.

No Re-compression

Supported formats are edited rather than re-saved, so picture quality is preserved exactly as it was.

Runs on Your Device

Scanning and cleaning both happen in your browser, so sensitive photographs are never uploaded anywhere.

FAQ

Frequently Asked Questions

JPEG, PNG and TIFF are cleaned at the byte level. Each container stores its metadata differently, so the location values are located inside that particular structure and then cleared in place.

It is scanned, and if coordinates are found the file is reported as unsupported rather than passed off as cleaned. WEBP is not on the byte level stripping path, so nothing is claimed that did not happen.

Use the metadata remover, which re-encodes the image rather than editing bytes in place. That drops every metadata group, not only the location, which is the reliable route for WEBP files.

No. On the supported formats the location entries are zeroed inside the existing file structure, so the compressed image data is never decoded or recompressed, and the picture quality stays exactly as it was.

Each file reports one of three states after processing: coordinates removed, no location data present, or unsupported for that format. Nothing is skipped silently and a clean file is never counted as a removal.

Yes. Add as many images as you like in one go, run the check, then collect the whole cleaned set together in a single archive instead of saving files one at a time.

It targets the GPS entries specifically. Camera settings, timestamps and other metadata groups are left in place, which is what you want when the location is the only sensitive part.

No. Scanning and cleaning both happen locally in your browser on your own device, so nothing is transferred or stored anywhere else, which matters most when the files being checked are the sensitive ones.

Because none was found in it. Many images have already had metadata removed by a phone, a messaging app or a previous export, and the tool reports that honestly instead of claiming it cleaned something.

A connection is needed the first time the metadata parsing library is fetched from its content delivery network, after which your browser caches it. The files themselves are never sent anywhere.