Text tools

Compare two text versions

Compare exact lines. CRLF and CR are normalized to LF; spaces, case and Unicode stay significant. Combined input: 100,000 UTF-16 units / 400,000 UTF-8 bytes; 1,000 lines per side. A final newline counts as an empty line.

Enter the two versions.

Both texts stay on this page. No upload, storage or semantic analysis.

Help & FAQs

Paste both versions, then compare their actual line changes.

How to compare text

  1. Paste the original on the left and the changed text on the right. Either side may be empty.
  2. Compare the texts. Review original and edited line numbers with + additions and − removals.
  3. Copy or download the line report. Editing either input clears the old comparison.

Exact lines with bounded work

Line endings CRLF and CR are normalized to LF before comparison. Other whitespace, case and Unicode representation remain significant. Input is limited to 1,000 lines per side and a combined 100,000 UTF-16 units / 400,000 UTF-8 bytes. The longest-common-subsequence table is at most 1,002,001 Uint16 cells (about 2 MiB), and the result at most 2,000 rows; output is bounded to 300,000 units / 400,000 bytes.

Common questions

Does this find plagiarism or semantic changes?

No. It reports exact line additions and removals. It does not identify meaning, code correctness, moved-block intent or similarity percentages.

Are blank lines and a final newline ignored?

No. Blank lines remain, and a final LF creates an empty final line. An empty document has zero lines. CRLF and CR are the only normalized differences.

Is the downloaded report a patch file?

No. The readable TXT report prefixes added lines with +, removed lines with -, and unchanged lines with a space. It is not a Git/unified patch and is not meant to be automatically applied.