Text guide
How to use find and replace safely
Find and replace can fix repeated text in seconds, but the search scope, capitalization, and replacement order determine whether the result stays accurate.
Open the Find and Replace toolDefine an exact search
Start with the smallest exact string that identifies only the intended matches. Searching for cat can also match the beginning of catalog unless the tool supports whole-word matching or you include surrounding context.
Safer example
To change a product label, searching for Plan: Basic is safer than searching for Basic throughout an entire document.
How to use find and replace
- Paste the source into the ToolPixels Find and Replace tool.
- Enter the exact text to find and the replacement text.
- Choose whether capitalization must match.
- Replace the first match when reviewing a risky edit, or replace all for a confirmed repeated pattern.
- Read the match count and inspect the output before copying it.
Case-sensitive versus insensitive matching
A case-sensitive search for May does not match may. That distinction is useful when a name is also a common word. A case-insensitive search is quicker for inconsistent capitalization, but one replacement spelling will usually be applied to every match.
If the source contains API, Api, and api, review whether all should become the same form before replacing them together.
Avoid cascading replacements
Replacement text can contain the original search text. Repeating the operation may then change content a second time. Several replacements can also interfere with each other, especially when one search term is part of another.
- Replace longer, more specific phrases before shorter ones.
- Keep a copy of the original text.
- Inspect boundaries around names, URLs, and code.
- Use a dedicated code refactoring tool for identifiers with references.
Common questions
Can the replacement be empty?
Yes. Replacing a search term with an empty value removes every selected occurrence. Check spacing and punctuation afterward.
Does ToolPixels use regular expressions?
No. It finds plain text, with optional case sensitivity and first-or-all behavior. Characters such as periods and brackets are treated literally.