Twitter Advanced Search: Every Operator, With Examples
Twitter advanced search cheat sheet for 2026: every useful operator (from:, since:, min_faves:, filter:) with examples, plus the search form and tips.
How Twitter advanced search works
There are two ways to run an advanced search on X. The first is the Advanced Search form at x.com/search-advanced, which has fields for words, accounts, engagement and dates. The second is typing operators directly into the normal search box. The form simply writes operators for you, so learning them is faster in the long run and unlocks options the form doesn't show.
Two things to know up front. First, search on X has required a logged-in account for some time now; logged-out visitors are sent to the sign-in page. Second, X does not publish a complete, versioned list of operators. The ones below are widely documented and worked at the time of writing, but some (marked as such) behave inconsistently or may change.
Using the Advanced Search form
- Log in on the web and go to x.com/search-advanced (on desktop you can also run any search, then open the filter menu and choose Advanced search).
- Fill in the Words fields: all of these words, this exact phrase, any of these words, none of these words, these hashtags, and a language.
- Use Accounts to set from these accounts, to these accounts, or mentioning these accounts.
- Set Filters for replies and links, and Engagement minimums for replies, likes and reposts.
- Pick a Dates range and press Search. The query box on the results page now shows the operators the form generated, which you can edit by hand.
The mobile apps have offered fewer advanced options than the website, so if a field is missing on your phone, type the operator directly into the search box instead.
On the search results page, switch between the Top, Latest, People, Media and Lists tabs. For operator searches, Latest is usually what you want, because Top re-ranks and can hide matching posts.
Word and language operators
These control which words must, may or must not appear. Separate terms with spaces; a space means AND.
| Operator | Example | What it finds |
|---|---|---|
| word1 word2 | coffee recipe | Posts containing both words, in any order |
| "exact phrase" | "cold brew ratio" | Posts with that exact phrase |
| OR | espresso OR latte | Posts with either word (OR must be uppercase) |
| -word | coffee -decaf | Excludes posts containing the word |
| #hashtag | #buildinpublic | Posts using that hashtag |
| $cashtag | $AAPL | Posts mentioning a stock ticker cashtag |
| lang: | ramen lang:ja | Posts X has classified as that language (ISO code) |
Use parentheses to group OR terms when mixing with other operators, for example (espresso OR latte) -starbucks lang:en. The lang: filter relies on X's automatic language detection, so very short posts are sometimes misclassified.
Account operators: from:, to:, @ and list:
| Operator | Example | What it finds |
|---|---|---|
| from: | from:nasa | Posts written by that account |
| to: | to:nasa | Replies sent to that account |
| @mention | @nasa | Posts that mention the account (including replies) |
| list: | list:123456789 | Posts from members of a list, using the list's numeric ID |
from: is the workhorse. Combine it with a keyword to search inside one account's history, like from:nasa artemis. To find what people said to an account but exclude the account itself, use @nasa -from:nasa.
If you just want to read an account's recent public posts rather than search them, you can open the profile in the PeekX profile viewer without logging in. It shows roughly the latest 20 public posts with filters and export, but it cannot search.
Content filters: media, links, replies and more
The filter: operators keep only certain types of posts. Put a minus in front to exclude that type instead.
| Operator | What it keeps | Notes |
|---|---|---|
| filter:media | Posts with any photo, video or GIF | Reliable |
| filter:images | Posts with photos | Reliable |
| filter:native_video | Posts with videos uploaded to X | Excludes linked YouTube videos |
| filter:links | Posts containing a URL | Media attachments may also count |
| filter:replies | Only replies | Reliable |
| -filter:replies | Only original posts, no replies | Very useful with from: |
| filter:quote | Quote posts | Behaviour has varied over time |
| filter:verified / filter:blue_verified | Posts from verified accounts | Meaning changed with paid verification; results may be inconsistent |
A common combination is from:handle filter:native_video to list every video an account posted. Once you find the one you want, paste its link into the Twitter video downloader to save any MP4 quality, or use the Twitter image downloader for original-size photos.
Engagement and date operators
| Operator | Example | What it finds |
|---|---|---|
| min_faves: | min_faves:500 | Posts with at least 500 likes |
| min_retweets: | min_retweets:100 | Posts with at least 100 reposts |
| min_replies: | min_replies:50 | Posts with at least 50 replies |
| since: | since:2024-01-01 | Posts on or after that date (YYYY-MM-DD) |
| until: | until:2024-02-01 | Posts before that date (the end date is not included) |
| since_time: / until_time: | since_time:1704067200 | Unix timestamp bounds, for hour-level precision; less documented |
Engagement operators are the fastest way to find someone's best-known posts: from:handle min_faves:1000. Date operators are how you reach far back in a timeline, which the profile page itself makes painful. Our guide on how to see old tweets walks through that in more detail.
Dates are interpreted in UTC. If a post seems to be missing at the edge of a range, widen the range by a day on each side.
Location, URL and conversation operators
- near: and within: — for example coffee near:"Berlin" within:10km. These rely on location data that very few posts include today, so results are often sparse or unreliable. Treat them as a hint, not a filter.
- url: — finds posts linking to a domain or URL fragment, such as url:github.com. Handy for seeing who shared an article.
- conversation_id: — use a post's numeric ID (the number after /status/ in its link) to pull up the posts in that thread's conversation, such as conversation_id:1234567890123456789.
If you have one post and want to read its thread or replies without searching, open it in the Twitter thread reader or the reply viewer. They work from the post link and don't need an account.
Combining operators and saving searches
Operators stack. Each one narrows the results further, so you can build very precise queries:
- from:handle -filter:replies min_faves:200 since:2025-01-01 — an account's most liked original posts since a date.
- "launch" (from:brandA OR from:brandB) filter:media — media posts mentioning a launch from two accounts.
- url:yourblog.com -from:yourhandle — who is sharing your site, excluding you.
- to:handle min_replies:20 — replies to an account that sparked their own discussion.
Common mistakes
- Adding a space after the colon. It must be from:nasa, not from: nasa.
- Writing or in lowercase. Only uppercase OR works as an operator.
- Using a display name in from: or to:. Operators need the username (handle), like to:nasa, not "NASA Official".
- Expecting until: to include its date. until:2025-03-01 stops at the end of February 28.
- Stacking too many rare operators at once. If results vanish, remove them one by one to find the culprit.
To save a search, run it, then open the three-dot menu on the results page and choose Save search (the exact place has moved between app versions). Saved searches appear when you tap into the search box. You can also simply bookmark the results URL in your browser; the query is encoded in it.
Where PeekX fits
PeekX can't search X, show trends or list likes and followers. What it does is open any public post or profile you found, without logging in: replace x.com with our domain in the link, or paste it into the X viewer. From there you can read the thread, see media in the media viewer, or download files. The bookmarklet sends the page you're on straight to PeekX.
