Textversion v1.0.0

Text / JSON Diff

Two texts in, a unified diff out — the kind you paste straight into git apply. JSON mode compares the two documents rather than the two files, so reordered keys stop being a change while 1.0 and 1 stay one.

Mode

A line diff. Only a line feed separates lines; a lone carriage return is data, the same rule diff and git use.

Whitespace

Line endings

Context lines

View

Original—

Modified—

Changes

Paste both sides above. Everything runs in this tab.

Unified diff

Patch name

Both sides carry this one name, and the a/ and b/ prefixes are added for you — so typing a/file.txt yields a/a/file.txt. Two different names make git apply look for a file that does not exist.

Copied exactly as rendered, ending in one newline.

There is no curl for this one

Every other tool here answers your terminal on the same URL. This one does not, and that is a decision rather than a gap. A request body carries one payload and a diff needs two — the only way to fit two into one request is to put your text in the URL, where browser history, proxy logs and CDN logs would copy it. And your machine already has the answer:

$diff -u old.txt new.txt

curl https://tools.primeforge.app/diff returns this page's HTML, not a diff.

Privacy

There is no server path at all. This tool has no endpoint, no route handler and no proxy entry, so there is no code in this application that could receive either side.

The two boxes are the only place your text lives: no local storage, no session storage, no query string, no history entry. Refreshing the page discards everything, and the HTML this page is served as contains no diff — every byte of it is produced here, after the page loads.