How do I find the differences between two texts?
Paste one version into each box. Differences are highlighted at once: green for added text, red for removed text, with a count of changes above the result.
Every change highlighted. Nothing leaves your browser.
Your text never leaves this device.
Paste two versions of a text to see exactly what changed: added parts are highlighted in green and removed parts in red, by line, word or character. Switch between side-by-side and inline views, and ignore whitespace or letter case when they do not matter. The comparison runs in your browser.
Paste one version into each box. Differences are highlighted at once: green for added text, red for removed text, with a count of changes above the result.
Use line level for code, lists and long documents to see which lines changed. Use word or character level for prose, where small edits inside a sentence matter.
Yes. Turn on “Ignore whitespace” to skip changes in spaces and indentation, and “Ignore case” to treat upper- and lowercase letters as the same.
Yes. Line mode works like a code diff, and you can copy a standard unified diff to share with others or paste into a review.
Copy the unified diff with one click and paste it into an email, chat or ticket. Nothing is stored online, so there is no link to share and nobody else can see your texts.
Yes. Both texts are compared inside your browser and are never uploaded, saved or logged, which makes the tool safe for contracts and confidential drafts.
Line level is best for code, lists and long documents, because it shows which lines changed. Word level suits prose, where a few edited words inside a sentence matter. Character level helps with short strings such as a version number, an ID or a typo that is hard to see. Switching levels does not change your text, so try all three.
Turn on "Ignore whitespace" when text was copied from Word, an email or a web page and the spaces and indentation differ, but the words do not. Turn on "Ignore case" when a tool changed capitalization and you only care about content. Leave both off when exact characters matter, as in a contract number or a line of code.
Format both with the JSON Formatter first, using the same indentation and sorted keys, then compare them in line mode. Otherwise a different key order or indentation fills the result with changes that do not matter. The same idea works for text that went through a different capitalization: run both through the Case Converter before you compare.
Put the original on the left and the changed text on the right, so green means added and red means removed. Moved blocks appear as one deletion and one insertion. You can copy a unified diff and paste it into an email, a chat or a review ticket. Nothing is stored online, so there is no link to share.
A last tip for edited drafts: after you see what changed, paste the new version into the Word Counter to check that it still fits its length limit. Formatting such as bold or colors is not compared; only plain text is.
Do not swap the two sides by accident; the colors depend on which text is the original. Do not compare text with very different line breaks in line mode without ignoring whitespace, or every line will look changed. And do not treat a clean result as proof that two files are the same when the formatting is part of the content, since only plain text is compared.
| This tool | Upload-based services | |
|---|---|---|
| Is your text sent to a server? | No | Usually |
| Account required | No | Sometimes |
| Length or usage limit | None | Often |
| Saved or logged | Never | Possibly |
Assistants easily miss small changes in long texts. The diff_text MCP tool, available remotely and locally, returns the exact additions, deletions and a unified diff, for example when checking what changed between two contract drafts.