What the Photo Location Finder does
This tool reads the GPS position a photo already carries in its Exif metadata and shows it as coordinates, a capture date, a camera and a direction, plotted on a plain vector map drawn in your browser. It finds a location only when the file contains one. If the GPS tags are missing, the honest answer is "no embedded location", and that is what you will get - a place cannot be worked out from the scenery, a face, a landmark or the file name, and this page will not pretend otherwise.
The photo is never uploaded. It is read with the browser's own file reader, parsed in the tab, and the map is a local plot of the coordinates rather than a tile from a map server - because asking a tile server for a map of that spot would tell the tile server exactly where the photograph was taken.
How to use it
- Drop a photo onto the box, or choose a file. JPEG, HEIC, TIFF, PNG and most RAW files carry Exif; screenshots and images saved from social networks usually do not.
- Read the first panel. It says whether the file has an embedded position and how much the metadata can be trusted, with the reasons behind that judgement spelt out.
- Check the coordinates in whichever form you need: decimal degrees for a spreadsheet, degrees-minutes-seconds for a report, a geohash for a database key, or the plain pair for pasting elsewhere.
- Look at the capture date, the device, the altitude and the direction the camera was pointing. Together they say far more about a photo than the coordinates alone.
- Export as GPX, KML, CSV or JSON if you need the position elsewhere - and read the warning first, because every one of those files carries the coordinates with it.
Reading the results
A position in the file means the camera recorded a fix at the moment of capture. It does not prove the picture shows that place: a phone can write the last known fix onto a photo taken indoors minutes later, and an editor can copy a GPS block from one file to another.
The confidence indicator is a plain sum of what the file contains - latitude and longitude, a GPS timestamp, a dilution-of-precision value, an altitude, a capture date - not a percentage pulled out of the air. Each reason is listed next to it so you can judge them yourself.
Dilution of precision, when a camera records it, describes the satellite geometry at the time of the fix. Roughly, 1 to 2 is excellent, up to 5 is good, and above 10 means the position may be tens of metres out.
The direction is where the lens was pointing, not the direction of travel, and it is recorded relative to true or magnetic north depending on the tag. Both are shown when they are present.
Worked example: a phone photo taken near India Gate
A photo from a modern phone carries GPSLatitude 28° 36' 46.1" N and GPSLongitude 77° 13' 45" E, which this page converts to 28.612806, 77.229167. The GPS block also holds an altitude of 216.4 m above sea level, an image direction of 118.6° - east-south-east - and a dilution of precision of 3.2.
The capture date reads 2025-03-14 10:32:07 with an OffsetTimeOriginal of +05:30, and the GPS timestamp reads 2025-03-14 05:02:07 UTC. Subtract one from the other and you get exactly five hours thirty minutes, so the camera clock and the offset tag agree: the local time is genuine, not a guess.
The confidence indicator reads high, with four reasons: coordinates present, a GPS timestamp present, a good dilution of precision, and an altitude. It also notes that the file says it was processed by an HDR pipeline, which is a reminder that metadata can be rewritten by software after capture.
Why there is no basemap under the marker
Every slippy map on the web works by asking a tile server for small square images around the point you are looking at. The request carries the coordinates in the URL. On a page whose entire purpose is to handle a photograph that may show someone's home, that request would undo the point of doing the work locally - the tile server would learn the location even though the file never left your machine.
So the plot here is drawn from the numbers alone: a box, a graticule, a scale bar and a marker, with a cone showing the direction the camera faced when the file records one. If you want to see the surroundings, the OpenStreetMap link does exactly that, but only when you choose to click it.
How this differs from the EXIF Privacy Remover
The EXIF Privacy Remover strips metadata out of a photo and hands you a clean copy. This page does the opposite: it reads what is there, decodes the GPS IFD into coordinates, and lays out the capture date, device, altitude and direction beside them. The two are meant to be used together - read the file here to see what it is carrying, then strip it there before the photo goes anywhere public.
Limitations: what the result does not prove
- No GPS tags means no location, full stop. Scenery, landmarks, faces and file names are not evidence, and nothing on this page infers a place from them.
- Metadata can be wrong or forged. A GPS block can be edited, copied between files or left over from an earlier fix, and a camera with no satellite lock can write the last position it knew.
- Many files arrive stripped. Most social networks, messaging apps and screenshot tools remove Exif on upload, so a photo that has been through one of them will usually carry nothing.
- The confidence indicator describes the metadata, not the picture. High confidence means the file's own GPS record looks internally consistent - not that the photograph was taken where it says.
Privacy: where your data goes
Everything you paste, type or drop is processed in this browser tab. It is not uploaded, logged, stored or sent to analytics. Session recording and tag-manager scripts are switched off on this page.
Standards and sources
- CIPA DC-008 Exif 2.32 specification - checked 19 Sep 2026
- NGA - World Geodetic System 1984 (WGS 84) - checked 19 Sep 2026
- Topografix - GPX 1.1 schema
- OGC - KML 2.2 standard
Frequently asked questions
Can you find where a photo was taken if it has no GPS data?
No, and neither can anything else that is honest about it. Without GPS tags the file contains no position, and identifying a place from the picture itself is guesswork - a matter for a human who recognises the scene, not for a metadata reader. This page says "no embedded location" and stops there.
Is my photo uploaded anywhere when I use this?
No. The file is read by your browser with the standard file-reading interface and parsed in the page. Nothing is sent to a server, and no map tile is requested either, because a tile request would disclose the coordinates even though the photo itself never moved.
Which image formats carry GPS metadata?
JPEG, HEIC and HEIF, TIFF and most RAW formats (DNG, NEF, CR2, ARW) can all carry an Exif GPS block. PNG and WebP can carry Exif but rarely do. GIF, BMP and SVG cannot in any useful way, and screenshots never have a position because there was no receiver involved.
Why does my photo show a position but no altitude or direction?
Those are separate, optional tags. A phone usually records altitude and often a compass bearing; a dedicated camera with a GPS module may record only latitude and longitude, and some record a bearing only when the compass has been calibrated. Anything missing is shown as "not recorded" rather than filled in with a plausible number.
What does the dilution of precision figure mean?
It is a measure of satellite geometry at the moment of the fix, recorded by some cameras as GPSDOP. Lower is better: 1 to 2 indicates an excellent fix, up to 5 a good one, and figures above 10 mean the satellites were poorly spread and the position could be tens of metres out.
How do I remove the location from my photos?
Use the EXIF Privacy Remover, which strips the metadata in your browser and gives you a clean copy to share. On a phone you can also turn off location tagging in the camera settings, and both iOS and Android can remove location when sharing a photo directly.
Can the coordinates in a photo be faked?
Yes. The GPS block is ordinary metadata and any editor can write it, so coordinates alone prove nothing in a dispute. Consistency helps - a GPS timestamp that matches the capture time and an offset tag that matches both is harder to fake by hand - which is why those fields are shown and compared here.
How accurate is a phone's recorded position?
Typically five to ten metres outdoors with a clear sky, degrading to tens of metres among tall buildings and indoors, where a phone may fall back on Wi-Fi or mobile network positioning or simply reuse its last known fix. Treat a coordinate as a neighbourhood, not a doorstep.
Last reviewed by the A2Z.Tools team against the sources listed above.
