Compare Two PDFs Free

Compare two PDFs to spot what changed between versions — matching pages side by side, with differences highlighted and scored.

Your files never leave your device — all processing happens in your browser.

PDF A

Select PDF

first version · .pdf

PDF B

Select PDF

second version · .pdf

Comparison complete

Everything happened inside your browser — your PDF was never uploaded anywhere, so there is nothing to delete.

Spot exactly what changed between two PDF versions

Contract v7 or v8? The client swears they "only fixed a typo," but the page count changed. The auditor sent back a "final" report that looks identical to the draft — except somewhere in 80 pages, a figure moved. Human eyes are terrible at diffing documents: we skim, we assume, we miss the one altered paragraph on page 47. Compare PDF tooling exists because "find the differences" is a job for software, not patience.

EzySize's comparison tool takes two PDFs and lays matching pages side by side, highlighting what changed and scoring each page by how much changed. Added paragraphs, deleted clauses, altered figures, shifted layouts — the differences surface visually instead of hiding in a skim-read. And like everything here, it runs in your browser: the two documents (often a draft and a confidential revision) never get uploaded anywhere.

The side-by-side, scored approach matters. A raw text diff of two PDFs drowns you in formatting noise; a visual comparison with per-page change scores lets you triage — pages at 0% you skip, the page at 34% you read carefully. That's the workflow that actually gets used under deadline pressure.

Compare PDF files the reliable way: how to compare two PDFs side by side

  1. Drop in both PDFs — the original and the revised version. Label which is which in your head (or in the filenames): the tool diffs them directionally, and "added vs. removed" only makes sense if you know which file is newer.
  2. Let the tool align the pages. Matching pages are paired up — page 5 with page 5 — even if the documents have slightly different page counts. If one version inserted two pages mid-document, the alignment accounts for the shift rather than flagging every subsequent page as changed.
  3. Scan the change scores first. Each page pair gets a percentage showing how much changed. Start with the highest scores — that's where the substantive edits live. Pages scoring near zero had only rendering noise or nothing at all.
  4. Review highlighted differences page by page. The side-by-side view marks additions, deletions, and modifications. Read the flagged passages in context — a highlighted paragraph might be a moved block (same text, new location) rather than new content, and the distinction matters.
  5. Check the unmatched pages. Pages present in one file but not the other are the easiest changes to miss and often the most significant — a deleted appendix, an inserted clause. Review these deliberately rather than treating them as alignment artifacts.

When PDF comparison saves the day

  • Contract redlines without the redline. When the other side returns a "clean" revised contract instead of a tracked-changes version, comparison reconstructs the diff. Every altered clause surfaces — including the ones they hoped you wouldn't notice.
  • Auditing report revisions. "Final" reports that differ mysteriously from drafts are a staple of consulting and finance. A scored comparison tells you in minutes whether the changes are cosmetic or whether the conclusions moved.
  • Verifying vendor deliverables. The agency delivered "version 2" of the spec document — did they incorporate your feedback or just re-export? Compare and see every change, or the absence of changes, objectively.
  • Regulatory and compliance review. Policy documents, terms of service, and disclosures change over time; reviewers need to certify what changed. A documented comparison beats a narrative summary for audit trails.
  • Proofreading layout changes. After merging or reorganizing a document, compare against the pre-edit version to confirm nothing was lost or duplicated in the shuffle — the page counts and scores tell the story.
  • Checking scanned vs. digital versions. When a signed scan comes back, comparing it against the digital original confirms the signed copy matches — no substituted pages, no missing exhibits.

