Why your Snapchat Memories show the wrong date

Gallery apps first look inside a photo for the date it was taken. That date lives in a block of metadata called EXIF. The photos in a Snapchat My Data export have no capture date in that block. With nothing to read, the gallery falls back to the file's own time, which is when your device saved the file, and for a fresh download that is the download day. Memories from many years then pile up on one date.

Take one made-up photo. You downloaded your export on 18 October 2026, and the photo is called 2019-03-05_6f1c2a9e-main.jpg. Your gallery files it under 18 October 2026, with no time and no place. The next steps show where its real time is.

The export keeps the real time in two places. Neither one is inside the photo.

• The first is the memories list: json/memories_history.json, or html/memories_history.html if you did not ask for JSON. Each entry has a date in UTC and, when Snapchat saved a place, a location. The entry for our photo reads "Date": "2019-03-05 09:24:50 UTC" and "Location": "Latitude, Longitude: 41.0082, 28.9784", a spot in Istanbul.
• The second is the time stored on the photo's entry inside the ZIP file. Snapchat sets it to the capture time, in UTC, with a precision of 2 seconds. For our photo it is 09:24:50 on 5 March 2019, the same moment as the list entry.

In the current export format, the list does not name the photos. Photo Date Fixer therefore pairs each file with an entry by the time stored in its ZIP entry and by media type, photo or video. If two or more entries fit, the time is still right to within 2 seconds, and a location is written only if those entries share it.

A gallery app reads neither of these places. It looks inside the photo, finds no date and uses the file's own time.

UTC, or Coordinated Universal Time, is one clock for the whole planet. Local time is UTC plus the offset of the place where the photo was taken. Snapchat stores UTC, so the list does not say what the clock on the wall showed. The fixer works it out like this:

1. It reads the location of the entry: 41.0082, 28.9784.
2. It finds the time zone of that place in open time zone boundary data. Here that is Istanbul, which is on +03:00 on that date.
3. It adds the offset: 09:24:50 UTC plus 3 hours is 12:24:50.
4. It writes that local time together with the offset, so an app that reads the offset can turn it back into UTC.

An entry without a location gives the fixer no place to look up. You then pick a time zone, and your device's time zone is the default. Memories taken in another zone come out off by the difference, so choose the zone where you took most of them.

Many places move their clocks twice a year, so one city does not have one offset. Amsterdam shows it well. On 30 March 2025, clocks there moved forward at 01:00 UTC.

The first photo was taken before the change, while Amsterdam was still on +01:00. The second was taken an hour later in UTC, after the clocks had moved forward, so its offset is +02:00. No clock in Amsterdam showed a time between 02:00 and 03:00 that morning. If the fixer had added +01:00 to both entries, the second photo would be stamped 02:30, a time that never happened there.

In autumn it runs the other way: the clocks go back, one local hour happens twice, and the offset written next to the time says which of the two you mean. That is why the fixer looks up the offset for each photo's own date and place and stores it with the time, instead of using one offset for the whole export.

Our photo comes back as 2019/2019-03-05_12-24-50_6f1c2a9e.jpg. The fixer writes the local time into the photo's EXIF date fields, the offset into the offset fields and the position into the GPS fields, with a GPS date and time stamp in UTC. A gallery then sorts the photo under 5 March 2019. The pixels are not re-encoded, so only the metadata block changes. MP4 videos get their creation time and location set the same way, without re-encoding the video. The CSV report lists every file and every list entry, so you can see what matched and what your export was missing.

Add the ZIP files of your export to the fixer. It shows the first five photos before it writes anything, so you can compare them with what you remember. If you have not requested your export yet, or some ZIP parts are missing, see the guide How to export Snapchat Memories with dates and locations.

If you are exporting because of Snap's storage changes, its help page says that starting in January 2027, Memories that are more than one year old and are not part of your oldest 5GB of Memories will be archived and remain stored on Snapchat. It also says no Memories will be archived before January 2027, and it lists downloading your Memories to access them outside the app as one of your options.

Source: Snapchat Support: How do I manage my Memories storage?, checked 20 October 2026.