Getting your Memories out of Snapchat
- 1
Request your data in the Snapchat app
Settings → My Data. Tick “Export your Memories, Chat media and shared Stories”, and leave “Export JSON files” on. The JSON is what carries the dates and positions that make the rest of this work.
- 2
Download the zip as soon as the email lands
This matters more on Snapchat than anywhere else. The Memories links inside expire roughly 7 days after the export is generated; once they do, the only fix is to request a fresh export.
- 3
Drop it here
The page reads memories_history.json in your browser and shows you every item with its real capture date and, where Snapchat recorded one, its location.
- 4
Take the generated script, or the rebuilt archive
If your export contains the media itself, you get a clean dated archive straight away. If it contains links, you get a script that fetches them from your own machine and stamps each file with its real date.
What it actually changes
- The expiring-link problem, solved locally: Each Memory is a link that must be POSTed to before it yields a file. The script generated here does that, one item at a time, on your computer, and skips anything already downloaded, so you can re-run it after a failure.
- Real capture dates on every file: Snapchat's JSON records when each Memory was actually taken. That date becomes the filename, the file's modified time and, for photos and videos in the zip, the EXIF and MP4 header timestamps.
- Location, where Snapchat kept it: memories_history.json stores a latitude and longitude per item. Those become proper EXIF GPS tags rather than a line of text nothing can read.
- No login, no cookie, no password: You authenticate with Snapchat, in Snapchat, to request the export. This page never sees a credential, which keeps this site's “no login” promise literally true rather than nearly true.
- Chat media and shared Stories too: Anything the export ships as an actual file is processed the same way, not just Memories.
Frequently asked
Why can't the page just download my Memories for me?
Because Snapchat's link endpoint sends no Access-Control-Allow-Origin header (checked directly, and confirmed on a preflight request). A browser will not let any website read that response. The only way around it is to relay the request through a server, which would mean a copy of your private Memories passing through ours. That is exactly what SnapSaved did in 2014 before it leaked around 90,000 photos, and it is not a trade worth making for convenience.
Is the generated script safe to run?
It is plain text you can read before running, and it is generated in your browser from your own file; nothing is fetched from us to build it. It contacts app.snapchat.com and Snapchat's media CDN, and nothing else. There is no credential in it, because none is needed: the links are already signed.
My links expired. Can anything recover them?
No, and nothing can: the signature in each link has a hard expiry. Request a new export from Settings → My Data; it is unlimited and free.
Can this get Snaps that were never saved to Memories?
No. A Snap that was viewed and not saved is deleted from Snapchat's servers, so it is not in your export and there is nothing anywhere to recover. Any tool claiming otherwise is claiming access to an account, not to a file.
What about someone else's private Snaps?
There is no mechanism here for that and there will not be. This processes an export that belongs to whoever requested it.
Does this work with the HTML version of the export?
Partly. The HTML files are for reading, not for machines. Keep “Export JSON files” ticked when you request the data; that is where the dates and coordinates actually live.
Where this fits
Snapchat is the only platform in this site's list with no content API, no scope to request, and no public URL for private media. The export is the entire legal route in, which is why it is worth making the export usable rather than pretending a token could do the job.