Paste two versions, see exactly what changed. Press Ctrl + Enter to compare instantly.
Paste text into both boxes, drop in two files, or start with a ready-made pair and poke around.
Whether you are chasing a stray comma in a contract or a missing bracket in a config file, this guide covers what a diff checker does, how to read what it shows you, and how to keep the results readable.
A diff checker takes two versions of a text and shows you precisely what is different. Instead of reading both copies side by side and hoping your eyes catch every edit, you paste each version in and let the tool mark the lines that vanished, the lines that appeared, and the exact words that were swapped.
The name comes from diff, a Unix command from the 1970s that programmers used to see how one file had drifted from another. The same trick now helps editors track revisions, lawyers review contract changes, and anyone who has ever asked, “So what did you actually change?”
Plenty of tools can tell you two texts are different. The useful ones tell you where, by how much, and whether it matters. Here is what you get in this one.
Edit either box and the comparison refreshes a heartbeat later. Prefer to stay in control? Switch Live off and press Compare when you are ready.
Side by side on a desktop, stacked like a patch file when you need a single column. Phones get the stacked layout on their own.
Pick line, word, or character precision to catch a single swapped letter.
A slim strip shows where changes cluster. Tap N or P to hop between them.
Drag a .txt, .md, .json, .csv or source file onto either panel. Up to 5 MB each.
Copy or download a standard unified patch.
The comparison runs inside your browser tab. Nothing is uploaded, stored, or logged, so drafts, contracts and credentials-adjacent configs stay yours.
Checking a two-line snippet is easy. Checking a forty-page policy or a 5,000-line export is where a sensible routine saves your afternoon.
Paste into each box or drop the files straight in. Older text goes on the left, newer on the right.
Reflowed paragraphs or re-indented code? Turn on Ignore whitespace before you look at anything.
Switch on Hide unchanged lines. You keep three lines of context around every edit, and can unfold any gap with a click.
Use the minimap, the arrow buttons, or the N and P keys instead of scrolling for pages.
Copy the patch or download a .diff file to attach to a ticket, a pull request, or an email.
The strip beside the results is a thumbnail of the whole comparison. A tight cluster of marks means a heavily edited stretch; empty space means calm. Click anywhere on it to jump there.
Results with more than a few thousand rows fold their unchanged parts automatically so your browser stays quick. If two texts have almost nothing in common, the tool shows the clashing stretch as one big replacement instead of grinding through it. For the sharpest result on a very large document, compare it chapter by chapter.
There is no secret server and no black box. Four small steps run in your browser each time the text or a rule changes.
Both texts are split at every line break, whether it came from Windows, macOS or Linux.
Case and spacing rules are applied to a hidden copy used only for matching. What you see on screen is always your original text.
A Myers-style search, the same approach Git uses by default, finds the fewest removals and additions that turn one text into the other.
Removed and added lines sitting together are paired, then compared again word by word or letter by letter. You see “Name” disappear, not a wall of red.
Most online diff tools handle the basics. The gaps show up when your texts get long, messy, or private. This one was built around those moments.
The right-hand column is a general picture of what you tend to find elsewhere. It varies, so treat it as a rule of thumb.
| What you care about | This tool | Typical online diff |
|---|---|---|
| Updates as you type | Yes, with a manual option | Often needs a button press |
| Edits inside a line | Line, word or character precision | Frequently whole lines only |
| Case, spacing and blank-line rules | All three, free | Sometimes locked behind a plan |
| Finding your way through long results | Minimap, next and previous, folding | Scroll and hope |
| Privacy | Never leaves your browser | Varies from site to site |
| Reading on a phone | Switches to a stacked layout | Often a cramped two-column view |
| Sharing the outcome | Copy or download a patch | Varies |
| Account or sign-up | Not needed | Varies |
If your work involves text that gets revised, you are already the target audience. These are the usual suspects.
A noisy diff is a useless diff. When every line lights up because of a stray space or a different line ending, nothing stands out. A few habits keep the signal strong.
Back to the toolIndentation changes, trailing spaces and doubled spaces are the number one source of false alarms. Switch this on for code, copied web text and anything that was reflowed.
Comparing exported lists, email addresses or headlines? Case is rarely the point. Leave it off for case-sensitive things like variable names.
Extra paragraph breaks should not drown out real edits. This keeps the comparison focused on lines that contain something.
A diff reads order literally. Sort keys, run a formatter, or export both files with the same settings before you paste them in.
Line suits structured data, Word suits prose, Char suits typos and IDs. If the highlights look busy, step one level up.
Hide unchanged lines to review just the edits, then unfold a gap only when you need the context around it.