Text Diff Checker

Compare two texts side-by-side. All processing happens in your browser — paste, see the diff, copy nothing leaves your machine.

Original80 chars · 6 lines
Modified102 chars · 6 lines
View
Granularity
+4 added4 removed
1function add(a, b) { 
2 return a + b; 
 1function add(a, b, c = 0) {
 2 return a + b + c;
3}3}
4 4 
5const sum = add(1, 2); 
6console.log(sum); 
 5const sum = add(1, 2, 3);
 6console.log("sum:", sum);

The ToolEdge Text Diff lets you paste two pieces of text and see exactly what changed, line by line and (optionally) character by character. Diff is the most common pre-merge sanity check in every developer workflow — comparing your branch to main, an HTTP response to its expected fixture, a config file before and after an edit, or two versions of a contract someone sent over email. We run the diff entirely in your browser using the Myers diff algorithm; nothing you paste is uploaded.

Beyond raw line-comparison, the tool offers a side-by-side view (best for reviewing changes the way GitHub shows pull requests) and a unified view (best for reading mostly-unchanged content with sparse edits — what `git diff` defaults to). Toggle between them to match the task: side-by-side for two roughly equal versions, unified for tracking small changes across a long file.

Common use cases

  • Comparing JSON, YAML, or config files before applying a change — spot accidental edits you didn't mean.
  • Reviewing what a teammate sent in two emails ("see attached v1 and v2") without firing up a code editor.
  • Comparing API responses across environments (staging vs production) to find drift.
  • Reviewing a contract or terms-of-service update — paste old + new, see exactly what changed.
  • Sanity-checking that two files claim to be 'identical' actually are — even invisible whitespace differences show up.

Frequently asked questions

No. The diff is computed entirely in your browser using JavaScript. Nothing leaves your machine — you can disconnect from the internet after the page loads and the tool still works. This matters when you're comparing sensitive data: contracts, customer records, API keys in config files, etc.