Text diff checker
Paste your two texts below. Every line, word and letter that moved gets marked, nothing else.
How this text diff checker compares two texts
It lines up your two texts and shows only what actually moved: the lines that match stay plain, the lines that do not get marked as added, removed or changed, and inside a changed line only the exact words or letters that differ get highlighted. Typing "colour" on one side and "color" on the other highlights just the extra "u", not the whole word, and a single line added near the top does not make every line after it look different, which is the test a lot of simpler comparison tools fail.
What algorithm does it use, and why
This runs Myers' algorithm, the same approach behind the diff you see in Git and most code editors (Eugene Myers published it in 1986, and it is still the standard). A line by line equality check marks everything after an insertion as changed, because it just compares text at the same position on both sides. Myers instead finds the longest run of lines the two texts already share and builds the diff around that, so inserting one line only shows up as one insertion.
How big a document can it handle
Comfortably up to a few thousand lines each side, instantly. Past 10,000 lines on either side, only the first 10,000 are compared and a note says so. If two texts are so different that finding the best match would take too long, this switches to a quicker line by line comparison instead of freezing, and tells you when that happens. Two 5,000 line documents with a few dozen scattered word changes compare in well under a tenth of a second on an ordinary laptop.
Why two texts with different line endings showed no difference
Windows saves a line break as two characters, Mac and Linux save it as one, and that mismatch alone used to make an entire file look rewritten when nothing in it had actually changed. This checker ignores that difference by default, which is why a file copied between the two looks identical here even though the raw bytes differ. Turn off "Treat different line endings as equal" if you specifically need to catch that mismatch.
Does it catch moved or reordered lines
No, and no text diff built this way does. A line that moved from the top of the file to the bottom shows up as removed from its old spot and added at the new one, not as a single move, because the algorithm is matching content, not tracking where a line travelled to.
What counts as similar
The similarity percentage is twice the number of matching lines divided by the total number of lines in both texts combined, the same ratio Python's difflib.SequenceMatcher.ratio() uses. Two identical texts score 100. Two texts that share nothing score 0, even if they happen to be the same length.
Does any of this get uploaded anywhere
No. Both texts are compared entirely in your browser and never leave your device. They are kept in this browser's local storage so a reload does not lose your work, and clearing the boxes clears that copy too.
Related tools
Everything here runs in your browser. Nothing you type is sent anywhere or stored on our side.