EXIF Image Metadata Scrubber

What is EXIF metadata

EXIF (Exchangeable Image File Format) is a standard that specifies how metadata about a multimedia file can be embedded directly within the file itself rather than kept in a separate sidecar file.¹ The photos taken with most modern smartphones and digital cameras contain far more hidden data than most people realise: the GPS coordinates where the photo was taken, the make and model of the device, the precise time and date, and camera settings such as aperture, shutter speed, ISO, and focal length.²

What travels with the file

This metadata stays invisible when you view the image normally, but it travels with the file whenever you share, upload, or send it to someone else. Tools such as ExifTool let anyone who receives the image read and modify those hidden fields, which means the embedded data persists across every copy you hand over until you deliberately strip it out.³

Screenshots are the one common image type that starts out clean. A screenshot is a new image file your operating system writes, not a photo a camera captured, so it carries no camera EXIF: no GPS coordinates, no lens data, no capture settings, and no camera make and model. Pasting a screenshot into the scrubber commonly lands on the no-metadata-found state, which is the correct result rather than an error. The one subtlety worth knowing: a screenshot of a photo copies the pixels but never the original's metadata, so the coordinates of the underlying photo do not survive the screenshot either.

GPS data privacy risk

GPS coordinates embedded in photos can be accurate to within a few metres, and most people never realise that a single snapshot can place them on a map with that level of precision.⁴ A photo taken at home and shared publicly reveals your home address, a photo taken at work reveals your workplace, and a series of photos taken over time can expose your daily routine in detail.

Why ordinary-looking photos still leak location

Location metadata is a privacy risk even when the image itself looks completely ordinary, because the coordinates sit silently alongside the picture data and travel with every copy. Some photo-sharing platforms strip metadata on upload, but that behaviour is a platform choice rather than a guarantee, and it does not apply to file hosting services, messaging apps, or direct file transfers where the original file passes through untouched.

Where unscrubbed files actually travel

Some transfer paths pass the original bytes through untouched. Messaging apps that send a photo as a file attachment, file-hosting links, marketplace and listing uploads, and email attachments all move the file itself, and the metadata travels exactly as embedded because nothing in the pipeline rebuilds the image. In each of these cases the recipient can open the file in a metadata viewer and read every field your camera wrote, the same as if you had handed them a copy on a USB drive. The platform's name on the interface says nothing about which case you are in.

Other platforms rebuild the image during upload. Resizing, re-compressing, and re-encoding all produce a new file, and producing a new file drops most of the original metadata as a side effect rather than as a privacy promise. That distinction matters: re-encoding is an engineering choice the platform can change at any time, and nothing obliges it to keep dropping your fields. The only behavior you control is the state of the file before you share it, so scrub at the source and every downstream path, from email to marketplace to messaging, is safe regardless of what the receiving service does.

How the scrubber works

This tool operates at the binary level, reading the raw bytes of your image file and removing the metadata containers directly, all without ever re-encoding the image data. Because the picture pixels themselves are never decoded and recompressed, the visual content of your photo is completely unchanged and there is zero quality loss of any kind.

For JPEG files, metadata lives in application-specific marker segments before the image data.⁵ For PNG files, it lives in ancillary chunks.⁶ For WebP, it lives in chunks inside the RIFF container.⁷ The scrubber iterates through each container, splices out the unwanted segments, and reconstructs a fully valid image file, producing output that is bit-for-bit identical to the original except for the removed metadata sections.

Keeping the fields you want

Removal does not have to be all or nothing, because the checkboxes let you name exactly what leaves the file. Every field in the metadata table starts checked, so the default pass removes everything the file carries, and unchecking any field or a whole category keeps it in the downloaded copy. The classic use is the GPS-only scrub: uncheck every category except GPS / Location, and the output keeps the camera data while the coordinates vanish. The live size estimate updates with every checkbox change, so you watch the cost of each decision before downloading rather than after.

The keep side has real uses. For a photographer publishing a portfolio, the exposure settings may be worth preserving while the location quietly disappears, because the settings are the craft and the location is the leak. A stock contributor may keep the copyright and credit fields while removing everything that identifies the shoot location, because credit must travel and coordinates must not. In both cases the checkboxes turn partial scrubbing into a first-class operation instead of an unsupported afterthought, and the same file can leave the device twice with two different purposes.

A before-and-after comparison shows exactly what changes. A typical smartphone photo's metadata table lists GPS coordinates such as 40.7128° N, 74.0060° W, a camera model of iPhone 15 Pro, and a timestamp of 2026-03-14 09:22:11 before scrubbing. After scrubbing, the same table shows none of those three fields, only the image dimensions and file size the browser reads directly from the pixel data.

Supported formats

The current version of the scrubber supports JPEG, PNG, and WebP, the three formats that cover the vast majority of images people share from phones, cameras, and the web today. Each of these stores metadata in a different binary layout, so the scrubber uses a format-specific parser to locate and remove the right segments without disturbing the image data around them.

Why HEIC is not yet supported

HEIC and HEIF, the formats Apple devices default to for high-efficiency photo storage, are built on a more complex container structure that bundles image items, metadata, and thumbnails in a way the current parser does not yet handle.⁸ Adding reliable HEIC support requires a separate decoding path, so it is planned for a future version rather than shipped as a partial implementation that could leave metadata behind.

Camera fingerprinting beyond location data

GPS coordinates receive the most attention, but EXIF contains several other fields that can identify you even without a location.¹ The camera make and model fields identify your device type, while lens data such as focal length, aperture, and lens model can narrow the equipment used for a photo.⁹ For journalists protecting source anonymity, photographers working in sensitive contexts, or anyone sharing images consistently from one device, GPS is only one part of the metadata risk.

Identifiers also hide in MakerNotes, a proprietary tag where camera manufacturers park settings the standard does not list, such as shooting modes, post-processing settings, and serial numbers.⁹ Beyond any metadata tag, unique noise patterns from the image sensor create a statistical fingerprint that correlates across photos from the same physical camera body.¹⁰ This analysis requires specialised software and is not visible in any EXIF viewer, but it is worth understanding that scrubbing EXIF removes the machine-readable metadata layer while the underlying image data may still carry sensor-level identifiers. For everyday privacy purposes, removing EXIF is the practical and effective step.

The evidentiary question runs in both directions. As evidence, metadata can support or undermine a claim about when and where a photo was taken, but the layer is machine-written and freely editable, and any tool that can read the fields can also rewrite them, which caps how much weight it can carry on its own.³ The flip side holds too: a scrubbed photo cannot testify about its own origin at all. Choosing to scrub trades a small evidence trail for privacy, and knowing which side of that trade you need is the actual decision.

IPTC and XMP metadata containers

EXIF is one of several metadata containers in image files.¹¹ IPTC (International Press Telecommunications Council) stores editorial metadata: caption, credit, copyright notice, keywords, and the creator's name and contact information.¹² Publishing workflows in news agencies and stock photo libraries write IPTC data automatically at export. XMP (Extensible Metadata Platform), developed by Adobe, stores a superset of both EXIF and IPTC fields in an XML format embedded inside the file.¹¹ Adobe tools can write or update XMP metadata alongside the original EXIF segment. CapyToolkit's scrubber targets all three metadata containers, removing the EXIF, XMP, and IPTC segments from JPEG, PNG, and WebP files in a single pass so you are not left with partial metadata behind after stripping only the EXIF segment.