Skip to content
RemixPDF

All tools

21 working

Compare two PDFs, free — see what changed

Two versions side by side, with every added, removed and reworded line marked. Rows stay level, so reading across actually compares the same thing.

Open both versions — right in your browser

The download asks for nothing.

…or drop both anywhere on this page

Most of this runs right here in your browser. If anything has to leave it, we tell you first. See how your files are handled

  • See what changed between two versions.
  • Free
  • No signup
  • No watermark

Runs on your device

What you have to hand while you work

Why it works

The rows stay level.

Where a line exists in only one version, the other side shows an empty gutter rather than sliding the next line up. Without that, reading across tells you two unrelated lines were reworded into each other — which is worse than no comparison at all.

Three hard cases get a plain answer.

Identical as documents but not as bytes. Both versions scanned, with no text to compare. A layout shift big enough to move whole lines. Each gets said plainly — the byte difference named, with the picture comparison one click away, the scan given a pixel compare that boxes what looks different, the moved lines flagged with a warning — instead of a bare difference count.

Word level, not just line level.

A changed line shows which words changed, so a rewritten sentence and a corrected figure do not look the same at a glance.

The reason to compare two PDFs is almost never curiosity. A contract came back from the other side and you need to know what they touched. A report went through three people and you want to see the third round’s changes without rereading all of it. In both cases the question is narrow — what is different — and the risk is a comparison that quietly answers a different question.

The commonest way to get this wrong is alignment. If one version has a line the other does not, and both columns are simply listed top to bottom, then everything below that point is offset by one row. Read across and you are told the third line of the old version became the third line of the new one, when they are unrelated. The comparison looks thorough and is actively misleading.

So here, both sides keep one row per pair, and where a line exists on only one side the other shows an empty gutter. Reading across is always comparing the same place in the document. Within a changed line, the words that differ are marked, so a corrected figure and a rewritten clause do not look alike.

Three cases get an explicit answer rather than a number. Two files that read identically but are not byte-for-byte the same are told exactly that: every line reads the same, something besides the words differs, and the picture comparison is offered to find it. Two scanned documents get an honest limit plus a way through: with no text in either file the words can’t be compared, but a pixel mode boxes the regions where the pages look different — offered as a choice, never silently substituted for a text diff. And a large layout shift is flagged: when whole lines reappear unchanged elsewhere, it says how many look simply moved, with a warning that a small edit inside a moved paragraph is the easiest thing in a comparison to miss.

Nothing is uploaded to compare, both files are left exactly as they arrived, and there is no limit on how long either document is.


How it goes

  1. Choose both versions.

    Pick the two files at once, or open one and add the other next.

  2. Read the difference.

    Each column names its file. Added, removed and reworded lines are marked, with a count of each. Switch to one side alone if the pair is hard to read.

  3. Swap sides if they landed the wrong way round.

    The older file belongs on the left; if the newer one landed there, Swap sides reads the pair the other way and flips every mark.

  4. Nothing is changed.

    Comparing reads both files and writes nothing — both come through untouched.

What you can check for yourself

Watch the network while you work — none of the requests carries your document; they only fetch the tool's own code and fonts. The two-minute checks live at how your files are handled.

Frequently asked questions

No. It reads both and reports; nothing is written. Whatever you download afterwards is the version you asked for.

Then it says every line reads the same. If the files are not byte-for-byte identical it says that too — something besides the words differs, perhaps only when each was made, perhaps a picture — and offers to compare the pictures. That is a real answer rather than "0 differences found".

Yes — in the way that works for them, and it offers it plainly. With no text in either file, a word-level comparison can't run, but it can compare the pictures themselves: a pixel mode that boxes the regions that look different, with a sensitivity control for how big a change counts.

Both. A changed line is marked, and within it the words that actually differ.

It warns you. When lines from one place turn up unchanged in another, it flags how many look like they simply moved, and cautions that a small edit inside a moved paragraph is easy to miss — rather than pretending a big reshuffle is a clean set of edits.

Two at a time. Comparing three at once is a different kind of view and not something we have designed.

Ready? Both versions open right here.

Choose the two PDFs

Language

English and Spanish cover the tools and almost every page — six info pages are still English-only: privacy · terms · third-party notices · security policy · status · imprint.