Image metadata remover

Image Metadata Remover

Reads and rewrites instantly — nothing is uploaded
QUICK ANSWER

Photos and screenshots carry more than the picture. A phone photo can hold the exact GPS coordinates where it was taken; a camera file can hold a serial number that ties every shot you've ever posted to the same body; a screenshot can name the software and account that produced it. Drop a JPEG, PNG, or WebP here and this tool shows you what's actually in the file, then strips it — in your browser, without uploading anything and without re-compressing the image.

  • Shows what it found before removing it
  • EXIF, GPS, IPTC, XMP, and comments
  • JPEG, PNG, and WebP
  • No re-compression, same pixels
  • Keeps the colour profile
  • Nothing uploaded

Files never leave your browser. Reading and rewriting both run locally on your device.

Why this tool exists

  • Runs in your browser. Files never reach our servers.
  • No signup. No usage cap.
  • Works offline once the page is loaded.
Trusted by creators at startups, agencies, and Fortune 500 teams.
This tool is free to use, with no signup.

How it works

  1. 1

    Drop in an image

    JPEG, PNG, or WebP, up to 50 MB. The file is read in the browser with the File API — it is never sent to a server, and the page works offline once loaded.

  2. 2

    Read what it found

    Every field is listed with a plain-English label and a sensitivity rating: GPS coordinates and camera serial numbers identify you outright, dates and device models narrow you down, software strings are low risk. Nothing is removed at this stage.

  3. 3

    Remove it and download

    One click rewrites the file without the metadata containers. The compressed image data is copied across byte for byte, so the picture is pixel-identical to the original — this is not a re-encode.

Where metadata actually leaks

The failure mode is rarely a public photo post — platforms re-encode those and the metadata goes with it. It is the file sent as a file: a screenshot attached to a support ticket, a photo emailed to a landlord, a camera original dropped into a shared Drive folder, an image sent over chat as a document rather than a photo. In every one of those paths the bytes arrive exactly as they left your machine, GPS tags and all. Cleaning the file before it leaves is the only step that reliably works.

Check before you share, not after

The report above runs before anything is modified, so you can use this purely as a viewer — drop a file in, see what it holds, and close the tab. If you are cleaning a screenshot for a bug report, it is worth pairing with blur video region for the recording that goes with it, and Clipy for sharing the whole thing as a link you can revoke instead of a file you cannot take back.

What is EXIF, and what does it actually give away?

EXIF is a block of structured data that cameras and phones write into the image file alongside the picture. The interesting part is not that it exists but how specific it is. GPS tags record latitude and longitude to roughly a metre, plus altitude and a UTC timestamp. BodySerialNumber records the physical camera, which is what lets two anonymous photos be linked to the same owner. Make, Model, LensModel, and Software describe the exact hardware and OS build. DateTimeOriginal records when the shutter fired, down to the second. The practical risk is aggregation. One photo with coordinates is a location. Fifty photos with coordinates is a map of where you live, work, and sleep. Most social platforms strip EXIF on upload, which is why people assume it is handled — but a file emailed, sent over Slack or Signal as a document, attached to a bug report, or uploaded to a forum that does not re-encode still carries everything.

Why this doesn't re-compress your image

The usual browser trick for removing metadata is to draw the image onto a canvas and export it again. That works, but it is a re-encode: a JPEG comes back out with fresh compression artefacts, the file size changes unpredictably, and the ICC colour profile is silently dropped, which can visibly shift colours on a wide-gamut display. This tool never touches the pixels. It walks the container structure — JPEG marker segments, PNG chunks, WebP RIFF chunks — and copies everything except the specific blocks that hold metadata. The compressed image data is passed through unchanged, so the output is bit-for-bit identical to the input everywhere except the parts you asked to remove. For WebP it also rewrites the VP8X feature flags and the RIFF length so the result stays a valid file rather than one that advertises chunks that are no longer there.

Content Credentials are treated as a disclosure, not as metadata

Some images carry a C2PA Content Credentials manifest, or an IPTC DigitalSourceType property, recording how the image was produced — including whether generative AI was involved. These describe the image, not the person holding the camera, so removing them does nothing for your privacy. What it does do is remove information other people rely on to judge what they are looking at. So this tool reports them, explains what they are, and leaves them in place by default while it removes your location and device data. Removing them is possible, behind a labelled checkbox, because there are legitimate reasons to — but it is a deliberate choice, not a side effect of cleaning a photo, and it is not something we recommend or market. Worth knowing either way: a C2PA signature covers the surrounding file bytes, so removing any other metadata already invalidates it. That is why the choice is put in front of you rather than made quietly.

Common questions

Does this upload my image anywhere?

No. The file is read with the browser's File API and rewritten in memory using plain JavaScript. There is no upload, no server-side processing, and no network request involved in the conversion — you can disconnect from the internet after the page loads and it still works.

Will removing metadata reduce my image quality?

No. This is not a re-encode. The tool copies the compressed image data across byte for byte and only omits the metadata containers, so the output decodes to exactly the same pixels as the input. The file gets smaller by roughly the size of the metadata that was removed, and nothing else changes.

Which formats are supported?

JPEG, PNG, and WebP. Those three have well-defined container structures that can be edited without re-compressing, which is what makes the lossless approach possible. HEIC, AVIF, TIFF, and GIF are not supported yet.

Does this remove GPS location from a photo?

Yes. GPS coordinates, altitude, and the GPS timestamp all live in the EXIF GPS IFD, which is part of the EXIF block this tool removes. The report shown before you strip anything decodes the coordinates into plain decimal degrees so you can see exactly what the file was carrying.

Do social platforms strip this for me already?

Usually, but you cannot count on it, and it does not help with the ways files most often leak. Instagram, X, and Facebook re-encode uploads and drop EXIF in the process. Sending the same file as an email attachment, a Slack or Discord file, a Signal 'document' rather than a photo, or an attachment on a bug report or forum post preserves it intact.

Does this remove the AI label from an image?

It isn't built to, and we don't recommend using it that way. C2PA Content Credentials and the IPTC DigitalSourceType marker are disclosures about how an image was made, not personal data, so the default privacy clean leaves them alone and the tool tells you when a file carries one. Removing them is available behind an explicit checkbox because some workflows genuinely need it, but it is a separate, deliberate action — and platforms also run their own detection, so stripping a marker is not a reliable way to change how an image is labelled.

Why keep the ICC colour profile?

Because it is not personal data. An ICC profile describes how the file's colour values map to real colours; dropping it can make an image render noticeably differently on a wide-gamut display. It is kept by default, with a checkbox to remove it if you want the absolute smallest file.

What about metadata in my screen recordings?

Screen recordings have the same problem in a different container — device names, account names, and software versions end up in the file. Recording with Clipy and sharing a link sidesteps it: the viewer streams from a URL you control and can revoke, rather than holding a file that carries whatever your machine wrote into it.

Tool not working the way you expect?

Tell us what broke. We resolve every report within 24 hours.

Send feedback →

More free tools

See all free tools.

Doing this for an AI workflow?

Clipy recordings are agent-readable out of the box. One link carries the video, keyframes, and transcript.

Clipy for AI agents