Compare two text blocks line-by-line with an LCS-based diff algorithm.
This tool runs 100% in your browser. All computation happens locally on your device — your input is never uploaded to any server. Results are for reference only.
This tool aligns the two texts by finding the longest common subsequence (LCS) of lines. Lines that match stay anchored in place; a removed line that sits next to an added line is treated as a modification pair (− old next to + new); everything after a gap is flagged as purely added or removed. That anchor = context, so a one-line edit doesn't renumber everything below it.
Same prefix/suffix lines are matched first (anchors). In the middle, a removed-old/new-added pair is shown side-by-side as a 'modified' block. Purely inserted or deleted lines keep only one side colored.
Two short blocks that share an opening line but diverge.
To compare texts: paste two versions of text into the panels — the tool highlights added, removed, and changed lines side by side, useful for code review and document comparison.
FreeToolHub Diff Checker is a free browser-based tool that compares two texts and highlights differences line by line, no signup, no upload.
Compare two blocks of text or code side by side and highlight every difference line by line. Free, no signup, files never leave your browser.
This tool compares two blocks of text or code and highlights every difference line by line: added lines, removed lines, and changed lines marked in place, with unchanged context around each difference so you can read the changes in position. It handles plain text, configuration files, logs, JSON, CSV, and any code where line structure matters. Comparison runs entirely in your browser — neither text is uploaded, which is the difference that matters for contracts, credentials, and client files.
Reviewers comparing contract or policy revisions to confirm only the agreed changes were made. Developers comparing config versions, log outputs, or API responses where a one-character difference matters. Writers reconciling edited drafts from collaborators. QA engineers verifying before-and-after outputs. Anyone who received version 2 of a document and does not trust version 1 to still be what they agreed to.
(1) Paste the original text in the left pane and the modified text in the right. (2) The diff algorithm aligns both sides and computes the minimal set of changes between them. (3) Differences render inline: removed lines marked on the left context, added lines on the right, with unchanged lines shown for position. (4) Scan or jump difference to difference; counts of added and removed lines summarize the change size. (5) Nothing is sent anywhere — the comparison happens locally, and closing the tab clears it.
A visual diff is only as useful as the reading discipline behind it, and the failure mode is scanning for expected changes while unexpected ones slip past. Read every hunk, not just the ones near what you were looking for — the changes you did not anticipate are the point of running the diff. For contracts and legal documents, hunt specifically for altered numbers (rates, dates, term lengths, thresholds), shifted obligations (party names swapped inside clauses), deleted qualifiers (reasonable, commercially reasonable, material), and modified termination or liability sections — small edits there carry the biggest consequences. For code and config, watch for whitespace-only changes masking real ones, changed defaults and fallbacks, and reordered lines that alter evaluation order. Normalize before comparing when it helps: strip trailing whitespace or line-ending differences (CRLF versus LF is the classic false-positive generator between Windows and Mac files) so the diff shows meaning, not encoding. And keep the original until the modified version is accepted — a diff you cannot reproduce is not evidence.
It uses the LCS (Longest Common Subsequence) algorithm to identify the longest sequence of lines common to both texts. Lines present in one text but not the other are marked as additions (+) or deletions (-). Unchanged lines are shown as context. The result is displayed side-by-side or inline with color highlighting: green for additions, red for deletions.
Yes. Paste two blocks of text or code (up to 50,000 characters each). The diff checker handles all text formats including source code, configuration files, JSON, XML, and plain text documents. It ignores no content by default—every character difference is shown. Use the inline view for a unified diff or the side-by-side view for a visual comparison.
What do you call a crab that plays baseball?
No paywalls, no signups, no data sold. Built by a solo developer who believes useful tools should be accessible to everyone.
☕Support me on Ko-fi— keep tools free100% of proceeds go towards hosting & building more free tools.