How to compare two PDF files and spot the differences
Last updated: July 7, 2026
It usually starts with an email that says something like "same contract as before, just a couple of small tweaks". Attached is a twenty-page PDF that looks identical to the one you approved last week. Somewhere in it, something changed. Maybe a payment term slipped from 30 days to 60. Maybe a date moved. Maybe a liability clause gained three words that shift the risk onto you. You won't know until you find it, and "just read both versions again" is not a plan.
This is the job a PDF comparison tool exists for: put the two versions next to each other, page by page, and highlight exactly where they differ. An anxious hour of squinting becomes a two-minute check. Here is how to do it in your browser, what a visual comparison is genuinely good at, and where its honest limits are.
Compare two PDFs in your browser, step by step
You don't need Acrobat Pro or a subscription. robinpdf's Compare PDF tool runs entirely in your browser and works like this:
- Open the Compare PDF page.
- Add the original version in the first slot and the new version in the second. Not sure which is which? The modification date in the document metadata usually settles it.
- Run the comparison. The tool renders both documents and shows them page by page, with the regions that differ highlighted.
- Step through the flagged pages. Untouched pages need no attention at all — you only read where the highlights are.
That last point is the whole trick. In a typical "small tweaks" contract, eighteen of twenty pages are pixel-identical, and the comparison says so instantly. Your reading collapses to the two pages that changed.
Why reading both versions side by side fails
It feels like careful reading should work. It doesn't, and the reason is well known to anyone who has proofread for a living: humans read for meaning, not for characters. Once your brain recognises a familiar clause, it stops inspecting it. A "3" that became an "8", a "shall" that became a "may", a deleted "not" — these are precisely the changes your eye skates over, because the sentence still looks like the sentence you remember.
It gets worse with fatigue. On page one you're vigilant; by page fourteen you're skimming — and page fourteen is exactly where an unhelpful counterparty would put the change. A machine comparison has no attention span to run out. It flags a tiny difference on page nineteen as reliably as a rewritten paragraph on page one.
There's also an asymmetry of stakes: the sender knows what they changed, and you don't. A comparison tool removes that disadvantage, because it finds every visual difference — not just the ones you were told about.
Where this saves you in practice
Contracts are the headline case, but the same two-minute check earns its keep all over:
- Contract revisions before signing. The classic. Compare the version you agreed to against the version sent back for signature — even the "unchanged" ones. Especially those.
- Invoice versions. A supplier reissues an invoice "with a small correction". Was it just the typo in your address, or did a line item quietly change? Thirty seconds and you know.
- Updated terms and conditions. Companies love announcing that terms have been "updated for clarity". Compare old against new and see what clarity looks like in practice.
- Manuscript and report revisions. A co-author or client returns your PDF proof with edits. The comparison shows you every touched page, including the one they forgot to mention.
- Verifying agreed edits were applied — and nothing else. You asked for two specific changes. The diff confirms both were made and, just as important, that no third change hitched a ride.
That last scenario deserves emphasis. The question is never only whether they made the change you agreed; it is also whether they made any change you did not agree. Reading can answer the first question. Only a comparison reliably answers the second.
What a visual comparison catches — and its honest limits
A tool like this compares what the pages actually look like when rendered, which has a real advantage: it sees everything. Text edits, moved paragraphs, swapped logos, an altered signature block, a changed stamp on a scan — if it looks different, it gets flagged. It works on scanned documents too, where there is no selectable text for a word-level diff to read.
The honest limit is the flip side of the same coin: a visual diff flags everything that looks different, including differences that don't matter. If the new version was re-exported with slightly different fonts, or an inserted sentence on page 2 pushed every following line down, the pages after the insertion will light up even though their wording is untouched. Visual comparison shines when the two versions share the same layout — which, happily, is exactly the "same document, small edits" situation it is most needed for. If a document has been fully re-typeset, treat the highlights as a map of where to read, not as a verdict on each line.
A practical workaround when layout has shifted: go to the first flagged page and read it properly — that is usually where the single insertion or deletion that moved everything downstream lives.
Why comparing in your browser matters here
Think about what you are holding when you compare documents: two versions of an unsigned contract, invoices with bank details, an unpublished manuscript. This is exactly the material you least want sitting on a third-party server, yet most online comparison tools upload both files and diff them remotely. robinpdf renders and compares both PDFs on your own device — the files never leave your computer, so a negotiation-sensitive draft stays between you and your counterparty. For the longer reasoning, see our guide on whether online PDF tools are safe.
Tips for a reliable comparison
- Compare before you sign, every time. Make it a reflex: any re-sent document gets diffed against the last version you approved, no matter how trusted the sender.
- Keep a dated copy of what you approved. You can only compare against a version you kept, so save the approved PDF with the date in the filename.
- Check the page count first. Different page counts mean something was added or removed — that alone is a finding, and it tells you where reflow will start.
- Don't stop at the first difference. Finding the change you expected is not the finish line; keep stepping through to rule out changes you didn't expect.
- Compare the originals, not processed copies. If you've compressed or merged a version, diff the files as received, so the only differences on screen are the sender's.
Frequently asked questions
Is it really free?
Yes — no sign-up, no watermark, no page limit.
Are my documents uploaded anywhere?
No. Both PDFs are rendered and compared in your browser, on your device. Nothing is transmitted to a server, which is rather the point when the documents are unsigned contracts.
Does it work on scanned PDFs?
Yes. Because the comparison is visual, it doesn't need selectable text — two scans of a paper document can be compared just like digital PDFs.
Will it show me exactly which words changed?
It highlights which regions of each page changed. In practice that's what you want for a contract: the highlight takes you to the clause, and you read the clause with your own eyes.
What if the two versions have different layouts?
Reflowed layout gets flagged as a difference, so heavily re-typeset documents produce noisy results. Use the first flagged page to locate the insertion that caused the reflow, then read from there.
Can I compare PDFs on my phone?
Yes. It runs in mobile browsers too, though stepping through highlighted pages is more comfortable on a larger screen.