Compare two blocks of text and see exactly which words were added or removed, which is faster than reading both versions side by side.

Word-level versus line-level

Version control compares lines. That is right for code, where a line is a unit. It is poor for prose: changing one word in a paragraph marks the entire paragraph as changed, hiding the actual edit.

Word-level comparison shows the specific tokens that differ. For a contract revision or a copy edit, that is the view that answers the question you actually have.

Whitespace and normalisation

Some diffs treat every space change as a modification, which buries real edits under reflow noise. Others normalise whitespace first, which hides a change that matters inside a code block.

Neither default is universally right. Knowing which one you are looking at prevents the classic mistake of concluding two files are identical when they differ only in indentation.

When a diff is not enough

A diff shows what changed, not whether the change is correct. For configuration files, a one-character change to a port number is easy to miss among reformatting noise, and for legal text the meaning of a reworded clause is a judgement no tool makes.

Use the diff to locate changes, then read the changed passage in full.

Frequently asked questions

Can it compare files?
Paste the contents of each. For whole directories, use git diff or a dedicated comparison tool.
Does it ignore case?
It compares as written, so a capitalisation change shows as a difference. That is usually what you want when proofreading.
Is my text uploaded?
No. Comparison runs in the page, which matters for contracts and internal documents.