You see a tweet worth keeping. Your thumb hovers. Like it, or bookmark it? For years the answer was easy, because likes were loud and bookmarks were quiet. Like a post and the whole world knew. Bookmark it and nobody did. That split is the entire reason bookmarks exist.
Then X changed the rules. In June 2024 it made likes private, and the old mental model broke. If likes are private now, and bookmarks were always private, what is the actual difference? Do you even need both?
You do, and the difference matters more than it looks. One is a signal you send. The other is a note you keep. They do different jobs, they hit the algorithm differently, and only one of them was ever built to be found again. Here is how they really compare in 2026, and which one to reach for.
- Likes are a signal, bookmarks are storage. A like reacts. A bookmark saves a post for you to read again.
- Likes went private in June 2024. Others cannot see what you liked, but the post’s author still can, and they get a notification.
- Bookmarks are fully private. No notification, no name, ever. The author only sees an anonymous total count.
- Bookmarks help the creator more. By readings of X’s open-sourced algorithm, a bookmark is weighted far above a like.
- Use likes to react, bookmarks to remember. And if you want to find a save later, X is the wrong place to keep it.
What is the difference between X bookmarks and likes?
A like is a reaction. You tap the heart to say “this is good” or “I agree” or “I’m here.” It pushes a notification to the author, it counts toward the post’s public like total, and it nudges the algorithm. A like is a social act. It points outward.
A bookmark is a save. You tap the ribbon to put a post somewhere you can come back to it. No reaction, no message, no notification. A bookmark is a private act. It points inward, at future you.
That is the core split, and it has not changed since bookmarks launched in 2018. Likes are for the room. Bookmarks are for you. The X Help Center describes bookmarks as a way to privately save posts to find later, viewable only inside your own account.
People still mix the two up, usually by using likes as a save button. They heart a post they want to read tonight, then lose it in a sea of other likes a week later. That is the wrong tool. A like was never built to be searched or revisited. A bookmark was. If you are liking things just to keep them, you are using the loud button for a quiet job.
Wait, aren’t likes public?
They used to be. This is the part that trips people up in 2026, so it is worth getting straight.
For most of Twitter’s history, your likes were public. Anyone could open your profile, hit the Likes tab, and scroll everything you ever hearted. That made a lot of people treat likes carefully, because a like was a small public endorsement.
That changed on June 12, 2024. X made likes private for every account. TIME covered the rollout, and X’s own engineering account spelled out exactly what shifted. The official post is still up: X Engineering announced that you can still see posts you have liked, but others cannot, and the like count on your own posts still shows in your notifications.
So here is the precise state of likes today:
- You can see everything you have liked.
- Other users cannot browse your likes. The public Likes tab is gone.
- The author of a post you like can still see that you liked it, and gets a notification.
- The like count on every post is still public.
Read that third point again, because it is the one that matters for this comparison. Likes are private from strangers, but not from the person whose post you liked. If you heart a competitor’s tweet or an ex’s post or a take you would rather not be seen agreeing with, that person can still see your name. A bookmark never does that.
Privacy: who can see each one
This is where bookmarks pull clearly ahead. Liking is now semi-private. Bookmarking is fully private.
When you bookmark a post, the author is not notified. There is no badge, no alert, no clickable list of who saved it. The only public signal is a total bookmark count, added back in March 2023, and that number never names anyone. X’s bookmark counts documentation is explicit that only the total is shown, not the accounts behind it. We went deep on this in Are Twitter Bookmarks Private, and the short version is that nobody, including the author, can ever see that you personally bookmarked their post.
Here is how the two stack up side by side.
| What you do | Can strangers see it? | Can the author see it’s you? | Author notified? | Public count? |
|---|---|---|---|---|
| Like a post | No (since June 2024) | Yes | Yes | Yes |
| Bookmark a post | No | No | No | Total only, no names |
If privacy is your reason for choosing, bookmarks win without a contest. A like is a name the author can read. A bookmark is invisible to everyone but you.
Which one helps the creator more?
Most people assume a like is the best way to support a post. It is not even close.
X open-sourced its ranking algorithm, and updated, transformer-based versions landed in early 2026. By widely cited readings of that code, the engagement signals are not weighted equally. A repost counts for roughly twenty times a like. A reply counts for about thirteen times. And a bookmark counts for around ten times the weight of a like. Sprout Social’s breakdown of the algorithm lays out the same picture: saves and shares signal lasting value, and the system rewards them far more than a passing heart.
The logic is simple once you say it out loud. A like is cheap. People tap it reflexively. A bookmark means someone wanted to keep your post and come back to it, which is a much stronger vote that the content was worth something. So the algorithm treats it that way.
This flips the usual advice. If you genuinely want to help a creator you follow, bookmarking their post does more for their reach than liking it. And if you are the creator, a high bookmark count is a better health check on your content than likes are. Likes tell you a post was pleasant. Bookmarks tell you it was useful.
So the honest answer to “which is better for the author” is bookmarks, by a wide margin. The honest answer to “which feels like support” is still likes, because that is the cultural habit. Both can be true. Just know that the quiet button is doing more work.
So which should you use?
Strip away the privacy details and the algorithm math, and it comes down to your intent in the moment.
Like a post when you want to react. You agree, you enjoyed it, you want to give the author a small nod. Likes are social glue. They are also fine for posts you will never need again, which is most of them.
Bookmark a post when you actually want it later. A thread you will reference, a tool you want to try, a competitor’s post you are studying, a recipe, a deal, a job listing. Anything where future you needs to find this again. That is the whole job bookmarks were built for.
Do both when a post is genuinely great. The like supports the author and feeds the algorithm. The bookmark keeps a copy for you. There is no rule against using both, and for your best finds you probably should.
The one habit to break is using likes as a filing system. Likes are not searchable in any useful way, they pile up by the thousand, and they were never designed to be revisited. If you are hearting posts to save them, switch to the ribbon. Your future self will thank you.
The catch nobody mentions
Here is the problem with this whole debate. Bookmarks are the right tool for saving, but X is a bad place to keep the things you save.
X only shows your most recent saves in the bookmarks tab, and older ones quietly fall off the bottom over time, which we broke down in the Twitter bookmark limit guide. There is no real search. Folders exist, but only if you pay for Premium, and even then you are sorting by hand. And if the original author deletes their post, your bookmark of it goes too. You can save something perfectly and still never see it again. We wrote about why this happens across every platform in Why Social Bookmarks Disappear.
So you make the smart choice, you bookmark instead of like, and you still end up with a write-only pile you cannot dig through. The tool is right. The storage is broken.
That gap is why I built ContextBolt. It is a Chrome extension that captures your X bookmarks (plus your Reddit and LinkedIn saves) into a knowledge base that lives on your machine. It auto-tags each save by topic, so your bookmarks organize themselves, and it lets you search by meaning instead of exact words. You can find a saved tweet by describing it, not by guessing the one keyword it happened to contain. That side is covered in Semantic Search for Bookmarks. Basic is free for 150 saves. Pro at $6/month lifts that to unlimited, adds encrypted cloud sync, and gives you an MCP endpoint so tools like Claude can read your bookmarks directly. The point is narrow. Bookmark, don’t like, but then keep your bookmarks somewhere you can actually use them.
The honest take
X bookmarks versus likes is not really a fight. They do different jobs. A like is a reaction, now hidden from strangers but still visible to the author and still notifying them. A bookmark is a private, anonymous save that the author never learns about and the algorithm rewards more.
If you want to react, like it. If you want to keep it, bookmark it. If a post is both worth supporting and worth keeping, do both. The only genuine mistake is using likes as storage, because that is the one thing likes were never built to do.
And once you start bookmarking properly, you run into the real problem, which is that a pile of saves you cannot search is barely better than no saves at all. Pick the save button for the right reasons. Then keep those saves somewhere they stay findable.