View liked tweets on X: every route to your own like history

Your likes are public by default, and the route you use to view them decides how far back you can actually see.

What this covers.The three routes to your liked tweets, and where each one stops.Why the Likes tab cannot show you a like history of any real depth.How to review and clear likes once you can see the whole set.

Circleboom reads your X archive to surface and remove liked posts across your full account history through official X Enterprise APIs. Start with your X like history.

Most people asking how to view liked tweets on X are not idly curious. They are checking what a stranger can see, which is a different question with a different answer.

The three routes, and where each stops

Your Likes tab is the obvious one. Open your profile, open Likes, scroll. It shows your own likes in reverse order and it is the fastest way to check the most recent ones.

Its limit is depth. The tab paginates, and the further back you scroll the slower and less reliable loading becomes. On an account with years of activity, reaching the oldest likes by scrolling is a project rather than a task, and there is no jump-to-date control to shortcut it.

The API window covers roughly your most recent 3,200 likes. Any tool working through the standard route sees that slice and nothing behind it.

Your X archive is the only complete record. X generates it on request and delivers it in about 24 to 48 hours, and it contains the full like history regardless of age or volume, in a file called like.js.

So the honest answer to "can I view all my liked tweets" depends entirely on what you mean by all. Recent, yes, easily. Everything, only through the archive.

The Likes tab shows you the top of the pile. The archive is the pile.

For the adjacent question of who is liking your posts rather than what you liked, how can I see who liked my tweets covers the other direction.

Why people check their like history

The reason matters, because it changes which route is sufficient.

Privacy checks. Likes are visible to anyone unless your account is protected. Years of them accumulate into a fairly detailed picture of interests, politics, humor, and associations, assembled across phases of life that may have nothing to do with each other.

Before a public moment. A job search, a media appearance, a funding round. Anyone doing diligence on a person checks the Likes tab, because it is unguarded in a way the timeline is not. People curate what they post and forget entirely what they liked.

Accidental engagement. Misclicks happen, and a like on a mobile double-tap is easy to miss. So is a like from six years ago on something that has aged badly.

Research trails. Anyone using likes as bookmarks has built a public record of what they were investigating, which is occasionally more revealing than they intended.

The first two need the archive, because the material that concerns you is old. The second two are usually recent enough for the Likes tab.

If the check turns into a cleanup, the archive route is also what lets you clear your X likes in bulk rather than tapping the heart icon several thousand times. Viewing and removing run off the same file.

Some people reach for a script instead, which works until X changes something. Script to delete Twitter X likes is worth reading for why that approach tends to break mid-run.

Worth knowing: X's guidance on liking posts confirms the visibility model, and it is the thing most people have simply never read.

What the archive shows that the tab does not

Opening like.js is a different experience from scrolling the tab, and the difference is not only depth.

The tab renders likes as a feed. You see them one at a time, in order, with no sense of scale and no way to ask a question about the set. The archive is a record, which means you can count it, sort it, and filter it.

That reframes the whole exercise. "Do I have anything embarrassing in my likes" is unanswerable by scrolling and straightforward against a filterable set. So is "how many likes do I actually have," which is a number most people guess wrong by an order of magnitude.

Circleboom processes that file and turns it into something you can act on, with the same filter model used for tweets: date ranges, keywords, and a protect list for anything you want to keep.

The ranking angle is useful too. If the question is which posts drew the most engagement rather than which you liked, how to sort tweets by likes covers that sorting problem.

How to view liked tweets on X and clear them

To view your complete liked tweets on X, request your archive, upload the like.js file to Circleboom, and review the full set before filtering. The archive is what makes likes older than the recent window visible at all, and the filters are what let you act on part of the history rather than all of it.

Six actions, with the review before the removal.

See the full set first

1. Log in to Circleboom Twitter and connect the X account whose likes you are reviewing.

2. Request your X archive from account settings and wait for the download link. This is also your permanent copy, since removal is not reversible.

3. Upload the like.js file from the archive folder. It is the likes equivalent of tweet.js, and it has to come from the account on your subscription.

Review, then decide what goes

4. Read the total the upload reports. That number is usually the first surprise, and it is the denominator for everything you decide afterwards.
5. Filter by date or keyword to isolate a period or a subject rather than treating the history as one undifferentiated block.
6. Protect anything worth keeping, then confirm against the count shown before the removal runs.

