Put Snapchat Memories back on the map

ExportSnaps/FixMyExport built a whole landing page on “no GPS.” The data was never missing — it was parked in JSON. Photo apps cannot read that JSON. We embed it.

1 free restore · then $19.99 once

Drop a Memories ZIP

Why the map is empty

Snapchat records latitude/longitude when location services were on. The export writes that as text on the JSON row. The JPEG/MP4 leaves with no GPS IFD. Map view looks at the file, not the sidecar.

GPS in the JSON is not the January 2027 archive. What that archive actually does.

What we write

If two JSON rows share a second and disagree on location, we omit GPS rather than guess. Filename-only dates (no JSON) will not get coordinates.

GPSLatitude / GPSLatitudeRef
GPSLongitude / GPSLongitudeRef
Only when the JSON row matched that memory. We do not invent coordinates.

Before you share a restored photo

Embedded GPS is what makes the map view work, which is also why it travels with the file if you post or send the original. For a copy you plan to share, strip the EXIF location from the photo first; it runs in the browser, so the file stays on your device. Keep the GPS-tagged copy in your own library.

If you only need to check where a photo was taken (without rewriting anything), check where a photo was taken reads the GPS already in the file.