EXIF Viewer & Metadata Remover

See exactly what your photos reveal — camera, timestamp, editing software, and GPS coordinates — then strip it all out without touching a single pixel.

What is EXIF metadata, and what does it expose?

Every photo file is two things at once: the compressed picture, and a set of hidden data blocks wrapped around it. EXIF (Exchangeable Image File Format) is the largest of those blocks. It was designed so cameras could record their own settings, and it is stored as a small TIFF structure tucked into a JPEG's APP1 marker segment, a PNG's eXIf chunk, or a WebP's EXIF chunk. A typical smartphone photo carries the make and model of the phone, the exact lens, the shutter speed, aperture, ISO and focal length, the orientation the phone was held in, the second the shutter fired, and — the part almost nobody expects — the latitude, longitude and altitude of the place it was taken. Alongside EXIF, files often carry XMP (an XML block written by Lightroom, Photoshop and Snapseed), IPTC records inside a JPEG's APP13 segment, plain text comments, and PNG tEXt/iTXt/zTXt chunks that editors use for arbitrary notes. GPS is stored in a way that hides how precise it really is. Latitude and longitude are each three rational numbers — degrees, minutes and seconds — plus a one-letter reference (N/S, E/W) that decides the hemisphere. Converted to decimal degrees, a typical phone writes six decimal places, which resolves to roughly ten centimetres. That is not "the neighbourhood"; that is a specific doorway. Social networks such as Facebook, Instagram and X strip EXIF when they re-encode uploads, which is why people assume the problem is solved. It is not. Email attachments, cloud drive links, Discord and Slack file shares, marketplace listings, forum posts, self-hosted galleries and anything you send over a messaging app in "original quality" all keep the original bytes intact — GPS included. The Software field leaks something subtler but still real: it tells a reader which app touched the file, which can quietly reveal that a "straight out of camera" photo was retouched, or which paid tools a business actually uses. Removing all of this is a header-level edit, not an image edit. The compressed pixel stream never has to be decoded, so a correct EXIF remover produces a file that is smaller but visually and mathematically identical.

Why remove metadata before you share a photo

Metadata removal is one of the cheapest privacy wins available: it costs nothing in quality, takes seconds, and closes a leak that most people do not know exists. This tool shows you the leak first, so you can decide with actual evidence instead of guesswork.

Stop broadcasting your home address. A photo of a bike for sale, a pet, or a room interior usually carries the GPS fix of the place you took it — which for most people is where they live.
Truly lossless. Metadata blocks are dropped at the byte level and the compressed image stream is copied through untouched, so there is no re-encoding, no generation loss, and no risk of the file getting bigger.
Smaller files as a side effect. EXIF blocks with embedded thumbnails, maker notes and XMP packets routinely account for tens of kilobytes per image, which adds up fast across a gallery or an email attachment.
Nothing leaves your device. Parsing and stripping both happen in your browser using the File API, so an image that already contains sensitive coordinates is never uploaded to a server to have those coordinates removed.

How to view and remove EXIF data

Inspection runs automatically the moment a file is added, so you see what is hidden before you decide what to do about it. Removal is a separate, deliberate step.

1

Drop in one or more JPG, PNG or WebP files. Each one is read locally and its metadata appears immediately in a table.

2

Check the results. If GPS coordinates were found, a red warning appears at the top with the decimal latitude and longitude and a link that plots the exact spot on OpenStreetMap.

3

Decide whether to keep the ICC colour profile. Keeping it (the default) preserves accurate colour on wide-gamut photos; the profile itself carries no personal data.

4

Press Remove all metadata, then download the cleaned files individually or as a ZIP. The summary reports exactly how many bytes were removed.

Frequently Asked Questions

No. This tool never decodes or re-encodes the picture. It walks the file's marker segments and chunks, skips the ones that hold metadata, and copies every remaining byte — including the entire compressed image stream — straight through. The output has identical pixels and identical dimensions to the input; the only difference is that the header blocks are gone. Tools that load a photo into a canvas and re-export it do lose quality, because a JPEG re-saved from a canvas is compressed a second time.
If you have ever granted your camera app location access, very likely yes. iPhones and Android phones write GPSLatitude, GPSLongitude and often GPSAltitude into every shot by default. Add a file here and the tool will tell you definitively — if a fix is present you will get the decimal coordinates and a map link, and if there is none you will see nothing in the warning area. You can disable it at the source too: iOS Settings → Privacy & Security → Location Services → Camera → Never, or the Android camera app's Location toggle.
The big social platforms do strip EXIF, because they re-encode every upload. That covers a narrow slice of how photos actually travel. Email attachments, Google Drive and Dropbox links, Discord and Slack uploads, WhatsApp and Telegram files sent as documents rather than photos, classified-ad listings, forum attachments, personal websites and printed-to-PDF documents all preserve the original bytes. Anywhere the file arrives unchanged, the metadata arrives with it.
The APP1 segment (EXIF and XMP), the APP13 segment (Photoshop image resources, which wrap IPTC captions and credits), the APP2 segment when it is not an ICC profile, and COM comment segments. Deliberately kept: the APP0 JFIF segment, because it holds the DPI value used by print software; the APP14 Adobe segment, because it declares the colour transform and CMYK files decode incorrectly without it; and, unless you turn the option off, the ICC colour profile.
From PNG: the tEXt, zTXt and iTXt text chunks (which hold software names, comments and embedded XMP), the eXIf chunk, and the tIME last-modified chunk. IHDR, PLTE, IDAT and IEND are kept, as are pHYs, gAMA, sRGB and iCCP so resolution and colour stay correct. From WebP: the EXIF and XMP chunks, after which the RIFF container length is corrected and the VP8X feature flags are updated so no decoder goes looking for a chunk that is no longer there.
Usually yes, which is why it is on by default. An ICC profile describes the colour space the image was captured in — it contains no camera model, no timestamp and no location. If you strip it from a Display P3 photo taken on a modern phone, browsers fall back to assuming sRGB and the colours shift noticeably, typically towards oversaturated reds and greens. Turn it off only when you are optimising for the smallest possible file and the image is already plain sRGB.
No. Files are read with the browser's File API and processed entirely in JavaScript on your own machine. Nothing is transmitted, nothing is cached server-side, and the tool keeps working if you disconnect from the network after the page has loaded. That property matters more here than on most tools: it would be self-defeating to upload a photo containing your home coordinates in order to have those coordinates deleted.
No — the removal is permanent for the downloaded copy, and there is no undo. Your original file on disk is never modified, so keep it if the camera settings matter to you. Photographers who want to preserve shooting data usually archive the untouched original and share only the stripped copy. If you need to keep the copyright and author fields while dropping location, remove everything here and re-add just those fields in your photo manager.

More Image Tools

Explore other powerful tools for your image editing needs