Delete X posts in bulk and keep your account

Review how to delete X posts, formerly called tweets: manual removal, archive selection, permanent deletion and the limits of bulk cleanup.

Quick answer

To delete X posts, open one of your posts, use its menu and confirm Delete. X provides individual deletion rather than a native bulk-delete button. For a larger selection of tweets, an archive-based tool can help you review dates and text first. Your account and following list stay in place when you delete your own posts.

Delete a few X posts directly

Open your profile, find a post you published and choose Delete from its menu. Repeat for each post. Undoing a repost and removing a like are separate actions; neither deletes someone else’s original post. X Help: delete a post.

Compare genuinely free tweet-deletion options

Review a fixed selection with Clearpost

Paid post cleanups are available. Preview recent posts, choose a package and pay once, load within its allowance, then Keep and confirm deletion separately. The demo uses sample posts. No X account needed.

  1. Sign in with X and preview up to 50 recent posts free. Pick a package and pay once.
  2. After payment, load posts within your package allowance. For older history, optionally choose tweets.js or supported post JSON from your archive.
  3. Choose your dates, search loaded text and mark posts to keep. Replies and quote posts are part of your own post selection.
  4. Save the list and check the account, actions and count. Selected item data and filter settings are sent to Clearpost; the full ZIP, DMs and contacts stay on your device.
  5. Check the saved list and confirm deletion separately. Payment alone never starts deletion.
  6. Follow saved progress and pause future work if needed. An action already in progress may finish after a pause or cancellation.

Try the demo · Download and choose your X archive files

How long it takes

Clearpost enforces at most 50 post-deletion attempts per user in a rolling 15-minute window. That works out to a theoretical ceiling of about 4,800 attempts in 24 hours, not a promised daily result. Shared queues, X response limits, pauses, reconnects and interruptions can make a cleanup take longer. Automated unlike cleanup is excluded. X API: rate limits.

What does a Clearpost cleanup cost?

Preview up to 50 recent posts free, once per X account. Then pay once for your package. No subscription. Cancel before loading and you get a full refund. Nothing is deleted until you confirm your saved list.

See pricing · Read the charge and refund rules

What deleting a post leaves behind

Deleted posts cannot be restored through Clearpost. Other people’s screenshots, copied text and search caches may remain. An archive preview covers supported entries in the files you supply; it cannot guarantee that every historical post is present or removable. X Help: delete a post.

Compare the three ways to delete all tweets

Common questions

Is deleting tweets with Clearpost safe?

Clearpost uses X authorization, a saved selection and a separate final confirmation. Its worker observes rate limits and saves progress. No tool can promise zero account risk or complete removal. Deletion is permanent, and copies elsewhere may remain. Keep your archive and review the selected account and posts first.

Do I give Clearpost my X password?

No. You sign in on X through OAuth; your password stays with X. Clearpost stores account tokens encrypted on its server. Signing in, importing an archive or paying does not authorize deletion: you confirm the saved selection separately.

Do I need my Twitter archive?

No archive is needed to load recent posts directly from X. Load up to 100 posts per page, within X’s limit of 3,200 recent posts and Clearpost’s loading allowances. For older history, choose tweets.js or supported post JSON from your archive. Both sources let you filter and keep posts before saving a selection. Neither source guarantees complete account coverage or that every selected post is still available.

How long does it take to delete all tweets?

Clearpost enforces at most 50 post-deletion attempts per user in a rolling 15-minute window. That works out to a theoretical ceiling of about 4,800 attempts in 24 hours, not a promised daily result. Shared queues, X response limits, pauses, reconnects and interruptions can make a cleanup take longer. Automated unlike cleanup is excluded.

What if a selected tweet is already gone?

The preview does not check live availability. Posts detected as already gone from saved cleanup history are skipped and refunded. Otherwise an affirmative X confirmation that a post is not on X is chargeable even if it was gone before; it does not prove Clearpost newly deleted it. Unconfirmed items receive their allocated refund. No paid pre-check lookups are made.