Guide

What “last modified” means on your Snapchat export files

Guides · Snapchat export

You went looking for when a snap was taken and the only date anywhere is “last modified” — and it’s the day you downloaded the export, not the day you were there. That date belongs to your computer, not to Snapchat. Here’s what it actually records, why it’s the only date you can see, and where the real one is hiding.

Last modified is a filesystem date, not a Snapchat date

Every file on your computer carries a small set of dates that the operating system maintains: when the file was created on this machine, and when its contents were last written. That second one is what Windows and macOS label “last modified”. It updates whenever the bytes on disk change — including when they are first written, which is what happens the moment you unzip your export.

So a last-modified date of, say, this Tuesday means one thing only: this Tuesday is when the file landed on your disk. It is not a claim about the photograph. That is also why the dates look suspiciously uniform — unzip an export of four thousand memories and all four thousand files were written within the same couple of minutes, so they all share essentially the same last-modified date regardless of whether the snap is from last month or from 2017.

Why it’s the only date your photo app will show

A photo app doesn’t want the filesystem date. Given the choice it reads the capture date recorded inside the file itself — EXIF DateTimeOriginal for a photo, the QuickTime creation atoms for a video. That field is the authoritative “when this was taken” and it travels with the file wherever it goes.

Snapchat’s export leaves that field empty. The media files come out as, in effect, blank slates: correct image and video data, no capture date, no GPS. With nothing to read, Apple Photos and Google Photos fall back to the only date available — last modified — and your entire Snapchat history stacks onto the day you downloaded it. The date you’re seeing isn’t wrong so much as it’s a substitute for a date that was never written.

Where the real capture date actually is

It’s in the export, in a separate file. Alongside the media folders, Snapchat ships a memories_history.json file that lists every memory with its true capture timestamp and, if location was on when you took it, its GPS coordinates. Nothing was lost in the export — the metadata was simply parked in a JSON file instead of being written into the photos and videos. There’s a full breakdown in what memories_history.json is.

Why re-dating the file by hand doesn’t stick

The obvious move is to change the file’s modified date and be done with it. It doesn’t hold. A filesystem date is a property of the copy sitting on that disk, not of the file’s contents, so it is routinely rewritten the moment the file is copied to another drive, synced to a cloud service, or imported into a photo library. And even where it survives, the library still sees an item with no capture date and treats it accordingly — it may sort by the fallback but it won’t put the memory on your timeline where it belongs, and no amount of filesystem tinkering restores a location.

The fix that lasts is to write the genuine date into the file, so it stops depending on which disk the file happens to be on.

Putting the real date back

This is what MemoriesExport does: it reads memories_history.json from the export you already downloaded, and writes each memory’s true capture date and GPS into the file itself — EXIF for photos, and for videos the QuickTime creation atoms plus the Keys:GPSCoordinates atom that Apple Photos reads to place a clip on the map. Overlays are merged back on, and you get a ready-to-import zip. After that, “last modified” can say whatever it likes — your photo app has a real capture date to use instead.

If you’ve already imported everything and it’s all landed on today, that’s recoverable too: recovering the original dates and locations walks through it. For the mechanics of the date field itself, see fixing Snapchat timestamps.

Fix my Snapchat export →

Frequently asked questions

What does 'last modified' mean on my Snapchat export files?

It's your computer's record of when the file itself was last written — which, for an export, is the moment you downloaded and unzipped it. It is not a Snapchat field and it has nothing to do with when the snap was taken. Every file in a fresh export tends to carry roughly the same last-modified date for exactly that reason.

Why is 'last modified' the only date my photo app will show?

Because it's the only date present. Photo apps prefer the capture date stored inside the file (EXIF DateTimeOriginal for photos, the QuickTime creation atoms for videos), and Snapchat's export leaves those empty. With no capture date to read, the app falls back to the filesystem's last-modified date.

Does a wrong last-modified date mean my memory's real date is lost?

No. The real capture date was never in the media file to begin with — it lives in memories_history.json inside the same export. Nothing has been lost; the date simply needs writing into each photo and video.

Can I fix it by changing the file's modified date?

It won't hold up. Changing the filesystem date is not the same as writing a capture date into the file: copying, uploading or importing the file usually resets it, and Apple Photos and Google Photos will still treat the item as undated. The durable fix is to write the real date into the file's own metadata.

Do videos behave differently from photos?

Yes, and it catches people out. A video needs its date in the QuickTime creation atoms rather than EXIF, and its location in a separate Keys:GPSCoordinates atom — the one Apple Photos reads to place a video on the map. Tools that only write EXIF appear to work on photos and quietly do nothing for videos.