Choose a search dimension
Start with a person, word, date, mailbox location, status, attachment, or size. The builder translates that choice into Gmail syntax.
Use the builder as an interactive Gmail search operators cheat sheet. Combine supported syntax and see a readable explanation before searching.
Choose filters to see how Gmail operators fit together. Copy the result, adapt it, or open it directly in Gmail.
Gmail search operators are short prefixes that constrain a search. Common examples include from: for sender, after: and before: for dates, is:unread for status, in:archive for archived mail, filename: for files, and larger: for message size.
Separate operators normally combine as AND conditions. Use braces or OR when either alternative may match, quotation marks for an exact phrase, and a minus sign to exclude a term.
Start with a person, word, date, mailbox location, status, attachment, or size. The builder translates that choice into Gmail syntax.
Add conditions that a message can satisfy together. Use comma-separated people when you intend alternatives rather than simultaneous senders.
Check what every generated fragment means, resolve any validation warning, then test the query against your Gmail account.
These combinations cover common retrieval and cleanup tasks without relying on a long memorized command.
People operators include from:, to:, cc:, and bcc:. Content operators include subject:, quotation marks, and exclusions. Time operators include after:, before:, newer_than:, and older_than:. State and location operators include is:, in:, label:, and category:.
File operators include has:attachment and filename:. Size operators include larger:, smaller:, and size:. Other official syntax supports mailing lists, delivered-to addresses, logical grouping, proximity with AROUND, and several Gmail-specific states.
When a long query returns nothing, test it incrementally. Begin with the most reliable condition, confirm the result, and add one operator at a time. This reveals whether a date, category, sender, or phrase is excluding the target.
Operator behavior depends on Gmail’s index, labels, classifications, and account state. InboxQuery validates obvious input conflicts but cannot predict which messages Google will match. The official Gmail documentation remains the authority for supported syntax.
Use sender and recipient addresses, subject text, included words, an exact phrase, and comma-separated exclusions. Blank fields remain outside the query, so you can work with incomplete information.
Combine a fixed date range or rolling message age with read status, mailbox location, Gmail category, attachment presence, filename, and complete-message size limits.
The result is standard query text for Gmail’s search box. InboxQuery also describes each fragment, flags conflicting boundaries, offers one-click copying, and creates a direct Gmail search link.
Begin with the condition you know is true. That may be a sender address, a broad date window, an attachment type, or a mailbox location. Run that simple query first. When the result contains the target but is too large, add one more condition. This incremental method is easier to debug than starting with a long query made from several uncertain memories.
If a query returns nothing, remove the condition you trust least. Display names can hide a different sender address, subject wording may not be exact, categories can be assigned unexpectedly, and date boundaries can exclude messages near midnight. Switching to in:anywhere is useful when Spam or Trash may contain the message, but it does not search another account or restore permanently deleted mail.
The builder handles empty, valid, and invalid states without contacting Gmail. A blank form shows a clear empty result. A valid combination enables copy and search actions. Reversed date boundaries, non-positive age values, and an impossible size band display an error and disable the actions until the input is corrected. Gmail—not InboxQuery—decides which existing messages match the finished query.
Copying the query is useful when you want to inspect or edit it in Gmail before searching. The direct link is faster when the generated text already matches your intent. Both actions use the same visible query, and neither grants InboxQuery permission to your account. Rolling age filters change over time, while fixed dates continue to describe the same period.
Teams that rely on Gmail search operators should document the purpose of important saved queries alongside the query text. Note whether dates are fixed or rolling, which account and labels are assumed, and what a successful result should contain. This context makes the search easier to review when staff, sender domains, or filing practices change. Test complex queries incrementally after any change instead of assuming that an older combination still describes the intended mailbox scope.
They are special terms such as from:, after:, is:unread, and has:attachment that narrow Gmail search results.
Put compatible operators in one query separated by spaces. Gmail normally requires every separate condition to match.
Write OR in uppercase between alternatives or place alternatives in braces, for example {from:a@example.com from:b@example.com}.
Most operator names are commonly used in lowercase. Logical OR should be uppercase for clear, reliable interpretation.
Operator syntax is based on Google’s official Gmail search documentation. InboxQuery is independent and does not access your account.