How to Delete or Hide Your X (Twitter) Likes History in 2026
Quick Summary
Explains how to view, manage, and bulk-remove X likes after the 2024 privacy change, including API limits and visibility boundaries.
Your first step: know the actual count
Stop guessing how many posts need cleanup. Get a real number from X API.
You can review the estimate before deciding to proceed.
Free count check. Pay only if you choose to proceed.
But "private" does not mean "invisible" — post authors can still see who liked their posts, and your like history remains accessible through the X API.
When you start worrying about your past X (Twitter) likes, the first thing to verify is who can see what. In June 2024, X made likes private for all users. But this change restricted visibility — it did not delete your like history. You can still see your own likes, and the X API allows you to remove them programmatically.
This article covers the practical steps for managing your X likes history, including visibility rules, deletion methods, rate limits, and what third parties can still access.
What Changed: Likes Became Private for All Users in June 2024
On June 13, 2024, X announced through its official account that likes would become private for all users.
"This week, we're making Likes private for all users."
Source: X Official Account (via Jiji Press) https://www.jiji.com/jc/v8?id=202406likes-team (Verified: 2026-06-19)
Three things changed with this update:
- Other users' "Likes" tabs disappeared from profiles — no one's like history is publicly browsable
- X Premium subscribers cannot revert to public — the previous toggle was discontinued
- Post authors can still see who liked their posts — visibility is restricted, not eliminated
"Private likes" means "invisible to other users' profiles, but visible to the post author." Understanding this boundary is critical for making informed decisions about your like history.
How to View Your Own Likes in 2026
After the privacy change, the method for viewing your own likes varies by device.
Mobile App (iOS/Android)
In the May 2026 update, the mobile app moved the "Likes" tab from the profile screen to the "History" menu.
- Tap your profile icon in the top-left corner
- Tap "History" from the side menu
- Select the "Likes" tab
Browser (x.com)
The browser version still shows the "Likes" tab on your profile page. The difference between app and browser is due to X's phased A/B testing of the UI change. The same account may display differently on the app vs. browser — this is not a bug, it reflects X's gradual UI rollout.
How to Remove (Unlike) Your Likes
"Deleting your like history" actually means "unliking posts." X does not have a feature to delete like history while preserving the like relationship — unliking removes your like from the post entirely.
Manual Method
- Open your profile on the X app or browser
- Go to the "Likes" tab (or "History" → "Likes")
- Tap the heart icon on the post you want to unlike
- The red color disappears when the unlike is complete
This takes effect immediately. However, if a like notification was already delivered to the post author, it cannot be recalled. Unliking quickly (within seconds) may prevent the notification from appearing, but this depends on timing.
Via X API
The X API's Unlike Post endpoint allows programmatic unliking.
"Causes the authenticated user to Unlike a specific Post by its ID."
Source: X API Unlike Post https://docs.x.com/x-api/posts/unlike-post (Verified: 2026-06-19)
This endpoint requires OAuth 2.0 authentication with the like.write scope. Tools that require your password cannot obtain this scope, so using official API-based tools is a prerequisite.
Bulk Unlike via X API: Mechanism and Limits
X API does not provide a "bulk unlike all" endpoint. Unliking is done per Post ID, so removing many likes requires one API call per like.
Key constraints:
- Endpoint: DELETE /2/users/{id}/likes/{tweet_id}
- Authentication: OAuth 2.0 User Token (like.write, tweet.read, users.read)
- Per-item processing: No batch unlike API exists
Additionally, you need to first retrieve your liked posts using the GET /2/users/{id}/liked_tweets endpoint, which also has pagination limits. For 1,000 likes, you need at least "retrieval requests + 1,000 unlike requests." This design means bulk unlike operations are inherently time-consuming.
Rate Limits and Account Safety
X API enforces rate limits per operation type.
"You can manage 50 Posts per 15-minute window for posting, deleting, and other POST operations."
Source: X API Manage Tweets Rate Limits https://docs.x.com/x-api/posts/manage-tweets/limits (Verified: 2026-06-19)
Unliking counts as a POST operation, subject to the 50-per-15-minute limit. Removing 1,000 likes requires at least ~5 hours including wait time. This limit applies equally to manual tools and automated scripts. Tools claiming "fast like deletion" do not bypass the limit — they simply automate the waiting.
Regarding account safety: using the official API with OAuth 2.0 authentication does not risk account suspension for unliking. However, unofficial scraping tools or password-sharing services carry suspension risk. See theaccount suspension risk articlefor details.
What Third Parties Can and Cannot See
As of 2026, here is what is and isn't visible regarding X likes:
Visible
- Like counts on each post — total counts remain public
- Post authors — can see who liked their specific posts
- X's internal systems — used for ad optimization and recommendations
Not Visible
- Others' "Likes" tabs — hidden for all users since June 2024
- Your "Likes" tab (from others' views) — inaccessible to anyone but you
- Liker lists — tapping like counts no longer shows who liked
X's privacy policy also notes that interaction data including likes may be shared with partners:
"Your interactions with other users' content, such as reposts, likes, bookmarks, shares, downloads, replies, if other users mention or tag you in content or if you mention or tag them..."
Source: X Privacy Policy https://cdn.cms-twdigitalassets.com/content/dam/legal-twitter/site-assets/privacy-policy-2024-11-15/en/x-privacy-policy-2024-11-15.pdf (Verified: 2026-06-19)
Even though likes are private on the platform, the data pathway to external partners is not fully closed. "Private" does not mean "nonexistent."
Deciding Your Like History Management Strategy
Whether to delete all likes or leave them private depends on your goals.
Consider deleting when:
- Preparing for job hunting or career changes
- Past likes include potentially controversial posts
- Cleaning up before account migration or deactivation
Leaving private is reasonable when:
- Third-party visibility is already restricted
- You use your like history as a personal reference
- You want to avoid notification side effects
If deleting, export your data archive first. Reviewing your X data archive before choosing a deletion scope prevents accidental removal.
Also note: deleting posts and unliking posts are separate operations. Deleting a post does not automatically manage your like history. For post deletion procedures, see theX post bulk deletion guide.
Plan by Volume for Effective Cleanup
Under 100 likes can be managed manually. At 500 or 1,000 likes, manual cleanup becomes impractical with missed items and lost progress.
Tools like X Deleter handle rate limit waiting, resume from interruptions, and maintain deletion logs. Start by checking your unlike count, then choose a method that matches the volume. Time estimates are available in thetime estimate article.
Like history management does not end with "it's private now." It begins with designing your deletion scope based on your actual goals.
Frequently Asked Questions
What should I check before starting x likes delete?
Confirm expected volume, target range, and whether waiting states are normal. That prevents false alarms and makes completion more predictable.
If deletion pauses midway, is the tool broken?
Not necessarily. High-volume deletion often pauses because of platform limits, not because the workflow failed.
Related Articles
These articles target closely related search intent and next-step questions.
X 投稿 一括削除 2026|過去ポストを安全に全消しする実務手順
Xリブランド後の「ポスト」削除に対応した実務手順。API仕様ベースで安全設計から完了確認までを整理。
ツイート削除に時間がかかる理由|件数別の所要時間目安と短縮方法
レート制限から逆算した所要時間の計算表。件数別目安・時間短縮テクニック・中断時のリスクを解説。
Will Twitter "Tweet Deleter" Tools Get You Suspended? How to Choose a Safe Bulk Deletion App
A risk-control article for users comparing unofficial deletion tools against official API-based approaches.
