How to Compare Two Files and Find Every Difference Diff Tools Explained

What a Diff Tool Does

A diff tool compares two versions of text and outputs exactly which lines were added, removed or changed. It tells you what appears in version B that was not in version A, what was in A that is no longer in B and what is identical in both.

The name comes from the Unix 'diff' command which has been a standard part of Unix and Linux systems since 1974. Every modern development workflow relies on diff in some form. Git's 'git diff' command, code review tools on GitHub and GitLab, merge conflict resolution in every IDE and online tools for quick comparisons all use the same underlying concepts.

Understanding the Output Formats

Unified diff shows both versions in a single column. Removed lines appear with a minus sign and typically a red background. Added lines appear with a plus sign and a green background. Lines unchanged in both versions appear without any marker. This is the format Git uses in the terminal. It is compact and good for following the logical flow of changes.

Split diff shows the two versions side by side, original on the left and modified on the right. Changed sections align with each other across the columns. This format makes it easier to see exactly what was replaced because you see the before and after simultaneously.

Word-level inline diff goes deeper than line-level comparison. When a line is modified rather than completely replaced, the tool highlights the specific words that changed within that line. Instead of showing the entire old line and entire new line, you see precisely which words were added or removed within the changed line.

The Algorithm Behind It

Most diff tools use the Myers diff algorithm, published by Eugene Myers in 1986. It finds the minimum number of insert and delete operations needed to transform one text sequence into another.

The algorithm identifies the longest common subsequence of lines that appear in both files in the same order. Those are the unchanged lines. Everything not in the common subsequence is either an insertion or a deletion.

This is why diff output sometimes looks surprising. The algorithm optimises for the fewest total changes, which occasionally groups them differently than a human would expect. Large refactors where code moves around rather than just changes can look messier than the actual change was.

Practical Uses

Code review before merging branches. Document revision tracking between contract or report drafts. Configuration file auditing to spot unauthorised changes. Debugging regressions by finding what changed between a working and broken version. Content monitoring to track changes to web pages or API responses over time.

Using the Diff Checker

Paste original text in the left panel and modified text in the right. The tool uses the LCS algorithm to produce line-level diff with inline word-level highlighting for changed lines.

Switch between Split view, Unified view and Summary view based on preference. Toggle Ignore Whitespace to skip formatting-only differences. Toggle Ignore Case for case-insensitive comparison. Adjust context lines to show more or fewer unchanged lines surrounding changes. Export the complete diff as a text file.