Text Diff Checker
Paste two versions of a text, config, or log and see exactly what was added, removed, and changed — all in your browser
Text
0 lines
0 lines
Line endings (CRLF/CR) are normalized to LF before comparing, so text that differs only in line endings shows no diff.
Options
Never Leaves Your Browser
Both texts are compared locally — no upload, no server
Side by Side or Unified
Switch views and compare by line, word, or character
Copy a Unified Diff
Export the result as plain -/+ patch text for a commit or ticket
Frequently asked questions
Why does my diff show every line as changed when I only edited one word?
That happens with line granularity: jsdiff compares whole lines, so any edit inside a line — even a single character — marks the whole line as removed and its replacement as added. Switch to Word or Character granularity to see the actual edit highlighted within the line instead.
Why do two files that look identical show no differences one time and a full diff another?
Line endings. Windows tools write CRLF (\r\n), Unix tools write LF (\n), and a byte-for-byte diff would flag every single line as changed even though the visible text is identical. This tool normalizes both inputs to LF before comparing, so a line-ending mismatch alone never shows up as a difference.
What is the difference between side-by-side and unified view?
Side-by-side puts the original and changed text in two columns so you can read each version in full. Unified shows one column with a +/- gutter, closer to a git diff or patch file — it is more compact and is what "Copy unified diff" exports. On narrow screens the tool switches to unified automatically since two columns do not fit.
Does my text get uploaded anywhere?
No. The comparison runs with the jsdiff library entirely inside your browser tab. Nothing is sent to a server, so pasting sensitive text — credentials, private notes, unreleased code — never leaves your machine.