> For the complete documentation index, see [llms.txt](https://docs.quadratichq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.quadratichq.com/formulas/wildcards.md).

# Wildcards

Using Wildcards in formulas to match certain cells.

Wildcard patterns can be used with several formula functions, including `MATCH` (with a `match_mode`of `0`) and `XLOOKUP`(with `match_mode` of `2`). They can also be used in [criteria](/formulas/criteria.md) with any equality-based comparison (`=`, `==`, `<>`, `!=`, or no operator)

In wildcards, the special symbols `?` and `*` can be used to match certain text patterns: `?` matches any single character and `*` matches any sequence of zero or more characters. For example, `DEFEN?E` matches the strings `"defence"` and `"defense"`, but not `"defenestrate"`. `*ATE` matches the strings `"ate"`, `"inflate"`, and `"late"`, but not `"wait"`. Multiple `?` and `*` are also allowed.

To match a literal `?` or `*`, prefix it with a tilde `~`: for example, `COUNTIF(A1:A10, "HELLO~?")` matches only the string `"Hello?"` (and uppercase/lowercase variants).

To match a literal tilde `~` in a string with `?` or `*`, replace it with a double tilde `~~`. For example, `COUNTIF(A1:A10, "HELLO ~~?")` matches the strings `"hello ~Q"`, `"hello ~R"`, etc. If the string does not contain any `?` or `*`, then tildes do not need to be escaped.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.quadratichq.com/formulas/wildcards.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.