Documentation

Everything you need to check two documents.

From your first comparison to running DocDiff from your own systems.

Getting started

A comparison takes four steps, and most finish in a few seconds.

Sign inEnter your email and the 6-digit code we send. No password.
UploadAdd the earlier version and the later version.
ReadEvery change is listed, ranked and linked to its page.
ReviewMark each change correct or wrong, then share or download.
  1. Open the app and enter your work email. We email you a 6-digit code that works once and expires in 10 minutes.
  2. The first time you sign in, accept the Terms of Service and Privacy Policy. DocDiff creates a workspace for you, or adds you to the workspace you were invited to.
  3. Drop the earlier version on the left and the later version on the right, then choose Compare files.

Files and limits

FormatWhat DocDiff reads
PDFText with its page and line, and ruled tables cell by cell. Scanned pages are read with OCR.
Word (.docx)Paragraphs, headings and tables.
Excel (.xlsx), CSVEvery sheet, matched row by row, so moved rows don't show as changes.
HTML, text, MarkdownText, headings and tables.
Images (PNG, JPEG, TIFF)Read with OCR, like scanned pages.
  • The two files can be different formats, for example a PDF against a Word file.
  • Each file can be up to 200 MB. Documents of thousands of pages are fine: a 1,349-page pair takes about 20 seconds on a 12-core machine, longer on smaller servers.
  • Comparing the same two files again returns the saved result at once.

Running a comparison

Two versions

Upload the earlier and later versions. Two options help with larger files:

  • Part to compare: when a file holds several documents (for example tabs in a workbook or parts of a manual), name the part, such as File #1 or Part A, to compare only that part.
  • Written summary: adds a short plain-English summary of the most important changes. Each sentence points to the changes it describes, so you can check it.

One file

Leave the later version empty to check one file for inconsistencies, such as the same item listed with two different values.

Reading the results

Each change says what changed, where (document, page and location, or sheet and cell), and how much it matters.

LevelMeaning
CriticalChanged amounts, rates, dates, codes and percentages, and added or removed rows or clauses.
MajorOther changed numbers, sections and references, and changed wording.
MinorChanges to descriptions that don't affect values.
HiddenNoise such as bookkeeping columns. Hidden by default; show them with the filter.

Changes that differ only in capital letters or spacing are left out. Changed words inside a sentence are highlighted, so you can see the difference without rereading the line.

Reviewing changes

  • Correct or wrong: mark each change. Your decision and its history are saved for your team.
  • Report a missed change: tell us about anything DocDiff didn't find. We use these reports to improve it.
  • Side by side: when both files are PDFs, the two documents open next to each other and each change jumps to its spot.
  • HTML report: download a report of every change to share or archive.

Keyboard: j and k move between changes, c marks correct, w marks wrong.

Teams and roles

Everyone in a workspace sees the same comparisons and reviews. Admins invite people by email; the invitation lasts 7 days.

RoleCan
OwnerEverything, including adding or removing other owners. A workspace always keeps one.
AdminInvite and manage members, create API keys, rename the workspace, and everything a reviewer can.
ReviewerRun comparisons, mark changes correct or wrong, report missed changes.
ViewerRead comparisons and reports.

You can belong to several workspaces and switch between them from the menu. Sign out everywhere ends your sessions on every device.

API

Admins create API keys in the workspace menu. Each key has a role, and you see it only once, so store it safely.

curl -X POST "https://orivantlabs.com/comparisons?wait=30" \
  -H "X-API-Key: $DOCDIFF_KEY" \
  -F baseline=@contract-2025.pdf \
  -F revised=@contract-2026.pdf

The answer includes an id and a status. With wait, the call waits up to that many seconds (at most 120) for the result. Otherwise, read GET /comparisons/{id} until status is done; the result lists every change with its location.

  • POST /checks checks one file for inconsistencies.
  • GET /comparisons/{id}/report returns the HTML report.
  • The full reference is at /api/docs.

Your data

  • Files and results stay in your workspace. People in other workspaces can't see them.
  • Data is encrypted in transit (HTTPS) and at rest.
  • Your files are never used to train AI models. The optional summary is written by an AI model that receives only the list of changes, not your files.
  • Sign-in codes, sessions and API keys are stored only as secure hashes.
  • To delete your files or your account, email privacy@orivantlabs.com.

Details are in the Privacy Policy. Please don't upload documents containing patients' health information or other sensitive personal data unless we've agreed to it in writing (see Acceptable Use).

How we test

DocDiff's comparison engine is exact: it doesn't guess, and the same two files always give the same result. We measure it against a growing test suite of real public documents, where every true change is known in advance.

  • Recall: of the changes we know about, how many DocDiff finds. In October 2026 it found all of them across 16 document pairs, including 842 changed codes in one pair.
  • False alarms: changes reported that aren't real. There were none across the same suite.
  • Speed: under 2 seconds for a 20-page pair, about 20 seconds for a 1,349-page pair on a 12-core machine (measured with nothing cached).

Every change marked wrong, and every missed change reported, can become a new test case, so the suite keeps growing.

Getting help

Email support@orivantlabs.com or use the contact form. We reply within 2 business days. To report a security issue, write to security@orivantlabs.com.