Text Diff
Compare two blocks of text line by line, with added/removed highlighted
What Is a Text Diff?
A text diff lays two versions of a document against each other and marks exactly which lines were added, removed or left alone, so one changed line cannot hide in an identical page. Paste the original left and the revision right, press compare, and each line gets a verdict: green for added, red for removed, neutral for unchanged context. Underneath, a longest-common-subsequence table over both line sequences is walked into the alignment, so scattered edits and moved blocks surface as precise line operations, not a vague score. A totals line reports added, removed and unchanged counts, and identical inputs honestly report no difference.
Reading the alignment output
- ➕ Added lines in green, present only in the revised version
- ➖ Removed lines in red, present only in the original
- ✔️ Unchanged lines kept as context around every change
- 📊 Running totals summarizing the size of the edit
- ⌨️ Explicit compare button, so big pastes never work mid-typing
Reviews where it proves its worth
- Seeing what a reviewer actually altered in your draft
- Auditing a config file before and after a find-and-replace sweep
- Confirming two extracts differ only where expected
Note the comparison is line-based: a one-word edit flags its whole line, and moved lines read as removed plus added rather than moved. The whole diff runs in your browser with neither version uploaded, safe for contracts, configs and unpublished manuscripts alike. Identical inputs report no difference instead of a misleading empty screen, so a clean result reads as a verdict.
Last updated · 2026-09-01
How the differences are computed
- A longest-common-subsequence over lines, grouped into change blocks — the classic diff model, computed locally.
- Line mode never matches partial lines: one changed word marks the whole line, keeping reviews honest.
- Whitespace-only churn is flagged separately so indentation noise cannot hide real edits.
A diff you can read beats one you can debug
Line-level precision
A longest-common-subsequence match pairs identical lines between the two versions, then marks every added line green and every removed line red — nothing in between is guessed at.
Change counts in the bar
Above the result, a running tally states exactly how many lines were added and how many removed, so a ten-line edit versus a hundred-line rewrite is visible before you read a single row.
Spot checks and clean copies
Compare a draft against its earlier version, a config file before and after a change, or two exports of the same list — when nothing differs, the result says so plainly.
Frequently asked questions
Does this compare word-by-word or line-by-line?⌄
Line-by-line. Each line is treated as a single unit, so a change in the middle of a line marks that whole line as removed-then-added rather than highlighting the exact changed word.
What algorithm does the comparison use?⌄
A classic longest-common-subsequence (LCS) line diff — the same family of algorithm behind tools like "diff" and Git's line-level comparisons.
Is my text uploaded anywhere?⌄
No — the comparison runs entirely in your browser. Neither text block is ever sent to a server.