How to save your X (Twitter) bookmarks before they disappear

X bookmarks are not durable — they disappear when the original tweet is deleted, the account goes private or gets suspended, or you exceed the bookmark cap. To keep them: export with Circleboom or Dewey ($9-$29/month), save individual tweets to Raindrop or Readwise Reader as URLs, or pipe them into a tool that captures the full text and image at save time so the bookmark survives even when the tweet does not.

The X bookmark button looks like it does the same job as a browser bookmark. It does not. An X bookmark is a pointer to a tweet that lives on X's servers — if the tweet stops existing, your bookmark stops existing too. Every time a poster deletes a thread, locks their account, or gets suspended, a chunk of your saved library evaporates without warning. There is no email, no recovered-items folder, no "this bookmark is now dead" indicator.

This is the 2026 playbook for getting your bookmarks out of X and into a place where they survive the next deletion.

Why do X bookmarks disappear in the first place?

Four failure modes, all documented in X's help pages but never surfaced in the bookmark UI itself.

Tweet deletion. When the original poster deletes a tweet, it is removed from the X graph entirely. Your bookmark row stays in the bookmark list for a few hours then vanishes silently. The X help page on bookmarks states that bookmarks "may not be available if the original Tweet is no longer on X" (help.x.com/en/using-x/bookmarks).

Account lock or deactivation. A poster who switches their account to protected mode retroactively hides every tweet — including the one you bookmarked when the account was public. Deactivation does the same thing permanently. There is no notification to bookmark holders.

Account suspension. When X suspends an account, every tweet by that account is dropped from public view. Bookmarks pointing at suspended-account tweets show a generic "This Post is from a suspended account" placeholder and the content is unrecoverable through X.

The bookmark cap. Free X accounts have a hard cap on stored bookmarks. Once you cross it, new bookmark taps appear to succeed but the row never actually saves — X silently drops it. The cap has shifted over the past two years; the current free-tier ceiling is documented at 200 active bookmarks.

All four are by design. X built bookmarks as a session-state feature, not an archive feature. The mismatch between how people use it ("save this for later") and how it actually works ("a pointer that might evaporate") is the entire reason this guide exists.

What is the actual X bookmark cap on free vs Premium?

The limits as of 2026:

Free tier: 200 active bookmarks, 100 bookmark folders blocked entirely. Once you hit 200, new saves silently fail. Old bookmarks do not auto-evict — the queue just stops accepting new entries.

X Premium ($8/month or $84/year): Unlimited bookmarks plus access to bookmark folders. Premium subscribers also get the official "bookmark folders" feature that lets you organize saves into named buckets.

X Premium+ ($16/month): Same bookmark behavior as Premium plus a few unrelated perks. There is no premium-only "bookmark archive" feature — even at $16/month, deleted tweets still take their bookmarks with them.

The practical takeaway: Premium fixes the cap problem but not the deletion problem. If you bookmark for "read it next week" it is fine. If you bookmark for "reference this in six months," Premium does not help.

How do you export X bookmarks in 2026?

Three working paths in mid-2026. They differ on cost, what data comes out, and how much manual work is left after the export.

