How to Download Your Own Private Photos and Videos

Updated 2026-09-09

If you have tried to save your own private posts, you have probably hit the same wall: paste the link into any downloader and nothing happens. That is not a bug, and no tool is about to solve it — a private post is not reachable by anyone who is not signed in as you. But there is a route that does work, and it is the one the platforms are legally obliged to keep open: ask them for your data, and they hand over your photos and videos. Here is how to do that on Instagram, Snapchat and TikTok, and how to turn the mess they send back into files you can actually use.

1. 1
   Ask the platform for your data

   Instagram: Accounts Centre → Your information and permissions → Download your information. Snapchat: Settings → My Data. TikTok: Settings and privacy → Account → Download your data. Choose JSON wherever you are offered a choice — it carries the dates and locations that HTML throws away.

2. 2
   Wait for it to be built

   Minutes on a small account, a couple of days on a large one. Instagram and Snapchat email you a link; TikTok puts the file in the app under its own Download data tab, which is why people miss it.

3. 3
   Open it on the export page

   Take the zip to the data-export page and drop it in. It is read inside your browser — there is no upload, no account, and nothing reaches a server.

4. 4
   Save the result

   You get your media back named and dated by when it was actually captured, foldered by year, with an index listing every date, caption and location.

Why no downloader can open a private post

A downloader fetches what a logged-out visitor can see. That is the whole mechanism. A private post is, by definition, not visible to a logged-out visitor, so there is nothing for the tool to fetch — the link does not lead to the video, it leads to a page saying you need permission.

This is why the answer is not a better downloader. Any site that offers to fetch private posts is offering one of two things: a scam, or a request for your username and password. The second is worse than it sounds. Handing your login to a website gives it your whole account, not one video, and it is the exact arrangement that ended SnapSaved in 2014 — a Snapchat-adjacent service that collected users' credentials and media and then leaked roughly 90,000 private photos.

Your own media is a different question entirely, and it has a real answer.

The route that works: your own data export

Every major platform has to give you a copy of your data if you ask. In the EU that is the GDPR's right to data portability; California's CCPA and a growing list of other laws say something similar. In practice all of them ship the same feature: a button that builds you a zip.

That zip contains your posts — including the private ones, the archived ones and, on some platforms, the ones you deleted recently. No password goes anywhere except into the platform's own app, where it already lives. It is slower than clicking download, and it is the only version of this that is actually yours to do.

What each platform actually sends you

They are not the same shape, and knowing which you are getting saves a lot of confusion.

Instagram sends the real files. Your photos and videos are inside the zip, alongside JSON describing each one. This is the easiest case — everything you need is in the archive.

Snapchat sends links, not files. memories_history.json holds one download link per Memory, and those links expire roughly seven days after the export is generated. If you file the email away for a fortnight, you have to start over.

TikTok sends a JSON of post links. user_data_tiktok.json lists every video you posted with its date and a URL. Like Snapchat, there is no media in the zip — and no realistic way to click a few hundred links by hand.

The date problem nobody warns you about

Here is what makes an export frustrating even once you have it. Exports routinely stamp every file with the date the archive was built, not the date the photo was taken. Import that into your phone's gallery and a decade of memories lands under a single day, in whatever order the zip happened to list them.

The real timestamp is not lost — it is sitting in the JSON next to the media, along with the location where the platform recorded one. Putting it back is a mechanical job: write it into the file's EXIF tags for photos, into the MP4 header for videos, and into the filename so it sorts correctly anywhere.

That is precisely what the export page does, and it does it in your browser rather than on a server, because the alternative is uploading your entire private archive to a stranger.

Why this happens in your browser and not on a server

It would be easier to build this the normal way: you upload the zip, a server processes it, you download the result. It would also mean a copy of your private photos sitting on someone else's machine, which is the thing you were trying to avoid.

So the processing runs as JavaScript inside your own tab. The file is read, not sent. Close the tab and nothing remains. For the link-based exports — Snapchat and TikTok — the page cannot fetch the links either, because browsers block a website from reading another site's response. Instead it writes you a short script that runs on your own computer and does the fetching there. You can read the script before you run it. It talks to the platform and to nothing else, and it needs no password.

How long it takes, and what to do while you wait

This is the part people abandon. Requesting the export takes a minute; receiving it can take two days. There is nothing to do in between, and no email from us — the request lives entirely between you and the platform.

Request it before you need it. If you are closing an account, migrating a phone, or worried about losing access, ask for the export first and deal with the zip when it arrives. On Snapchat especially, the clock on those links starts the moment the archive is built, not the moment you download it.

Can I use this on someone else’s account?

No, and it would not work if you tried. An export is issued to the account that requested it, after that account authenticates in the platform's own app. The links inside are bound to that request. There is no version of this that reaches another person's private posts.

That is not a limitation to route around. Getting your own media out is a right; taking someone else's is not, and the tooling here is deliberately shaped so it cannot do the second thing even by accident.

FAQ

More guides