How it works
- 01
Paste both versions
Type, paste, or open two text files. The old one on the left, the new one on the right.
- 02
Pick how to read it
Unified, side by side, or inline. Compare by line, by word or by character.
- 03
Take the result
Copy the changed text, or save a unified .diff patch that git can apply.
How the comparison works
The diff lines up what has not changed and reports the rest. It uses the longest common subsequence, the same idea behind version control diffs. It has no notion of a move. A block that changes position shows up twice, removed from one place and added in another. That is why reordering sections looks like a bigger edit than it felt like.
Granularity sets what counts as a difference. Line mode suits code, where the whole line is the unit. Word mode suits prose. Change three words and only those three light up. Character mode is for a single typo or a stray comma.
- Modes
- Unified, side by side, and inline. Line, word or character granularity.
- Length
- No cap. Turn off Live compare if typing in a long document feels slow.
- Input
- Type, paste, or open .txt, .md, .csv, .json, .log and .yml files.
- Output
- Copy the changed text, or a standard unified .diff patch.
Ignoring noise
Whitespace can bury the real edits in a reformatted text. Change the indentation or re-wrap a paragraph, and every line reads as edited. Turn on Ignore whitespace and only the changed words are left.
Ignore case does the same for text put through a style pass. It also hides a capital letter someone meant to change, so it is off by default.