October 23, 2026

Does cropping or editing a photo remove its metadata?

Short answer: no. Cropping changes which pixels are in the file. Metadata lives in a separate part of the file entirely, and almost every editor copies it forward untouched.

Worse, editing usually adds fields. And in some cases the part you cropped out survives inside the file you just saved.

Why editing doesn't touch metadata

A JPEG is a container. The pixels sit in one section, and metadata sits in others — EXIF in an APP1 segment, XMP in another APP1, IPTC in APP13, colour profile in APP2. Crop the image and you have rewritten the pixel section. Nothing instructs the encoder to clear the rest, so a well-behaved editor preserves it, because preserving it is usually the correct behaviour. Photographers want their copyright tag and capture settings to survive an edit.

GPS is in that preserved block. So are the timestamp, the camera model, the lens, and the serial number. Crop a photo down to a single face and the file still says where and when it was taken, and which camera took it.

This covers nearly everything people assume is a fix:

What editors add

Beyond keeping what was there, editors write their own records.

Software            : Adobe Photoshop 26.2 (Windows)
Creator Tool        : Adobe Photoshop Lightroom Classic
Document ID         : xmp.did:9c2f1a4b-...
Original Document ID: xmp.did:41ab77e0-...
History Action      : saved, derived, converted
History When        : 2026-10-23T14:02:11+01:00

Adobe's XMP history fields are the notable ones. OriginalDocumentID links an exported image back to the master file it came from, which means two images you published separately can be tied to the same original — and to each other — even if nothing else about them matches. That is the same correlation problem as the camera serial number, created at edit time rather than capture time.

The thumbnail that didn't get cropped

EXIF can carry a small embedded preview of the image, stored in a second directory inside the metadata block. Viewers and file managers use it to render thumbnails without decoding the full picture.

Here is the problem. It is a separate image. If an editor updates the main pixels and writes the metadata block back without regenerating that preview, the file contains a cropped photo and an uncropped thumbnail of the same photo.

This is not hypothetical. It caused a well-documented privacy incident in 2003, when a presenter published a photo cropped in a then-current version of Photoshop and the embedded thumbnail still held the original frame. The editors involved were fixed long ago, and mainstream tools now regenerate the preview — but "mainstream tools now do the right thing" is a weaker guarantee than it sounds when the set of tools touching your photos includes phone galleries, web editors, and whatever app you installed once to add a border.

Check it yourself. It takes one command:

exiftool -b -ThumbnailImage photo.jpg > thumb.jpg

Open thumb.jpg and compare it to the photo. Empty output means there's no embedded preview, which is the answer you want. If a thumbnail comes out, look at it before you decide the crop did its job.

The same logic applies to black boxes and blur. You painted over pixels in the main image. If a preview generated before that edit is still in the file, it was never painted over.

The exceptions that do strip

Some editors drop metadata, and it's worth knowing why, because the rule generalises.

Simple tools that rebuild the file from a bitmap — MS Paint, many basic online croppers, anything that decodes to raw pixels and re-encodes — lose metadata as a side effect. They don't have a metadata model, so there is nothing to write back. This is the same mechanism that makes social platforms strip EXIF on the copies they serve.

But treating that as a privacy feature is a bad bet. It's incidental, it varies by tool and by version, and an online cropper that strips metadata still received your original with the GPS intact. Don't infer the behaviour — test the specific tool you use, once:

exiftool -a -G1 edited.jpg

What about screenshotting the photo?

Screenshotting an open photo does break the EXIF chain, since the screenshot is a new capture of the screen. It's a real technique, and it has three costs: you lose resolution, you lose colour accuracy, and the screenshot carries metadata of its own — device, screen dimensions, sometimes a timestamp. On top of that, cropped screenshots had their own serious flaw for years on both Android and Windows. What screenshots actually leak covers that.

It works, but it's a lossy workaround for something a cleaner does properly in a second.

Order of operations

The practical rule is about sequence, not tools.

Edit first. Clean last.

If you clean a photo and then crop it in your usual editor, the editor writes a fresh Software tag, a new XMP history block, and possibly a new document ID into the output. You cleaned the input to the step that re-dirties the file. Any cleaning has to be the final operation before the file leaves your control.

To actually remove metadata, the file has to be rebuilt from pixels alone. Draw the image to a canvas, read the bitmap back, encode a new file — metadata never enters a bitmap, so nothing carries across, including the embedded thumbnail. That's what the metadata cleaner does, locally in your browser, which also avoids the online-cropper problem of handing your original to a server to get a clean copy back.

Then verify, on the file you're actually about to send:

exiftool -a -G1 -GPS:all final.jpg

No exiftool to hand? The image metadata viewer lists every field it finds, including the embedded thumbnail, and runs on your phone.

The short version

Cropping, resizing, filtering, and rotating all change pixels and leave EXIF alone, so GPS and camera details survive every one of them. Editors add their own tags on top, including identifiers linking exports back to a shared original. The embedded preview is worth one check of your own, because a crop that leaves it in place hasn't fully cropped anything. Edit first, clean last, and verify the final file rather than the edit step.

Related: does converting HEIC to JPG remove metadata? — the other transformation people assume cleans a photo.