Find and replace

Find and replace changes matching text. Filtering only changes what is visible. Use a filter first when you want to restrict a replacement to a particular part of the job.

Quick steps

Filter to the segments you want to change, open Find and Replace, choose the language side, and test Replace on one occurrence. Check From here and the filters before Replace All.

Start with a precise search

1. Open the Find and Replace tab, directly or through the ribbon or segment toolbar.
2. Enter the text in Find. A selected phrase can be used as the starting search.
3. Choose the source or target side.
4. Set options such as case sensitivity, whole words, or Regex.
5. Use Find next and inspect the highlighted occurrence.

In a translation job you will normally replace the target. Source replacement is only available when that source is editable in the current workflow. In a single-language review, work with the document text.

Choose the text, language side, and matching options before replacing.

Replace one occurrence first

Enter the intended text in Replace, then use Replace next. Read the complete sentence afterward. A term change can affect articles, agreement, capitalization, or punctuation around the match.

For example, changing a product name is more controlled when you enable whole-word matching and inspect the first few occurrences. A broad substring search can also change longer words containing that text.

When case-sensitive search is off, replacement can adapt capitalization to the matched wording. If exact case is important, use case-sensitive matching and test each form you need.

Which segments Replace all changes

Replace all changes matching text in segments that pass the current filters. It is not limited merely because one row happens to be active. The From here option further restricts the search and replacement to the current position onward.

Before a broad replacement:

1. Check which file or View is open.
2. Check the source/target choice.
3. Check the current filters and From here setting.
4. Test one replacement.
5. Run Replace all only when those boundaries match your intention.
6. Inspect the replacement count and any skipped-content warning.

Bulk replacement skips locked segments. It can also skip a segment when the replacement cannot be applied, and report the reason. Check reported skips if you expected those segments to change.

Work with formatting and tags

The non-Regex find and replace fields can represent formatted text. This lets you distinguish wording with particular formatting from plain wording. Check the formatting in the fields when a visible word does not match as expected.

Tags and protected content require extra care. A search for ordinary text and a search that includes tag content are different operations. Prefer the dedicated tag tools for inserting or repairing document tags.

With Track changes enabled, applicable target replacements can remain visible as revisions. Inspect both the accepted wording and the recorded changes when preparing a review handoff.

Use patterns when literal text is not enough

Enable Regex for a pattern-based search. Enter the pattern itself, without surrounding slashes. For example, \d+ finds one or more digits. Use capture groups and replacement references when part of a match needs to be retained.

A simple example is finding (Part)\s+(\d+) and replacing with $1 $2 to reduce variable whitespace between that label and its number. Test this on sample content before using Replace all.

Regular expressions explains these building blocks and common mistakes.

Save a reusable replacement

Use the save action to give a frequently used find/replace setup a meaningful name. Load it later through the replacement controls and check its saved search side and options before running it on a different job.

A saved replacement is a tool, not a rule that automatically applies to every document. Keep client-specific replacements clearly named so they are not mistaken for a general cleanup step.