Most of the time you want to find where a photo was taken, the answer is already sitting inside the file, written down to a few meters. And most of the time you go looking, it’s gone, because whoever posted it ran it through something that wiped it first. Both of those are true at once, and knowing which situation you’re in saves you a lot of squinting at background buildings.
So this is really two questions wearing one coat. Can the file tell you where it was taken, and if it can’t, is there another way to find out anyway.
The location lives in the EXIF
When a phone takes a photo, it usually stamps a block of hidden data into the file called EXIF. Camera model, the exact time, shutter and ISO, and if location services were on, the GPS coordinates. That last part is the good stuff. A modern phone’s GPS is accurate to roughly 3 to 5 meters out in the open, so a photo with its coordinates intact doesn’t just point at a city, it points at a spot you can drop a pin on.
That little map that shows up in your phone’s photo app, the “where this was taken” line, is just reading that GPS tag straight out of the file. It never looks at the picture itself. Same data, every viewer, whether it’s your phone or a stranger’s.
How to actually read it
You don’t need anything fancy for a single photo.
On an iPhone, open the photo in the Photos app and swipe up. If a map appears, that’s the GPS tag, and tapping it opens the exact point. On a Mac, open the file in Preview and press Cmd+I, then look at the GPS tab for raw latitude and longitude you can paste into a maps search.
On Windows, right-click the file, hit Properties, and open the Details tab. Scroll down to the GPS section. If there are numbers there, that’s your location. Copy the latitude and longitude, drop them into any map, done.
For a photo on the web, or a batch of them, an online EXIF viewer reads the file in the browser and lays the fields out for you, coordinates included, without installing anything. If you’re doing this at real scale, ExifTool on the command line will pull GPS out of a whole folder and dump it to a spreadsheet, but that’s overkill for anything but bulk work.
Some photos also store the compass direction the camera was pointing when the shutter fired. So on a good file you can know not just where the photographer stood, but which way they were facing. Handy, occasionally a little unsettling.
Why it’s so often just not there
You save a photo off Instagram or a group chat, check the metadata, and there’s nothing. No coordinates, sometimes no EXIF at all. That’s because the platform stripped it on the way to you.
Most public social feeds pull GPS and most other metadata out of the copy other people can download. Instagram, Facebook, X, TikTok, Reddit, they all do some version of this on public posts. It’s a privacy default, and a sensible one, because otherwise every vacation photo would broadcast your hotel. The catch is that the platform still read your full-metadata original when you uploaded it. So the stripping guards your photo against everyone downstream while the platform itself already has your coordinates on file.
Where the coordinates usually survive is the more direct routes. A photo emailed as an attachment, sent through a chat app’s file or document mode, or dropped into certain messaging tools often arrives with its EXIF untouched. The rule of thumb, and it’s a rough one because these behaviors change without announcement, is that the more a service treats your photo like a file instead of a post, the more likely the location rode along with it. I wouldn’t bet a privacy decision on any single app behaving a certain way this month, but that’s the pattern.
Screenshotting a photo strips the location too, which catches people out. A screenshot is a brand new image, and it carries the metadata of the device that took the shot, not the original’s GPS. So if someone sends you a screenshot of a picture, the coordinates are already gone, no matter how good the original was.
What to do when the location isn’t in the file
If the GPS was stripped, no metadata tool can invent it back. The internet is full of services that promise to tell you where any photo was taken, and they work in two completely different ways.
Some read the data that’s already in the file. If the coordinates are there, they show them, accurately, because reading a tag is a solved problem. If the coordinates are gone, a decent tool says so and stops.
The rest guess from the picture itself. Give one a landscape and it tries to match the mountains and the architecture and whatever road signs it can make out, then spits out a best-guess location. Those can be impressive. They can also be confidently, wildly wrong, and none of it involves reading anything out of your file. It’s visual detective work, the kind a sharp-eyed human does squinting at the background, just faster and less accountable. Fine as a lead. Not something to hang a conclusion on.
The tool imgi is building does the reading kind. It reads the GPS that’s actually in the file and shows it on a map, and when a photo’s location has been stripped, it says so and explains that the platform likely removed it, rather than dressing up a guess as an answer. That page, a “where was this photo taken” reader, isn’t live yet, but that’s the design: upfront about what a file can and can’t tell you.
For now, the workflow that actually works is the low-tech one. Check the EXIF first, because when the coordinates are there they’re exact and there’s nothing to solve. If they’re gone, accept that you’re now doing inference from the image, treat any AI location guess as a lead and not a fact, and go corroborate it with the boring stuff, visible landmarks, street signs, a reverse image search, the caption someone forgot to delete.
Either the coordinates are in the file or they aren’t. Most of the trouble people run into comes from hoping some clever tool can pull an answer out of a file that stopped holding one the moment it got posted.