Skip to content
checkaifree

Local tool

Remove metadata from an image

Choose whole metadata categories to remove from a static JPEG, PNG or WebP, then download a verified copy. Compressed image bytes are copied unchanged. The file stays in your browser.

18 October 2026 · Check AI Free

Local metadata remover

Choose metadata to remove and download a copy

Choose a static JPEG, PNG or WebP image. Select whole metadata categories, keep the ICC color profile if wanted, and create a copy in your browser. Nothing is uploaded.

No file chosen, or drop one here

Up to 20 MB. APNG, animated WebP and multi-picture JPEG are rejected. GPS lives inside EXIF; removing EXIF removes that entire container and its orientation tag, which may change displayed orientation. Unknown metadata or previously shared copies can still exist. Browser acceptance: Chromium; Safari and Firefox compatibility has not yet been checked.

Clean a batch and download verified copies in a ZIP

Apply a whole-container policy to up to 20 static JPEG, PNG or WebP files, one file at a time. Each copy is re-read and its retained compressed image bytes checked before it enters the ZIP. The original files stay unchanged and nothing is uploaded.

No files chosen, or drop them here

20 MiB per image, 100 MiB total. APNG, animated WebP and multi-picture JPEG are rejected. The ZIP stores the verified files without recompression, so its size is close to the combined image size.

Whole metadata categories to remove

EXIF removal includes orientation and all GPS inside that container, and may change displayed orientation. JPEG APP11 removal covers other JUMBF data too; APP13 removal covers other Photoshop resources. PNG text removal also removes XMP inside those text chunks. Unknown metadata may remain, and existing credentials are not re-signed.

The original sample includes a JPEG with fictional GPS, a PNG with duplicate author fields, a WebP with an invented creator and a deliberately damaged PNG. The JPEG and PNG share same-name.img; output extensions follow their actual containers. Default removal produces three verified copies and one error.

After downloading, inspect the copies with the batch metadata inspector or image privacy checker. Removal is limited to supported containers; visible text, watermarks and hidden information can remain.

Choose containers and verify the copy

Select the supported categories you want to remove. JPEG EXIF and XMP use APP1; Photoshop/IPTC use APP13; the credential option removes all APP11 containers, including other JUMBF data. JPEG comments, unrecognized APP1 and trailing bytes form a separate option. The compressed scans and unselected segments are copied byte for byte. Multi-picture JPEG is refused because its internal offsets need a different writer.

PNG options cover eXIf, text, XMP with the exact XML:com.adobe.xmp keyword, caBX credentials, ICC and other supported ancillary metadata. PNG text includes prompts and workflows. All text is removed together when that category is checked. APNG is refused, including files with acTL, fcTL or fdAT. Unknown critical chunks are refused. In WebP, selected EXIF, XMP, ICCP and C2PA chunks are removed, corresponding feature flags and RIFF length are updated, and the compressed image data is copied. Animated WebP is refused.

Keep the embedded ICC profile checked to preserve that profile’s bytes. A profile cannot be preserved if none was present. Removing EXIF can remove an orientation tag and change displayed orientation even though the compressed pixels match. Before the download appears, the output is parsed again, selected containers are checked absent, and every retained segment or chunk is compared with the input. A selection with no matching containers gives a genuine unchanged copy. There is no automatic Canvas fallback.

When to strip, and when to keep the original

  1. Step 1

    Keep an untouched original

    Stripping is for the copy you are about to send. The camera original, the generator’s download, or the file a client delivered is evidence of what that file contained. Download the cleaned copy under a new name. The tool suffixes the name with metadata-copy and does not overwrite a file on disk by itself.

  2. Step 2

    Read the fields you are about to drop

    GPS, a creator name, a prompt and a Content Credentials manifest are easy to delete and hard to remember. If the question is “what did this file claim?”, read it with the viewers on this site before you strip it. A later argument about a missing EXIF block is much weaker if you never recorded that the block was there.

  3. Step 3

    Prefer the segment copy for photos

    Select the EXIF category to remove the full camera/location container. The result lists the actual method and removed containers. Reopen the downloaded copy in the EXIF viewer to inspect the result. Keep your untouched original.

  4. Step 4

    Do not confuse stripping with anonymity

    A face, a house number, a school shirt or a screenshot of an account is still in the pixels. Metadata removal does not blur those. It also does not pull the picture back from a platform that already stored a copy. The metadata guide explains why a platform’s own recompress is a different event from this download.

There is a second, quieter reason people strip a file: they hope a detector will stop naming a generator. That is a reason to understand the limit, not a reason to expect a different pixel. A Stable Diffusion parameters block and a ComfyUI workflow are PNG text. Removing them removes the claim. It does not change the image data. The image checker can still look at a smaller copy of the pixels, and it will say when it is doing that. This remover never sends the file. If you wanted the workflow saved somewhere, copy it first with the ComfyUI reader.

Files over 20 MB are refused before the browser holds several copies. A smaller file can still fail when a segment length points past the end of the buffer. That failure is reported without a download. Container removal is not a forensic wipe. The status line says the work happened in the browser and the file was not uploaded.

Questions

Is the photo uploaded to remove its metadata?

No. JPEG, PNG and WebP files are rewritten in your browser. The cleaned file is downloaded from this page. It is not sent to a server for stripping.

Does this remove GPS?

Yes, when the location is stored in EXIF or XMP the way cameras usually store it. Those segments and chunks are dropped. GPS hidden inside the compressed pixels, or already copied to another service, is outside what a container rewrite can do.

Will the picture look the same?

For supported static JPEG, PNG and WebP containers, the compressed image data is copied unchanged. You can keep or remove the embedded ICC profile. Removing orientation or color metadata can still change how a viewer displays the image. Animated files and unsupported structures are refused.

Does stripping metadata make an AI image look like a photo?

No. It only removes containers. A detector that looks at pixels can still run. A person can still recognize a synthetic picture. Removing a manifest or a prompt also removes a clue you might have wanted to keep.

What does the download not promise?

It does not erase copies in a chat, a social network, a backup or a camera roll. It does not remove a watermark drawn into the pixels. It does not make the file anonymous if your face, a document, or a background already identifies you.

Sources

  • JPEG specification — Why APP segments can be removed without rewriting the entropy-coded scan.
  • W3C PNG specification — Chunk structure, text metadata, and animation chunks; unsupported critical chunks are refused.
  • WebP container — EXIF and XMP chunks, and the VP8X flags this tool clears.
  • Metadata survival, edition 1 — A local export that omitted metadata, and a screenshot, both lost the camera fields.

Related