Why your X (Twitter) bookmarks disappeared

When your old X (Twitter) bookmarks disappear, it's almost always one of four causes: the posts were deleted or their authors went private or got suspended, your list grew past what X reliably shows, the app glitched, or you're signed into the wrong account. Only the first one is permanent. This guide helps you work out which case you're in, what you can still get back, and how to make sure disappeared X bookmarks never cost you anything again.

Start with the reversible causes, because they're the most common.

Rule out the boring explanations first

Before assuming loss, spend two minutes on the basics:

Wrong account. If you juggle a personal and a work handle, check which one is active. Bookmarks are per-account, and an empty list on the wrong login looks identical to a wiped one.

App glitch or stale cache. Sync delays and loading bugs regularly make big bookmark lists render as empty or truncated, especially in the mobile app. Multiple trackers of this problem report that a suddenly empty list is usually a UI or sync issue rather than deletion.

Force-quit the app, or better, open x.com/i/bookmarks in a desktop browser, which tends to be the more honest view. Log out and back in if it still looks wrong.

A moved entry point. X reshuffles navigation now and then, and app updates have relocated where saved content lives. If the icon you're used to is gone, search the app's sidebar before concluding the data is.

If the list comes back after any of this, you're done. If specific posts are missing from an otherwise healthy list, keep reading.

The sixty-second version of that diagnostic, in order: open x.com/i/bookmarks on desktop while logged into the right handle; hard refresh; log out and back in; check the mobile app afterwards, not before. Web first matters because the app caches aggressively, and a stale cache is the most common source of false alarms.

The permanent cause: the post itself is gone

A bookmark is a pointer, not a copy. X stores no snapshot of the post for you. So when the author deletes the post, protects their account, or gets suspended, your bookmark points at nothing, and X quietly drops it from what it shows you. Circleboom's write-up of this problem lists deleted, protected, and suspended source accounts as the leading reasons individual bookmarks vanish.

This is the cause behind most "my bookmarks are slowly shrinking" stories. It doesn't hit all at once. It erodes. High-engagement posts get deleted by their authors surprisingly often, accounts go private during pile-ons, and spam sweeps take suspended accounts' posts with them.

There is no fix after the fact. If the post is deleted, no tool operating inside X can show it to you again. The only defenses are copies made before the deletion, which is the entire case for backing up your X bookmarks.

Telling a deleted post from a suspended account

If you can still remember what a missing bookmark pointed at, you can usually work out what happened to it in about a minute, and the answer changes what you should do next.

Search the author's handle. If their profile loads normally and the post is nowhere in their timeline, they deleted it. If the profile comes back with a suspension notice instead, X removed the whole account, and every post it made went with it. If the profile loads but the posts sit behind a follow request, the account went private, and the post still exists.

Only that third case tends to reverse itself. A private account that opens up again, or accepts you, should make the post visible to you once more. Suspended accounts are occasionally reinstated on appeal and their posts return with them, but that is not something to plan around. A deleted post is final.

If you saved the URL anywhere, a web archive may still hold a copy of the text. That will not put the bookmark back, but it can get you the thing you actually wanted, which was what the post said.

The ceiling nobody announces

The third cause is scale. X's API returns at most your 800 most recent bookmarks, a documented cap, and the app's own display behavior on large lists is unreliable: some users hit a wall somewhere past 800 saves where scrolling just stops feeding older posts, while others scroll much further without trouble.

Your old saves may still exist server side, but a bookmark you can't scroll to or search for is functionally gone. I've separated what's documented from what's folklore in the X bookmark limit, explained.

If your missing bookmarks are specifically your oldest ones, and your list is well into the hundreds, this is the likely culprit.

You can get a rough sense of where you stand without counting anything. Scroll your bookmark list to the bottom. If you reach an end, you are inside whatever X is currently willing to render, and the list you see is the list you have. If it keeps loading until you give up, you are past the point where the app works as an inventory, and an export is the only accurate count available to you.

Will they come back on their own?

Sometimes, and which way it goes follows directly from the cause.

Bookmarks missing because of a sync problem or a stale cache come back without you doing anything. Usually within a day, often within minutes. Nothing was deleted; the app failed to draw a list it still had.

Bookmarks that aged past the point where X will load them do not return on their own, but they were never deleted either. They sit there, unreachable by scrolling, until something reads further than the app does.

Bookmarks whose source post is gone never come back. There is nothing left to point at.

This is why waiting is worth doing before you spend an evening on recovery tools. If your entire list vanished at once, give it a day before assuming the worst. Whole-list disappearances are almost always the reversible kind, and the permanent cause almost never takes everything at the same moment.

