You take a photo on your Android phone. Your gallery app shows exactly where it was taken, pinned on a map. You then open a website that reads photo metadata, upload the very same picture, and the location is gone. The date might survive. The camera model might survive. The coordinates do not.
This is not a fault in the website, and it is not something you configured wrongly. Android removes the GPS coordinates from the copy of the photo it hands to your browser. The file on your phone still has them. The copy the website receives does not.
Android’s photo picker strips location data from images shared with apps and websites. Chrome uses that picker, so uploads through Chrome arrive without coordinates. Your phone’s built-in browser often uses an older path that keeps them, which is why the same photo can work in one browser and not another.
The symptom is oddly specific, and that is what makes it confusing. Everything about the photo seems intact except the one field you wanted:
If metadata had simply been stripped — as happens with screenshots or photos sent through a messaging app — you would lose all of it, not just the coordinates. The selective loss is the clue.
A photo stores its metadata in a block called EXIF. Within that block, GPS data lives in its own section with entries for latitude, longitude, altitude, and a timestamp. Each entry is a small record pointing to where its value sits elsewhere in the file.
When Android redacts location, it does not delete the GPS section. It leaves the structure in place and empties the values. Inspecting a redacted photo shows something like this:
Note the details. The file is its full original size. The JPEG header is valid. Sixty-five EXIF tags are present, including every GPS field by name. But the coordinate values read as empty.
That combination — tag names present, values absent, file size unchanged — is the signature of redaction rather than stripping. The photo was modified in transit specifically to remove position data, and nothing else.
Location is treated as more sensitive than other photo metadata, and reasonably so. Coordinates reveal where you live, where you work, where your children go to school, and where you were at a particular moment. A photo shared casually can disclose all of that without the sender realising.
Android therefore requires a specific permission before an app may read location from photos in shared storage. Apps that need it must request it explicitly, and the system redacts coordinates for everything else by default.
Web pages have no way to request that permission. There is no browser prompt for it and no setting a website can toggle. When Chrome passes a photo to a page, it passes what the system gave it, which has already been redacted.
The newer system photo picker — the grid interface that appears when apps request an image — applies the same protection, and does so without a prompt. Nothing on screen indicates that anything was removed.
Your gallery app reads the file directly from storage with the permission needed to see location. It is not receiving a shared copy. That is why the map appears there but not in your browser: the two are looking at different versions of the same photo.
Manufacturer browsers — the OnePlus browser, Samsung Internet, Mi Browser, and similar — often use an older file-selection path that does not apply the same redaction. Opening the same metadata site in one of these and selecting the same photo frequently returns full coordinates.
This is the quickest thing to try, since it needs no cable and no computer. It is not guaranteed, as manufacturers update these apps independently, but it works often enough to be the first option worth attempting.
This always works. Connect your phone by cable, choose file transfer mode when prompted, and copy the photo to your computer. A file copied this way is the original, untouched, with its coordinates intact. Uploading it from a desktop browser gives you the full location.
It is the least convenient option and the only one that never fails.
If your photos back up to a cloud service, downloading the original-quality version to a computer preserves the metadata. The important detail is original quality: services that compress uploads to save space usually discard metadata in the process. A resized copy will have the same problem as a redacted one, for a different reason.
| Attempt | Why it fails |
|---|---|
| Granting location permission to Chrome | That permission controls your device’s live position, not reading location from photo files. They are unrelated. |
| Trying a different metadata website | Every site receives the same redacted copy. The data is removed before any site sees it. |
| Re-sharing the photo to yourself | Messaging apps strip metadata as well, so this usually makes matters worse. |
| Renaming or converting the file | The coordinates are already absent from the copy. Nothing can recover a value that is not there. |
No. Redaction applies to the copy handed to the browser, not to the file on your phone. The original retains its coordinates, which is exactly why your gallery can still map it.
Any route that reaches the original file rather than a shared copy — USB transfer, an original-quality cloud download, or a browser using the older selection path — will show the location.
Before concluding that redaction is your problem, rule out the simpler explanations. Each leaves a different trace:
| Cause | What you see |
|---|---|
| Android redaction | Date and camera details present, location blank |
| Shared through a messaging app | Everything missing; filename often contains the app’s name |
| Screenshot | Only the screenshot time; no camera information at all |
| Location services were off | Date and camera present; gallery cannot map it either |
| No satellite lock | Coordinates recorded as zero; common indoors and on aircraft |
The distinguishing test is straightforward: if your gallery app can show the photo on a map, the data exists and the browser is not receiving it. If your gallery cannot map it either, the coordinates were never recorded.
Possibly. Android’s photo picker has been evolving, and a permission prompt that would let users choose to include location when sharing has been discussed. If that ships broadly, browser uploads could keep their coordinates with explicit consent.
Until then, treat it as expected behaviour rather than a bug. Chrome on Android will not show photo locations, and the workarounds above are the practical routes around it.
Photo Trace reads EXIF data entirely inside your browser — your photo is never uploaded or stored. It also detects the redaction signature described here and tells you when coordinates were removed in transit, rather than simply reporting no location found.