Twitter/X Bookmark Limit:
Everything You Need to Know (2026)

The Bookmark Limit X Doesn't Talk About

If you've been using X (formerly Twitter) for any length of time and you're a heavy bookmarker, you've probably noticed something unsettling: bookmarks you know you saved have vanished. No notification. No error. They're just gone.

You're not imagining it. X does have a bookmark limit — it's just not documented anywhere in their help center, their terms, or the app itself. The platform quietly removes your oldest bookmarks once you cross a threshold, and it does so without asking you or giving you a chance to archive them first.

Based on reports from users across Reddit, X itself, and developer communities, the limit for free accounts sits at around 800 bookmarks. Some users hit it at 750, others report getting to 900 before seeing drops — suggesting the exact number may vary or change over time. The common thread is that no one was warned.

What's the Actual X Bookmark Limit in 2026?

Here's what we know based on user reports and community research:

• Free accounts: approximately 800 bookmarks before silent deletion begins
• X Premium (formerly Twitter Blue): a higher cap, but still undocumented — users report limits in the thousands
• X Premium+: also has a cap, exact number unknown
• API access: the bookmarks/lookup endpoint confirms a maximum of 800 for free tier accounts via the v2 API

The 800 number for free accounts has been inferred partly from the X API documentation, which sets a maximum max_results of 100 per page with an implied total cap. Developers building bookmark-related tools have confirmed this ceiling in practice.

The frustrating part isn't just the limit itself. It's that X treats bookmarks as ephemeral storage, not permanent saves. That's a fundamentally different expectation than most users have when they tap that bookmark icon.

What Happens When You Hit the Limit?

When you cross the bookmark threshold, one of two things tends to happen — and neither involves X telling you about it:

• New bookmarks silently push out your oldest ones (FIFO — first in, first out)
• New bookmarks simply fail to save, with no error message shown

There's no warning notification. No "you're approaching your limit" banner. No email. You'll only notice when you go looking for something you saved weeks or months ago and it's no longer there.

Why Are My Twitter Bookmarks Disappearing?

Bookmarks can disappear for a few different reasons, and it's worth understanding which one you're dealing with:

1. You hit the bookmark limit

The most common cause. If you've been bookmarking actively for months or years, you've almost certainly crossed 800 at some point. The oldest bookmarks get dropped first, so the ones you saved earliest — often the ones you'd most want to keep — are the first to go.

2. The original tweet was deleted

If the person who wrote a tweet deletes it, the bookmark disappears too. There's no copy held on X's side. Once a tweet is gone, the bookmark becomes a dead link and X removes it from your list. This is especially common with viral threads where the author later deletes parts of a conversation.

3. The account was suspended or deactivated

When an account gets suspended or the user deletes their account, all their tweets become inaccessible. Any bookmarks pointing to that content disappear from your list as well.

4. Private account you no longer follow

If someone switched their account from public to private after you bookmarked their content, and you don't follow them, that bookmark becomes inaccessible and may disappear from your list entirely.

5. Sync issues (rare)

Occasionally, bookmarks fail to sync properly across devices due to app glitches. In these cases, the content may still be there — try force-closing the app, clearing the cache, or accessing bookmarks from a different device to see if they reappear.

How to Check How Many Bookmarks You Have

X doesn't display a running bookmark count anywhere in the app, which makes it impossible to know how close you are to the limit without counting manually — or using the API.

Here's the most practical way to get a rough count:

• Open X on desktop at x.com/i/bookmarks
• Scroll to the very bottom of your bookmarks list
• The count isn't shown, but you'll have a rough sense of volume after scrolling
• If scrolling takes more than a couple of minutes, you likely have several hundred or more

For an exact count, developers can use the X API v2 bookmarks endpoint, but that requires API access and a bit of technical setup — not realistic for most users.

The honest answer is that X has made it deliberately opaque. You can't easily know where you stand, which is exactly why the limit catches people off guard.

Better Alternatives to Twitter Bookmarks

If the built-in bookmark system is this unreliable, what should you use instead? Here are the realistic options:

Save directly to your browser (recommended)

Tools that extract and store tweet content locally — to your own computer or browser storage — are immune to X's limits and deletions. Even if X removes a tweet tomorrow, you already have the full text, media, and metadata saved on your device. This is the most resilient approach because you're not dependent on X's infrastructure at all.

Read-later apps (partial solution)

Services like Pocket or Instapaper can save tweet URLs, but they typically only store the link — not the actual content. If the tweet is deleted or the account goes private, you lose the content just the same. They also don't handle threads well, often only capturing the first tweet.

Note-taking apps (manual, time-consuming)

Copy-pasting threads into Notion, Obsidian, or Apple Notes works but doesn't scale. It takes 3–5 minutes per thread and requires you to manually format and organize everything. If you're saving more than a few threads a week, this gets unmanageable quickly.

Screenshots (fragile)

Screenshots preserve the visual appearance of tweets but aren't searchable, take up storage space, and make it impossible to copy the text later. They're a last resort, not a system.

How to Export Your Bookmarks Before They're Gone

X does not offer any native bookmark export feature. There is no "download my bookmarks" button, no CSV export, nothing. This is either an oversight or intentional — either way, it means if you want your bookmarks in a portable format, you have to act before they disappear.

Your options for getting bookmarks out of X:

• Save each thread individually using a browser extension that extracts the full content as you browse
• Use the X API to programmatically pull your bookmarks before they hit the cap (requires developer access)
• Request your data archive from X (Settings → Your Account → Download an archive of your data) — note that this archive includes your tweets and likes but does not include bookmarks

The data archive exclusion is particularly frustrating. X will let you download your entire post history, but the things you saved from other people? Those aren't included. You're on your own.

Stop Losing Threads — A Permanent Fix

The root problem with X bookmarks is that they're stored on X's servers, subject to X's limits, X's deletion policies, and X's infrastructure. You never truly own them.

The only real fix is to get your saved content off X's servers entirely.

TweetThreadSaver is a free Chrome extension that saves entire threads — every tweet, every reply, author details, and media — directly to your browser's local storage. Your computer. Your data.

There is no limit on how many threads you can save. There's no subscription required to access your own library. If X deletes a tweet tomorrow, you still have the full text. If you're offline on a flight, you can still read everything you've saved. The content is yours, permanently.

For anyone building a personal knowledge base from X — researchers, writers, developers, marketers — the built-in bookmark system was never going to cut it. An 800-item cap, no export, no search, and silent deletion isn't a knowledge management tool. It's a temporary hold queue.

Save your threads somewhere that actually keeps them.

Frequently Asked Questions