Short answer: on Android, a photo can have GPS in your gallery and still show "no location" when you open it in a browser tool. Android's developer documentation says that for apps using scoped storage, "the system hides location information by default", and an app needs the ACCESS_MEDIA_LOCATION permission and a request for the original file to read it (Android Developers). A browser is an app too. Which browsers and phones pass location through when you pick a photo is not documented, so the practical fix is to try a different way of choosing the file, then confirm with the EXIF viewer.
This guide explains what is documented, what is not, a fix order that works through the likely causes, and how to tell "this photo never had GPS" from "my phone hid it".
What Android documents about photo location
Here is what Google's Android developer pages say, as read in October 2026:
- Location is hidden by default. On the page about media files in shared storage: "If your app uses scoped storage, the system hides location information by default." To read it, the app requests ACCESS_MEDIA_LOCATION and calls
setRequireOriginal()to get "the exact bytes of the photograph" (Android Developers). - It started with Android 10. The same page says: "If your app targets Android 10 (API level 29) or higher and needs to retrieve unredacted EXIF metadata from photos, you need to declare the ACCESS_MEDIA_LOCATION permission in your app's manifest, then request this permission at runtime."
- You may be asked. Google adds that because the permission is requested at runtime, "there is no guarantee that your app has access to unredacted EXIF metadata from photos", and the app needs your explicit consent.
- The photo picker. Android's system photo picker runs on Android 11 and up with Google System Updates, and a backported version can run on older devices. Where it is not available, apps fall back to the document picker (Android Developers). The photo picker page does not say how location is handled for the photos you pick.
What is not documented
Be careful with anyone who says "Android always strips location in the browser". The pages above do not say that. Here is what we could not find in Android's documentation:
- Whether a given browser (Chrome, Samsung Internet, Firefox and others) asks for ACCESS_MEDIA_LOCATION or for the original file when a web page asks you to pick a photo.
- How the system photo picker treats location in the files it hands over.
- Whether phone makers change this behaviour in their own gallery or file apps.
So two Android phones, or two browsers on the same phone, can behave differently. We do not claim every Android phone behaves the same.
What you see in the EXIF viewer
When you open a photo in the EXIF viewer, one of three things happens:
- A map with coordinates. The copy the browser received has GPS.
- "No location in this photo." The copy the browser received has no GPS fields.
- "Invalid GPS coordinates." The copy has GPS fields, but the values cannot be turned into a real place on the map. We have not confirmed which phones or browsers cause this, so treat it as "the location did not come through properly", not as proof of anything.
The key words are "the copy the browser received". The viewer reads the file it is given. If your phone hid the location on the way, the original in your gallery may still have it.
Fixes, in order
Try these one at a time and re-check after each.
1. Confirm the original really has a location
Open the photo in your gallery app and look for Details or Info, usually by swiping up or through the three-dot menu. Menu names vary by brand.
One catch: a map in the gallery does not prove the file has GPS. Google says Google Photos "estimates your location from information such as landmarks and locations in your other photos", and that "if you share a photo with a location estimated by Google Photos, the location won't be shared" (Google Photos Help). If the location is an estimate, the file never had it. More on this in does Google Photos store your location.
See what your photo is actually revealing
Drop a photo to view its GPS location and full EXIF. Everything runs in your browser — the file never leaves your device.
Read in your browser. Your photo is not uploaded or stored.
2. Pick the file from Files instead of the photo grid
When the browser asks you to choose a photo, you may see a photo grid. Many phones also offer a Browse option, a Files app or a Documents view. Try choosing the same photo from there, for example from the DCIM or Camera folder.
This is not documented to work, and it may change nothing on your phone. It is still worth trying, because it can open the photo through a different route than the photo grid.
3. Check the camera's location setting
If new photos have no location at all, the camera may not be saving it. On Pixel phones, Google's help says to open the Camera app, tap Settings, then More settings, and look for Save location (Pixel Camera Help). Other brands use similar names, such as Location tags. Your phone's location also needs to be on when you take the photo. Take a new test photo outside and check it.
4. Share from the gallery instead of picking in the browser
Some gallery apps offer a location option on their share screen. If yours does, make sure it is not set to remove location, then share the photo to where you need it. If you installed GeoTag.world as an app on Android, you can share a photo straight to it from the gallery, and it opens in the GPS remover. If the app asks you to choose the photo again, do that. Whether location survives a share depends on the gallery app and is not documented in a general way.
5. Use a computer
Copy the original file to a computer over USB, or download it from your own cloud backup with an option that keeps the original. Then open it in the EXIF viewer in a desktop browser. This skips the phone's picker entirely and is the most direct check of what the file contains.
Never had GPS, or the phone hid it?
| What you see | Most likely meaning |
|---|---|
| Gallery shows a camera location, browser shows none, computer copy has GPS | The phone or browser hid it when you picked the file |
| Gallery shows a location, but it is marked as estimated or you cannot find it on a computer copy | The file never had GPS |
| Screenshot, or a photo saved from a chat or social app | Usually never had GPS. See do screenshots have location data |
| Camera location setting was off | Never had GPS |
| "Invalid GPS coordinates" in the viewer | GPS fields exist in the copy, but the values are not usable |
The computer check is the tie-breaker. If the copy on a computer has GPS and the phone browser copy does not, the location was hidden on the way, not missing from the photo.
A privacy warning that goes with this
If the viewer says "No location in this photo" on your phone, that describes the copy the browser read. It does not prove the original is clean. Other apps you share with may get the original file, location and all, depending on how they read it. See which apps strip EXIF data.
If you want a photo to travel without location, remove it from a copy and share that copy. Use Remove GPS from Photo, then check the cleaned copy in the viewer. The photo is read and cleaned in your browser and is not uploaded.
Limits
- This guide is based on Android's public developer pages and Google's help pages. It does not cover every phone maker's changes.
- Browsers update often. A fix that works today may stop working, or stop being needed.
- No tool can recover a location that was never saved, and we do not guess locations from the picture.
For more on how Android stores GPS in photos, read the Android photo GPS metadata guide, or our guide on how to check if a photo has location data. When you are ready, open the EXIF viewer and check the file again.