Back to tools

Text Compare

Spot the difference between two blocks of text instantly. Line, word, and character diff modes. Export as a unified diff or .patch. Runs in your browser. No data sent anywhere.

0 chars
0 chars
Granularity

Diff result

+0−0=0

Paste content on both sides to see the diff.

How It Works

  1. 1

    Paste both versions

    Drop the original text on the left and the changed text on the right.

  2. 2

    Pick a granularity

    Line for code or configs, word for prose, character for tiny typos.

  3. 3

    Review highlighted diff

    Additions in green, deletions in red, unchanged in muted text. Stats update live.

  4. 4

    Copy or download

    Export as a unified diff or download as a .patch file for code review.

Use Cases

  • Code review preview

    Diff two versions of a function or config before opening a PR. Catch surprises before reviewers do.

  • Test fixture validation

    Compare actual vs expected output from a test run to pinpoint why a snapshot failed.

  • Log diffing

    Spot the meaningful difference between two log files when reproducing a bug.

  • Content editing

    Show stakeholders exactly what changed in a piece of copy. By word, not by line.

Frequently Asked Questions

It performs a real-time, side-by-side comparison of two blocks of text and highlights additions, deletions, and unchanged sections. Useful for spotting differences between two versions of a config file, log output, copy variant, or test fixture without leaving your browser.
Paste the contents of the first file on the left and the second file on the right. The diff appears live as you type — added lines in green, removed lines in red. Switch the granularity to Word or Character if you want to spot smaller-than-line differences. Copy the unified diff or download as a .patch file to share or apply.
A string compare in code only tells you whether two values are equal. This tool shows you exactly where they differ, by line, by word, or by character, so you can act on the diff. Same engine that powers `git diff` (Myers algorithm via the npm `diff` package), running entirely client-side.
Yes. Use the Granularity selector. Line mode is best for code and configs. Word mode is best for prose and copy edits. Character mode is best for tracking small typos or whitespace changes.
No. Everything runs in your browser. No network calls, no logging, no storage. Safe for sensitive snippets, secrets, internal copy, or test data you do not want leaving your machine.
Yes. Copy the unified diff to your clipboard, or download it as a .patch file. The format matches `git diff` output and can be applied with `git apply` or `patch -p1`.
A standard text format where added lines start with `+`, removed lines start with `-`, and unchanged lines start with two spaces. It is the default output of `git diff` and what most code review tools render.
No hard cap. Performance stays comfortable up to a few hundred kilobytes per side. For very large files (e.g. minified bundles), prefer Line mode.
Yes. CRLF and LF are both handled. If you want to ignore whitespace-only differences, paste your text through a normalizer first or use Word mode.

Comparing test output by hand? Automate the whole test.

Bug0 writes end-to-end tests from plain English, runs them on every deploy, and a forward-deployed engineer reviews every failure. So you stop diffing logs and start shipping.

From $2,500/mo. Results in 7 days.

Go on vacation. Bug0 never sleeps. - Your AI QA engineer runs 24/7

Go on vacation.
Bug0 never sleeps.

Your AI QA engineer runs 24/7 — on every commit, every deploy, every schedule. Full coverage while you're off the grid.