X (Twitter) Search Operators: The Complete Guide

Finding the right public conversation on X (formerly Twitter) takes more than entering a topic and scrolling. A reporter investigating product complaints, a researcher comparing campaign messages, or a marketer tracking customer questions needs to separate original tweets from replies, retweets, and promotional noise. Search operators turn that task into a repeatable method: specify an author, preserve a phrase, narrow a period, or request posts containing particular media.

The vocabulary still carries Twitter’s history, but familiar instructions are not necessarily reliable instructions. Since the platform’s acquisition by Elon Musk and subsequent rebranding, interfaces, access arrangements, and developer services have continued evolving, a shift that also shapes how X compares with Threads in 2026. The practical distinction is between what a query asks for and what the platform actually indexes or exposes. Throughout this reference, Maya, an analyst at the fictional outdoor brand Northstar, uses X to investigate launch feedback. Her example tweets illustrate how constraints improve relevance without guaranteeing completeness. Whether she wants customer tweets, an engagement threshold, or a developer workflow through an API, the governing principle remains the same: test the smallest useful query first, then add restrictions deliberately.

At a glance

• Use uppercase OR, quotation marks, and exclusions to make tweets easier to isolate.
• Separate original posts, replies, and retweets before comparing engagement.
• Older Twitter instructions can contain legacy syntax; test filters directly on X.
• Check endpoint documentation before transferring any search-bar query to an API.

What Are X (Formerly Twitter) Search Operators?

Search operators are instructions embedded in a query. Instead of searching only for words, they ask for tweets with particular authors, publication periods, or content characteristics. If you prefer a form to typed syntax, the Twitter advanced search guide shows how to build many of these queries without memorizing them.

X Search Operator Syntax: Spaces, OR, Minus Signs, and Parentheses

Spaces generally mean AND: northstar jacket requests both terms. Use uppercase OR for alternatives, quotation marks for phrases, and parentheses to keep related choices together: (northstar OR "north star") jacket.

A leading minus excludes a term, or a filter where negation works: jacket -giveaway. Write from:NorthstarDemo, never from: NorthstarDemo; misplaced spaces can change how tweets are matched.

On X, excluding retweets can further reduce duplication. Twitter terminology survives in documentation, but an API can interpret similar-looking syntax differently: grammar is only useful when the search surface supports it.

Keyword and Exact Phrase Search Operators on X

Begin with vocabulary your audience actually uses. Maya searches customer tweets for "broken zipper" rather than relying exclusively on a campaign slogan.

Search Exact Phrases, Alternatives, Hashtags, Cashtags, Emoji, and Exclusions

Try ("broken zipper" OR "zip failed") -sale to collect alternative descriptions while excluding obvious promotions. Search a tag directly with #NorthstarDemo, or use $AAPL when investigating a financial symbol; surrounding context still matters.

Literal emoji can be pasted into searches, but matching and tokenization vary. Question marks and emoticons are not dependable sentiment classifiers, and an asterisk is not a reliable universal wildcard for word stems or phrase gaps.

Older Twitter tips sometimes overstate punctuation tricks. Compare returned tweets against a simple keyword baseline before trusting a more elaborate expression.

Account and User Search Operators for X

from:NorthstarDemo targets tweets authored by that placeholder account. to:NorthstarDemo targets replies directed to it, while @NorthstarDemo searches mentions rather than proving a reply relationship.

Find Posts by Account, Replies, Mentions, Lists, Verified Users, and Followed Accounts

Maya compares from:NorthstarDemo jacket with to:NorthstarDemo jacket: company announcements and customer responses answer different questions. Neither query automatically eliminates retweets or isolates every relevant conversation.

Public-list syntax such as list:owner/list-slug and filters such as filter:verified or filter:follows require surface-specific testing. List accessibility, account state, and verification categories can affect interpretation.

Twitter-era verification assumptions are especially misleading: a badge is not a universal credibility signal. When comparing tweets, inspect authors directly, starting with how complete and credible their profile is, and verify any equivalent API capability separately.

X Date and Time Search Operators

Use since: and until: to restrict tweets to a publication window. Write dates as YYYY-MM-DD, not a regional day/month format.

Use since:, until:, Rolling Time Windows, and Tweet-ID Boundaries

jacket since:2026-02-01 until:2026-03-01 targets February: the starting boundary is inclusive and the ending boundary exclusive. These sample dates represent Maya’s hypothetical launch period, not a promise of historical availability.

Legacy Twitter searches may show within_time:2d, since_id:, or max_id:. Treat these as surface-dependent rather than dependable substitutes for calendar boundaries on X.

A Snowflake ID is a time-linked identifier, not a simple consecutive counter. ID boundaries can help order tweets where supported, but inclusivity, timestamp precision, and API parameters must be checked independently.

