Skip to content

Text Diff Tool

Compare two texts with aligned line differences. Review whitespace, case and newline policies, inspect both originals, and export a complete text report.

Choose your path

Built around the job you need to finish

Compare two independent originals through bounded line alignment, retaining exact and explicitly ignored differences in a review report.

Developer reviewing a small change

Avoid false changes after a line insertion.

Paste original and revised text separately, compare, inspect original line numbers and hide unchanged preview rows.

Later matching lines stay aligned; full report retains both originals.

Editor reconciling formatting

Separate content changes from intentional whitespace or case differences.

Compare exact text, then enable one normalization policy and inspect equivalent rows.

Ignored differences are disclosed, not mislabeled identical.

Cross-platform maintainer

Review CRLF/LF and missing final terminators.

Import two UTF-8 files, compare before editing, adjust newline policies, swap sides and request the report.

Decoded terminators remain visible; report is not presented as an apply-ready patch.

Was this tool helpful?

Reference & details

How it works

Tokenize lines with their terminators

Each line retains its text and CR, LF, CRLF or absent terminator. Empty lines are real tokens. Imported UTF-8 preserves decoded endings; editing or pasting through a textarea can normalize them.

Align with bounded sequence comparison

The pinned jsdiff engine aligns line keys under explicit whitespace, ending and case policies. Limits are 100,000 characters and 2,000 lines per side, 2,000 edits or 1.5 seconds for alignment, and a 10-second outer worker timeout.

Retain the originals in the review

Rows are added, removed, exactly unchanged or equivalent under selected options. Report text quotes original values and terminators. Moves are edits, repeated lines may align in different valid ways, and the report is not a patch.

Updated: August 2026

Example Scenarios

Avoid false changes after a line insertion. Paste original and revised text separately, compare, inspect original line numbers and hide unchanged preview rows.

Separate content changes from intentional whitespace or case differences. Compare exact text, then enable one normalization policy and inspect equivalent rows.

Review CRLF/LF and missing final terminators. Import two UTF-8 files, compare before editing, adjust newline policies, swap sides and request the report.

Common Mistakes to Avoid

Calling normalized text byte-identical

Equivalent means a chosen policy ignores differences; check both original values.

Applying the report as a patch

It is a human review report, not a unified diff or merge instruction.

FAQ

They avoid reserving a separator string and introducing artificial newline boundaries. The old separator token is now ordinary content.

No. Whitespace, case or line-ending differences hidden by your policies are labeled equivalent, and both original values remain in the report.

Import UTF-8 files and compare before editing to retain decoded CRLF/LF distinctions. You can normalize endings for comparison or ignore the last terminator explicitly.

No. It aligns lines and reports insertions/deletions. There is no character-similarity percentage, semantic move recognition, merge or patch application.

The worker refuses oversized input or stops at its budget without a partial result. Editing source or policies cancels stale work. Copy and UTF-8 .txt export include the full current report, even when preview rows are hidden.

About Text Diff Tool

Review changes without a magic separator or misleading similarity score. Line alignment keeps later matches together; exact and intentionally ignored differences remain distinct.