Reached the Twitter bookmark limit? How to save past 800 (and why it hurts)

What the limit actually is

X caps your bookmarks. Heavy users hit a ceiling — often discussed in the 800-ish range, though X has never published a clean, official number and the behavior has shifted over time. The point isn't the exact figure. The point is that there *is* a wall, you can't see it coming, and the platform doesn't tell you when you've hit it.

The failure is silent, and that's the cruel part. When you're at the cap, the bookmark icon still animates as though it saved. You move on. Days later you go looking for that thread, search your bookmarks, and it's gone — except it was never there. You didn't lose it. It never landed. By then the original tweet may be buried, deleted, or behind an account that's gone private. The save you trusted was a no-op dressed up as a success.

There's no bulk-delete to claw back room, either. To make space you delete bookmarks one at a time, by hand, which is exactly the kind of unpaid chore nobody does. So the cap doesn't just stop you — it quietly turns your most recent saves into ghosts.

Why this hurts more than it should

A bookmark is a promise to your future self: *I'll come back to this.* The whole reason you save instead of read-now is that you trust the save. A silent cap breaks that trust without telling you, so you keep making promises the system has already stopped keeping.

And the people who hit the limit are precisely the people for whom it's most expensive. If you bookmark 800-plus tweets, you're not a casual scroller — you're using bookmarks as a research pile: founder threads, teardown breakdowns, "I wish this existed" complaints, revenue screenshots. That pile is the raw material for real decisions. Losing the newest saves silently means losing the freshest signal, the stuff you grabbed *because* it felt urgent.

The native tools make the squeeze worse. Folders exist but don't raise the cap, search is thin, and there's no overview of what you've collected. You can read more about that in our honest take on organizing X bookmarks and on why native bookmark search barely works.

Workarounds that don't really fix it

Before the real answer, here's the honest tour of the patches people try — and where each one falls short.

• Delete to make room. Works mechanically, fails in practice. One-at-a-time deletion with no bulk tool means you're trading the thing you wanted to keep for the thing you want to keep. You'll do it twice and quit.
• Switch to Likes as a second bucket. Likes are public, get their own limits and quirks, and turn your research pile into a feed-visible signal you may not want broadcast. A bad filing cabinet.
• Screenshot the good ones. Now you have a camera roll of un-searchable images with no link back to the source, no text you can query, and no author. You've preserved the pixels and lost the data.
• The official data archive. You can request a full account export, but it's a stale one-time snapshot built for compliance, not reading — and it doesn't *raise* the cap, it just lets you back up what's already under it. We cover its catches in the export guide.

Every one of these treats the symptom. None of them changes the fact that your bookmarks live inside a capped container you don't control.

The actual fix: get your bookmarks out of the cap

Stop storing the things you care about inside the limited box. The limit only bites because X's bookmark list is your only copy. The moment your saves also live somewhere with no cap, hitting 800 stops being a loss — it's just a number on a screen you've outgrown.

Concretely, that means syncing your bookmarks to an external store the same way you'd back up photos off a full phone. A browser extension can read your bookmarks in your logged-in session and pull every one of them into a place that doesn't impose a ceiling, keeps the text and author and link, and stays searchable. Once that's running, the native cap becomes X's problem, not yours — and even your *oldest* saves are safe from the silent drop.

This is also where the pile starts earning its keep. Out of the capped box, those saved threads can be grouped, searched properly, and mined — which is the whole premise behind treating your bookmarks as a second brain rather than a junk drawer with a lock on it.

Where IdeaCoach fits

IdeaCoach is built for exactly this problem. Its Chrome extension syncs your X bookmarks out continuously, so the 800-ish cap stops mattering: new saves land in a store with no limit, and you're no longer one silent no-op away from losing a thread. That alone solves the thing that brought you here.

The rest is what you do once they're out. IdeaCoach uses Claude to read the pile, cluster it, and turn it into ranked, buildable business ideas — each with next steps and recommended tools — plus AI chat over everything you've saved. It's free for your first 50 bookmarks; Pro is $12/mo (or $120/yr, or $149 lifetime), and the LAUNCH50 code takes 50% off Pro for three months. Pricing details are on the pricing page.

If you'd rather kick the tires before connecting anything, the free no-signup tools do it in seconds: paste one tweet into Tweet to Idea to see the idea extraction, or run a concept through the Idea Validator. No account, no card, no cap.