Is it safe to upload your Snapchat export?

A full export is not a folder of photos. It's a dated, located, captioned record of where you were and who you were with, going back as far as your account does. The JSON alone is a movement history with timestamps.

Uploading that means it exists on somebody else's disk. Even with the best intentions on their side, you've now got a copy in a place you can't see, governed by a policy you didn't read, on infrastructure you can't audit, retained for a period you're taking on faith.

• Where does the file go? If the answer is a server, ask which one, in which country, and under whose law.
• How long is it kept? "Deleted after processing" is a promise about a background job you can't observe. Ask what happens if the job fails.
• Who can reach it? Every employee with production access is a person who could open your photos. Small teams are not automatically safer. They usually have fewer controls.
• What happens if they're bought, or breached? Data outlives the company that collected it. A privacy policy is a statement of current intent, not a guarantee about the next owner.
• Can you verify any of it? This is the one that matters. Almost every answer above is unfalsifiable from outside.

Nothing is uploaded here, because there is nowhere to upload it to. No route on this site accepts a file. The unzipping, the caption compositing, the video re-encoding and the date writing all happen in the browser tab, using code that arrived when the page loaded.

You don't have to believe that. Load the page, turn off your Wi-Fi, and run your export anyway. It works. That's not a demo mode. It's the only mode there is.

Want to watch it happen? Right-click the page, choose Inspect, and open the Network tab. That's the list of everything the page sends, the same one web developers use. Run your export with it open: nothing carrying your photos ever appears in it. The browser enforces this too. Every page ships a Content-Security-Policy that lets the tab talk to this site and nothing else, so even an open-source library tampered with upstream couldn't send your files to a third party, and this site has no address that accepts a file. You can read that rule yourself in the same developer tools, under the page's response headers.

Doing the work locally is slower than a server farm would be, your computer's fan will notice a large library, and if something goes wrong mid-run there is no copy on our side to recover from, because there's no copy on our side at all. That trade is deliberate. It's the only version where "your photos are none of our business" is a fact rather than a promise.

Reasonable. The metadata is sitting in memories_history.json inside your own archive, and a determined person with exiftool and an afternoon can put it back by hand. The matching is the fiddly part (Snapchat's export has no field joining a photo to its entry), but nothing about the format is secret.