
Snapchat’s export keeps a date on your photos and videos, but it leaves the GPS location out of the files and stores it, along with each Memory’s original capture date, in a separate file called memories_history.json. Gallery apps never read that file. That’s why exported Memories often show no location and can land on the wrong day in Google Photos or Apple Photos.
| Information | In the exported file | In memories_history.json |
|---|---|---|
| Capture date | A date is present, but not always in the fields every app reads | Yes, in UTC |
| GPS location | No | Yes, when location was on |
| Text, stickers, captions | Separate overlay file | Linked to the Memory |
| Long videos | Sometimes split into clips | One entry per clip |
Photo apps read metadata embedded inside the file itself: EXIF fields such as DateTimeOriginal for photos and the equivalent fields for videos. Information sitting in a JSON file next to the photo is invisible to them.
Partly. Snapchat doesn’t write location into exported files, and the date it leaves is not always stored where Google Photos, Apple Photos or Windows Photos look first. The full record, date and location, exists only in memories_history.json, which you get when you turn on “Export JSON Files” in My Data.
With “Export JSON Files” turned on, Snapchat puts a json folder in the main ZIP of your export, and memories_history.json is inside it. If your export has several ZIPs, only the main one (usually the one without a number) has it; the numbered parts contain just more media. No JSON means the option was off, so request your data again with it on.
Each Memory has an entry with its capture date and time in UTC, whether it’s a photo or video, and its GPS coordinates when location was on:
"Date": "2021-08-10 14:23:19 UTC",
"Media Type": "Image",
"Location": "Latitude, Longitude: 51.5072, -0.1276"
The entries also have Download Link fields, but in current exports these are empty: your photos and videos come inside the ZIPs instead. See what JSON files on Snapchat are for the full breakdown.
To fix one Memory manually, you find its entry in the JSON, copy the date and coordinates, and write them into the file with an EXIF editor. That’s minutes per file. For a library of 5,000 Memories, it isn’t realistic.
FixMyExport reads memories_history.json and writes each Memory’s original capture date and GPS location into the file itself. It runs on Mac, Windows, iPhone, iPad and Android, and everything is processed on your own device.
Full metadata writing is supported for JPEG photos and MP4 or MOV videos. Memories that never had a location get none; nothing is guessed. The free version processes up to 200 files per export; Pro is a one-time purchase that removes the limit (pricing).
For details on which fields are written, see export Snapchat with EXIF and why exported Snapchat photos have no location.
Snapchat leaves GPS location out of exported files and does not always store the date in the fields every app reads. The full date and location record is kept separately in memories_history.json.
Choose your Snapchat ZIP files in FixMyExport. It reads memories_history.json and writes each Memory’s capture date and GPS location into the file, on Mac, Windows, iPhone, iPad or Android.
Snapchat keeps a date on the file but stores location only in memories_history.json. Gallery apps cannot read that file, so map views stay empty until the coordinates are written into each photo.
Technically yes, by copying each date and location from the JSON into the file with an EXIF editor. For more than a handful of Memories it takes far too long.
No. FixMyExport writes metadata tags; it does not re-compress the image or video content.
Snapchat records every capture time in UTC in memories_history.json. If a tool copies that time without converting it, your Memories shift by your time zone offset. FixMyExport converts each time using the timezone you choose before writing it into the file.
In the json folder of the main ZIP, the one usually named without a number. The numbered ZIP parts don’t contain it.