# How to Easily Mass Block and Mass Delete Tweets on X > Block lists, bulk deletion and the tools for each, plus the rate limits that decide how long either one actually takes. - Source: https://tweetsweep.com/blog/how-to-easily-mass-block-and-mass-delete-tweets-on-x - Published: 2024-03-21 - Updated: 2026-08-16 - Reading time: 5 min --- ## Separate tooling for each job Both jobs share a problem. The X UI is designed for one action at a time and for example neither blocking a hundred accounts nor deleting ten thousand posts appear plausible in one swoop. The web client and the mobile apps expose a block button on a profile and a delete item in the post's overflow menu. Neither surface accepts a list. Do not treat blocking vs deleting as a combined workflow with no one button to click, but rather two workflows with separate tools, separate permissions, and separate failure modes. That divide crops up right away with communities that share spam lists and people throwing away posts from years back. X imports a block list via the app's own settings pages and doesn't meddle with your timeline. There is no native control for deleting posts. In any tool that does this in one click, you are mixing two permission models. Give the write access only to the job you now doing and than cut them. Also mixing the jobs makes it less clear if a failure came from the block import or deletion queue. ## Native block list import X allows importing and exporting your block lists through its own web interface. Step 1: Open Settings and privacy, Step 2: Privacy and safety, Step 3: Mute and block, Step 4: Blocked accounts The import and export selections are on this particular screen. Export saves your existing blocks into a CSV file. Import: This takes a CSV and executes all handlers in a single action. That is how spam and harassment accounts lists are shared between communities. Use the web client for this step — not the iOS or Android apps. The import and export buttons never appear on those apps. Do the CSV prep before you pull that screen up. The import does literally the same thing with each row, it expects a user id or handle in format X that is already being exported and if you try to omit this the line is simply skipped without any useful error. Once the import has finished, remain on Blocked accounts and scroll the list to verify that the new names have landed. If you use a list someone else made, do a quick skim over it first. Unlike shared lists, stale data is why you get locked out of accounts that you still need. First, export your own block list so you can restore it if necessary. ## Third-party engagement blocking X doesn't allow blocking with specific post users who liked, replied to, or reposted it. That task usually uses a 3rd get together device that reads the engagement listing and submits a block for every account. These tools will require write access to your account. Only give write permission for that single session. Once the run has finished go toSettings, Security and account access, Apps and sessions and revoke the app A forgotten app that is granted write access can continue to operate on your account long after you believe you have severed ties. So only choose a tool which allows you to see the accounts it is going to block before it starts. The engagement list consists of real people you know, quote-posters who echo your sentiments as well as bots. A virally-posted mass blind hit will score all three. Check Blocked accounts to see if the names match your original expectations, make sure you run a small batch first. Do not use it if the tool can not spotlight. Only thing wrong is that will given the same block permission which you use for yourself, and bad selector to undo by hand approach expensive. ## Deletion rate limits X has no bulk delete, you delete one post at a time thru the overflow menu on that post. Note that if there is a limit on the deletion API (e.g. 50 requests/15 min/user, refer eshoponly for different tool limits) this limit applies to all tools equally. The price for removing a post is equal to that for reading one. A queue that processes at a rate of approximately one per second, lending to the accurate description of bulk deletion being a batch rather than wipe. Anything promoted as instant is either lying or on the verge of failing halfway down the queue. Time plan against that cap, not against a progress bar as if the work was already completed. If the tool does not miss a window, fifty deletions every fifteen minutes amounts to two hundred an hour. This translates to roughly fifty hours of wall-clock time for ten thousand posts. And weeks, a big-and-established account with years of replies will etch out in that queue the days. Close the tool and if it doesn't persist, you start fresh. You can select something that retains the other ids and continues after a browser restarts. ## Archive calendar deletions Those are the efficient way to read your memory: work from downloaded archive instead of re-reading last timeline. A complete timeline sync is cut off at X's 3,200-post ceiling, which means that posts older than this threshold will never be returned in a live scrape. In your settings, request for the archive from X, wait and email, download the zip. Thi ma is a full history of posts and replies and timestamps that no live client would provide you with. TweetSweep archives it all, lays your history out like a calendar — you can select by day or range rather than scrolling through a feed. When TweetSweep is deployed to a range, deletions are queued at a pace no higher than the 50-request limit, so that one big account clears reliably. That way you can see which days are in the past and which are yet to come. Which is why the visibility of these kind of actions – when an organized assault via quote-tweet target a week-old or two-week-old posts matters. Delete the week first keep the rest. Since the queue is constructed from the archive, you are not reliant on X to serve those posts back to you on a timeline that has already written them off. The calendar keeps that state. ## Recommended sequence Get the archive first before you touch anything else. Allowing keeps your ability to still see everything, blocking and deleting change that, and you want a local copy of the posts you're going to wish you kept later on. Harassment if you block next. Use the common csv or execute the participation tool, then bind large application. Blocking prevents the incoming replies and quote tweets Just enqueue the removals after that. Delete deletes The Material that is quote-tweeting you, which happens to be the part that maintains the pile-on. As soon as the deletions begin you will need to leave the queue running and not continue visiting the live profile to count what was left. It still displays posts which the API has not yet exceeded, and refreshes do not speed up the cap. Check TweetSweep's calendar instead. A day disappears when it becomes clear. If you need proof of a report or lawyer, hijack the archive zip onto your disk elsewhere; X will never furnish those posts back to you once they're deleted. End last task: Revoke all third-party apps.