Are Twitter Bookmarks Private? Who Can See Them (2026)

You bookmark a tweet about a salary negotiation, a thread on a competitor, a post you would be a little embarrassed to be caught reading. The icon turns blue and you move on. Then a small worry shows up. Did anyone just see that? Will it show on my profile next to my likes? Can the person who wrote it tell that I saved it?

It is a fair question, and it comes up more than you would think. Likes on X are public. Reposts are public. Your follower list is public. So people reasonably assume bookmarks work the same way, and that one careless save could end up on display.

The short version: they do not work the same way. Bookmarks are the most private thing you can do on X. But there are two wrinkles worth understanding, a public count that confuses people, and a privacy boundary that quietly disappears the second you try to back your bookmarks up. This guide covers both, with the facts straight from X’s own documentation.

Are Twitter (X) bookmarks private?

Yes. This is one of the few questions on X with a clean, documented answer. The X Help Center page on bookmarks says it plainly: bookmarks are private and only viewable to you within your X account.

That has been true since bookmarks launched in 2018, and it has stayed true under X’s current ownership. Bookmarks were built as a quiet, personal save feature, the opposite of a like. A like is a public signal. A bookmark is a private note to yourself.

Think of it this way. When you like a post, you are telling everyone something. When you bookmark a post, you are telling nobody anything. The save sits in your bookmarks tab, visible only to you when you open it. If you want a refresher on where that tab even lives, we mapped it out in Where Are My Bookmarks on X.

Who can see your X bookmarks? (nobody)

Let me be specific, because “private” can feel vague. Here is the full list of people who can see what you have bookmarked on X:

• You.

That is the list. Your followers cannot see your bookmarks. The accounts you follow cannot see them. The author of a post you saved cannot see that you saved it. Random users browsing your profile cannot see them, because bookmarks do not appear on your profile at all. There is no “bookmarked by” tab the way there used to be a public likes tab.

There is also no notification. When you bookmark someone’s post, they get nothing. No alert, no badge, no entry in their activity feed. Compare that to a like or a repost, where the author gets pinged and your name shows up in a clickable list. Bookmarks generate none of that. You are invisible.

This is exactly why so many people use bookmarks as a stealth save. You can bookmark a rival’s announcement, a job posting, or a post you disagree with, without leaving any trace that the author or your followers could find. That stealth is the whole point of the feature.

What the public bookmark count actually shows

Here is where the confusion creeps in, and it is the source of most “wait, are bookmarks public now?” panic.

In March 2023, Twitter added a public bookmark count to posts. PC Tech Magazine covered the rollout at the time. Now, next to the reply, repost, and like icons, you can see a number telling you how many times a post has been bookmarked. Anyone can see that number. The author can see it, and so can every reader.

That sounds like a privacy leak until you read the detail. The count is a total, not a list. X’s bookmark counts documentation spells it out: only the total number of bookmarks is shown, not the specific accounts that have added a post to their bookmarks.

So with likes, you can tap the number and see a list of names. With bookmarks, you cannot. The number might say 1,400, but there is no way to expand it into “here are the 1,400 people.” Your individual save is rolled into an anonymous tally and nothing more. The author learns that their post was saved a lot. They never learn that you were one of the savers.

The count exists for one reason: it is a strong popularity signal. A post with a high bookmark count is one people wanted to keep, which is often a better quality marker than likes. Creators watch it closely. But it tells them about their post, not about you.

The viral “X is making bookmarks public” rumor, debunked

Every so often a screenshot rips through X claiming bookmarks are about to go public. The most widespread version showed a fake post, dressed up to look like it came from X’s engineering account, announcing that “bookmarks will be public for accounts that are not subscribed to X Premium.”

It was a hoax. Soch Fact Check traced it to a parody account. The quoted announcement appears nowhere on X’s real engineering handle, and the viral post itself carried a Community Note flagging it as parody. X has never announced any plan to make bookmarks visible to followers or the public, and no such change has shipped.

The reason the hoax spreads so well is that it pokes a real nerve. People genuinely do not want their bookmarks seen, because bookmarks are honest in a way likes are not. Your likes are partly performance. Your bookmarks are what you actually came back for. A leak there would expose your real interests, not your public ones. So the fake “bookmarks are going public” post lands every time, even though it has never once been true.

If you see that claim again, you can ignore it. The documented behavior has not moved in years.

Are Reddit and LinkedIn saves private too?

If you save content on more than one platform, the good news carries over. Reddit saved posts are private to your account. LinkedIn saved posts are private to your account. On all three networks, saving is a personal action that nobody else can browse.

The pattern is consistent across the major social platforms: liking, upvoting, and reacting are public or semi-public, while saving is private. Saving is treated as a low-stakes, just-for-me action, so the platforms keep it quiet by default. We dug into how each platform handles saves, and why they all eventually lose your older ones, in Why Social Bookmarks Disappear.

Here is how privacy lines up across the places you save and the tools you might use to keep them.

When your bookmarks stop being private

Here is the wrinkle nobody warns you about. Your bookmarks are private inside X. The instant you take them out of X, that guarantee ends.

The two ways you take them out are the official data export, which we walk through in How to Export Twitter Bookmarks, and connecting a third-party bookmark tool. Both move a copy of your saves to a place X no longer controls. From that point, the privacy of your bookmarks is only as good as the privacy of wherever they landed.

A cloud-based bookmark manager stores your saves on its own servers. That is convenient, and for most people it is fine. But it does mean your private list of saved posts now lives on a company’s database, readable in principle by that company, exposed to whatever breach or subpoena that company is exposed to. You traded X’s privacy promise for theirs. Worth knowing before you connect anything.

This is the exact tension that shaped how we built ContextBolt, so read the next part with that bias in mind. ContextBolt is a Chrome extension that captures your saves from X, Reddit, and LinkedIn into a knowledge base that lives locally, on your machine, by default. Your bookmarks do not get uploaded anywhere unless you turn on cloud sync, and when you do, that sync is encrypted. The starting position is the same one X gives you: nobody sees your saves but you.

The difference is what you can then do with them privately. Because the data is yours, you can search it by meaning instead of exact words, and you can point your own AI tools at it without that list ever becoming public. We explain the search side in Semantic Search for Bookmarks. The honest scope: Basic is free for 150 saves, and Pro at $6/month lifts that to unlimited with encrypted sync and an MCP endpoint for tools like Claude. The point here is narrower than a sales pitch, though. If privacy is why you care about bookmarks in the first place, do not hand them to a tool that quietly makes them less private than X did.

The honest take on bookmark privacy

Strip it back and the situation is simple. X bookmarks are genuinely private, more private than likes, more private than your follows, and the author never knows you saved their post. The public count is a total with no names attached, and the recurring “bookmarks are going public” rumor is a hoax that has never come true.

The one thing worth actually thinking about is not whether X keeps your saves private. It does. It is what happens when you move them. The reason people move bookmarks out of X is that X is bad at keeping them. The visible list caps out and your older saves quietly vanish, which we covered in the Twitter bookmark limit guide. So the natural fix, exporting or syncing to another tool, runs straight into a privacy question most people never pause on.

If your saves are mundane, none of this matters and a cloud tool is fine. If your bookmarks are a real map of what you are working on, who you are watching, and what you are quietly learning, then treat that list the way X does: as something only you should be able to read. Pick the tool that keeps it that way.