Facebook Saved Posts: Find Them, Sort Them, Get Them Out

You saved something on Facebook months ago. A post about rewiring a house, a recipe, a long thread about a school catchment area. Now you want it back, and you cannot even find the button you pressed, never mind the post itself. Nothing was deleted. Meta has moved the door about three times since you last walked through it.

That is the easy half of the problem. The hard half arrives once you find the list. You can filter your saves by type and you can scroll them. You cannot search them for what the post was actually about. That is the entire toolkit, and it has been the entire toolkit for years.

So this is two jobs, not one. Finding your saves, then making them findable. Facebook has a decent answer to the first and no answer at all to the second. Which is why the honest advice at the bottom of this page is to get a copy out of Facebook rather than to keep tidying up inside it.

Where Facebook actually keeps your saved posts

One address does most of the work. Type facebook.com/saved into the address bar on desktop and you land straight on the list, no menu archaeology required.

If you would rather click, the entry point is the left menu on the home feed, under Saved. It is often hidden behind See more, which is a large part of why people think the feature was removed. On the mobile app, tap the menu icon, then Saved, expanding See more if it is not on the first screen.

Facebook’s own Saving and Collections help section is the reference if the menus shift again, which they will.

The second list

Here is the part almost nobody knows, and it explains more missing saves than every menu redesign combined. Marketplace keeps its own saved list. Listings you saved while browsing Marketplace live at facebook.com/marketplace/you/saved, reachable from the Marketplace page rather than the main Saved feed.

Two lists. Two addresses. No link between them, and no message telling you the other one exists. If you saved a sofa and cannot find it, you are almost certainly looking in the wrong list.

Why your saved items look like they vanished

Nothing on Facebook deletes your saves for you. Three things make them look deleted, and only the last one is real.

The menu moved: Meta has reorganized Facebook’s navigation repeatedly, and Saved has slid between the sidebar, the More tab, and the overflow menu behind See more. The list did not change. The route to it did.

You are in the wrong list: covered above, and it is the most common cause.

The original post is gone: this one is real, and it is permanent. When the author deletes a post, switches its audience so you can no longer see it, deactivates the account, or Facebook removes the content, your save turns into a slot that will not open. Nothing is recoverable, because there was never a copy to recover.

That third case deserves its own section, because it is the reason the rest of this advice ends where it does.

Facebook search matches names, not meaning

You saved a post about mortgage rates. You remember roughly nothing else about it. You open your saved list and type “mortgage”.

The box will happily match a page name, a collection name, or a title. It does not reach the text inside the post you saved. If the useful part of that save was the third paragraph of somebody’s status update, it is not indexed for you and typing the right word will not surface it.

So the fallback is scrolling. Which works fine at forty saves and is useless at four hundred.

The uncomfortable version

Every minute you spend building collections is a minute spent compensating for a missing search box. Filing is what people do when search does not work. Facebook launched Save on July 21, 2014, describing it as a way to keep “links, places, movies, TV and music” for later. Twelve years on, the button still works exactly as well as it did that week, and the thing that would make a twelve-year-old pile useful still is not there.

This is not incompetence. A save is a session that ends. Meta’s business is sessions that continue. A great search box over your saved posts is a feature that sends you away from the feed, so it keeps losing to the feed. Nobody is going to fix this for you.

Collections, and the shared ones most people miss

A collection is a named folder inside your saved items. You create one, then add saves to it manually. Recipes, house stuff, work reading, whatever shape your pile takes.

Collections do two things well. They cut a long list into piles you can skim, and they survive the menu moving around. What they do not do is make the contents searchable, so a collection is a smaller haystack rather than a way to find the needle.

The feature worth knowing about is shared collections: You can invite friends to a collection and they become contributors, which means they can add their own saves to it as well as see yours. It is genuinely good for a holiday, a house move, or anything where two people keep sending each other links. It is also the one part of Facebook Saved that has had real thought put into it since launch.

One caution before you spend an afternoon on this. Sorting a pile you cannot search is worth doing only if the pile is small enough that the folders are the answer. If you have hundreds of saves, the folders are a coping mechanism. Export first, organize second.

