Strip EXIF, GPS and IPTC data at the byte level — the pixels come out bit-identical, because nothing is ever re-encoded.
Your files never leave your browser — all processing is local.
Recommended. Keeps a minimal Orientation tag so viewers show the photo upright, plus the colour profile if the switch below is on. Everything else — camera, GPS, timestamps, thumbnails — is removed.
Drop photos here
or click to browse — JPEG and PNG, any number of files
Lossless here has a precise, checkable meaning, so start with what happens to the bytes. A JPEG is a chain of marker segments, and the metadata sits in segments of its own: APP1 carries EXIF — camera, timestamps, GPS — APP13 carries the IPTC and Photoshop blocks, APP2 can carry an ICC profile. Cleaning the file means walking that chain, dropping the segments that hold metadata, and copying the compressed scan data straight through. The entropy-coded image data is never decoded, requantised or re-encoded; it is copied byte for byte, so the pixels that come out are bit-identical to the pixels that went in. Not visually identical. Identical.
Almost every other metadata remover works the other way round: it decodes your JPEG, loses the metadata by virtue of having discarded the whole file, and encodes a new one. That does clean the photo, and it costs you a generation of quality every time — fresh quantisation on top of the old, blocking around edges that were already soft, and often a bigger file than you started with. Strip metadata twice and you pay twice. PNG gets the same byte-level treatment: a PNG is a chain of chunks, so tEXt, iTXt, zTXt and eXIf are dropped while the IDAT image data is copied untouched. Nothing is recompressed, in either format.
Drop in a whole folder of photos and they are cleaned in one pass, downloadable individually or all at once. Each file comes with a before/after metadata comparison — which tags were found, which were removed, what is left — because 'metadata removed' as a bare claim is not something you can check, and being checkable is the entire point of this page. Re-open a cleaned file in the EXIF viewer if you want a second opinion from a different code path. All of it runs in your browser: a tool that offered to protect your photos' privacy by uploading them to a server first would be a strange thing to trust.
The reason this matters is dull and specific. A photo taken in your living room and posted publicly usually contains the coordinates of your living room to within a few metres, plus the time it was taken and the phone that took it. Sell something on a marketplace with a shot taken at home, post your dog in a hobby group, send a holiday picture to a forum — the address travels along in fields nobody reads until somebody does. Big platforms recompress uploads and strip metadata as a side effect, but direct file transfers do not: email attachments, cloud links, Discord and Telegram file sends, anything handed over as a file. Clean it once, before it leaves.
No, and it is worth being concrete about why. Metadata and pixels live in different parts of the file. In a JPEG the pixels are the entropy-coded scan data; in a PNG they are the IDAT chunks. This tool never hands either of those to a decoder — it copies them to the output unchanged and simply omits the metadata segments around them. Nothing is decompressed, so nothing is recompressed, so there is no quality generation to lose. The output is a few kilobytes smaller, or a few hundred if an embedded thumbnail went with the EXIF, and every pixel is bit-for-bit what it was. If you want to prove it, compare the two files in the binary diff tool: the only bytes that moved are the ones that described the photo rather than being the photo.
Removed: EXIF in APP1 (camera, lens, exposure, DateTimeOriginal, GPS, camera serial), the IPTC and Photoshop blocks in APP13, XMP, JPEG comment segments, and any thumbnail embedded alongside the EXIF; in PNG, the tEXt, iTXt, zTXt, tIME and eXIf chunks. Kept by default: the ICC colour profile — APP2 in JPEG, iCCP and the colour chunks in PNG. That last one is a judgement call, and the reasoning is that an ICC profile says nothing about you, your camera or where you stood, while removing it changes how the photo looks: a Display P3 image rendered as sRGB comes out visibly duller. A privacy tool should not quietly shift your colours. If you want the profile gone as well, there is a switch for it.
This is the one real trap, so the tool takes a side. Phones usually store the frame in the sensor's native orientation and add an EXIF Orientation tag meaning 'rotate this when displaying'. Strip that tag with everything else and the pixels are still untouched, but any viewer that was relying on the tag now shows the photo sideways. Rotating the pixels for real would fix it and would also mean re-encoding, which is the one thing this page exists not to do. So the default output keeps exactly one tag: a minimal APP1 block containing Orientation and nothing else — no camera, no timestamp, no GPS — which is all a viewer needs to draw the photo the right way up. Strict mode drops even that for a file with zero metadata; use it when you want absolutely nothing left, and expect some viewers to show the photo rotated. The comparison table tells you which case a given file is in, since a photo whose Orientation is already 1 loses nothing either way.
JPEG and PNG. Those two cover almost everything people need to clean — .jpg/.jpeg off a camera or phone, where EXIF and GPS live, and PNG for screenshots and tool exports, which pick up tEXt chunks naming the software that made them. WebP, HEIC, AVIF and TIFF are not supported yet, because each container needs its own byte-level surgery to keep the same promise; WebP's RIFF chunks are the likely next step. Converting one of those to JPEG would re-encode it, so it is not offered here as metadata removal — if a conversion is what you want, the image converter does that job openly, and you can clean the result here afterwards.
No. Every file is opened locally with the File API, the segment and chunk surgery runs in JavaScript in your own tab, and the cleaned file is handed back as a download your browser generated. This page is a static file with no API behind it, so there is nowhere to upload to even in principle, and it keeps working with the network switched off. For this particular tool that is not a detail: the photos you most want to strip GPS from are the photos you least want to send to an unknown server, and an upload-based cleaner has already had the coordinates you were trying to remove.
Read every EXIF tag first, or re-open a cleaned file to check it.
Compare the original and cleaned files byte by byte.
Need a format change too? Convert here, then clean the result.