CompleteToolkit

Diff Checker

Compare two texts and see every added and removed line highlighted — like git diff, in your browser.

About this tool

"What changed between these two versions?" is one of the oldest questions in working with text, and eyeballing two documents side by side is the least reliable way to answer it. A diff checker answers it mechanically: paste the original on the left, the new version on the right, click Compare, and every difference is highlighted — removed lines in red with a − sign, added lines in green with a +, unchanged lines left plain for context.

Under the hood this uses a longest-common-subsequence algorithm — the same family that powers git diff — which is why the output feels familiar if you've ever reviewed a pull request. A changed line appears as its old version removed and its new version added, adjacent, so the edit reads naturally. The summary line counts additions and removals at a glance, and explicitly tells you when the two texts are identical — sometimes the most useful answer of all, instantly settling "did anything actually change?"

Practical uses are everywhere: comparing contract revisions a client sent back, checking what a colleague edited in your copy, verifying two config files match across environments, or spotting the one-line difference between working and broken code. Both texts stay in your browser — safe for contracts, credentials-adjacent configs and anything else you'd rather not upload to compare.

How to use the Diff Checker

  1. 1Paste the original version in the left box.
  2. 2Paste the changed version in the right box.
  3. 3Click Compare.
  4. 4Read the result: green + lines were added, red − lines were removed; the summary counts both.

Frequently asked questions

How does the comparison work?

Line by line, using a longest-common-subsequence algorithm — the same approach behind git diff. It finds the largest set of lines the two texts share, then marks everything else as added or removed.

Why does an edited line show as one removed plus one added?

Because line-level diffing treats a modified line as its old version disappearing and its new version appearing. The two are shown adjacent, so the change reads naturally — exactly as code reviews display edits.

Does it detect changes within a line, like one word?

The granularity is the line: a line with a single changed word is shown as removed-then-added in full. Reading the red and green pair side by side makes the changed word easy to spot.

Can I compare sensitive documents safely?

Yes — both texts are processed entirely in your browser and never uploaded, which makes this safe for contracts, internal documents and configuration files in a way that upload-based comparison sites aren't.