Questions people actually ask

No. There's nothing on our end that could. The website is just the delivery: once the page loads, your own device does all the work, unzipping, drawing captions, rebuilding videos, on the same chip that plays your Netflix. We don't own a server that could do it. We own a website and a strong opinion. And we never ask for your Snapchat login: you download your export from Snapchat yourself. Don't take our word for any of it. Turn off your Wi-Fi after the page loads and it still works. Or right-click the page, choose Inspect, open the Network tab, and watch nothing with your photos in it leave.

In Snapchat: profile → gear icon → Privacy Controls → My Data. Switch on “Export your Memories” and “Export JSON Files”, choose All Time, submit. The email usually lands within a day or two, and Snapchat says up to seven. The how it works page walks through every tap.

For the tool, and for how it's built. Doing the work in your browser instead of on a server was the harder way to build this, and it's the only version where “your photos never leave your machine” is a fact rather than a promise. Five dollars, once, however many files you have, and the first 500 are free, so you can check the dates landed before you pay.

No, and you shouldn't on any site that isn't Snapchat. You ask Snapchat for your data in the Snapchat app, download the ZIP they email you, and drop that here. We never see your username or password, because there is nowhere on this site to type them.

Any of them works. On a laptop or desktop, Chrome, Edge and most browsers built on Chrome (Arc, Opera, Vivaldi, Dia) do the best job: your photos go straight into a folder, it needs less free space, and a run that stops carries on where it left off. Brave does too after one setting: paste brave://flags/#file-system-access-api into the address bar, set File System Access API to Enabled, and restart Brave. Safari and Firefox give you one big ZIP instead, which needs more free space for a moment and starts over if it stops. Same dates, locations and captions either way.

Your export's size once more, temporarily. Your ZIPs and your fixed photos have to exist at the same time for a bit, like moving house: for one weekend you own two couches. When it's done, delete the ZIPs. Short on room? Pick a folder on an external drive, or let it tell you which finished ZIP to delete as it goes. In Safari or Firefox it needs about three times the export's size for a moment, while the finished ZIP is copied into Downloads, and then drops back down.

In Chrome, Edge and most browsers built on Chrome, yes. Every photo is saved the moment it's done, so drop the same ZIPs in, pick the same folder, and it skips what's finished. In Safari and Firefox it starts over, because the result is one ZIP and a ZIP only works once it's complete.

Nothing, it's fine. Safari on a Mac unzips downloads by itself unless you tell it not to, so the export turns into folders: one called mydata~ and a long number, then memories, memories 2 and so on. Drag them all onto the drop box together, or press Choose folder. Same dates, locations and captions as the ZIPs.

On a laptop or desktop in Chrome or Edge, size is a disk space question, not a browser one. Snapchat splits a big export into ZIPs of about 2GB, so 100GB is around 50 of them. Drop them all in at once. It works through them one at a time and only ever holds about one photo in memory. You need the export's size free once more, or pick a folder on an external drive, and if it stops, drop the same ZIPs in again and it carries on. You never re-add the first ZIP by hand: after the first run, the dates are saved in your folder. It has been run on a 100GB test export built to match Snapchat's format (50 ZIPs, 87,500 memories, 10,937 videos): 1 hour 40 minutes in Chrome on a Windows PC, with every date, caption and location in place. A 60GB one took about an hour on a Mac. Real exports run through it so far go up to about 12GB. The free 500 files are the quickest way to see how it does on your own export and your own machine. For anything this size, Chrome or Edge is the better pick: Safari and Firefox do the same fixes but build one ZIP at the end, which needs about three times the space and starts over if it stops.

A few minutes for most exports. A big library takes longer: a 100GB test export took an hour and 40 minutes. Go doomscroll on your phone. Not here: this tab needs to stay in front, because a tab in the background can get put to sleep.

Yes. Tested on Windows 11 in Edge and Chrome: captions drawn onto photos and videos, the real dates under Date taken, and a stopped run carrying on where it left off. Edge is already installed, so there's nothing to download. There's a Windows guide with the steps.

Yes, it's a website, and the free 500 files are a good way to find out how your phone copes. For a whole library, use a laptop or desktop if you have one: it has far more room, it's faster, and it doesn't pause the tab when the screen locks. If a phone keeps stalling, run smaller batches, but always include the first ZIP, because that's the one with your dates in it. There are guides for iPhone and Android.

Their captions get drawn back into the video itself, frame by frame, so text, stickers and city filters are back in the picture the way you posted them. Long videos that Snapchat cut into 10 second pieces are joined back into one: each piece secretly keeps a few seconds of the piece before it, your computer compares those seconds with the end of every other piece, and lines up the ones that match. Nobody watches anything. It's your computer comparing pixels in this tab, and the result never leaves it. If the order isn't certain, it leaves the pieces alone rather than guess. The capture date goes into the video's own header, which is where photo apps look for it.

Chrome gives the site the one folder you pick, and only while this tab is open. It can't see anything else on your computer, and we can't see the folder at all: your own browser writes into it. Make a new, empty folder for it so there's nothing else in there anyway. Chrome will say the site wants to edit files; that's how it puts your fixed photos in.

Up to 4 browsers. Chrome and Safari on the same laptop count as 2, and a browser whose data you cleared counts as a new one. Safari clears a site's saved data by itself if you haven't visited for about a week, so there you may need the emailed link again. On a new one, choose “Already paid, on another device?” and we email a link to the address you paid with. It lets that browser in and signs out the one you used longest ago, so you can't lock yourself out.

Yes. Snapchat records only UTC. Each time is converted to the local time of the place it was taken, worked out from its own location, summer time included. A memory with no location takes the time zone of the nearest one taken that day, or failing that, your computer's. The CSV names the time zone of every file.

Usually because Snapchat never recorded one: location off, or airplane mode. Almost everything else gets its own location back: Snapchat's list of locations doesn't name the files, but each photo is matched to its own entry exactly. The rare exception is a handful of snaps that can't be told apart even so: those get their shared place if there is one, and nothing if not, because a pin in the wrong town looks exactly like a pin in the right one. The CSV marks each location exact, approximate or blank.

If the tool can't handle your export and we can't fix it, yes. Get in touch within 14 days with your Stripe receipt and what went wrong, and we'll either get it working or refund the $5. It's also why the first 500 files are free: you can watch it work on your own export before paying anything.