A diff highlights what changed between two texts: additions, removals, and sometimes moves. It is used in code review, config audits, and content comparison.
Version control shows diffs between commits. Seeing line-level changes helps reviewers catch bugs, secrets, and unintended edits before they ship.
The UI shows differences according to the implementation on the page—often line-based for prose and configurable views for finer detail.
Yes. Invisible trailing spaces can mark lines as different. Normalize with the clean text tool if you want to ignore those differences.
For structural JSON comparison, format both sides with the JSON formatter first so indentation and ordering do not create noise in the diff.
Classic diff algorithms find shared structure between sequences to minimize edit steps. That math powers readable diff output in tools and Git.
Textual diff compares bytes or lines. Semantic diff understands language structure (e.g., AST for code). This browser tool is textual unless noted otherwise.
A merge conflict is overlapping edits. Diffs help you see both sides and choose or combine changes; understanding plain diffs builds intuition for merges.
Very large inputs can be slow or unwieldy in the browser. Consider chunking by section or using specialized desktop tools for multi-megabyte files.
Windows CRLF vs Unix LF can make identical content look changed. Normalizing line endings avoids false positives when comparing cross-platform files.