Compare texts — see every change
Git-style line diff for contracts, configs and drafts — both versions stay in your tab.
"What exactly did they change?"
The question behind every diff: a contract comes back "with minor updates", a config stops working after an edit, two versions of a paragraph need reconciling. Reading both side by side misses things; a proper LCS diff doesn't. And the documents people compare are precisely the ones that shouldn't touch a server — which is why this one runs as pure algorithm in your browser tab.
Related text tools
Frequently asked questions
How do I compare two texts for differences?
Paste the original on the left, the changed version on the right, hit Compare. Added lines show green with a +, removed lines red with a −, and the summary counts both.
What kind of diff is this?
A line-based LCS (longest common subsequence) comparison — the same family of algorithm behind git diff. It finds the minimal set of added and removed lines rather than naively matching position by position.
Why does privacy matter for a diff tool?
Because of what people diff: contract revisions, config files with credentials, unpublished drafts. Both texts stay in this tab — no server sees either version, let alone both.
Can I compare code with it?
Yes — line-based diffing is exactly how code review works. Indentation counts as content, so mixed tabs/spaces will show as changes (which is usually worth knowing anyway).
Is there a size limit?
A practical one: beyond a few thousand lines per side the tool asks you to trim to the relevant sections rather than freezing your tab. Typical documents and configs are nowhere near it.