Twitter Advanced Search: What It Is and How It Works
Every advanced search operator that still works, what each one filters, and the queries worth saving.
What Advanced Search Actually Does
X x have enabled one of the most powerful functions imaginable, an advanced search that transforms a boring search box into a query instrument to find on of your cathartic posts across years. Searchbar understands natural language and makes an inference about your intent (standard search), whereas advanced search allows you to specify exact conditions. You can filter results by who posted it, who they replied to, the content of the post word for word, when that was sent and what type of media it contained. That distinguish between scrolling mindlessly and directly to the answer.
The most straightforward access point is found at the x.com/search-advanced. It provides you with fields labelled for the commonly used scenarios: These words, this exact phrase, any of these words, none of these words, from accounts, to accounts, mentioning accounts and Date range. The formulation is convenient, but anything it spits out can be written out by hand in the standard search box. The reason to learn the manual syntax is that you can combine operators in ways that don't even get exposed via a form, plus you can use them on the fly without going to another page.
The Operators Worth Memorising
Most of the load is carried by four operators. The from: operator narrows the results to posts sent from a single account. Filters the to: operator for posts that reply to or mention a user The since: and until: operators accept a date in YYYY-MM-DD format which restricts the search across that window. A quoted phrase, entered with quotation marks, results in those words appearing together in that order. Collectively, these five building blocks capture most of the searches in the wild.
For instance, from:yourhandle since:2015-01-01 until:2016-01-01 returns all the posts you posted within that year. If you put from:yourhandle "launch day" it only matches posts with that explicit phrase. to:somecompany returns all posts that you replied to or mentioned that company. Using the same format, you can find all tweets sent during a time period: from:yourhandle to:support since:2024-01-01 will give you everything you've tweeted in support this year. After you become acquainted with this, the rest of the operators are just derivatives of same logic.
Content Filters and Exclusions
Filters cut down the results based on what is attached with the post. The filter:media operator returns only the posts that includes any photo, video or gif. But there are more specific versions, for example filter:images, filter:videos and filter:links. The filter:replies operator displays tweets that are replies, while the filter:nativeretweets shows reposts. You can prepend a minus sign to invert each of these. In this case, -filter:replies tells no replies and -filter:links tells that the post does not contain a link. The minus sign works with any operator not just a filter.
The actual value is separating the signal from noise. Filter:media jumps past all spammier text posts in any search for a post that shared a photo. So to see only original posts by a particular account: from:handle -filter:replies hides the threads of replies. If you are sifting through a timeline, filter:links is a shortcut to find posts that reference outside pages; these will likely be the ones you want to police or delete. The exclusions are as mighty as the inclusions, and they are free to type.
Engagement Thresholds and Other Limits
Engagement floors allow you to find posts performing above a threshold. The min_faves: operator accepts a number as input, only returning posts that received at least that many faves. min_retweets: do the same for retweets, and min_replies: for replies. This is the closest thing to a quality filter in X's search. A search such as from:yourhandle min_faves:500 shows your most engaging posts, which can help you know what to keep or get rid of when cleaning up an older timeline.
The tool is supplemented by two more operators. The url: operator with a domain like url:example. com, will find every post that links to that site. lang: — this operator filters the results to a specific language code; the supplementary example being lang:en for English. Either one is just a simple addition to all your queries. You can add everything else to it, so from:yourhandle url: yourblog. Search: com lang:en X itself documents the full list of operators; the above are those that find real daily usage.
Practical Search Combinations
The operators are better understood as combinations that address actual problems. To perform an audit of one year of your own posting, run: from:yourhandle since:2015-01-01 until:2016-01-01. Run from:yourhandle min_faves:500, if you want to find your best content. To locate all posts on 1 subject run from:yourhandle keyword where keyword any word you commonly use. The last query is the one that usually initiates a cleanup because it exposes how much you wrote about a topic, and how repetitive it looks in list form.
You can also use it to do research on a variety of other accounts. Run from:competitorhandle pricing since:2024-01-01 to see what a competitor posted about pricing. Execute this search to know if a brand responded to your complaints: run to:brand -filter:replies To look for mentions of you but not replies, search mentions:yourhandle -filter:replies. Each combination is simply the fundamental operators in a row. You are trained from the data until Oct 2023 There was no special query constructor for combining queries; just put in the same search box different words also separated by spaces.
Where the Search Run Out
There are real limits to search, and understanding these saves time and effort. It does not consistently serve every post for older or higher-activity accounts. X is a rolling window so if something was posted more than years ago it may simply never show up even though your query could point you to the exact post (good luck with that). Posts from private accounts will not appear unless the user follows them. It's a good scalpel For finding a needle in the haystack. It is not the right tool for taking a full inventory of your own history.
Your archive download — which requires setting a password, and then downloading all of your posts as one file — is where the entire record resides. That file is exempted from the 3,200-post limit or the advanced search rolling index you use. It becomes your only true inventory of history. The secret is TweetSweep reads that file directly, applies the same filters you would type into search, and appends deleting to the result. Thus, the same mechanism that hits on a search post can kill it permanently without having to rely on what X has in its index to show you.