<p>There's a short description of what it does in the <a href="http://buildwithcraft.com/updates#build2524" rel="noreferrer">2.0 release notes</a>.</p>

<blockquote>
  <p>Added a new Find and Replace tool in Settings, for <strong>finding/replacing text within all Rich/Plain Text fields</strong> (including ones in a Matrix field).</p>
</blockquote>

CC BY-SA 3.0
2015-03-13T13:46:58.050Z
I'll mark this as correct, but it would be good to get a more full definition. What about custom fieldtypes that store content in the content table as plain text for example.
Luke Holder
CC BY-SA 3.0
2015-03-13T13:55:33.073Z
It says Rich/Plain Text fields, so if this information is correct then all other fields shouldn't be affected.
carlcs
CC BY-SA 3.0
2015-03-13T16:01:57.733Z
Yup... purely limited to Rich/Plain text fields.
Brad Bell
CC BY-SA 3.0
2015-03-13T13:45:26.913Z
2015-03-13T13:45:26.913Z
carlcs
<p>I see the feature, but would like to read about what and where it finds before replacing.</p>

<documentation>
Is the 'find and replace' feature (found in the control panel settings screen) documented?
# Is the 'find and replace' feature (found in the control panel settings screen) documented?

(Asked by: username_0 on 2015-03-13)

I see the feature, but would like to read about what and where it finds before replacing.

**Tags:** documentation


---

## 1 answers

### Answer by username_1 on 2015-03-13. Score: 5 | Accepted answer

There's a short description of what it does in the [2.0 release notes](http://buildwithcraft.com/updates#build2524).

> Added a new Find and Replace tool in Settings, for **finding/replacing text within all Rich/Plain Text fields** (including ones in a Matrix field).

> **Comments:**
> **username_0**: I'll mark this as correct, but it would be good to get a more full definition. What about custom fieldtypes that store content in the content table as plain text for example.  
> **username_1**: It says Rich/Plain Text fields, so if this information is correct then all other fields shouldn't be affected.  
> **username_2**: Yup... purely limited to Rich/Plain text fields.  

---