X Engagement Search Operators for Likes, Reposts, and Replies

Popularity filters help Maya prioritize widely noticed tweets, not necessarily accurate or representative ones. Twitter terminology also persists in operators: the repost-related threshold still uses retweets.

Set Minimum and Supported Maximum Engagement Thresholds

Query component	Intended effect	Important qualification
min_faves:100	At least 100 likes	Counts change after indexing.
min_retweets:20	At least 20 reposts	Does not measure unique endorsement.
min_replies:10	At least 10 replies	Activity can include disagreement.
-min_faves:501	Exclude posts reaching 501 likes	Only useful where threshold negation works.

For example, jacket min_faves:100 min_retweets:20 requests tweets crossing both thresholds. Treat engagement as a discovery aid: retweets can reflect criticism, and indexed values may lag live counters.

Do not invent a universal max_faves: operator. A negated minimum can approximate an upper engagement boundary where supported, but checking individual tweets remains necessary.

X Search Operators for Replies, Reposts, Quotes, Polls, and Threads

Post types represent different relationships. Replies address another post, retweets redistribute one, and quote posts add commentary around an embedded reference.

Filter Posts by Type, Conversation, and Thread Activity

In web searches, try filter:replies for reply tweets and -filter:replies for their exclusion. Legacy forms including filter:retweets, filter:quote, and filter:polls need testing against known examples.

Twitter guides often confuse filter:nativeretweets with every historical use of “RT.” Native retweets and manually copied text are different objects, so a filter should not be assumed to capture both.

For tweets within a conversation, conversation_id: is surface-dependent; API support must be assessed separately. Thread membership also does not imply one author: inspect reply relationships before calling collected tweets a complete thread.

X Media Search Operators for Images, Video, GIFs, and Links

Media restrictions are useful when Maya needs visual evidence rather than general complaints. A photograph of a damaged seam can support a different investigation from a text-only allegation.

Find Media Posts and Filter Sensitive Content

Try jacket filter:images, jacket filter:videos, or jacket filter:links. Broader filter:media searches can surface mixed-format tweets, while filter:native_video and GIF-specific filters require additional surface checks. For a dedicated walkthrough, see our guide to the Twitter video finder.

Linked video, uploaded video, and animated GIFs are not necessarily indexed identically. Media retweets can also duplicate the same evidence, so inspect the original publication before counting independent reports.

Some interfaces recognize filter:safe, but account settings and moderation still govern visibility. No sensitive-content filter guarantees that all returned tweets are suitable—or that every relevant item is available.

X Search Operators for Language, Location, Source, URLs, and Cards

These filters describe different kinds of metadata, meaning information attached to a post. Their coverage is often less complete than ordinary text matching.

Filter by Language, Geolocation, Client, Link, and Card—with Limitations

jacket lang:en requests tweets classified as English; short or multilingual text can be misclassified. Legacy geographic syntax such as near:London within:15km should not be treated as a census of local conversation.

A profile location is not a post’s geotag, and relatively few posts expose usable geographic data. If you are unsure what that field actually does, read how to make the best use of the Twitter profile location field. On X, geographic results therefore need particularly careful validation.

url:example.com can help locate linked domains, but shortened links and indexing complicate matching. Legacy client searches such as source:"Twitter for iPhone", Android client labels, and card_name: filters are not dependable across surfaces.

Check these against known tweets before use; an API may expose different metadata or no equivalent searchable field.

How to Combine X Search Operators for More Precise Results

Build restrictions progressively so that each addition has an observable effect. Starting with a complicated expression makes an empty result set difficult to diagnose.

Build a Query Step by Step with Grouped Alternatives and Exclusions

Maya begins with "broken zipper", then expands to ("broken zipper" OR "zip failed"). She adds to:NorthstarDemo, followed by since:2026-02-01 until:2026-03-01.

Only after reviewing the sample does she add -giveaway -from:NorthstarDemo. If retweets dominate, she tests a supported exclusion separately rather than assuming the full expression behaves correctly.

An engagement threshold comes last because it can hide valuable low-visibility tweets. Grouped alternatives establish meaning; incremental testing establishes trust.

Practical X Search Operator Examples for Everyday Research

The following examples use fictional account names. Replace them with real handles without inserting spaces after colons.

Monitor Brand Mentions, Find Topic Replies, and Exclude Your Own Posts

("Northstar" OR @NorthstarDemo) -from:NorthstarDemo looks for brand-related tweets outside the company’s own account. It can still match unrelated businesses sharing that name, so Maya checks context before tagging a complaint.

For support-oriented tweets, she tries to:NorthstarDemo zipper filter:replies. This is narrower than a general Twitter mention search and may miss indirect complaints that never address the brand.

Find Popular Posts by Date, Locate Media, and Search Quote Posts

