Home/What the restored Snapchat Memories ZIP contains
Output
What is inside the restored Snapchat Memories ZIP
Before you drop a ZIP in, it helps to know what comes back. This is the exact layout the tool wrote for a test export, free and Pro side by side.
Same test export, restored free and with Pro
| Free restore | Pro restore | |
|---|---|---|
| Photos written | 15 of 25 | 25 of 25 |
| Videos written | 0 of 2 | 2 of 2 |
| Files in the ZIP | 35 entries (15 JPEGs, 18 folders, report, README) | 54 entries (25 JPEGs, 2 MP4, 25 folders, report, README) |
| Overlays baked onto photos | On the 15 photos | On all photos that had one (7 paired overlays in this export) |
| Source ZIP uploaded | No, restored in the browser | No, restored in the browser |
The folder tree
Everything sits under Snapchat-Memories. Below it is one folder per year and, inside each, one per month that has memories in it. In the test export that came to 25 folders for 27 memories (the root, 3 years and 21 months), because most months held one or two photos.
Google Photos and Apple Photos read the date from the file's EXIF data, not from the folder, so the folders are for you. Keep them when you import; they make the library easy to check month by month.
The two extra files
restore-report.csv has a header line and one row per memory. The gps cell holds latitude and longitude in one quoted cell, and is empty when Snapchat's JSON had no real location (0, 0 is never written). The overlay column says whether an overlay was baked in.
README.txt lists what was written to JPEGs and MP4s, three import routes (Google Photos, Apple Photos, camera roll), and the final count: for the test export it says "Restored 27 files. 0 skipped." for Pro and "Restored 15 files." for the free run.
How this was measured
On 2026-10-04 we dropped a 27-memory test export into the live restore in desktop Chrome, once without Pro and once with a Pro unlock, downloaded each result and listed it. The test export follows the My Data layout (-main and -overlay files, memories_history.json); it is not a real person's Memories. Numbers will differ for a real library, but the layout will not.
Writing the report also turned up a fault that is now fixed: the gps cell was not quoted, so rows with a location had one column too many. A spreadsheet then shifted the overlay, split_parts and date_source columns by one. The cell is quoted now, and the repo's verify script fails if any row has a different column count from the header.
Next
Why dates come out wrong in a gallery is on wrong dates after export. How the whole flow works is on how it works. To see what your own ZIP would produce before restoring anything, use the free scan on the home page.
Common questions
What are the restored files called?
The capture time in UTC: 2022-01-01_10-00-00.jpg inside Snapchat-Memories/2022/01/. Two memories in the same second get _2, _3 added before the extension so one never overwrites another. Videos add _video before .mp4.
Is the folder date the date taken?
It is the capture date from memories_history.json, in UTC, so a photo taken late in the evening in a western time zone can land in the next day's name. The date inside the JPEG is written as EXIF DateTimeOriginal.
What is restore-report.csv for?
One row per memory: file, kind, capture_utc, gps, overlay, split_parts and date_source. It tells you which date each file got and where it came from, so you can spot the ones that fell back to the ZIP file date.
Does the ZIP include the original -main and -overlay files?
No. Photos with an overlay are written once, with the overlay baked in. Overlays that could not be matched to a photo are kept in their own folder instead of being dropped.