Straightforward interface and useful features. I appreciate having these tools available directly in Chrome.
Postwash is a bulk tweet deleter that works from the browser you already use. It reads your X (Twitter) account, shows you everything it found, saves a backup, deletes only what you approve, and checks every single deletion with X — without ever asking for your password.
Straightforward interface and useful features. I appreciate having these tools available directly in Chrome.
A practical extension with features that make managing X activity easier.
I like having options to filter the content I want to manage. It makes the cleanup process more organized.
A useful tool for anyone who wants to organize their old X account activity.
Managing old posts manually takes a lot of time. Having tools to handle multiple posts is really convenient.
I wanted to clean up some of my old likes, and this extension made the process much easier.
The interface is simple and easy to understand. It makes managing old posts much less complicated.
I was looking for an easier way to clean up my old X posts. The bulk deletion feature is exactly what I needed.
There is no “delete all” button anywhere on X. Clearing an account means opening each post, tapping the menu, confirming, and starting over. Likes and bookmarks have no bulk option at all, and X lists only the latest 3,000 or so posts of a profile, so older ones are hard to even find.
Hundreds or thousands of posts means days of clicking, and nothing tells you whether a deletion really went through.
You always know what is about to go, and afterwards you get the real numbers: deleted, already gone, failed.
Nothing is deleted until you confirm, and you decide the pace.
Posts, replies, reposts, likes and bookmarks. Delete tweets in bulk, remove your reposts, clear Twitter likes and empty your saved posts from one dashboard.
Select by date (older than 30 days, 90 days, 6 months or 1 year, or your own range), by words, by likes or views, and by media. Your pinned post stays untouched.
A CSV or JSON file with the text and details of everything about to go is saved to your Downloads folder before the first deletion. If it cannot be saved, nothing is deleted.
X can say “success” when something went wrong. Postwash asks X again after each deletion and counts it only when the post is really gone, and keeps an activity log you can export as CSV.
Import your X data archive (tweets.js and like.js) and delete by ID without relying on the list X shows. The files are read on your computer and never uploaded.
Set a daily or weekly cleanup, for example posts older than 30 days every week. Every scheduled run saves a backup first and is written to the log.
Pick a gentle, balanced or fast pace with random pauses. Postwash watches X’s own rate-limit counter, slows down before it runs out and stops by itself if X pushes back.
Postwash works through the X session already open in your browser. Your posts are read on your device and are never sent to a server of ours.
The same flow whether you are clearing fifty posts or several thousand.
Log in to x.com, click the Postwash icon in Chrome and sign in with your Google account. Postwash never asks for your X password.
Pick posts, replies, reposts, likes or bookmarks, add filters if you like, and press Scan. Postwash reads your list in small steps. Nothing is deleted at this stage.
Every item is shown with its date, its text and its engagement. Untick what you want to keep, or protect it so it is never deleted, whatever the filters say.
Postwash saves a backup file first, then deletes at a gentle pace and checks every result with X. Pause, resume or stop at any moment.
X has no “delete all” button, so by hand you open every post, tap the menu and confirm, one at a time. Postwash is a tweet deleter that reads your list in the browser, shows you everything it found, and deletes only the items you approve. You confirm once and it works through the list at a gentle pace.
Yes. Use the date filter to select posts older than 30 days, 90 days, 6 months or 1 year, or set a date range of your own. Postwash also keeps your pinned post and lets you protect individual posts that are never deleted, whatever the filters say.
Yes. Postwash cleans five lists: posts, replies, reposts, likes and bookmarks. Removing a repost only removes your repost, and unliking a post leaves the post itself on X. Likes and bookmarks have no bulk option on X at all.
Yes. X is Twitter under its new name: it is the same account, with the same tweets, replies, reposts and likes. Postwash works on the account you are logged in to on x.com, so it deletes your Twitter posts exactly like it deletes posts on X.
X can answer “success” even when something went wrong, and deleting the same post twice looks identical. After each deletion Postwash asks X again and counts the post only when it is really gone. The result is sorted into deleted (verified), already gone and failed, with the reason for each failure.
No. It never asks for your X password. It works through the X session already open in your browser, and your posts are read on your device and never sent to a server of ours. Signing in with Google only shares your name, email address and profile photo.
X lists only around the latest 3,000 posts of a profile and limits how fast lists can be read. If your account is older than that, import your X data archive into Postwash (tweets.js and like.js). It then deletes by ID and skips the listing completely. The files are read on your computer and never uploaded.
Postwash waits a random time between deletions, follows X’s own rate-limit counters and slows down before they run out. If X pushes back, for example with a daily limit or an automation warning, the cleanup stops by itself and tells you why. Nothing can promise an account is never flagged, so start with a small batch and raise the pace only if you want to.
No. A deleted post cannot be restored to X. That is why Postwash saves a backup file (CSV or JSON) with the text and details of everything about to be deleted before it removes anything, and why nothing is deleted until you confirm.
Yes. Set a daily or weekly cleanup, for example posts older than 30 days every week. It runs while Chrome is open, saves a backup first, and writes every run to the activity log.
No. Postwash is an independent extension. It is not affiliated with, endorsed by, or connected to X Corp. “X”, “Twitter” and “Tweet” are trademarks of their respective owners and appear here only to describe what the extension works with.
Install the extension, open X, and let Postwash do the repeating while you stay in charge.
Add Postwash to ChromePosting on X (formerly Twitter) takes seconds; undoing it takes much longer. Anyone who has tweeted for a few years ends up with thousands of old posts, replies, reposts and likes they would rather not have on their profile — a job change, a rebrand, a bad take from long ago. Searching for how to delete all tweets turns up the same answer everywhere: do it one by one, because that is the only thing X itself offers.
X treats every post as an individual item, so its menu only ever acts on one at a time. Likes and bookmarks are worse: there is no bulk option for them at all. On top of that, X shows only around the latest 3,000 posts of a profile and limits how fast a list can be read, so even finding your oldest tweets is a task of its own.
The risky part of any bulk tool is that it acts faster than you can check. A tweet deleter worth installing should show you the full list before anything is removed, let you take items off that list, and save a copy of what it is about to delete. It should move at a pace you chose, stop when X pushes back, and — above all — tell you the truth afterwards. X can answer “success” when a deletion failed, so Postwash asks X again after every deletion and only counts a post once it is really gone.
Most people do not want an empty profile; they want the old posts gone. Postwash filters by date (older than 30 days, 90 days, 6 months, 1 year, or a range of your own), by words you want to catch or never touch, by a maximum number of likes or views so your popular posts survive, and by media. Your pinned post is kept, and you can build a protected list of posts that are never deleted, whatever the filters say. If you want a clean-up that never ends, schedule it: a weekly run for posts older than 30 days keeps the account tidy without any effort.
Deleting your own posts is only part of a cleanup. Removing a repost takes away only your repost; the original stays with its author. Unliking in bulk leaves the posts themselves on X. Emptying bookmarks clears your saved list in one run. Postwash treats all five lists the same way: scan, preview, back up, confirm, verify.
If your account is older than what X will list, request your data archive from X, then drop tweets.js and like.js into Postwash. It deletes by post ID and skips the listing completely. The files are read on your computer and never uploaded.
Your posts do not. Postwash never asks for your X password and has no way to receive it; it works through the session you already have open in the browser, the same way the X website does. Your history, the backup files and the activity log stay on your device. Signing in with Google shares only your name, email address and profile photo. If you also manage who you follow, see X Unfollow AI, and for exporting tweets, followers and bookmarks before you delete them, see Roostbox.
Postwash is an independent extension. It is not affiliated with, endorsed by, sponsored by, or in any way officially connected to X Corp. “X”, “Twitter” and “Tweet” and related names, marks and logos are trademarks of their respective owners and appear here only to describe what this extension works with.