DEV Community

François
François

Posted on

Why your Snapchat export comes back broken, and how to repair it

Ask Snapchat for your Memories and you get an export you cannot use as it is.

The files arrive loose, spread over several ZIP files. The date is not written inside the photos. The files keep their date when they come out of the ZIP, but once you copy them to your phone or send them to Google Photos or iCloud, they take today's date. Years of Memories pile up on one day, mixed with yesterday's screenshots.

Videos are cut into 10-second pieces. The text and stickers you put on a Snapchat photo sit in a separate file, and the location is gone.

What a repair has to do

  1. Put every file in a folder per year, then per month, without duplicates.
  2. Bring each Memory back to its real day in your gallery or cloud.
  3. Glue the 10-second pieces back into one video, only when the order is certain.
  4. Put the caption and the stickers back on the photo.
  5. Put the location back when Snapchat knows it.

Why it runs in the browser

Memories are private. Uploading years of them to a server to repair an export is a bad trade, so I built GetMemoriesOut to run in the browser, on your computer. Nothing is sent anywhere. You need a computer for the repair.

The first 500 Memories are free. After that it costs 9.90 EUR once, no subscription, with a 14-day guarantee.

Try it: https://getmemoriesout.com/en

Top comments (1)

Collapse
 
launchgatecheck profile image
Launch Gate •

The underlying defect is worth naming: the export keeps provenance in container metadata (ZIP entry dates, chunk filenames) instead of in the records. Anything stored outside the record dies at the first copy, which is why years of Memories collapse into today's date on import. That also fixes the repair order: convert container metadata into record metadata - EXIF DateTimeOriginal, embedded creation time - before any other step, because every later move is lossy. "Glue only when the order is certain" is the honest line in the list, and worth holding as a rule: chunk order inferred from filenames is a guess, and a guessed merge produces a video that plays fine while being wrong - frames from one year spliced into another. A repair that can't prove the order should ship the pieces separate and name the uncertainty, rather than deliver a confident wrong answer.