Compare PDFs
Availability: not available. At the time of writing, Compare PDFs has no web page, no CLI plugin, no MCP tool and no API endpoint in Documentize. The project folder for it is empty and the capability catalogue lists document comparison as a known gap. (Do not confuse it with the candidate-versus-job scoring inside Resume Analyzer, which compares a CV to a job description, not two PDFs.) This chapter gives you the best working method today. If the app is released, check the live site and What's new.
In one sentence
Comparing two versions of a PDF means finding exactly what changed between them, and today you do it by turning both into plain text and comparing the text.
What makes it unique
Nothing yet. What is worth knowing is why it matters in this family: after a negotiation round, the dangerous change is the one nobody mentioned. A comparison is the control step before you sign (Sign) a "final" file.
When to use it / when not to
- You need a comparison when two versions of a contract, policy or report circulate and you must see all differences, not just the ones the other party flagged.
- A comparison will not help when the pages are scans without a text layer. First make them searchable with Searchable, or the text of both is empty.
- It cannot tell you whether a change is acceptable. It only shows what moved.
Before you start
- Have both versions as PDFs: the earlier and the later.
- If either is password-protected, unlock it first with Unlock.
- If either is a scan, run Searchable first so there is text to compare.
- Make sure both come from the same kind of source. A Word-exported version compared with a scan of a printed copy will show differences everywhere.
Step by step
A practical workaround with Documentize plus any text-difference tool you already have (a code editor, or the "compare documents" function in a word processor):
- Run version A through Extract Text. Download the text.
- Do the same for version B.
- Open the two text files in a text-comparison tool and read the highlighted differences.
- For differences you cannot judge from text (images, layout, signatures), open both PDFs side by side in your viewer, and use Extract Image to compare pictures.
- Check Extract Metadata on both for changed author, dates or producer.
- Record the verdict, then continue with the rest of the chain.
📷 Screenshot placeholder: none, because there is no page.
Options explained
| Option | What it does | Default | Recommended |
|---|---|---|---|
| – | No options exist, because the app does not exist | – | – |
What you get
A text-level view of the changes, produced by your own comparison tool. Documentize does not produce a "changes" document. Your originals are never modified.
Quality & limits
- A text comparison misses changes to images, signatures, layout, fonts and hidden items.
- Different line breaks and page numbers can create false differences. Extract with the same setting for both versions.
- For legally important comparisons, use a dedicated document-comparison product and keep its report.
- AI chat apps (Ask PDF) can describe differences, but their answers are drafts, not proof: see Trust, verification and limits.
Works well with
- Use before: Unlock, Searchable.
- Use after: Flatten, Sign and Verify Signature.
- Recipes: Contract round-trip, Screen candidates (a different "compare"; see the note at the top).
Common mistakes & fixes
- "Everything is different." One version is a scan or was exported with other fonts; compare like with like.
- "No differences found, but the file is bigger." The change may be in images, metadata or hidden content.
- "I compared after signing." A signed file must not be changed; compare before signing.
Same thing elsewhere
- CLI: none. MCP: none. API: none for PDF comparison.
Try it
Take a two-page PDF and make a copy with one number changed (for example 1,000 to 10,000) by editing the source document and exporting again. Extract the text of both and compare in a text tool. Can you spot the change in under a minute, and would you have caught it by reading?