TrailCam

Guides

Why a photo loses its location when you share it

A photo taken on a hike can carry a GPS coordinate in its own file, the same way a note carries a date. Send that photo to someone else, though, and the copy that arrives can turn out to have no location at all, even though the one still sitting in your camera roll does. Nothing was lost — a second, different copy was made, and that copy was made without the coordinate in it.

The short answer

The location lives in the photo's file metadata, and a fair number of the ways a photo travels off a phone do not carry that metadata along with it. Some strip it on purpose, as a privacy step. Others strip it as a side effect of processing the image before sending it. Either way, the original file on the phone is not touched by any of this — only the copy that left it is affected, and only the copy going through that particular route.

What "location" on a photo actually is

A photo's GPS coordinate is a field inside its file metadata, written automatically at the moment the shot is taken if Location Services is allowed for the camera and a fix was available right then. It is a single latitude and longitude sitting alongside the other metadata a photo carries — the date, the camera model, the exposure settings — not something drawn on the image itself. That is exactly why it can be quietly dropped without changing how the photo looks at all: removing it edits the invisible part of the file, not the picture.

Why sharing strips it

On purpose, as a privacy setting

iOS itself offers a deliberate way to remove it: the share sheet's options include a toggle for location, letting you send a photo with the coordinate left out entirely, on the reasoning that a picture and its exact GPS position are two different things to share and not everyone receiving a photo needs the second one. Where this toggle is offered, its default varies by where the photo is going, so it is worth a glance before assuming either way.

As a side effect of processing the image

Separately, a lot of what a photo passes through before it reaches someone else is not a simple copy. Messaging services and social platforms commonly re-encode an image to save space or standardise it, and rebuilding a file from scratch that way does not automatically carry every field of the original along with it. The location is one of the fields that often does not survive that kind of re-processing, whether or not stripping it was the specific goal.

Where it tends to survive, and where it tends not to

As a rough rule, a route that hands over the actual file — AirDrop, Mail with the original attached, copying through Files — tends to preserve whatever metadata the file already had, location included, because nothing about the file itself changes in transit. A route that re-processes the image on its way through — most messaging apps by default, and essentially all social platforms — tends to strip it, sometimes as policy and sometimes as an incidental result of how the image gets rebuilt.

This is not a fixed list, and it changes with settings and with updates on either end, so it is closer to a pattern worth expecting than a rule to rely on for any one photo.

Checking whether a specific copy still has it

The Photos app shows a location for a picture, on a small map, in its info panel, when one is present in that copy's metadata — checking there before and after sending is the direct way to see whether a particular route stripped it. A copy with no location shown there has none to lose a second time, which also means re-sharing an already-stripped photo cannot make things any worse.

What this does and does not affect on a hike

  • The original photo on your phone keeps its location no matter how many stripped copies get sent from it elsewhere — sharing makes a new file, it does not edit the one already saved.
  • A photo sent to someone with its location intentionally removed for privacy still shows the walk it belongs to just fine; only the exact coordinate is gone, not the picture.
  • If a photo's location was going to be used later to match it against a GPS track of the same walk, that matching has to be done from the original copy on the phone, since a stripped copy sent elsewhere has nothing left to match against.
  • A photo that never had a location to begin with — Location Services was off, or no fix was available at the moment it was taken — was never going to keep one through sharing either way; there was nothing there to strip.

Where TrailCam fits in

TrailCam pins a photo, a video clip of up to two minutes, or a spoken voice note to the exact point on the route where it was captured, inside the app itself, rather than relying on the photo's own embedded coordinate. Replaying a saved route later shows each one in its place regardless of what any shared copy of that photo elsewhere does or does not carry in its metadata. TrailCam is free to download.

Questions

Does sending a photo delete its location from my phone?
No. Sharing creates a new copy for the recipient; the original photo saved on your phone keeps whatever metadata it already had, location included.
Is stripped location metadata always on purpose?
Not always. Some apps remove it as a deliberate privacy option, and others drop it as a side effect of re-encoding the image before sending it, without that being the specific goal.
How can I tell if a photo I received still has a location?
Open it in the Photos app and check the info panel — a location shows as a small map when the copy in front of you still carries the coordinate, and nothing appears there when it does not.

Recording your own routes

TrailCam is an iPhone app that records your route with GPS, keeps video clips, photos and voice notes pinned to the spot where you took them, and exports the result as GPX 1.1 or CSV. It is free to download.

Download on the App Store