> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/app/generation/generators/generator-reference/find-and-replace.md). # Find and Replace This generator replaces all instances of the find string with the replace string. For example, you can indicate to replace all instances of `abc` with `123`. ## Characteristics


Consistency	No, cannot be made consistent.
Linking	No, cannot be linked.
Differential privacy	No
Data-free	No
Allowed for primary keys	No
Allowed for unique columns	No
Uses format-preserving encryption (FPE)	No
Privacy ranking	5
Generator ID (for the API)	`FindAndReplaceGenerator`

## How to configure To configure the generator: 1. In the **Find** field, type the string to look for in the source column value.\ \ To use a regular expression to identify the source value, check the **Use Regex** checkbox.\ \ If you use a regular expression, use backslash ( `\` ) as the escape character. 2. In the **Replace** field, type the string to replace the matching string with. 3. If [Structural data encryption](/app/generation/generators-assign-config/generators-data-encryption-config.md) is enabled, then to use it for this column, in the advanced options section, toggle **Use data encryption process** to the on position. --- # 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.tonic.ai/app/generation/generators/generator-reference/find-and-replace.md?ask=&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.