Every document that matters goes through versions: a contract that comes back from the other side, a policy that was “lightly updated”, a configuration file that suddenly behaves differently. Reading both versions side by side and hunting for differences by eye is slow and unreliable. A comparison tool does it in seconds and shows exactly what moved.
What a diff actually shows
A diff lists the minimum set of additions and removals that turn the original into the revised text. It works by finding the longest sequence of items the two versions share in the same order; everything else is either new or gone. If a sentence was reworded, you see the old one removed and the new one added. If a paragraph was moved, the diff reports it as removed in one place and added in another, because it compares order, not meaning.
Choose the right level of detail
- Line level suits lists, configuration, code and anything where each line is a unit. It is fast and easy to scan, but one changed word marks the whole line.
- Word level suits prose, contracts and articles. It highlights the changed words inside a sentence, so a switched “may” to “shall” is impossible to miss.
- Character level suits short strings such as IDs, codes, URLs and names, where a single swapped letter matters.
Remove noise before you read
Many differences are not real changes. A document re-saved by another program may differ only in trailing spaces, line endings or capitalisation, burying the edits that matter. Use the ignore whitespace, ignore case and ignore punctuation switches to filter that noise, and only show changes to collapse long unchanged stretches. If text came from a PDF or a web page, clean it first with the Text Formatting Cleaner so both versions have the same line breaks.
A safe review routine
- Put the older version on the left and the newer on the right, so green always means “added by the new version”.
- Start at word level for prose, line level for structured text.
- Read the change counts first. A document you were told had “minor edits” that shows hundreds of changes deserves a closer look.
- Review every red and green block, not just the first few. The risky edit is often near the end.
- Check the context around each change; a harmless-looking deletion can alter the meaning of the sentence that follows.
- Export the result as a unified diff if you need to send the list of changes to someone else.
What diff tools cannot tell you
A diff shows what changed, not whether the change is acceptable. It cannot detect a number that was changed in both versions, and it does not understand formatting such as bold text or tables in a word processor, only the characters you paste. For legal or financial documents, treat the diff as a guide for your review, not a substitute for it.
Other uses
Compare two exports to confirm a data clean-up removed only what you intended, check that a translation preserved every line of the source, verify a backup against the live file, or see how a colleague edited your draft. Paste, compare and keep the habit: it takes less time than the single re-read you would otherwise do.