How to Find What Changed Between Two Versions of a Document

Someone sends back "the contract, with a few small changes." A colleague edits a config file and now the service won't start. You have two drafts of the same report and can't remember which paragraph you rewrote. In every case the fix is the same: instead of re-reading two near-identical documents line by line, compare them and let the differences jump out.

Why the eye is bad at this

Two versions of a long document are mostly identical, and that's exactly the problem. Your eye slides over the matching parts and it's easy to miss the one line that changed — a deadline moved from 30 days to 14, a single value flipped, a clause quietly added. The important edit is hidden in a sea of sameness. A comparison tool inverts that: it hides the sameness and shows only what moved.

How a diff works

A "diff" (short for difference) lines the two texts up and marks each line as unchanged, added, or removed. It does this by finding the longest run of lines the two versions share, in order, and treating everything else as an edit — the same technique behind the comparison view in version-control tools like Git. That's why a small change in the middle of a long file shows just that change, rather than flagging every line after it as different.

How to compare two texts

Paste the original into one box and the new version into the other in our Diff Checker, and the differences highlight line by line — additions in green, removals in red — with a count of how many lines changed. It's the fastest way to answer "what actually changed here?" And because the comparison runs in your browser, neither version is uploaded — which matters when the thing you're comparing is a contract, a config with credentials, or an unreleased draft.

Getting cleaner results

Ignore whitespace when indentation or trailing spaces changed but the content didn't — otherwise a re-indented file looks entirely rewritten.
Ignore case when only capitalisation differs and you don't care about it.
Tidy both sides first if they came from messy sources. Trimming and sorting both versions with a text cleaner before comparing removes noise so only real differences remain.

Common uses

Contract revisions — see exactly what a reviewer changed before you sign.
Config and code — find the one line that broke a working setup.
Writing — compare two drafts and keep the better wording from each.
Verification — confirm two lists or exports are genuinely identical, not just similar.

Frequently asked questions

Does it compare word by word or line by line?

Line by line, which is the most useful view for documents, config and code. If a single word changes, you'll see the old line marked removed and the new line marked added.

Is my text uploaded when I compare?

No. Both versions stay in your browser — nothing is sent or stored. That's the point of comparing locally, since these are often sensitive documents.

Can it handle large files?

Yes, within your device's memory — the work grows with the size of both texts, so very large inputs may take a moment, but there's no server size limit because nothing is uploaded.