Fix the dates, time and location of your Snapchat Memories export

1. Request your data from Snapchat under My Data, with Memories included. If the request page offers JSON files, switch that on too. Without it, the export has an HTML version of the memories list, and the fixer reads that as well. The full checklist is here: how to export Snapchat Memories with dates and locations.
2. When the export is ready, download every ZIP part. The names look like mydata~1739000000000.zip, mydata~1739000000000-2.zip, -3.zip and so on. Keep them zipped.
3. Add all the parts here at once. The fixer reads them on your device, finds the memories list in the first part and shows you the first five photos before it writes anything.
4. Pick where the fixed parts should go and start. Each part is at most 300 MB, and you can choose 100 or 200 MB instead.
5. Save the parts and the CSV report. Unzip each part and add the photos to Google Photos, Apple Photos or your phone's gallery, where they sort by the day they were taken.

In the current export format, the photos sit inside the ZIP files and the memories list does not name them. The fixer therefore matches each file by the time stored in its ZIP entry, which Snapchat sets to the capture time in UTC with 2-second precision, and by media type. Each file ends up with one of these statuses:

• Exact: one entry in the list fits, so the date, the time and any location come from it.
• Same 2-second window: 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.
• ZIP time only: no entry fits. The time comes from the ZIP entry and no location is written.
• Date from name: rare. Only the date in the file name could be used.
• Entry without a file: the list has a memory, but the ZIPs hold no file for it. My Eyes Only items are one example.

Nothing is skipped quietly. The CSV report lists every file and every entry, so you can see what was fixed and what your export was missing.

The page carries a Content-Security-Policy in its own HTML that tells your browser to block every outgoing connection from the page except one: the visit counter's report to cloudflareinsights.com. The line that does it is connect-src https://cloudflareinsights.com, and form-action 'none' stops forms from being sent anywhere. Your photos are read and written inside the browser tab, by a processing script that contains no network code.

The panel also shows a live counter, “Sent from this page”, which counts the network requests the page and that script make after you add files, not counting the visit counter's. It stays at 0. After your first visit, a service worker keeps the page cached, so it works offline: switch on airplane mode and run the whole fix. There is no account, no cookies and no ads. We count page visits with Cloudflare Web Analytics: no cookies, no personal data, and never your files.

How to check this yourself with your browser's developer tools

On a computer, use a current Chrome, Edge, Firefox or Safari. Chrome and Edge can write the fixed parts straight into a folder you choose. Firefox and Safari keep them in the browser's private storage instead: you save each part with its own button and can then delete the temporary copies.

On Android, use a current Chrome and save each part with its own button. On iPhone and iPad, use Safari and pick the ZIPs from Files or Downloads. If a ZIP in iCloud Drive will not open, move it to On My iPhone first. For very large exports a computer is faster.

Whatever you use, plan for free space of about the size of your export, and keep the tab open while the fixer works.