About this tool
Compare two text blocks and highlight differences. Useful when reviewing API responses, cleaning config before commit, or sharing readable snippets in docs and PRs.
Paste the original text into the Original editor. Paste the changed text into the Modified editor. Example — Spot a latency line change in a status dump: try `Original: GET /health status: ok latency_ms: 12 Modified: GET /health status: ok latency_ms: 48` and expect something like `GET /health status: ok - latency_ms: 12 + latency_ms: 48`.
Diffs are line-based — word-level or semantic diffs are not highlighted. See also: JSON Diff, Patch Viewer, and JSON Formatter. Runs in your browser — nothing you paste gets uploaded.
How to use
- Paste the original text into the Original editor.
- Paste the changed text into the Modified editor.
- Click Compare to generate a line-oriented diff (+ / − prefixes).
- Copy the Diff output when you need a quick textual patch summary.
Example
Spot a latency line change in a status dump
Input
Original: GET /health status: ok latency_ms: 12 Modified: GET /health status: ok latency_ms: 48
Output
GET /health status: ok - latency_ms: 12 + latency_ms: 48
Limitations
- Diffs are line-based — word-level or semantic diffs are not highlighted.
- Binary or non-text content will not produce meaningful results.
- There is no three-way merge or conflict-resolution UI.
Related tools
3Frequently asked questions
What does the Text Diff do?
Compare two text blocks and highlight differences. Runs in your browser — no install, no account.
How do I use the Text Diff?
Paste the original text into the Original editor. Paste the changed text into the Modified editor. Click Compare to generate a line-oriented diff (+ / − prefixes). Copy the Diff output when you need a quick textual patch summary.
Is the Text Diff free?
Yes. No signup, no usage limits, no paywall.
Does the Text Diff upload my data?
No. Processing happens locally in JavaScript. Your input is not uploaded, stored, or logged.
What are the limitations of the Text Diff?
Diffs are line-based — word-level or semantic diffs are not highlighted. Binary or non-text content will not produce meaningful results. There is no three-way merge or conflict-resolution UI.