TL;DR. Bookmarks on Twitter/X are private. Nobody can see what you saved, browse your bookmark list, or get a notification when you bookmark their post. The only public piece is the total bookmark count on each post, which shows how many people saved it, never who.
Are Twitter bookmarks public? No. Every bookmark you save on Twitter/X is private to your account: there's no public bookmark feed, no bookmarks section on your profile, and no way for another user to browse what you've saved. The one genuinely public number is the bookmark count on a post, and that count is anonymous. This explainer walks through exactly what's visible, what isn't, where the recurring "bookmarks are going public" rumors come from, and the single real exception worth knowing about.
Can people see your bookmarks on X?
No. Bookmarks are private on X by default (most people still call them Twitter bookmarks, years after the July rebrand), and there is no setting that makes them public. Your bookmark list lives behind your login, visible only when you're signed in to your own account. Other users can't visit it, search it, or stumble onto it.
This surprises people because almost everything else on the platform is visible to someone. Your follows are public. Your replies are public. Your reposts are public. Bookmarks are the exception: a private shelf inside a very public building. When you tap the bookmark icon on a post, the save is recorded to your account and nowhere anyone else can look.
The reverse is also true. Just as nobody can browse your bookmarks, you can't browse anyone else's. There's no trick, no viewer tool, no profile tab you're missing. If you've ever wanted to peek at what a favorite account has been saving, the honest answer is that the feature simply doesn't exist, for you or for anyone.
The privacy extends to Bookmark Folders, the organization feature X offers Premium subscribers. Folders are private too: the names, the contents, and the fact that they exist at all are invisible to everyone but you. Paying for Premium changes how you can organize your saves, not who can see them.
One caveat worth stating plainly: private means private within X's current design, not encrypted or legally shielded. Your saves live on X's servers like everything else you do there, and platforms can change their rules. For everyday purposes, though, the answer to "can people see your bookmarks on Twitter" is the same flat no it has been since the feature launched. And if your list has quietly grown past the point of usefulness while nobody was watching, that's a different problem, and we wrote a complete guide for it: how to manage Twitter/X bookmarks.
The one thing that is public: the bookmark count
Everyone can see how many times a post has been bookmarked. Nobody can see who did the bookmarking. That's the entire nuance of Twitter/X bookmark privacy in two sentences, and it's the detail that trips up most people who search for this question.
X made the bookmark count a public metric in , displaying it alongside replies, reposts, and likes on a post's detail view. Open any reasonably popular post and you'll see something like "1,204 bookmarks" in the stats row. That number is visible to the author and to every other user on the platform.
The public count also changed how people read posts. A thread with 40 replies and 4,000 bookmarks tells you something a like count never could: people didn't just enjoy it, they filed it away for later. Plenty of readers now scan the bookmark count as a quality filter, the way you might judge a cookbook by how splattered its pages are. None of that shifts the privacy picture. The jar gets more famous; the marbles stay unlabeled.
The count is an aggregate, and it's fully anonymous. Think of it like a jar of marbles outside a shop: anyone walking past can count the marbles, but there's no label saying who dropped each one in. Your individual save contributes one anonymous unit to a public total, and that is the entire trace it leaves.
It's worth noticing what this means in both directions. If you bookmark someone's post, they'll see their count tick up, but they can't connect that movement to you. And if your own post racks up bookmarks, you get a satisfying number and zero information about the people behind it. Many writers on the platform treat a high bookmark count as the strongest compliment a post can receive, precisely because it's the signal people send when they think nobody is watching. A like is a public gesture. A bookmark is a private decision that the post was worth keeping.
Can you see who bookmarked your tweet?
No, and this applies to everyone: regular accounts, Premium subscribers, and the post's author alike. X shows you how many bookmarks your post received, both in the public stats and in your post analytics, but the identity of each bookmarker is not exposed anywhere, to anyone, at any subscription tier.
People search "how to see who bookmarked your tweet" in surprising numbers, so let me be direct about the landscape. There is no official method. There is no hidden setting. And as of this writing, no legitimate third-party tool can produce that list either, because X doesn't make the information available outside its own systems. Any app or viral thread promising to reveal your bookmarkers is guessing, showing you likes instead, or fishing for your login credentials. Treat those the way you'd treat a "see who viewed your profile" offer, because it's the same genre of scam.
If you're on the other side of the question, worried that an author could somehow find out you bookmarked something awkward: they can't. Your save is one anonymous marble in the jar, and there's no way to fish it back out with your name on it.
Does Twitter notify someone when you bookmark their post?
No. Bookmarking sends no notification of any kind. The author doesn't get an alert, an email, or a subtle hint. Their bookmark count goes up by one, silently, and that's the complete footprint of your save.
Don't expect this to be "fixed" someday, either. Bookmarks have been a private, notification-free save since the feature first shipped, and that's the entire point of them: saving something for yourself is nobody else's business. As of this writing, that design hasn't budged.
This makes bookmarks structurally different from every other common action on the platform. Likes notify the author and are attached to your account. Replies are public by definition. Reposts broadcast to your entire follower list. Follows ping the person you followed. Bookmarks alone are silent, which is why the bookmark has become the platform's discretion tool: the save you make when you don't want to start a conversation about it.
In practice, this silence is the feature's superpower. You can save a competitor's pricing thread, an ex-colleague's announcement, or a health thread you'd rather not broadcast, and there's no social residue at all. The author sees a number. You keep your privacy. Everyone moves on.
Is Twitter making bookmarks public?
Not as far as anyone can tell. Every few months a rumor wave rolls through the platform claiming that X is about to make bookmarks public, and as of this writing, none of those waves have come true. Bookmarks remain private by default, and X has announced no change to how bookmark privacy works.
The rumors do have an understandable origin. In June , X removed the public Likes tab, hiding everyone's likes from other users. That was a real, significant change to the visibility rules of a core feature, and it landed with little warning. The lesson people took from it wasn't about the direction of the change (likes actually became more private, not less). The lesson was that visibility rules on X can change at all. From there, "what if bookmarks go public next" practically writes itself as a viral post, because it taps a real anxiety: millions of people have years of unfiltered saves sitting in that tab.
So how should you treat the rumor cycle? With calm, and a small dose of realism. Nothing currently suggests bookmarks are going public, and flipping years of private saves to public retroactively would be a radical move by any standard. At the same time, the honest posture on any platform is that features evolve, and the only saves you fully control are the ones you've processed or backed up. If the thought of your bookmark list becoming visible makes your stomach drop, that's probably a sign the list needs attention regardless of what X does. For the clean-slate option, we wrote a walkthrough: how to delete all your Twitter bookmarks.
The exception: tools that publish bookmarks on purpose
There is one real way a Twitter/X bookmark list ends up on the open web, and it isn't X. A handful of third-party bookmark managers, Dewey being the best-known example, let users publish selected bookmark folders at a shareable public URL. Curators use this to turn months of saves into a public resource page: "my favorite design threads," that sort of thing.
The key word is deliberately. Publishing through one of these tools requires you to sign up for the service, connect your X account, pick a specific folder, and explicitly turn on sharing. Nothing about it is passive, and nothing about it happens on X itself. Your bookmarks don't leak; they get exported and published by you, through a separate product, on purpose.
It's still worth knowing this exists, for two reasons. First, if you ever run into someone's "bookmarks" on the open web, this is how they got there, not through some hidden X setting the rest of us forgot to switch off. Second, whenever you connect any outside tool to your bookmarks, you're extending your trust from X to that tool. Good services are upfront about what they read and what stays private, and that's a fair question to ask of any of them, ours included.
Why private bookmarks quietly pile up
Bookmark privacy has a side effect nobody warns you about: because no one can see your saves, nothing and no one ever resurfaces them. There's no social pressure to revisit them, no friend asking "did you ever read that thread you saved?", no feed that puts your own shelf back in front of you. The pile grows in perfect silence.
Compare that to the public parts of your account. Your replies pull you back into old conversations. Your reposts earn reactions. Your follows shape what you see tomorrow. Bookmarks generate nothing. They're the only thing you do on the platform with zero external feedback loop, and the psychology of why that guarantees a backlog is a whole article of its own: why Twitter bookmarks pile up.
This is the exact problem we built Bulkmark around. I had well over a thousand saves that nobody, including me, ever looked at, and the privacy that made bookmarking feel safe was the same privacy keeping the pile invisible. Bulkmark syncs your Twitter/X bookmarks in the background and sends you a weekly email with each save summarized, so your private shelf finally gets a feedback loop without becoming any less private. Your bookmarks stay yours; they just stop being invisible to you too. If the format is new to you, the full explainer is at what is a Twitter bookmark digest.
Bottom line
Bookmarks are the most private mainstream feature on Twitter/X. Nobody can see your list, nobody can see that you saved their post, and nobody gets notified when you tap the ribbon icon. The only public trace is an anonymous count on the post itself, and the only way your saves ever reach the open web is if you deliberately publish them through an outside tool.
The quiet irony is that the feature's privacy is also its trap. A list nobody can see is a list nobody reminds you about, and that's how a few thousand thoughtful saves turn into a graveyard. So save freely; the privacy is real, and as of this writing there's no credible sign of that changing. Just make sure something, whether a weekly ritual or a digest landing in your inbox, puts those saves back in front of the one person who was ever allowed to see them.