How to Compare Two Texts and Find the Differences

Spotting what changed between two versions of text is a job you hit constantly: a config file before and after an edit, two drafts of a contract, or a teammate’s code review. Eyeballing it never works for more than a few lines. A diff tool does the comparison for you and highlights exactly what moved, vanished, or appeared.

What a diff actually shows

A diff compares two texts line by line and labels each line with one of three states:

Added: a line that exists in the new text but not the old one, usually shown in green with a +.
Removed: a line that existed in the old text but is gone in the new one, usually shown in red with a -.
Unchanged: a line that is identical in both, shown plain for context.

A “changed” line is really just a removal paired with an addition: the old version is marked removed, the new version is marked added, sitting next to each other. That is why a one-word edit shows up as two highlighted lines rather than one.

How to use it

Open the Diff Checker and paste your original text on the left.
Paste the new version on the right.
Read the highlights: green for added lines, red for removed, plain for unchanged.
Toggle whitespace or case sensitivity if small formatting noise is hiding the real changes.

Everything runs in your browser. Nothing is uploaded, which matters when you are comparing contract clauses, environment files, or anything you would not paste into a stranger’s server.

Reading a side-by-side diff

The Diff Checker lines up the two versions in parallel columns so matching lines stay aligned. When a block is added or removed, the other side shows a gap, so your eye can follow the same paragraph down both columns. Scan top to bottom: most of the page should be plain context, and the colored lines are the only things you need to think about. For long files, jump straight to the first highlight instead of reading every line.

When whitespace and case matter

Two lines that look identical can still register as different. Common causes:

Trailing spaces or a mix of tabs and spaces.
Line endings, where Windows CRLF differs from Unix LF.
Capitalization, where True and true are not the same string.

Sometimes those differences are exactly what you are hunting, like a stray space breaking a config value. Other times they are noise, like indentation churn in a code review. Use the ignore-whitespace and ignore-case options to switch between the two. Turn them off when precision matters, turn them on when you only care about the words.

Common uses

Config changes: confirm exactly which settings an edit touched before you deploy.
Code review: see what a change adds and removes without trusting a summary.
Contract and copy edits: catch every wording change between two drafts.
Version comparison: line up an old export against a new one to find drift.

Need to swap a recurring string across the whole text? Use Find & Replace.
Comparing lists where order is noise? Sort and dedupe first with Line Sorter & Dedupe.
Diffing two API responses? Format them consistently first with the JSON Formatter.

Stop squinting at two windows. Paste both versions, read the colors, done.