When a text diff in the browser is the right tool
A text diff answers a small, precise question: what changed between these two versions? You do not always need a repository to ask it. People paste two drafts of a paragraph, two log excerpts, two configuration files, or two translations into a page like this because creating a project around a five-minute comparison is ceremony. This homepage tool is for that job. It runs in your browser, marks additions and deletions, and lets you choose whether a “change” means a line, a word, or a character.
If the text already lives in Git, use git diff. If the document is XML, JSON, or source code you want to discuss with a specialised explanation, start on those tool pages instead. Come here when the material is plain text, or when you specifically need word-level or character-level marks.
Line, word, and character modes
Line mode is the default. It is the right starting point for code, logs, lists, and configuration, where a line is already a useful unit. Split view keeps the original on the left and the modified text on the right, with line numbers aligned. Unified view lists every line with a plus or minus prefix.
Word mode is for prose. If a sentence is the same except for one date, a refund window, or a translated term, a line diff paints the whole sentence red and green. Word mode marks only the tokens that moved, which is usually what an editor, a translator, or a reviewer actually needs to see.
Character mode goes one step further. Use it on short strings: an identifier that changed spelling, a URL with an extra slash, two product codes that differ by a digit. On a long paragraph it is noisy, so switch back to words or lines when the text gets longer.
The refund window is 14 days.
The refund window is 30 days.In line mode this is one removed line and one added line. In word mode, “14” and “30” are the marks that matter; the rest of the sentence stays put. That is the usual reason to leave line mode when you are not reading code.
Use cases
Editing copy, a contract clause, or a translation
Two versions of a paragraph often differ by a deadline, a party name, or a single verb. Word mode makes that edit obvious, and keeps the unchanged words as context so you can see whether the sentence still reads correctly.
Comparing logs or configuration that is not XML or JSON
Environment files, nginx snippets, and plain-text logs are still lines of text. A line diff shows a new flag, a changed port, or a missing line without asking you to parse a format first. When the file is structured XML or JSON, use XML Diff or JSON Diff instead, so formatting can be normalised first.
A quick look before the change goes into Git
Sometimes you only have two pastes, and you want to know whether they are worth committing. This page will show you the edit. It will not keep history; once you decide the change is real, the right place for it is still a repository.
How the comparison works
You paste the older or expected text on the left and the newer text on the right, then choose Compare. Nothing is sent to a server. The result is computed locally, which is why there is no account and no upload progress bar. You can load a short sample, swap the sides, copy a unified result, or clear the panes when you are finished.
The tool does not validate a file format, does not merge conflicts, and does not connect to GitHub. Identical texts are reported as such. If the two sides differ only by trailing spaces or line endings, those differences will show up, because they are real differences in the pasted bytes even when they are hard to see in an editor.
How to compare text here
- Paste the original text on the left, or load the sample to see the layout with example input.
- Paste the modified text on the right.
- Choose line, word, or character mode, then Compare.
- In line mode, switch between split and unified views if you want a different reading. Use Swap if the sides are reversed, and Clear when you are done.
Frequently asked questions
Is my text uploaded to a server?
No. The comparison runs in this browser. Closing the tab discards what you pasted. Do not paste secrets, passwords, or private documents if you would not be comfortable with them sitting in memory on this device.
When should I use line, word, or character mode?
Line mode is the default and is best for code, logs, and any text where a line is a meaningful unit. Word mode is better for prose, translations, or a legal sentence where only a few words changed. Character mode is for short strings that differ by typography or spelling, such as identifiers or URLs.
How is this different from Code Diff or XML Diff?
The homepage tool is a general text comparison and is the only one of the three that offers word and character modes. Code Diff is the same line comparison with a code-oriented explanation and sample. XML Diff adds a pretty-print step for tag-based documents. If your file is XML, JSON, or HTML, start on the specialised page.
Should I use this instead of git diff?
Use Git when the text already lives in a repository and you need history, branches, or a patch. Use this page when you have two pastes or exports that are not in a repo. An online diff is not a substitute for version control.
Can I compare files from my computer?
You can paste their contents here, or use File Diff to select two local text files. Nothing is uploaded in either case.
Is there a size limit?
There is no server-imposed limit. A few thousand lines is comfortable. Very large dumps may make the page feel slow; compare a smaller excerpt or use a local tool in that case.