πŸ” Free Β· Private Β· Client-Side

Compare PDF Files

Load two PDFs, then spot exactly what changed. Side-by-side, overlay, or pixel-level diff views β€” with similarity percentages per page and a summary of every difference. Nothing is ever uploaded.

πŸ” Load two PDFs to begin
πŸ”

No comparison yet

Load the original PDF into slot A and the revised PDF into slot B. Once both are ready, the tool compares them page by page.

A Original β€”
B Revised β€”
Content only in A (red) Content only in B (cyan) Content in both
Unchanged Changed pixels

πŸ“‹ Comparison summary

PDF Aβ€”
PDF Bβ€”
Pages comparedβ€”
Thresholdβ€”
Resultβ€”
PrivacyNothing uploaded

What PDF comparison actually does πŸ”

Comparing two PDFs means asking a simple question: does page 1 of document A match page 1 of document B? If not, what's different? That question turns out to be harder to answer than it looks, because PDFs are not text files β€” they're rendering recipes.

Two PDFs can have identical visible content but completely different bytes, because of how they were produced. Word exports look different from Chrome exports look different from LaTeX exports, even for the same content. Two versions of the same page might differ by a single digit or by an entire paragraph β€” and the visual difference may be obvious or invisible at a glance.

The reliable approach is visual comparison: render both pages to a canvas, compare them pixel by pixel, and highlight the regions that differ. That's what this tool does.

What this tool catches: visible changes in content, layout, formatting, images, and typography between two PDFs.

What it doesn't catch: invisible changes like text that renders identically but uses a different character, or metadata changes that don't affect appearance.

Three ways to compare πŸ“Š

Each view answers a slightly different question. Switch between them depending on what you're looking for.

ViewWhat it showsBest for
Side by side Both pages shown at the same scale, next to each other Detailed reading comparison β€” checking a paragraph word by word
Overlay Both pages blended together with red/cyan color-coding Spotting layout shifts, moved elements, and subtle position changes
Diff highlight Document A faded to grey, with changed pixels highlighted in red Getting an immediate answer to "what changed?" without reading

How to compare two PDFs β€” step by step πŸ“‹

  1. Load PDF A into the top upload slot β€” this is the original or reference version.
  2. Load PDF B into the bottom upload slot β€” this is the revised version you want to check.
  3. Wait for processing. Every page of both PDFs is rendered and compared automatically. Progress shows in the sidebar.
  4. Review the summary. Identical, different, and only-in-one counts appear in the sidebar along with the overall similarity percentage.
  5. Navigate to any page with the page list or the navigation buttons. Pages with the biggest differences are easy to spot β€” they show a red dot in the list.
  6. Switch between view modes. Side by side for reading, overlay for layout shifts, diff for a quick highlight.
  7. Adjust the threshold if needed. If a page looks identical but shows as different, increase the threshold. If a tiny change isn't being flagged, decrease it.

When to use this tool πŸ“‹

Use caseHow it helps
Verifying a revised contractSpot every clause that changed before you sign
Checking a proof-read documentConfirm the editor only changed what they said they changed
Confirming a scanned re-copySee if two scans are actually the same document
Detecting unauthorised editsCompare a stored copy with a received copy to see what's different
Reviewing design revisionsSee layout shifts between two versions of a report or brochure
Auditing compliance documentsVerify that only permitted sections changed
Checking exportsEnsure two exports of the same source produced identical output

How the diff algorithm works πŸ”¬

The tool follows the same pipeline that desktop diff software like Adobe Acrobat's "Compare Files" uses:

  1. Render both pages to canvases at the same scale.
  2. Read the pixel data for each canvas using getImageData().
  3. Compare pixel by pixel β€” for each position, compute the average color difference between A and B.
  4. Apply the threshold β€” if the difference exceeds your threshold (default 30 out of 255), the pixel is marked as changed.
  5. Count changed pixels and compute similarity = 100 Γ— (unchanged / total).
  6. Render the diff by drawing A's pixels faded, then overdrawing changed pixels in red.
Why the threshold matters: anti-aliasing, JPEG compression, and font hinting all produce pixels that differ by 1–10 units even between visually identical pages. The threshold filters that noise. Set it too low and every page shows as different; too high and real changes slip through. 30 is a good balance for most documents.

