Hide and block X (Twitter) spam accounts by post keywords, author name or mentions. Fully local, no data collection.
Users
2
store count
Rating
5.0 / 5
unchanged in 30 days
Ratings
1
total ratings
Store rank
#344K
#287K among extensions
Version
1.8.8
updated 21 Nov 2026
Publisher and listing changes
From our daily record of this listing since 7 Nov 2026
No change of publisher name, contact email, website, privacy policy or listing name since 7 Nov 2026.
About Spam Account Cleaner (X / Twitter)
X (Twitter) spam is rarely an obvious ad. Most of it is a normal-looking post that simply
@-mentions a promo account. This extension catches exactly that.
When an account mentioned in a post has a matching display name or bio, the post is hidden
and that mentioned account is queued for blocking — you don't have to wait for it to post
an ad itself. Blocking then runs in small, paced batches. Configure your keywords once.
DETECTION — three independent paths, any match triggers the action:
1. Mentioned accounts (the main one): checks the name and bio of every @-mentioned account;
a hit hides the post and queues that account, optionally the poster too.
2. Post keywords: text in posts and replies. Supports the & wildcard, && for a literal
ampersand; emoji, spacing, full/half-width brackets and curly quotes do not matter.
3. Author display name: catches accounts whose posts look normal but whose name is an ad.
Accounts already queued are hidden regardless of content.
STARTER RULES
Fresh installs ship with a starter keyword set matching the browser language (12 languages
built in; English is the fallback). Existing users keep their own lists — updates never
overwrite saved keywords. All four lists are editable;
deleted entries are never restored by an update. Keywords match literally, so a default word
may hide a legitimate post — hiding is reversible, one click on "exempt" in the queue.
WHY HIDE FIRST
X rate-limits bulk blocking. Hiding is local and sends no block request; judging a mentioned
account needs one public profile lookup. Blocking runs on a timer — 5 per batch by default,
10-minute gaps, auto-blocking capped at 720/day (our own safety line, not an X limit;
manual blocking still works after that), 30-minute cool-down on 429/403 — all adjustable. Two switches:
"auto block" stops only the timer; the master switch stops everything and restores hidden posts.
WHO GETS SKIPPED
Your own account, accounts you follow, your allow-list, and verified accounts (blue/gold/grey)
are skipped by default; exemption is re-checked right before each block.
VISIBILITY
A badge in the bottom-right shows how many posts were hidden; expand it for the author, the
matched keyword and what happened. The popup has three tabs: status, queue and rules.
Every queued account shows why it was queued and the result of the block.
PRIVACY & REQUIREMENTS
No servers, no accounts, no analytics. Settings, queue and profile cache live in
chrome.storage.local; storage.sync is not used. Requests go only to X's own domains
(x.com / twitter.com / abs.twimg.com) using your own signed-in session, for public profile
lookups and the blocks you configured. Desktop Chrome 111+ on x.com or twitter.com;
both the current and previous X page structures are supported. Does not read DMs or modify
your posts.
Not affiliated with or endorsed by X Corp. "X" (formerly Twitter) identifies the platform only.
Please follow X's terms when using bulk blocking. All features are free: no paywall, no in-app
purchases, no ads, no feature limits.
Note: translated by a non-native speaker; minor errors may exist.
Growth
Window
Users
Change
Ratings
Rating
7 days
−2
−50.0%
0
0.00
Version history
7 versions recorded
No update since 7 Nov 2026 changed the permissions or site access.