Find Text Differences: Paste, Don't Upload
Docify finds differences between two pasted strings, not between uploaded documents. Compare runs diff_main then diff_cleanupSemantic in the browser. Load sample Compare writes a deleted brown beside an inserted red, keeps the shared jump equal and paints a deleted s beside an inserted ed, then a deleted lazy beside an inserted sleeping. There is no .pdf, .docx, or image picker, and no line-based git output. Nothing is uploaded.
“Document comparison” in Word, Acrobat, or a legal review platform means files. The text diff means two textareas. If you already copied the wording out of a contract or a README, paste it. The page will not open the file for you. Load sample is that same pasted-string path: it fills the pangram pair and does not run Compare.
What you can compare
Plain text you paste
Drafts, paragraphs, config snippets, or any string you can put on the clipboard. Both Original and Modified must be non-empty before Compare enables. Load sample fills Original with this older line and Modified with the newer one. Compare then deletes brown and lazy and the s after jump, and inserts red, ed, and sleeping. See how Compare paints the hunks.
Not a PDF or Word compare
There is no file input, no page-by-page PDF overlay, and no Track Changes import. Layout, fonts, and signatures are out of scope. Load sample does not attach a document — it only fills those two textareas. For a visual PDF stamp (not a text diff), see the PDF signer.
Not git
The library diffs characters, then groups nearby inserts and deletes. You do not get @@ hunk headers, a three-way merge, or a patch you can git apply. Load sample Compare is not a unified-diff export: after semantic cleanup, jumps vs jumped keeps the shared jump equal. Developers can still paste two versions of a snippet; it is not a code-review product.
Character-level, then semantic cleanup
Google's diff-match-patch walks the two strings character by character. A changed word usually shows as a deleted span beside an inserted span, not as a whole-line replace. Load sample Compare writes a deleted brown beside an inserted red, then later a deleted lazy beside an inserted sleeping. Newlines remain in the text and render as <br> after & / < / > are escaped.
That is useful for copy edits. It is a poor substitute for a binary or layout-aware document compare, and it does not promise that every legal change was caught.
Compare pasted text, not files
Two text boxes, then Compare. Load sample fills the pangram pair and does not run Compare. No upload, no PDF, no git patch.
Use Text Diff →FAQ
- Can I upload a Word document or PDF to compare?
- No. There is no file picker. You paste the text you want compared. Load sample fills Original with The quick brown fox jumps over the lazy dog. and Modified with The quick red fox jumped over the sleeping dog. and does not run Compare. That pair is pasted strings, not a .docx or .pdf. The tool does not extract pages from a PDF, open .docx, or run a three-way merge.
- Is this a line-based git-style diff?
- No. diff-match-patch diffs at the character level, then applies semantic cleanup. Load sample Compare writes a deleted brown beside an inserted red, keeps the shared jump equal and paints a deleted s beside an inserted ed, then a deleted lazy beside an inserted sleeping. That is not a @@ hunk header and not a patch you can git apply. Newlines stay in the text and render as line breaks.
- Can I use this for contract or code review?
- You can paste two plain-text extracts and click Compare. Load sample Compare is that pangram pair — brown→red, jump+s→jump+ed, lazy→sleeping — after semantic cleanup. It is not Microsoft Word Compare, not git, and not a legal-discovery tool. It does not certify that no change was missed.
- Does the result include a “modified” highlight?
- No. Replacements appear as a deletion next to an insertion. Equal text is unhighlighted. Load sample Compare is not three whole-word swaps: jumps vs jumped keeps jump equal. This is pasted-text compare only.