Why a browser-based comparator matters πŸ”’

Contract revisions, medical records, legal filings, confidential business proposals β€” these are precisely the documents where you'd want to compare versions, and precisely the documents you don't want to upload to a stranger's server.

This tool runs entirely in your browser. Both PDFs are read into memory locally, rendered to canvases on your CPU, and compared pixel by pixel without any network activity. Close the tab and every trace is gone.

Who uses a PDF comparer? πŸ‘₯

Common problems and how to fix them πŸ› οΈ

"Every page shows as different, but they look the same"

Almost certainly a threshold issue. Two PDFs of the same content exported from different tools will have pixel differences of 5–15 due to font hinting and anti-aliasing. Increase the threshold to 50 or 60 β€” the visible differences will still be flagged, but the invisible noise disappears.

"A tiny change isn't being detected"

Lower the threshold to 15 or 20. Small text changes (a single digit or a comma) can produce pixel differences of only 20–30 in a small region. The lower threshold catches these but may introduce false positives elsewhere.

"PDFs with different page sizes show as different everywhere"

That's expected. If page A is A4 and page B is Letter, the canvas sizes differ and the comparison treats the smaller page's overflow area as changed. The tool uses the larger of the two dimensions and fills the missing regions with white. For an accurate comparison, resize one PDF to match the other with our PDF Page Resizer tool first.

"Scanned PDFs show as different even though they look the same"

Scans vary slightly between captures β€” lighting, dust, paper texture, and sensor noise all produce pixel-level differences. Set the threshold to 70 or higher. Real content changes will still be caught, but the noise won't.

"The page takes a long time to load"

Very large PDFs (100+ pages each) can take 30–60 seconds to process at default settings. The tool yields to the UI between pages so the progress bar updates, but rendering is CPU-bound. For very large documents, consider splitting them first with our Split PDF tool and comparing section by section.

"I only want to see the pages that changed"

Use the page list in the sidebar. Every page shows a colored dot: green for identical, amber for minor differences below the "different" threshold, red for pages with substantial changes. Click any page to jump to it in the comparison view.

Is it safe to compare PDFs here? πŸ”

Yes. Here's exactly what happens when you use this tool:

  1. You pick two PDFs from your computer.
  2. Both are read into memory locally.
  3. Pages are rendered to canvases on your device.
  4. Pixel data is compared in JavaScript β€” nothing leaves the tab.
  5. When you close the tab, every trace disappears.

At no point does either PDF leave your device. No data is sent to SkillsInsider's servers. No tracking cookies watch your comparison. Turn off Wi-Fi after the page loads and it still works perfectly.

Frequently Asked Questions

Is this Compare PDF tool free?+

Yes β€” completely free. No sign-up, no watermark, no page limits, no per-file fee.

Are my PDFs uploaded to a server?+

No. Both PDFs are read and compared locally in your browser using PDF.js and canvas. Neither file leaves your device.

How does the comparison work?+

Both PDFs are rendered page by page to a canvas at the same scale. Each pair of pages is compared pixel by pixel. Where the difference between corresponding pixels exceeds the threshold you set, those pixels are marked as changed and highlighted in red.

Can it detect text changes that look identical?+

The comparison is visual. If two pages look identical at the pixel level but the underlying text differs (for example a hidden character), the diff will not catch it. This tool is designed for spotting visible layout and content changes.

What if the two PDFs have different page counts?+

The tool compares up to the longer document's page count. Extra pages on one side are shown alone with a note. Pages with no counterpart are marked as unmatched.

How should I set the sensitivity threshold?+

Start at the default of 30. Lower values catch tiny changes like anti-aliasing differences but produce false positives. Higher values only flag obvious changes. If pages look identical but still show as different, increase the threshold.

Does it work on scanned PDFs?+

Yes. The tool works on any PDF that renders to a canvas, including scans. Note that scans of the same page may differ slightly due to lighting, dust, or sensor noise, so you may need to raise the threshold to filter that out.

Does it work offline?+

Once the page has fully loaded, yes. Turn off Wi-Fi and it still compares.