Does Google Photos Remove Metadata?

A different kind of question

Every other platform in this series is a feed. You upload, it re-encodes for display, and metadata disappears as a side effect of that processing.

Google Photos is storage. Its entire purpose is to keep your originals safe and searchable, which means preserving exactly the data a feed discards. The capture time drives the timeline, the coordinates drive the map view, and the camera model drives the search filters. Stripping any of it would break the product.

So the starting assumption inverts: assume everything is preserved, because preservation is the feature.

What that means when you share

The question that matters is not what Google keeps but what a recipient receives, and that depends entirely on how you shared.

• A shared link or album lets recipients view and usually download. What they download is close to your original, metadata included, unless a setting says otherwise.
• Downloading from the app or the web gives the stored file rather than a display-sized re-encode.
• Sharing onward from Google Photos to a messaging app hands the file to that app, whose own behaviour then applies — which may or may not strip it.
• A screenshot of a photo in the app is a new image with none of the original's metadata and considerably less quality.

The setting worth knowing about

Google Photos includes an option to remove location information from items shared by link. It is off by default in most accounts, it applies to link sharing rather than to every path a file can take, and its exact name and placement move between app versions.

It is worth turning on, with two caveats. It covers the sharing route it covers and no other, and it does nothing about the copy sitting in your library or about what the picture itself shows.

Treat it as a useful default rather than a complete answer, and check what a recipient actually receives rather than assuming the toggle covers your case.

Takeout is the part people miss

Exporting your library through Google Takeout produces something unusual: alongside each image, the archive typically includes a JSON file describing it — capture time, geographic coordinates, device details, album membership and more.

This matters because the metadata is no longer inside the image where a metadata cleaner would find it. Clean every photo in the export and the coordinates are still sitting in the sidecar files next to them.

If you are moving a library somewhere else, or handing an export to anyone, the JSON files need attention in their own right. No image tool — including this one — will touch them, because they are not part of the image.

What Google holds regardless

Your originals live in Google's storage with everything they contained, which is the deal you accepted when you chose a backup service. Location history, face grouping and search indexing are built on exactly that data.

This is not a criticism — it is the product working as designed, and it is why the map view and the search work at all. It does mean that cleaning a copy before sharing addresses what recipients see, not what the service holds.

The practical routine

Photos leaving your library for someone outside it are the ones worth cleaning, and the cleaning has to happen after the download rather than before the upload — because the library is where the originals are supposed to live.

• Download the photo you intend to share, clean it, and share the cleaned copy rather than a library link.
• Turn on the option to remove location from link shares as a baseline for the times you forget.
• Treat a Takeout archive as containing metadata twice: inside the images and in the JSON beside them.
• Remember that the shared album stays live — anyone with the link keeps access until you revoke it.