Compare Text
How to compare text changes clearly
Compare Text works best when the output helps you answer one question fast: what changed, and does it matter? That depends on the view you choose and how much context you keep visible while reviewing.
Start with the right view
Side by Side is best when you want to keep the old and new versions visible at the same time. It is easier for line-by-line reading, design copy checks, and technical reviews where the surrounding context matters. Unified is better when you want one compact stream of edits that reads like a patch.
Use Character-Level Highlights when wording is sensitive
Character-Level Highlights are especially useful for short lines, legal clauses, pricing values, and edited labels. They make tiny but meaningful changes visible, such as a single number, punctuation mark, or variable name. That prevents a reviewer from missing small edits inside otherwise similar lines.
Keep syntax context on for code and structured text
Syntax-aware comparison does not replace a parser, but it helps keep your bearings. For code, JSON, SQL, or markup, the syntax selector adds useful context so changed lines are easier to understand. It is one of the fastest ways to reduce review fatigue on technical text.
Export the result when the review matters later
Share and Export are not just convenience features. They make comparison work reusable. A shared link helps someone else inspect the same material, while an exported diff gives teams a record they can attach to tickets, approvals, or release notes.