Inspect private details
Review embedded camera, date, author, GPS, and editing metadata, then create a clean re-encoded copy.
JPG, PNG, WebP, or AVIF · up to 32 MB · adaptive 8–24 megapixel limit
Your image never leaves this browser
Images stay in browser memory and are never uploaded by these tools.
Decode and export JPG, PNG, WebP, and AVIF using browser and WebAssembly codecs.
Re-encoding can alter metadata, animation, profiles, or quality, so verify every output.
Complete tool guide
See the hidden information stored inside a photo—camera make and model, lens, capture date and time, software, author, copyright, and GPS latitude and longitude—then save a clean copy without it. Everything is read in your browser, so a photo you are checking for privacy is never uploaded to do so.
Your input is processed in the current browser tab and is not sent to the application server.
Choose or drag in one JPG, PNG, WebP, or AVIF image.
Review the file size, dimensions, and format, then scan the metadata table for GPS, date, and camera fields.
Set the output quality for the clean copy; 82% is the default for JPG, WebP, and AVIF.
Select Create clean copy and download the file named …-metadata-removed.
Lists every readable field, sorted alphabetically, with its value. Look for latitude, longitude, and GPS fields for location; Make, Model, and LensModel for the device; and DateTimeOriginal for when the photo was taken.
The clean copy is created by re-encoding the visible image, so JPG, WebP, and AVIF use this quality setting. PNG remains lossless.
After creating the clean copy, the tool reads it again. If any GPS, camera, author, date, location, or similar field is still present, the copy is not offered for download and an error explains why.
Start with: IMG_5512.jpg · 4032 × 3024 px · taken with location services on
IMG_5512-metadata-removed.jpg · 4032 × 3024 px · no GPS, camera, or date fieldsThe clean copy was re-read before download, and it would have been blocked if any location, device, or date field had remained. The pixels are the same upright photo; only the hidden data is gone.
Start with: screenshot.png · 1920 × 1080 px
No GPS or camera fields · PNG header information onlyScreenshots are created by software, not a camera, so they rarely contain location or device data. Some editors add a Software or creation-time field, which the clean copy removes.
EXIF holds camera settings, dates, orientation, and GPS coordinates. XMP and IPTC hold editing history, captions, keywords, author, and copyright. ICC profiles describe color. PNG files also have a header with width, height, bit depth, and color type.
Instead of editing fields in place, the tool draws the visible pixels and encodes a brand-new file. Browser encoders do not write EXIF, GPS, XMP, or IPTC data, so none of it carries over. Because it is re-encoded, file size and compression can change, and wide-gamut color may look slightly different.
File size, dimensions, and format are shown for every supported image. Embedded fields are read from JPG, PNG, and AVIF files; WebP metadata is not read by the current viewer, although a clean copy of a WebP is still created by re-encoding.
Choose the photo and look for latitude, longitude, or fields beginning with GPS in the metadata table. If none appear, the viewer found no location in a format it can read.
Choose the photo, select Create clean copy, and download the new file. It is re-encoded from the visible pixels, so EXIF, GPS, XMP, and IPTC data are not included, and the tool double-checks the result before offering it.
No. It appears only when location access was enabled for the camera and the data survived any later editing or sharing. Screenshots normally have no GPS data.
No. The metadata is parsed by a library running in your browser tab, and the clean copy is created there too.
The current viewer does not read WebP metadata blocks, so an empty table does not prove a WebP is clean. Creating a clean copy still re-encodes it without metadata.
Keep working
Continue with another focused tool from the same collection.