April 7, 2026
X Bookmark Limits Explained — and How to Bypass Them
What are the actual limits on X (Twitter) bookmarks? Is there a maximum? Here's what we know in 2026 — and how to bypass any limit you might hit.
People ask this all the time: "How many bookmarks can I have on X?" The answer is more complicated than it should be, and it has changed several times since X bought Twitter. This article walks through what's actually true in 2026 — what limits exist, what limits don't, and how to work around the ones you might hit.
The official answer in 2026
As of 2026, X has no hard limit on the total number of bookmarks for a regular account. You can save tens of thousands. Some power users have reported libraries in the 50,000+ range with no errors. The bookmark feature itself does not enforce a cap.
That said, there are several soft limits that affect how usable your bookmarks become as the number grows. These are the ones that actually matter day-to-day.
The real limits (the ones that bite you)
1. The UI breaks above ~5,000 bookmarks
X's bookmarks page loads items lazily. The infinite scroll is designed for the median user, who probably has 50-200 bookmarks. Beyond a few thousand:
- The page becomes slow, especially on mobile
- Scrolling jumps and re-renders
- Older bookmarks become practically unreachable — you can't scroll past a certain depth without things breaking
So technically you can have 30,000 bookmarks. Practically, you can only see the most recent 1,000 or so without pain.
2. Bookmark Folders are limited and paid
X Premium users can create bookmark folders. Free users can't. And even with Premium, there are caps:
- Maximum number of folders per account
- Maximum bookmarks per folder
- No nesting (folders inside folders)
These caps change occasionally, but the structural problem doesn't: folders are a manual organization system that doesn't scale and locks you into paying.
3. Sync delay
Bookmarks sync between devices, but there's an unspecified delay — sometimes seconds, sometimes hours. If you're a power user who saves dozens of bookmarks a day across multiple devices, you'll notice the lag. Occasionally bookmarks vanish briefly during the sync window.
4. The "Clear all" trap
X has a "Clear all bookmarks" button. There's no per-folder clear, no undo, no soft delete. If you tap it accidentally, your entire library is gone instantly with no recovery.
This isn't a quantity limit, but it's a de facto ceiling: the bigger your library, the more catastrophic an accidental clear becomes.
5. Deleted tweets disappear from your bookmarks
If a tweet you bookmarked is deleted, suspended, or made private, it disappears from your bookmark list. Your library shrinks without you doing anything. Over a few years, this can quietly remove hundreds of bookmarks.
How to bypass these limits
The key insight: all of these problems come from relying on X to be the storage layer for your bookmarks. The fix is to keep your own copy.
Option 1: Manual export (occasionally)
You can manually export bookmarks via the X API if you have a paid developer account. This is annoying, expensive, and not real-time. It works as a last resort if you just want a one-time backup.
Option 2: A bookmark manager extension
This is what we recommend, and it's why we built XSaved. A bookmark manager extension solves all five limits at once:
| Limit | How XSaved fixes it |
|---|---|
| UI breaks at scale | XSaved has its own search-first UI that handles 50,000+ bookmarks fast |
| Folders are paid + capped | Free unlimited tags + auto-clusters, no folder caps |
| Sync delay | Local-first storage, no sync layer to be slow |
| Accidental "Clear all" | Local copy survives even if you nuke X bookmarks |
| Deleted tweets vanish | Local cache preserves deleted tweet content |
You install it, let it sync once, and from that point on your bookmarks live in your own browser, not on X's servers. The limits stop mattering.
Option 3: Roll your own (not recommended)
You could write a script that uses the X API to pull bookmarks daily and save them to a database. This works if you're a developer and you enjoy maintaining infrastructure. For everyone else, it's overkill.
"Will X ever raise the limits?"
Probably not in a meaningful way. The limits aren't there because X can't support more — they're there because the bookmark feature isn't a priority. As long as bookmarks don't move engagement metrics, expect them to stay roughly as they are.
The thing that has changed over the past few years is the appearance of paid Premium tiers with slightly better bookmark features (like folders). The trend is more limits removed for paying users, not for everyone.
TL;DR
| Question | Answer |
|---|---|
| Is there a hard limit on X bookmarks? | No, not officially |
| What's the practical limit? | ~5,000 before the UI gets painful |
| Are bookmark folders free? | No, X Premium only |
| Do deleted tweets stay in my bookmarks? | No, they vanish |
| How do I bypass all of this? | Use a local-first bookmark manager like XSaved |
The cleanest fix in 2026 is to stop treating X as the source of truth for your bookmarks and start treating it as the capture layer. You save things on X. You read, search, and organize them somewhere you control.
That mental shift solves every limit on this page.
Tired of losing track of your X bookmarks?
XSaved is a free Chrome extension that turns them into a searchable, organized library.
Install XSaved