Photo metadata
Why is my photo location missing? Check GPS on iPhone
If Photos showed a map but a shared image has no location, you may be looking at two different files. Here is how to check the original and understand why GPS can disappear.
What is actually being lost
When your camera takes a photo it writes two things: the picture, and a block of structured data describing the picture. That block is called EXIF, and it holds the capture date and time, the camera and lens, exposure settings, orientation, and — if Location Services were on — latitude, longitude, altitude and compass heading.
EXIF lives inside the image file, but it is not part of the image. Nothing in the pixels records where the photo was taken. Strip the EXIF and you still have a perfectly good picture that now knows nothing about itself.
That distinction is the whole problem. Every system that touches your photo on the way to someone else decides independently whether to carry that block along.
Why platforms remove it
Three reasons, and only one of them is about you.
- Privacy. A public photo carrying exact coordinates tells strangers where you live, work, or were at a given hour. Platforms that host public content generally strip location rather than field the consequences.
- File size. Uploads get re-encoded to save bandwidth. Re-encoding means writing a new file from the decoded pixels, and metadata is not carried across unless the code deliberately copies it.
- Indifference. A lot of stripping is not a policy at all. It is a side effect of resizing, and nobody wrote the extra lines to preserve the block.
Roughly what survives where
Behaviour changes without announcement, and often differs between a platform's app and its website. Treat the table below as a starting point and verify anything that matters — the next section shows how.
| Route | Typically keeps location? | Notes |
|---|---|---|
| AirDrop | Yes | Transfers the original file, metadata intact. |
| Email attachment | Usually | Depends on the client; some offer to resize, which strips. |
| iOS Messages | Yes, unless you turn it off | The share sheet remembers your last choice. |
| No | Images are re-encoded on send. | |
| Instagram, Facebook, X | No | Stripped on upload for public content. |
| Cloud storage links | Usually | Syncing the original file generally preserves it. |
| Screenshot of a photo | No | A screenshot is a new image with its own, unrelated metadata. |
How to check any photo yourself
On iPhone
Open the photo in Photos and swipe up, or tap the info button. If a map appears, the file has coordinates. If the panel shows no map, it has none. You can also tap Adjust beside the location to see the exact values.
On a Mac
Open the file in Preview, then choose Tools ▸ Show Inspector and select the GPS tab. No GPS tab means no GPS data.
The test worth running once
Send yourself a photo by whichever route your team actually uses — the group chat, the ticketing system, whatever it is — and check the copy that arrives. That single test tells you more than any table, because it tests your real workflow rather than a general claim about a platform.
Why you cannot get it back
This is the part people find hardest to accept. If a copy arrives without coordinates, the coordinates are not hiding somewhere in the file. They were not written. There is nothing to recover.
You can go back to the original in your own camera roll, which almost certainly still has them. But if the original is gone, or it was someone else's phone, or the chain has passed through two platforms — the location of that photo is simply unknown, and no tool can reconstruct it from the pixels.
Which is why relying on EXIF surviving a journey you do not control is a fragile way to keep records.
The approach that survives everything
There is one form of metadata no platform strips, because it is not metadata at all: pixels.
If the date and coordinates are drawn into the visible image, they travel wherever the image travels. Re-encode it, screenshot it, print it, paste it into a report — the information is still legible, because it is part of the picture now.
That is what Metadata Engraver does. It reads the EXIF your camera already wrote and renders the fields you choose onto the image itself, on your device. The export is an ordinary photo that happens to state its own date, coordinates, address and camera settings.
It does not invent anything. If the photo has no GPS, the location fields stay empty — the app can only show what the camera recorded. Which brings us to the honest caveat below.
What a burned-in stamp is not
A stamp makes information durable. It does not make it verified. The app displays what the file says; it has no way to confirm the camera clock was right or that the coordinates were accurate. Anyone relying on a photo for an insurance claim, inspection or legal matter should treat the stamp as a convenience, not as proof, and keep the original file.
We have written about that distinction in more detail in what a timestamped photo does and does not prove.
Common questions
Does taking a screenshot of a photo keep its location?
No. A screenshot is a brand-new image file. Its metadata describes the moment you took the screenshot, on the device you took it on, and it carries no location unless your screen itself displayed one. The original photo's EXIF is not copied across.
Why does Photos show a map but the photo I sent has no location?
Photos is reading the original file in your library, which still has its coordinates. The copy that was sent went through a process that discarded them. Both statements are true at once — they are different files.
Is there any way to recover GPS from a photo that lost it?
Not from the file. If the original still exists in the camera roll that took it, the coordinates are there. Otherwise the information is gone. Tools claiming to recover location from pixels are inferring a guess from landmarks, not reading data.