Text Diff

What is Text Diff?

Text diff, short for “difference,” is the process of algorithmically comparing two blocks of text to identify exactly what was added, removed, or changed between them. Under the hood, most diff tools use a variant of the Longest Common Subsequence (LCS) algorithm, which finds the longest sequence of lines shared by both inputs and then marks everything else as a change. Additions are typically highlighted in green, deletions in red, and unchanged lines serve as surrounding context so you can orient yourself within the file. The concept dates back to the Unix diff command, first released in 1974 as part of the Fifth Edition of Unix. Today, diff is the foundation of every version control system—Git, Mercurial, and SVN all rely on it to track history, generate patches, and resolve merge conflicts. This tool runs the comparison entirely in your browser using the Monaco Editor’s diff engine (the same one that powers VS Code), so your text is never transmitted to a server. That makes it safe to compare proprietary source code, credentials files, or any other sensitive content.

Common Use Cases for Text Comparison

The most frequent use case is code review: comparing a file before and after a set of changes to verify that a bug fix, refactor, or feature addition looks correct. But diff is useful far beyond code. DevOps engineers diff configuration files—Nginx configs, Kubernetes manifests, Terraform plans—to audit what changed before deploying to production. Legal professionals and editors use text comparison to track revisions across contract drafts or policy documents, where a single word change can alter the meaning of an entire clause. Database administrators compare schema migration files to ensure ALTER TABLE statements match expectations. API developers paste two JSON or XML responses side by side to spot regressions after an endpoint update. QA teams diff build outputs between release candidates to verify that only intended changes shipped. System administrators compare environment variables or .env files across staging and production to catch misconfigurations before they cause downtime. Content teams use it during editorial workflows to see a clean summary of changes an author made between draft revisions, rather than reading two entire documents from scratch.

Understanding Diff Output

Diff tools present results in several formats. Unified diff, the format used by git diff, shows removed lines prefixed with - and added lines prefixed with +, grouped into “hunks” that each begin with an @@ header indicating the line numbers affected. Side-by-side view (the default in this tool) places the original and modified text in parallel columns, making it easy to scan large files visually. Inline view interleaves additions and deletions within a single column, which works better on narrow screens or when changes are sparse. Modern diff engines go further with word-level (intraline) highlighting: even when an entire line is flagged as changed, the specific characters that differ are highlighted within it, so you can instantly spot a renamed variable or a single-character typo. The .patch export from this tool produces a standard unified diff file that can be applied directly with git apply or the patch command-line utility. Related concepts include three-way merge, which compares two changed versions against a common ancestor to automatically resolve non-conflicting edits—the mechanism behind git merge and pull request conflict resolution.