Does Cropping a Photo Remove GPS Metadata Too?

What is actually happening

A digital photo file has at least two layers people casually merge into one idea: the raster (the pixels you see) and the metadata (structured tags stored alongside those pixels). GPS coordinates live in metadata — commonly in EXIF GPS IFD fields, sometimes mirrored or supplemented in XMP. Cropping is an operation on the raster: the encoder keeps a rectangular subset of the image, updates width and height, and writes a new or modified file. Whether the encoder also copies GPS tags is a separate decision in the software’s save pipeline.

Many consumer editors default to preserving as much metadata as they can, because photographers want timestamps and camera settings to survive routine edits. Location often rides along for the same reason. Other editors re-encode from a decoded bitmap and only write a minimal header, which can drop GPS as a side effect. Both outcomes exist in the wild. That split is why a friend can swear “cropping removed my location” while your phone still embeds coordinates after an almost identical gesture.

Cropping also does not rewrite the meaning of coordinates. If you cut the house out of the frame but leave GPS intact, the file still asserts “taken at these lat/long values.” Viewers who never open Properties will not see that; anyone who does — or any tool that reads EXIF — will. Pixel redaction and metadata redaction solve different leaks. For dedicated location cleanup, see remove GPS from a photo and how to remove GPS and location data from a photo.

Related misconceptions travel with this one: “screenshots remove GPS” (they create a new file; they do not define your editor’s crop behavior), “social networks always strip GPS so cropping is enough” (network pipelines vary and do not clean your email attachment), and “a smaller file means metadata is gone” (recompression can shrink bytes while copying tags forward).

How to handle this with MetadataWipe

Crop first for composition and privacy-in-frame (remove badges, screens, reflections, house numbers). Save that visual result. Then open the cropped file in the MetadataWipe browser tool and strip identifying metadata, including GPS. Processing is client-side in your browser — no account and no server upload for cleaning — so you are not sending the image to a remote processor just to clear tags. Share the cleaned export, not the pre-strip crop.

Verify after. Open file properties or an EXIF viewer and confirm location fields are absent. If your threat model includes device serials or exact timestamps, confirm those categories too. Keep an unshared original with full metadata if you need it for your own records; distribution copies should be the cleaned ones.

If you crop again later, strip again. Each new save from a gallery or editor can reintroduce or retain tags depending on the app. Make “crop → strip → share” a fixed order rather than hoping the crop alone was enough this time.

Real scenarios

A parent crops a kids’ party photo to exclude another child’s face before a class WhatsApp share. Faces are handled; the GPS still points at their home address. A classmate’s relative downloads the image and inspects it out of curiosity. The crop solved a consent problem and missed a location problem.

A marketplace seller crops a serial number off a device photo but leaves EXIF location from the packing room. Buyers do not need that. The seller assumed “edited photo” meant “clean photo.”

A hiker crops a trail panorama to a vertical for Instagram. Instagram’s pipeline may strip GPS from the public feed derivative, and the hiker concludes cropping worked. Later they email the same cropped JPEG to a friend; GPS is still present because email never ran the social re-encoder. The crop was innocent either way — it was never the control that removed location.

A journalist crops a bystander’s identity out of a documentation shot for publication. Newsroom policy also requires metadata review. Without that second step, the cropped file could still carry coordinates of a sensitive site. Professional workflows treat crop and strip as paired, not interchangeable.

Common mistakes

Equating “looks different” with “metadata changed.” Trusting one app’s crop behavior on all devices. Checking only the in-app map preview (which may hide file GPS) instead of the file’s EXIF. Cropping after a clean strip in an editor that writes location back from the library database. And posting a cropped image while simultaneously linking a cloud folder that still holds the full-frame GPS-rich original.

Another mistake is heavy quality reduction “to destroy metadata,” which may still fail and costs image fidelity. Use a real strip pass. When you select the file in MetadataWipe, ordinary Upload UI language is fine — what matters is browser-based local processing, not avoiding the word upload entirely.

Finally, do not confuse on-photo map stickers or social “check-in” locations with EXIF GPS. You can remove file GPS and still reveal a place by typing it into the post. Cropping neither writes nor clears those product features.

Related guides

See also:

• Remove GPS from a photo
• How to remove GPS and location data from a photo