A Facebook save is a pointer, not a copy

When you tap Save, Facebook does not keep the post’s text, the images, or the author’s name anywhere you own. It records that you saved a specific post, and it looks that post up again each time you open your saved list.

Which means your save is only as durable as the original. Delete the post, restrict its audience, deactivate the account, or let a moderator remove it from a group, and the entry in your list stops resolving. There is no notification. The slot just stops opening one day, and you find out at the exact moment you need the thing.

This is not a Facebook problem. It is how saving works nearly everywhere. Social bookmarks disappear for the same structural reason on every platform, and the loss is gradual enough that most people never notice it happening.

How to export your Facebook saved items

Meta does let you take your saved items with you, and has a help page specifically for downloading saved items and collections. The flow lives in Accounts Center now, not in Facebook’s own settings.

1. Open Settings and privacy, then Accounts Center.
2. Choose Your information and permissions.
3. Start an export. Meta has labeled this both Download your information and Export your information, so take whichever one your app shows.
4. Pick the profile you want, then narrow the categories to saved items and collections. Do not export everything unless you want to wait days for an archive you will never open.
5. Choose JSON if you want a file you can actually process, or HTML if you just want to click through it in a browser.
6. Wait for the email, then download it promptly. The link sits in Available downloads for a few days and then expires.

The date range control is worth setting to your full history. The default is not always all time, and a partial range quietly leaves your oldest saves out of the file, which are exactly the ones most at risk.

What the export gives you, and what it does not

This is where expectations need managing, because the export is better than nothing and considerably worse than a backup.

You get a structured record of what you saved and where it pointed. What you do not reliably get is the content itself. The archive describes your saves. It does not contain the posts as they looked on the day you saved them, and it cannot resurrect the ones that already went dark before you ran it.

Which produces a rule that is easy to state and easy to ignore. An export only preserves what still exists at the moment you run it. Every save that broke last year is already unrecoverable, and no export will bring it back.

If that pattern sounds familiar, it is because every platform ships the same disappointing file. Reddit’s official export hands you a CSV of bare permalinks with no titles and no post text, and LinkedIn’s does much the same. The shape of the problem does not change when you switch social networks.

Read across that table and the pattern is hard to miss. Every one of these platforms will let you save, and every one of them will let you leave with a list of addresses. Not one of them will let you ask a question about what you saved. The save button is a universal feature and the search box is a universal omission, which tells you something about whose problem each one is solving.

The fix that actually holds

There are only three honest options, and it is worth being blunt about how well each works.

Screenshot the handful that matter: ugly, manual, and completely reliable. If ten of your saves are genuinely important, this beats every clever alternative. It does not scale past that.

Export on a schedule: run the Accounts Center export every few months. This protects you from losing access to the account and gives you a record you control. It does not protect any individual post from being deleted between exports, and it depends on you remembering.

Capture the content at save time: the only approach that fixes the cause rather than the symptom. If something copies the full text the moment you save it, later deletion of the original stops mattering, and the copy is yours to search however you like.

The third one is the only one that gives you both durability and search, because once you hold the text, searching it is a solved problem.

Facebook is not going to do this for you, and no browser extension can make Facebook’s own list searchable by meaning. What you can do is stop treating a save button as storage. Save the things that matter into somewhere you control, and let Facebook’s list be what it actually is, which is a short-term parking space.

If the platforms you save from most are the ones with the same broken search, the job is identical there. Finding an old bookmark on X runs into the same wall, and LinkedIn saves have no native search at all.

That is the part ContextBolt was built for. It captures your X, Reddit and LinkedIn saves automatically through a Chrome extension, keeps the full content on your own device rather than a pointer, tags it, and makes it searchable by what the post was about. Facebook is not one of the platforms it captures, so this page is not a pitch to solve your Facebook pile. It is an argument that the pile is the predictable result of trusting a save button, and that the platforms where the same problem is solvable are worth solving first. The free Basic tier covers 150 saves, and Pro is $6 a month for unlimited saves plus an MCP endpoint that lets Claude read the collection directly.