Image Metadata Remover

Image Metadata Remover

What the metadata remover does

This page creates a copy of an image with most embedded metadata removed. It accepts JPG, PNG and WebP files, decodes the image in the browser, and re-encodes it to a new file. The result is usually free of EXIF, GPS coordinates, camera details and software tags. You can keep the original format or choose JPEG, PNG or WebP, adjust the quality and download the cleaned image. It is a privacy cleanup tool, not a full metadata editor.

What image metadata can contain

Photos often carry more than pixels. EXIF data can include the camera model, lens, exposure, date, orientation and GPS coordinates. Other chunks can contain software names, editing history, thumbnails, copyright fields or color profiles. Some of that is useful, and some is sensitive. A photo taken at home can reveal a location; a screenshot can reveal an application or a device. Removing metadata reduces that exposure, but it does not make the visible content private.

How removal works

The primary path draws the image to a canvas and exports a new file. That process keeps the visible pixels but generally drops the original metadata blocks. It is not a selective editor: you cannot choose to keep the date while removing GPS. If the browser path fails, the page may use a server-side fallback that processes the image with an image library. Either path creates a new file rather than editing the original in place.

Output format

The output menu defaults to keeping the original format and also offers JPEG, PNG and WebP. Choose a format based on where the image will be used. JPEG is small but lossy, PNG is lossless but can be large, and WebP can be efficient but may not be supported by every older application. Converting a PNG with transparency to JPEG can replace transparency with a solid color. Check the preview before downloading.

Quality and prefer-smallest

The quality slider runs from 10 to 100, with 92 as the default. It matters for lossy formats such as JPEG and WebP; PNG is lossless, so the quality setting has little or no effect there. The prefer-smallest option tries to keep the smaller result when both the original and the re-encoded file are available. A smaller file can mean more compression artifacts, so inspect the result rather than choosing the lowest size automatically.

How to use it

Choose or drop a JPG, PNG or WebP image. Select an output format, or leave the original format selected. Adjust the quality and the prefer-smallest option if you need a smaller file. Press the clean button. The page shows the original and cleaned previews and a size reduction percentage. Download the cleaned file. The output is named with a -clean suffix so it does not silently overwrite the source.

Preview and file size

The dual preview lets you compare the visible result before downloading. The reduction percentage compares the cleaned file with the original, but a smaller file is not always better. A high-quality JPEG may grow when re-encoded, while a low-quality JPEG may shrink and lose detail. Check edges, text and gradients. If the image looks softer or blockier, raise the quality or keep the original format.

Re-encoding is lossy for JPEG and WebP

Removing metadata by re-encoding is not a lossless operation for JPEG or WebP. The image is decoded and compressed again, so some detail is lost even at a high quality. Repeated cleanups can compound the loss. Keep the original file as your master and clean a copy for sharing. If you need a truly lossless metadata strip, use a tool that removes metadata blocks without recompressing the pixel data.

What else may be lost

Canvas re-encoding may also drop color profiles, embedded thumbnails and some ancillary chunks. That can change how a color-managed image appears in another application. It may also bake in the current orientation, which is usually what you want for a shared photo but can surprise a workflow that expects the original orientation tag. For print or color-critical work, compare the cleaned file with the original in the target application.

Limits and server fallback

The client-side path does not state an upload size limit, but very large images can exhaust browser memory. If the primary path fails, the page may send the image to a server-side fallback, and that path has no stated upload cap. Do not use a huge file on a slow connection. The page does not offer selective metadata fields, batch cleaning, a metadata viewer or an undo history.

Privacy and local processing

The primary path runs in the browser, so the image is not uploaded to Newisty. The fallback path may send the image to the server, so the privacy depends on which path succeeds. The cleaned file is downloaded to your device and is not stored in a gallery. Clear the page after use on a shared computer. Removing metadata from a copy does not remove the metadata from the original file.

Common problems

If the download is larger than expected, the re-encode may have used a high quality or a less efficient format. If transparency disappeared, you may have chosen JPEG. If colors look different, a color profile may have been dropped. If the page is slow or crashes, use a smaller image. If the button does nothing, try another browser or a simpler JPG. If the reduction is negative, the cleaned file grew.

When to use it

Use it before posting a photo publicly, sending an image to a client or uploading a screenshot that may contain location or device details. It is also useful for a quick size reduction when you do not need the original metadata. It is not a secure redaction tool for visible information. If the image shows a face, a document or a location, removing metadata does not hide those pixels.

What not to do

Do not assume the metadata is gone from the original. Do not repeatedly re-encode the same JPEG. Do not choose JPEG for an image that needs transparency. Do not use the tool as the only privacy step for a sensitive photo. Do not ignore a visible document or face in the image. Do not treat a smaller file as proof that the image is safe to share.

Frequently Asked Questions