How to Find Changes Between Two Versions of a Document

Someone sent back a 'lightly edited' contract and you need to find every change. Here's how to compare two PDF versions and catch the edits you'd never spot by eye.

"Just a couple of small tweaks." That's what the other side said when they returned the contract — and now you have to verify it, because "a couple of small tweaks" is exactly how an unfavourable clause slips through. A single changed number in a payment term, a deleted "not", a quietly softened deadline: the edits that matter most are the ones designed not to be noticed.

Reading two long documents side by side and spotting the differences by eye is unreliable and slow. Comparing them automatically is neither. This guide covers finding every change between two versions of a PDF.

Why you can't trust your eyes for this

Human proofreading of two near-identical documents is genuinely bad. Your brain reads what it expects to see, skims familiar passages, and fatigues after a few pages. A one-character change on page 23 — $50,000 to $60,000, within 30 days to within 90 days — is almost invisible to a person and completely obvious to a comparison tool.

If the stakes are real (a contract, a spec, a compliance document), don't rely on a manual read.

The steps

  1. Open Blackpdf's Compare PDF tool and load both versions — the original and the revised one.

  2. Choose a view mode:

    • Side by side — the two documents next to each other, with differences marked. Best for reading through and understanding what changed in context.
    • Difference (overlay) — the two versions superimposed so changes jump out visually. Best for quickly finding where the changes are, especially moved or reformatted content.
  3. Walk through every flagged difference. Don't just note that something changed — read what it changed to. A comparison tells you where; you still have to judge whether each edit is acceptable.

The two changes people miss most

  • Deleted words that reverse meaning. The most dangerous edit isn't adding text — it's removing a single word. "The vendor shall not be liable" becomes "The vendor shall be liable" with one deletion. A comparison catches it; a skim rarely does.
  • Changed numbers. Amounts, dates, percentages, quantities. They look almost identical (30/90, 5%/8%) and change everything. Comparison flags them instantly.

These are precisely the edits that "a couple of small tweaks" is sometimes cover for, which is why an automated compare is worth the two minutes on anything you're signing.

When comparison struggles

Be aware of its limits so you don't over-trust a clean result:

  • Reformatted documents. If the whole thing was re-exported with different margins or fonts, everything shifts position, and the tool may flag layout differences that aren't content changes. Read past those to the real edits.
  • Scanned versions. Comparing a scan against a digital original compares images, which is far noisier than comparing text. If both are scans, OCR them first for a more meaningful comparison.
  • Moved content. A paragraph relocated to another page reads as a deletion in one place and an addition in another. The overlay mode helps you recognise these.

Common questions

Which view mode should I use?

Side by side to review changes in context and understand them. Difference / overlay to quickly locate where changes are, especially visual or moved content. On an important document, use both — one to find, one to read.

Can it compare two scanned documents?

It can, but it's comparing images, so expect noise from scan-to-scan variation. OCR both first for a cleaner, text-level comparison.

The tool flagged a huge number of differences but the text looks the same.

The document was probably re-exported or reformatted, so everything shifted position. Focus on differences in the actual words and numbers, not layout. If both versions came from the same source, that's rare; if one was rebuilt from scratch, it's expected.

Can I compare more than two versions?

Compare them in pairs — original vs v2, then v2 vs v3 — to trace changes across a chain of revisions. That also tells you which revision introduced a given change.

How do I keep a record of what changed?

Keep every version as a separate file (don't overwrite), named clearly (contract-v1.pdf, contract-v2.pdf). The comparison plus a versioned archive is your audit trail.

Wrap-up

  1. Load both versions into Compare PDF.
  2. Use Side by side to read changes in context, Difference to find them fast.
  3. Read what each change became — especially deleted words and altered numbers.
  4. For scans, OCR first.

The edits that matter are the ones built to be missed — a removed "not", a nudged number. Your eyes won't catch them reliably; a comparison will. For the full tour of the tool, see our Compare PDF guide.

Keep reading

How-To

How to Save One Page of a PDF as a Separate File

Just need page 7 out of a 60-page document? Here's the fastest way to save a single page — or a handful — as its own PDF, and how to grab many pages as separate files at once.

July 17, 2026 · 3 min read
How-To

How to Password-Protect a PDF Before Emailing It

Sending something confidential by email? Here's how to encrypt the PDF first — and the step most people get wrong: how to share the password safely.

July 17, 2026 · 4 min read