Path 1: Official X data archive (free, slow, IDs only). Go to Settings → Your Account → Download an archive of your data. X emails you when the ZIP is ready, usually 24-48 hours. Unzip and find data/bookmark.js. The file is a JavaScript array of objects, each with tweetId and bookmarkedAt. It does NOT include the tweet text — only the numeric ID and the timestamp. You then have to either reconstruct URLs (https://x.com/i/web/status/{tweetId}) or run each ID through a tool that pulls the text. If the tweet is already deleted, you get the ID and nothing else (X data download docs).

Path 2: Circleboom (paid, fast, metadata only). Connect Circleboom to your X account and run the bookmark export module. Output is a CSV with tweet_url, tweet_text (if still live), author, created_at, and bookmarked_at. Pricing starts at $24.99/month for the Pro plan that includes bookmark export. Strong upside: it works on free X accounts. Downside: if a tweet was already deleted before you ran the export, Circleboom can only give you the URL, not the text (circleboom.com/twitter-bookmark-export).

Path 3: Dewey (paid one-time, fast, text included). Dewey is a desktop app that does the export and the text-snapshot in one pass. One-time $29.99 license, no monthly subscription. For tweets currently live, it captures the full text. For tweets that have been deleted recently, it sometimes pulls the cached version from a CDN — not guaranteed, but more than the other paths. (dewey.tools)

Whichever path you pick, run it once a week if your bookmark library matters to you. Tweets keep getting deleted. The export from January will be missing rows by June.

Which tool keeps the text after the tweet is deleted?

The key distinction across the six tools above: did the tool save the tweet text and image into its own database at the moment you bookmarked it, or did it save a pointer that re-fetches from X every time?

Pointer-only tools: X bookmarks themselves, the X official data archive (IDs only), and Raindrop in its default URL-save mode. If the tweet dies, the content dies.

Snapshot tools: Raindrop with the "save full page" Pro option, Readwise Reader (snapshot is default), Dewey export, and dEssence. These store the tweet body, the author handle, the image, and the timestamp at the moment of save. The original tweet can vanish and your archive still has the text.

The practical test: bookmark a tweet, wait an hour, then open the tweet on X in incognito mode while logged out. If you see a placeholder telling you the tweet is from a protected account, the poster locked their account in that hour. Check your bookmarking tool. If the tool shows you the original text anyway, you have a snapshot tool. If it shows the same placeholder, you have a pointer tool. Run this test before you trust any tool with the bookmarks that matter to you.

"I bookmarked a 47-tweet thread on prompt engineering in March. In May the author went private. The bookmark in my X account is now a grey box. The same thread in my Readwise Reader is still fully there. That moment changed how I think about saving anything on X."

— X power user, r/Twitter discussion thread

How do you make old bookmarks searchable by topic?

Once you have a few thousand bookmarks in an external tool, the next problem is finding the one you want. X's bookmark search is limited to keyword matches inside the tweet text — useless when you remember the topic but not the exact words.

The options in order of effort:

Premium bookmark folders. $8/month, works only inside X, requires you to file each new bookmark into a folder by hand. Good for someone who saves 5-10 bookmarks a week with clear topic buckets. Breaks down at high volume.

Tag-based external tools. Raindrop and Pinboard let you tag each saved tweet. Same problem as folders: requires manual filing per save. Auto-tag tools that scan tweet text help, but they tag on surface words, not topic.

Meaning search. Save tweets into a tool that indexes them by what they are about, not just what they say. dEssence is built around this pattern — save it, forget it, ask for it later. You ask "the thread about why senior engineers are leaving FAANG" and the right tweet comes back even if the word "senior" never appeared in the body.

The best tag system in the world fails the same way Pocket did: nobody actually maintains tags long term. The honest answer is to pick a tool that does not require you to maintain anything and accept the imperfect first results in exchange for not having a tagging chore.

What is the cheapest path if you have a few thousand bookmarks?

For a one-time rescue under $30: Dewey ($29.99 one-time) plus the free X data archive as a backup. Run Dewey once, export the CSV, store it in Dropbox or Google Drive, and treat it as your durable copy.

For ongoing capture under $5/month: free X data archive every 30 days plus Raindrop Free (10,000 saves). Re-run the archive request the first of every month and diff against your last export to find new bookmarks; bookmark important tweets directly to Raindrop with the bookmarklet so the snapshot is captured immediately.

For zero-budget DIY: the X data archive on its own. You lose the text for any deleted tweet, but the timestamps and IDs are enough for many people who just want the count and the original URL.

For anyone whose bookmarks contain reference material they will actually need to find later — Readwise Reader at $9.99/month or dEssence in beta. The $9.99 buys you the snapshot, the highlight system, and full text search. dEssence buys you the meaning search instead of the keyword search, at zero cost during beta with a 500-item free cap.

How do you stop new bookmarks from also disappearing?

The export step solves the back-catalog problem. The going-forward problem is harder — every time you tap the bookmark icon, you are creating a new fragile pointer.

The pattern that works: replace the bookmark tap with a save-to-external-tool action. Three approaches:

Share-sheet replacement. On iOS and Android, the X share sheet lets you send a tweet directly to Raindrop, Readwise Reader, Pocket (now gone), or a custom app via URL scheme. Set your most-used saver as a one-tap share destination and stop using the in-app bookmark button entirely.

Browser extension on desktop. Raindrop, Readwise, and dEssence all ship a Chrome extension that adds a save button to every tweet's quick action bar. Click that button instead of the X bookmark. The save fires through to your durable archive.

Telegram or messaging-app bridge. Some tools accept saves via direct message — forward a tweet to a bot, the bot stores the URL and the snapshot. dEssence offers a Telegram bot save surface on top of the Chrome extension and web app. Useful if you read X mostly on mobile and the share-sheet route is two taps too many.

Whichever route you pick, the goal is the same: no tweet you actually care about should live only inside X's bookmark feature. If the answer to "where else is this saved" is "nowhere," you are one delete away from losing it. Ask in your own words. No folders, no tags, no organizing — just save it, forget it, ask for it later from a tool that owns the snapshot, not X.