That sequence matters because viewing and deleting are genuinely separate decisions, and the interface makes it easy to collapse them into one. Seeing the total first, before any filter, is what stops a privacy check from turning into a reflexive wipe you have not thought about.

One useful behavior: the same file can be re-uploaded later for another pass, and anything already removed is skipped. A cautious review across several sessions costs nothing.

Watch the review flow: how a full like history becomes a filterable, countable set instead of an endless scroll.

→ review your liked posts on X

Viewing is not the same as auditing

There is a gap between looking at your likes and actually knowing what is in them, and scrolling never closes it.

Reading a feed is sequential and unbounded. You have no idea what proportion you have seen, no way to mark where you stopped, and a strong tendency to lose interest around the point where the interesting material starts. The likes that worry people are rarely in the first two hundred.

An audit works differently. It asks specific questions of a known set:

• How many likes exist in total?
• Which periods hold the most?
• Does anything match terms I would rather not be associated with?

Those are answerable in minutes against a file and effectively unanswerable by scrolling. The keyword question in particular is one no amount of browsing substitutes for, since you cannot reliably spot a term you are not actively searching for.

The mobile route has its own constraints, and delete Twitter likes on iPhone covers what changes when the phone is where you are working.

Export the record before you clear it

If your likes have been doing a job, removing them removes the job too, and that is worth thinking about for a minute before the count screen.

Plenty of people use likes as bookmarks. It predates the actual bookmark feature and the habit stuck, which means a like history is frequently a reading list, a research trail, or a pile of references somebody intended to come back to. Clearing it for privacy reasons destroys that at the same time.

The archive already solves this, as long as you keep it. The downloaded file is a permanent local copy of every liked post, so the material survives even after the public association is gone. What it does not do is stay convenient, since a raw file is not a browsable list.

Exporting into a structured format is the better middle path when the content genuinely matters to you. Circleboom's Export Tweets route produces a file you can search and sort, which turns a like history into something you can actually reuse rather than just retain.

Decide which likes were load-bearing

Before running anything, separate the history into three rough groups:

• Likes that were genuinely bookmarks, holding something you meant to return to.
• Likes that were social, acknowledging a person rather than saving a thing.
• Likes that were reflexive, and which you would not miss.

The middle group is the largest on almost every account and the one nobody needs to preserve. The first group is small, and it is the only part where losing the record would actually cost you something.

Once you have made that distinction, the deletion stops feeling risky. You are not clearing a memory, you are clearing a public signal while keeping the handful of things that had value, which is a much easier decision to make quickly.

Keep the archive, export what mattered, then clear the signal.

What likes reveal that posts do not

Circleboom is an official X Enterprise Developer company, which is why the archive route runs through authorized access rather than automation against your browser session. Worth saying plainly, because a like history is among the more sensitive things on an account.

The sensitivity comes from a simple asymmetry. People compose posts knowing they are public and like things as a reflex, so the like history is a less edited record than the timeline. It reflects attention rather than intention.

That is also what makes it interesting to anyone evaluating you, and why it deserves a periodic look even when nothing specific prompted one.

A few caveats on what removal does and does not achieve:

• Removing a like does not delete the post you liked.
• It does not notify the author, and it does not undo whatever the like contributed at the time.
• It removes your public association with it, which is the actual goal.

Removal is permanent. There is no recovery path, and if the likes were functioning as bookmarks, export the record before clearing anything.

There is a broader question underneath this one. What type of content do people most like on Twitter approaches it from the content side rather than the privacy side.

Check the whole record, not the top of it

Viewing liked tweets on X is easy for the recent ones and only possible through the archive for everything else. Use the Likes tab for a quick look, and request the archive whenever the question is about what a stranger could find rather than what you remember doing.

See the total first, filter second, and keep the archive regardless of whether you remove anything.

→ open your X like history

Questions about viewing likes on X

Can other people see my liked tweets?

Yes, unless your account is protected. The Likes tab on your profile is public and visible to anyone who opens it.

How far back does the Likes tab go?

In principle all the way, in practice not far. Loading degrades as you scroll and there is no jump-to-date control, so deep history needs the archive.

What file holds my likes in the X archive?

like.js, which sits alongside tweet.js in the downloaded archive folder and holds the complete like record.

Does removing a like notify the person who posted?

No. The post stays up, the author is not notified, and only your public association with it is removed.

Can I remove some likes and keep others?

Yes. Filter by date or keyword to define the set, and use the Protect List for anything that should survive the run.