jacket since:2026-02-01 until:2026-03-01 min_faves:100 prioritizes popular tweets during the sample launch. Adding filter:images changes the task from broad reaction monitoring to visual discovery.

Where recognized, quote:NorthstarDemo is worth testing for tweets quoting that account; otherwise, inspect a known post’s quote view. A mention plus a quote filter does not prove whose post was quoted, and retweets are not equivalent.

X Search Results: Indexing, Ranking, Privacy, and Completeness Limits

Searchable does not mean exhaustive. Missing tweets may reflect indexing gaps, deletion, protected accounts, suspension, moderation, or anti-spam systems rather than an incorrect expression. If your own posts seem to be missing, you can test for a shadowban on Twitter before blaming your query.

Understand Top Results, Latest Results, Personalization, and Missing Posts

Top results emphasize relevance and ranking signals; Latest emphasizes recency within the available matching set. Personalization, spelling correction, and account context can still influence discovery on X.

Twitter screenshots from another user therefore need not reproduce your own results. Engagement figures and retweets may also change between collection and verification.

Record the query, collection time, selected tab, and visible examples. Neither browsing nor an API guarantees recovery of all historical tweets, and no operator bypasses privacy restrictions.

How to Troubleshoot X Search Operator Queries

When a query fails, simplify it before assuming the topic has no matching tweets. Test one restriction at a time against a known public post. For broader account and platform issues, the troubleshooting hub covers common problems.

Fix Lowercase OR, Spacing, Date Formats, Ungrouped Terms, and Query Errors

Replace lowercase or with OR; repair from: username to from:username; use the documented calendar format. Group alternatives so that an author or time restriction is not accidentally attached to only one branch.

Inspect spelling corrections and remove unsupported operators. Overlong expressions may fail or behave unexpectedly, and numerical limits differ by interface rather than following one permanent operator-count rule.

In multilingual team notes, “opérateurs de recherche,” “mots-clés,” “filtres,” “résultats,” and “médias” can label the same workflow. Translate the explanation, not literal operator names; API validation remains a separate troubleshooting step.

X Search Operators vs. API Query Syntax

A search-bar expression is not an API contract. Historical Twitter examples frequently mix web syntax, older endpoints, and developer-only capabilities.

Check Operator Support for the Specific API Endpoint and Access Tier

Start with the current official developer documentation for the exact endpoint. API search availability, historical reach, supported operators, and account entitlements must be checked together.

Do not infer support from a successful web search. An unsupported API filter may trigger rejection or different handling; silent omission is not a universal rule.

Separate X Search-Bar Queries from API Requests

Every query example above is intended for interactive testing, not presented as a ready-to-send API request. For implementation, map the research requirement to an API-supported field, operator, or parameter only after checking its documented behavior.

This matters especially for retweets, geographic restrictions, and threshold filters. A developer collecting tweets should retain original identifiers and collection metadata so later verification remains possible.

Verify Current Authentication, Pagination, Rate Limits, and Query Constraints

Confirm authentication for the chosen API endpoint, then inspect its pagination mechanism and rate-limit rules. Query-length limits, available fields, and expansion options also belong to that specific API contract.

Record these settings alongside the collection script. Repeatability depends on documenting access conditions, not merely saving the search string.

Best Practices for Reliable X Search Operator Workflows

Maya keeps a small validation set: known replies, original tweets, media posts, and quote examples. She checks that each proposed restriction includes and excludes the expected items before using it for reporting.

Test Queries Across Surfaces and Treat Results as Searchable, Not Exhaustive

Compare X web results with the mobile interface where relevant, but do not expect identical rankings. Legacy TweetDeck instructions may describe behavior absent from another interface; references to TweetDeck should always be checked against the actual surface available.

Save the query, tab, timestamp, and representative post links. If an API feeds a dashboard, document its endpoint and retrieval window separately from manual searches. To go deeper on building repeatable X workflows, explore the Birdy courses.

For consequential findings, combine search with direct account inspection and source verification. Operators improve selection; they do not establish completeness or truth.

Why does an exact phrase return fewer posts than expected?

Quotation marks narrow matching, while indexing gaps, deleted content, and visibility restrictions can remove otherwise relevant posts. Test a distinctive shorter phrase before adding more filters.

Can I find every post mentioning my brand?

No. Search can miss indirect references, spelling variations, private content, and unindexed material. Combine alternative brand spellings with direct account and conversation checks. More answers are in the Birdy FAQ.

Does a repost threshold measure approval?

No. Redistribution can express criticism, amusement, or disagreement. Read the surrounding conversation before treating popularity as positive sentiment.

Can I paste these queries directly into an API request?

Not without checking the selected endpoint’s current documentation. Supported operators, authentication, access scope, pagination, and query constraints can differ from interactive search.