What X support can do about it

Not much, and knowing that early saves you a week of waiting on a ticket.

X keeps no user-facing backup of your bookmark list. There is no restore button, no recently-deleted folder, and no support flow that puts saves back. Bookmarks are also absent from the data archive you can download, which catches people out, because the archive sounds like it should cover everything the account ever touched. What it actually contains is in the X data archive, explained.

The one thing worth reporting is a suspected outage. When bookmarks break for a lot of people at once, it shows up in X's developer forums before it shows up anywhere official, and those threads are the quickest way to find out whether the problem is yours or everyone's.

What you can still recover

Be honest with yourself about which bucket each missing save is in:

• Glitch or wrong account: fully recoverable. The data was never gone.
• Aged out of reach: possibly recoverable. If the posts still exist, a browser extension that reads the rendered page as you scroll can sometimes surface more than the API ever will; the tooling is in how to export your X bookmarks.
• Source post deleted or hidden: not recoverable from X. Your only hope is an external copy that existed before the deletion, like an extension's local cache (XSaved keeps one), an old export file, or a bookmark manager that stored the content.

If you land in the middle bucket, the order that works is: export what the app will still hand you today, before anything else changes, and only then worry about reaching further back. An export you already have beats a longer list you might get. Extensions that read the rendered page while you scroll can reach past what the API returns, but they are reading a live page, so they capture only what X is willing to draw at that moment.

That last case stings, and it's worth letting it change your setup.

Make it never matter again

Two habits close the door on this whole class of problem. First, keep an export file: ten minutes with a free extension gets your current list into CSV and JSON you own. Second, put something in place that copies new saves continuously, so the file never goes stale. The options, from free extensions to sync services, are compared in the best X bookmark managers, and the broader series is on the X bookmark guides hub.

The export is the part people skip, and it is the part that matters when something goes wrong. Do it once today, then again whenever it crosses your mind. Keep the file somewhere you will actually look for it later, not in a downloads folder you clear out every few months. What you want from it is the post URL, the author handle, and the text. Those three are enough to find or rebuild almost anything you lose.

One habit is worth adding on top. When a post genuinely matters, do not only bookmark it. Bookmarking is the weakest way to save something on X: it depends on the post surviving, on your list staying short enough to load, and on X not changing how the feature works. Copy the text somewhere you control, or save it into a tool that keeps its own copy.

Bookmarx handles the continuous half of that. It syncs new bookmarks through the official X API from the moment you connect, and it stores its own copy of each synced post's text along with an AI summary. If the author deletes the post next month, your library keeps the content and the takeaways. It won't recover anything that vanished before you connected, and it doesn't export files, so pair it with a one-time export if you need one. But going forward, deletion stops being your problem.

Frequently asked questions

Can X support restore my disappeared bookmarks?

No. X keeps no user-facing backup of your bookmark list, there's no restore feature, and bookmarks aren't in the downloadable data archive. If the underlying posts still exist, they may resurface after a glitch clears, but nothing X offers can bring back saves of deleted posts.

Why did only some of my bookmarks disappear?

Scattered gaps almost always mean the source posts became unavailable: deleted, made private, or removed with a suspended account. Your list shrinks quietly because X drops what it can no longer show you.

My entire bookmarks list is empty. Is it gone?

Probably not. A fully empty list usually points to being signed into the wrong account, a sync delay, or an app glitch. Check the web version, confirm the handle in the sidebar, and try again after logging out and back in before assuming loss.

Do bookmarks expire after a certain time?

No. There's no expiry date on a bookmark. Age only matters indirectly: older posts have had more time to be deleted, and very old saves can fall out of reach as your list grows past what X reliably loads.

How do I recover disappeared Twitter bookmarks?

It depends which bucket you are in. A glitch or a wrong login is fully recoverable, because the data was never gone. Saves that aged out of reach may still be recoverable if the posts themselves exist, since a browser extension that reads the rendered page as you scroll can sometimes surface more than the API returns. If the source post was deleted or made private, nothing on X brings it back, and your only hope is a copy that existed before it went.

How many bookmarks can you have on Twitter?

There is no documented cap on how many you can save. The limit people actually hit is on retrieval: X's API returns at most your 800 most recent bookmarks, and scrolling behavior on large lists gets unreliable somewhere past that. You can keep saving well beyond 800, but reaching the oldest ones stops being dependable.

My bookmarks show on the web but not in the X app. Why?

That pattern points at the app rather than your account, and it is the most recoverable case of all. A stale cache or a sync delay can leave the app rendering an incomplete list while the web version still has everything. Check the web version first, then log out and back in on the app, before assuming anything is lost.