Someone sends back a contract "with a few small changes". A config file works on one server and not another. A translation was edited by three people. In each case you have two versions and one question: what is different? Reading both and trying to spot it by eye is how changes get missed. The Text Diff Checker compares them line by line and marks every addition and removal. This guide shows how to use it for different jobs, and how to read the result.
What it compares
The tool compares two texts line by line with the Myers diff algorithm, the same approach git uses. A line that exists only on the left is marked as removed (red), and a line that exists only on the right as added (green). A changed line appears as one removed and one added line, so a single word edited in a long line shows the whole line twice; this is how line-based comparison works. Inputs over about 200 KB are processed in a background worker so the page stays responsive. Nothing is uploaded.
Step by step
- Paste the original text in the left box and the changed version in the right box. Or use the upload button on either side to load a plain-text file: .txt, .md, .json, .js, .ts, .css, .html, .xml or .csv. Dropping a file onto a box also works.
- Choose the View: Side by side, Unified or Inline.
- Decide what to ignore with the switches: Ignore whitespace, Ignore case. Turn Line numbers on or off.
- Read the Differences section. You can copy the diff as plain +/- lines or swap the two sides.
Which view
| View | Looks like | Best for |
|---|---|---|
| Side by side | Old on the left, new on the right, aligned | Reading changes in prose or code, with context |
| Unified | One column with - and + lines, like a patch | Pasting into a ticket, a chat or a review |
| Inline | One column with changes marked in place | Narrow screens such as a phone |
Ignoring noise
Many "differences" are not changes in meaning. Two switches remove the noise.
- Ignore whitespace treats runs of spaces and tabs as a single space and trims the ends of lines. Use it when text was re-indented, when a program converted tabs to spaces, or when trailing spaces differ. Line breaks are never ignored: a paragraph that was rewrapped to different line lengths still shows as changed.
- Ignore case compares lines without regard to upper or lower case. Use it for lists of names or codes where capitalisation changed.
Switch them on one at a time. If a difference disappears when you turn on whitespace, you know that it was only formatting. Turn them off again for legal or code reviews where such things matter, such as a space inside a quoted string.
Jobs and how to approach them
Contracts and documents
Copy the text of both versions as plain text from the documents. Different line breaks from the PDF or word processor will create many false differences, so also try the same text with Ignore whitespace. Do not rely on the tool for formatting changes, such as bold or table layout, which are lost when you paste as plain text. Review the full document yourself as well when the stakes are high.
Config files and code
Paste the working and the failing version. Hidden differences, such as a trailing space, a changed line ending or a different quote character, often explain "it works on my machine". For JSON, format both with the JSON Formatter with Sort keys on, so key order does not create false changes.
Translations and copy edits
Compare the file before and after review. The unified view gives a compact list of changed lines to send back to the editor.
Lists and exports
Two exports of the same list, such as emails or product codes, show what was added and removed. Sort both lists first, because the comparison depends on order.
Reading results correctly
- Moved text shows as a removal and an addition. The algorithm does not detect moves; a paragraph moved elsewhere appears twice.
- Whole-line marks. If only a comma changed, the entire line is marked; look inside it for the actual difference.
- "No differences" means that, with your current settings, the texts are the same. Check that the ignore switches are off if you expected an exact match.
If you only want a single number for how close two texts are, use Text Similarity, which can then open the two texts in the diff checker.
Limits
It compares plain text. It does not read Word, PDF or spreadsheets; copy the content out as text. Very large files work, but the page may take a moment to show the result. For a project with many files, git or an editor with a built-in diff is the better tool.
Sharing what you found
To send the changes to someone, switch to the unified view and copy the diff as plain lines starting with a minus or a plus. Pasted into a ticket, an e-mail or a chat, the lines show exactly what was removed and what was added, without screenshots. Add one sentence of context above it: which files or versions you compared and which switches were on, because someone repeating the comparison with Ignore whitespace on will see fewer differences. If the comparison is part of a review, keep both original texts, since the diff is only a view of them and does not replace them.
Frequently asked questions
Is my text uploaded anywhere?
No. The comparison runs in your browser.
Why are unchanged lines marked as changed?
Probably a difference in spaces, line endings or case. Try the Ignore switches.
Can I compare more than two texts?
Compare them in pairs.