X advanced search: the operators that still work

#Quick answer

X advanced search is the free form at x.com/search-advanced. X's own help page says it "is available when you're logged in to X.com", so it is web-first and account-gated, and it lets you filter by words, exact phrases, accounts, places and date ranges. The form writes the operators into the search bar for you, which means you can build a query by clicking, then copy the finished syntax and reuse it forever.

Last updated: September 2026

#TL;DR

Most of the "every operator that still works" posts on this topic are copies of each other, and several list location operators that have not returned useful results in years. The reliable way to think about X (formerly Twitter) search is in two layers.

Layer one is what X documents: the fields in its own advanced search form. Those are safe, they are what the product team maintains, and the form generates the syntax so you never have to trust a cheat sheet at all.

Layer two is the typed extras, the engagement floors and filters that power users pass in the search bar. They are genuinely useful and they are also undocumented, which means they can change quietly. Test one before you build on it.

Below: how to reach the form, the operator table split by which layer it belongs to, ten queries worth saving, and the one divergence between browser search and the API that trips up anyone wiring search into a tool.

#Where advanced search lives

The path X documents:

1. Search for anything in the search bar on x.com while logged in.
2. On the results page, click Advanced search under Search filters on the upper right, or open More options and choose Advanced search.
3. Fill in the fields you care about and click Search.

You can also jump straight to x.com/search-advanced and skip step one.

Two constraints follow from X's wording. Being logged in is required, so an incognito window will not do. And this is an X.com feature, not an app feature: on iOS and Android the Advanced search link is not in the search UI, so either open the URL in a mobile browser or type operators directly into the app's search box, which still parses them fine.

#The form writes your operators for you

This is the part the cheat-sheet posts skip, and it is the single most useful thing to know here.

Fill in the form, hit search, and look at the search bar on the results page. X has translated your inputs into operator syntax: quotes for exact phrases, from: for the account field, since: and until: for the date pickers. That string is now yours. Save it in a note, tweak the numbers, and paste it into the search bar next time to skip the form entirely.

So the honest advice is not "memorise 30 operators". It is: use the form once for the query shape you need, steal the syntax it produces, and only hand-type the extras that the form does not expose.

#The operator table

The Documented rows map to fields X lists on its own advanced search help page. The Typed only rows are conventions that work in the search bar but that X does not publish, so treat them as useful and unguaranteed.

Combine freely. Order does not matter, and every term is an AND by default unless you write OR.

#Ten queries worth saving

Swap the handles and numbers for yours.

1. from:yourhandle min_faves:100 -filter:replies - your own greatest hits, the fastest content brief there is.
2. from:yourhandle since:2026-01-01 until:2026-03-31 - what you were posting in a specific quarter.
3. from:competitorhandle min_replies:20 - the posts of theirs that started arguments, which is where the audience is.
4. "your product name" -from:yourhandle - people talking about you without tagging you.
5. url:yourdomain.com min_faves:5 - who is sharing your links and what they said about them.
6. to:bighandle min_faves:50 - replies that outperformed, a masterclass in reply writing.
7. "looking for" ("recommendations" OR "suggestions") yourkeyword min_faves:5 - live buying intent in your niche.
8. yourkeyword filter:media min_retweets:50 lang:en - the visual formats that travel in your topic.
9. from:yourhandle "same phrase you overuse" - a self-audit for verbal tics before they become a bit.
10. yourkeyword since:2026-08-01 min_faves:200 - what actually broke through this month, minus the noise.

Queries 3, 6 and 7 are the ones that turn search into a growth routine rather than a lookup tool. They surface conversations that are already hot and already relevant, which is the hard part of replying on X in a way that gets noticed.

#The API divergence that breaks tools

If you plan to run these queries programmatically, check the operator against the API before you assume it carries over. X's developer documentation for building a v2 search query lists operators such as from:, to:, lang:, has:media, has:links and is:retweet, and splits them into core operators available to any project and advanced operators reserved for higher access levels. The engagement floors that make browser search so useful, min_faves and its siblings, are not in that documentation.

Practical consequence: a query you tuned in your browser can return a different result set through a tool, without an error to tell you why. Filter engagement on your side after fetching, rather than assuming the endpoint understands it. The wider cost picture for anyone going down this road is in our breakdown of X API pricing and access, which changed hard in February 2026.

#When search is the wrong tool

Advanced search reads the live index, and that has edges worth knowing:

• Deleted posts and deactivated accounts are gone. For your own history, request your archive instead.
• Blocks are one-way walls. Posts from an account that blocked you will not surface for you.
• Protected accounts stay protected. Nothing in search exposes them.
• Results are not a complete corpus. Search is a ranked index, not a database dump, so "no results" means "nothing surfaced", not "this never existed".

For recurring monitoring rather than one-off lookups, Lists are usually the better instrument, and saved searches sit somewhere between the two. If you want the numbers behind your own posts rather than other people's, that is your X analytics dashboard, not search.

#Turning search results into a posting habit

A good query gives you a queue: ten conversations you could add something real to today. The bottleneck is never finding them, it is being at the keyboard when they are still warm, every day, in your own voice.

That gap is what X-Autopilot exists to close. It drafts on-brand posts and replies through real Chrome on your own Mac, so the daily presence does not depend on your calendar. One honesty note, since your account is the thing at risk: engaging through a browser tool is a gray area under X's automation rules rather than a sanctioned API route, and no tool removes account risk. Running locally on your own machine and IP is a smaller detection surface than cloud tools posting from shared pools, which is reduced risk, not zero.

Short version: open the form once, steal the syntax it writes, keep five queries in a note, and check them before you post rather than scrolling the timeline and hoping. If you want the tool-side view of the same job, we compared the search tools worth paying for separately.