Pro tips for trustworthy comparisons

  • Compare the right pair. It sounds obvious, but most "the tool found thousands of changes" panics trace to comparing v6 against v8 instead of v7 against v8. Verify filenames and dates before concluding anything — the diff is only as meaningful as the pair.
  • Ignore sub-1% scores on scanned pages. Scans of the "same" page differ pixel-wise every time (scanner noise, slight rotation), producing tiny change scores on identical content. Mentally filter these; focus on pages with real percentages.
  • Moved text is not changed text. A paragraph relocated from page 10 to page 12 flags as deleted-plus-added. Before reacting, check whether the content is new or just moved — the response to each is very different in a negotiation.
  • Flatten before comparing annotated files. If one version has comments and highlights and the other doesn't, the annotation layers create diff noise. Flatten both (or strip annotations from both) so the comparison measures content, not markup.
  • Extract text for the fine print. For the highest-stakes passages — liability caps, payment terms — supplement the visual diff by extracting the text with a PDF to text pass and reading the two versions' wording side by side. Visual diffs catch location; text extraction catches wording.
  • Save the comparison evidence. Screenshot or export the scored results for the pages that matter. "The comparison showed a 22% change on page 14" is a citable fact in a dispute; "I think something changed" is not.

PDF diff tool: text, visuals, and change scores

Find differences between PDFs visually

Visual comparison catches what text diffs miss: a swapped chart, a resized logo, a paragraph that moved without changing a word. EzySize renders both pages and highlights the visual deltas, so layout changes — the kind that alter meaning without altering text — don't slip through. For contracts and reports, the visual layer is where the sneaky edits hide.

Compare PDF documents online with page-level scores

The percentage-changed score per page is the triage mechanism that makes comparison practical on long documents. Instead of reading 80 pages twice, you read the six pages that changed. Scores also give you a language for the conversation: "pages 12–14 changed substantially, the rest is untouched" is a precise, defensible summary of a revision.

Free online comparison without uploading

Document comparison is inherently sensitive — you're feeding the tool two versions of something confidential, often a negotiation in progress. A pdf compare tool online that uploads both versions to a server doubles the exposure. Browser-local comparison keeps both files on your machine; the only thing that leaves is your conclusion about what changed. If the diff reveals pages that shouldn't have been shared at all, redact them before the next round goes out.

Trust, but verify — and when the document matters, verify with software. Compare the versions, read the scores, and never again take "only a typo" on faith.

How it works

  1. Add both PDFs

    Drop the two versions into PDF A and PDF B — both are read locally, never uploaded.

  2. Flip through pages

    Matching pages render side by side. Use Prev/Next to walk through the document.

  3. See what changed

    Switch to the Difference overlay — changed pixels glow red, with a % changed score per page.

Tips

Frequently asked questions

How is the % changed score calculated?

Both pages render at the identical scale, then every pixel is compared. The score is the share of pixels that differ beyond a small anti-aliasing tolerance.

Can I compare PDFs with different page counts?

Yes — matching pages are compared pair by pair, and extra pages in the longer file are clearly flagged.

Does it compare the text or the visuals?

The visuals, pixel by pixel. That catches font changes, moved images and layout shifts that a text-only diff would miss.

Are my PDFs uploaded anywhere?

No. Rendering and pixel comparison happen entirely in your browser.

How do I compare two PDF files to find differences?

Drop both PDFs into EzySize's comparison tool — original and revised version. It pairs up matching pages, shows them side by side with changes highlighted, and scores each page by how much changed. Start with the highest-scoring pages; those hold the substantive edits. Both files stay in your browser, never uploaded.

How is the percentage-changed score calculated?

Each page pair is analyzed for visual and content differences, and the score reflects what share of the page changed — 0% means effectively identical, higher percentages mean heavier edits. Use scores to triage long documents: skip the near-zero pages and read the high scorers carefully. Tiny scores on scanned pages are usually just scanner noise.

Why does the comparison show changes when the documents look identical?

Usually one of three causes: you're comparing the wrong pair of versions, one file has annotation layers the other lacks (flatten both first), or the pages are scans with pixel-level noise. Check the filenames and dates first — most false alarms trace to comparing v6 vs v8 instead of v7 vs v8.

Are my PDFs uploaded anywhere during comparison?

No. The comparison runs entirely in your browser — both documents stay on your machine. This matters because compared documents are often confidential negotiations or unreleased revisions; uploading both versions to a server would double the exposure for zero benefit.