Sources & Imports

How to keep the posts you save on Instagram

By the Muse team· 5 August 2026· 6 min read

Instagram's own Download Your Information tool can include your saved posts and collections, but only as links back to the original posts, not copies of the images. If the person who posted it deletes the post or the account, the link breaks. Here is what actually survives, and what does not.

Designers and other visual thinkers use Instagram's save button as a working reference library. Hundreds of interiors, layouts, colour palettes and outfits, collected over years and filed into named collections that felt organised at the time. Then a client asks for the mood board, or a phone gets replaced, and the truth about that library becomes obvious: it never actually belonged to you. It sat inside someone else's app, held together by a tap that Instagram calls saving and everyone else quietly assumes means keeping.

That gap between saving and keeping is worth taking seriously before it costs you something. Instagram does let you export your data, and saved posts really are part of it, but the export is not a backup in the way most people picture one. It reads more like a list of receipts than a box of the things you bought.

Does Instagram's own export include your saved posts?

Yes. Inside Accounts Center, under Your information and permissions, Download your information, also called Export your information, lets you choose which parts of your account to include, and saved content is one of the options. Instagram's own help article on exporting your information sets out the steps: open Accounts Center, choose Export your information, pick the profile, choose what to include and a format, then start the export. When saved content is selected, the file that arrives lists your saved posts, your saved reels, and the collections you filed them into, with the collection names attached.

What format does the download arrive in, and what does it actually contain?

You choose between JSON and HTML when you set the export up. JSON is the more useful of the two if you ever want to search or reuse the data yourself; HTML opens as a set of linked pages in a browser, which reads more like a small website than a spreadsheet. Instagram's own help pages state the file can take up to 30 days to arrive by email, and once it does, there is a limited window, four days, to open the link and download it before it expires.

Open the saved-content part of that file and the shape of the problem becomes clear. Your own posts, the photos and videos you actually uploaded, come through as real media files sitting in the export. A post you saved from someone else does not. It comes through as a reference: a link back to the original post, a caption, a timestamp, the collection it was filed under. Instagram never had the right to hand you a copy of someone else's photo inside your personal export, so it hands you the address instead.

The address is the whole problem.

A link works exactly as well as the post it points to. Once that post is gone, so is everything the link was standing in for.

Why can a saved post disappear even though you never touched it?

Because nothing about a save ever belonged to you in the first place, in the app or in the export. Saving a post creates a pointer to it, not a copy of it. If the person who posted it deletes it, or deletes their account entirely, that pointer breaks. Inside Instagram, the tile often stays visible in your Saved tab right up until you tap it, then shows something like this content isn't available. Inside the exported file, the same thing happens quietly: the link is dead on arrival, and nothing marks it as broken until you try to follow it.

This is not a fault in the export. It behaves exactly as designed. A save was only ever a bookmark, and a bookmark to a page that no longer exists was never going to become a copy of that page just because you asked Instagram for a file of it.

What is the honest way to keep something that is not yours?

The material you save from other people's Instagram accounts is reference, not your own work, so the honest way to keep it treats it that way. Screenshot the post, or save the image, and keep the source alongside it: who posted it and where it came from, not just the picture on its own. Some sites make even that harder than it should be by blocking a plain right-click save, and what to do when a website will not let you save an image covers the honest workarounds for that. That single habit does two things at once. It means the image is still useful to you later, once you have forgotten which account it was or why you saved it. And it means that if you ever want to credit the person whose work it is, or ask permission to use it more directly, you still can.

An image without its source is close to worthless a year later. You will recognise the room, the outfit, the layout, but you will not remember whose it was, and you will have no way back to ask. Keeping the link is not a formality. It is the part of the save that protects you, and the part that protects the person who made the thing you saved.

Do not go further than that. Bulk-download tools and scrapers that pull someone else's Instagram library wholesale sit outside what Instagram allows and outside what is fair to the person who posted it. Screenshotting or saving individual images you have actually looked at, for your own reference, with the source kept alongside, is a different thing entirely, and it is the version worth building a habit around.

What Muse does, and does not do, with what you save

Muse is built around that habit rather than around pretending Instagram's export is something it is not. When you save an image into Muse, whether by dragging a screenshot in or pasting one from your clipboard, it keeps the picture itself alongside a note field where the source link and the account name belong. That pairing, the image and where it came from, is what actually survives.

Be clear about the limit, because it matters here more than almost anywhere else: Muse does not archive web pages, and it cannot stop a post being deleted. If the original disappears, the live page is gone. What survives is your own copy of the image, sitting in your library, with the note that says where it came from and whose it was. That is a smaller promise than nothing is ever lost, but it is a true one, and it is the same promise a proper reference library has always made: keep the thing, and keep the receipt.

Frequently asked

Does Instagram's Download Your Information tool include saved posts and collections?
Yes. When you choose saved content as part of your export, the file includes your saved posts, saved reels, and the collections you filed them into, with the collection names attached.
What format does the Instagram data export arrive in?
You choose JSON or HTML when you set up the export. Instagram's own help pages state the file can take up to 30 days to arrive by email, with four days to download it once the link is sent.
Will my saved posts survive if the person who posted them deletes the post or their account?
No. A saved post is a link back to the original, not a copy of it. If the original is deleted or the account is removed, the link breaks both inside Instagram and inside the exported file.
Does Muse archive the original Instagram post?
No. Muse does not archive web pages and cannot stop a post being deleted. What it keeps is the image you saved plus the source link and account name you add alongside it, so the reference survives even when the original page does not.

Keep what you save, and where it came from

Free for 30 days. Then $29 once, and it is yours.

Written by the Muse team

We build Muse, a native Mac app that keeps everything you collect in one private library and finds it again in seconds.