Most people searching "twitter bookmarks" want a real answer to one of three questions. Are these private? Is there a ceiling? How do I get them out of X if I need to?
The help center answers the first one in a sentence and then ghosts you on the other two. So here is the whole thing.
Where bookmarks live on each device
The bookmarks tab moved around a lot in the last few years, which is probably why "how to check bookmarks on twitter" is still a recurring search.
On desktop web click your profile icon in the left sidebar (or the three dots) and pick Bookmarks. Or go directly to your bookmarks list.
On iOS and Android tap your profile avatar in the top left, then Bookmarks. Same place as your Lists and your Drafts.
If you have X Premium Basic or higher (from $3 a month), you also get Bookmark Folders, which let you sort saves into named buckets. That is the only part of the bookmark product gated behind a subscription.
Are X bookmarks private
They are. X's own help page spells this out: bookmarks are private and only viewable to you within your X account. Nobody else sees the list. Not your followers, not X's recommendation feed, not the author of a tweet.
Saving a tweet on X is closer to taking a screenshot than to liking it. It leaves no trace on your profile.
(If you got here because you bookmarked something you really did not want anyone knowing about, you are fine. Sleep well.)
Can people see your bookmarks on X
No. Not the poster, not your mutuals, not anyone clicking through your profile. The author of a tweet does not get pinged when you bookmark it. There is no "who bookmarked this" reveal the way there used to be a "who retweeted this" list.
The count itself is public. The small ribbon next to likes and reposts shows how many people saved a tweet. The world knows 4,200 people bookmarked it. The world does not know you were one of them.
That mismatch is the confusion behind most "are twitter bookmarks public" and "can anyone see my bookmarks" searches, and it is why the occasional "bookmarks are now public" panic goes viral every year or two. The count is public. Your list is not. Those are different things.
Is there a Twitter bookmarks limit, really
This one gets reported wrong constantly, including on pages that currently rank. I went looking for a primary source and could not find one. X does not publish a cap in its help center, the X Premium page does not sell a "more bookmarks" upsell, and the in-session bookmarks timeline is cursor-paginated all the way down. Any tool that walks that timeline (our own Chrome extension included) reads to the end of the list. X's paid /2 bookmarks API is a separate story and tends to cap out around 800 to 1,000 per user in practice, which is a good reason full-archive tools scrape the timeline rather than hit the API.
When blogs say "Twitter bookmarks limit is 1,000" or "10,000", treat those as guesses. I have not been able to reproduce a hard cap, and the API does not behave like there is one.
What is true is that the native UX starts to creak with volume. Infinite scroll gets sluggish past a few thousand items, the built-in search only looks at tweet text (not the thread underneath, not the article a tweet links to), and there is no jump-to-date or filter. The data is there. Finding a specific old bookmark by hand is the problem.
Why your Twitter bookmarks disappeared (and what to actually do)
"Twitter bookmarks disappeared" has real search volume because this happens a lot. The causes are boring.
The tweet got deleted. By far the most common one. If the author removes the post, or their account gets suspended, the bookmark stays in your list as a broken row. Sometimes it vanishes entirely. You cannot recover it from X, because X never stored a copy of the tweet for you. It only stored a reference.
You un-bookmarked it by accident. The bookmark ribbon sits right next to the share button on mobile. Thumb taps happen.
The tweet went private. If someone flips their account to protected after you saved a tweet, and you do not follow them, your bookmark becomes unreadable.
The fix is the same for all three, and it is annoying. There is no fix inside X. The tweet is gone. The only way to survive this kind of rot is to save a copy of the content somewhere else, which is where this article is about to get a bit opinionated.
How to export your Twitter bookmarks
There are three real paths, in order of how much work they are.
1. The X data archive (official, incomplete)
X lets you download a ZIP of your account data. Settings, Your account, Download an archive of your data. It takes a few days to generate and arrives as HTML plus JSON files.
The archive includes your posts, DMs, media, Moments, Lists, followers, following, interests, and ad history. Your bookmarks are not on that list. I checked the help page for the current contents and they are not in there. This is the number one thing people expect the archive to contain, and it is missing.
The official archive will not export your bookmarks. Sorry.
2. Third-party bookmark exporters
Tools like Dewey read your bookmarks through the X API (or a scrape) and give you a CSV, PDF, or Google Sheet. Dewey has a free tier that covers manual sync and basic export, a $10 a month Pro tier with automatic sync, and a $225 lifetime option. Their export format is clean and the product is bookmark-first.
A handful of free scraper sites exist in the same niche but most are unreliable and some are gone altogether by the time you try. The X API access rules have shifted enough times that any third-party tool you find on the first page of results is worth spot-checking before you trust it with a backup.
3. An automatic bookmark sync
This is the path that actually survives a tweet getting deleted, because the content lives in a second place you control. Two tools do this well.
Readwise Reader syncs your X bookmarks into Reader after you connect your account. It stores them alongside your articles, books, and PDFs, where the workflow is highlight-centric and built around a daily review queue. Reader is where to start if you already highlight a lot of what you read and want X threads in the same pile.
Keep syncs your X bookmarks in close to real time, saves the full tweet (text, media references, thread context), and stores every save as clean markdown in a library you can search, tag, and export as Markdown, CSV, or JSON. There is no daily review queue (for now). The shape is closer to a personal web archive than a reading app.
If you are choosing between the two, Reader is stronger if you want spaced review of highlights. Keep is stronger if you want a searchable, exportable backup of the actual content. Both beat trying to babysit the native bookmarks tab past a few hundred saves.
Organizing bookmarks once you have a few hundred
Folders help. They are not enough.
X's own Bookmark Folders (Premium Basic, $3/mo) give you named buckets. You can file a bookmark into one folder, which is useful if you want to separate "articles to read" from "jokes to steal" from "threads about running a business." A flat list is worse than a folder list at any real volume.
Where folders stop being enough is search. X's bookmark search is shallow. It looks at tweet text, not at the replies underneath, not at the linked article behind a tweet, not at what a video says. Once you have more than a few hundred saves you remember "there was that thread about onboarding" without remembering which handle posted it, and folders do not help you find it faster than scrolling would.
What does help, in order of effort:
- Tag by intent, not topic. "Steal this", "read this week", "refer to later" beats "marketing", "design", "writing". Intent narrows faster than topic.
- Move the stuff you care about most into a system that searches the content, not just the tweet. A read-later app with full-text search, a note in Obsidian, a row in a spreadsheet. Whatever you will actually open.
- Prune. A hundred bookmarks you actually look at beats three thousand you never will. Same rule as a digital commonplace book.
That last one is the piece nobody wants to hear. Bookmarking is capture. Capture without a pruning habit turns into a pile.
Where Keep fits, and where it doesn't
Keep auto-imports every bookmark you save on X into your Keep library. Full-text search across the tweet text and any linked article. Tag, export, archive. The saves survive the original tweet getting deleted, because the content lives in your Keep library on R2 storage, not on X.
Keep wins if you want a searchable, exportable backup of everything you bookmark. It does not have a daily-review queue, it does not do passage-level highlighting inside a tweet, and it does not try to be where you read the rest of the web (it tries to be where you save it). If your top need is highlight-first reading with spaced review, Readwise Reader is the better call.
If your only need is "I just want my bookmarks to stop disappearing and be searchable", try Keep for the archive shape, Reader for the reading shape, or Dewey for pure export without any app to live inside.
Useful side tools
A couple of the free utilities on Keep get used a lot alongside bookmark workflows.
- X Thread Unroller for turning a long thread into a single clean reading view before you save it.
- Tweet to Image for the times you want a PNG of a tweet for a slide or a blog post.
Neither requires an account.
Plugging the hole
If your bookmarks have ever disappeared on you (and they will), the fix is upstream of X. Save a copy of the content you care about somewhere that does not get to decide whether it stays.
Keep auto-imports every X bookmark into a full-text-searchable library you can export anytime. Connect your X account once and every future bookmark lands in your library within seconds. Start saving bookmarks automatically.