Compare two JSON documents as parsed values, so key order and formatting are invisible, and get every difference named by JSON Pointer.
Waiting for two JSON documents
Compared as parsed values, so key order and formatting are invisible.
The differences appear here
Every position where the two documents disagree, named by JSON Pointer.
JSON Diff runs entirely on your device — nothing is uploaded.
You’re on the Free plan. Compare plans
A text diff of two JSON documents reports a reordered object as a wholesale rewrite and a reformatted file as every line changed. Neither is a difference in the data. This compares the parsed values, so key order and whitespace are invisible and what comes back is a list of positions where the two documents genuinely disagree.
Every position is a JSON Pointer, which is what makes the result usable rather than merely informative. A pointer naming one field of one array element can be pasted into a JSON Patch, a test assertion or a bug report and means exactly one place in the document, with no ambiguity about which of three fields called name you meant.
Four distinctions this refuses to blur. Absent is not null, null is not an empty string, and an empty string is not an empty array. Each is reported as its own kind of change, because they are four different states and an API returning one where you expected another is a bug you want named rather than smoothed over. A number against the same number written as a string is a type change, not a match. One and one-point-zero are equal, because JSON has a single number type and they are the same number.
Arrays are compared by position by default. Inserting an element at the front of an array therefore makes every later position differ, which is correct and sometimes unhelpful. A membership strategy is offered as an alternative and applies only to arrays of primitives, because matching an object to a differently placed object has no single right answer and a tool that picked one would be guessing on your behalf.
There is a second view that ignores values entirely and compares which fields exist. That is the question do these two responses have the same shape, which is usually the one being asked when an API changes, and it is a different question from are these two responses the same. Nothing is uploaded: both documents stay in the browser.
No. The documents are compared as parsed values, and a JSON object has no meaningful key order. Reordering keys or reformatting the file produces no differences at all, which is the main reason to use this rather than a text diff.
No, and they are reported differently. Absent, null, empty string and empty array are four distinct states, and an API returning one where you expected another is exactly the kind of bug worth naming precisely.
The same position holding a different JSON type in each document — a number in one and the string form of that number in the other. It is reported separately from a value change because it usually means a serialiser changed rather than data changing.
Because they are compared by position, so inserting one element near the start shifts everything after it. Switch to membership comparison when order is not meaningful; it applies to arrays of primitives.
The RFC 6901 notation for one position in a document, written as slash-separated tokens. It is what JSON Patch, JSON Schema references and most validation error messages use, which is why it is the form this tool reports.
No. Both are parsed and compared in your browser, so an API response containing real data never leaves the page.