What the JSON Diff does
JSON Diff compares two JSON documents, such as two API responses, config versions or exports, and lists every difference by its path: what was added, what was removed and which values changed, from what to what. Key order and spacing are ignored, so only real changes show. Tick the option to ignore the order of items in lists, and copy the changes as a standard JSON Patch (RFC 6902) to apply elsewhere.
How to use it
- Paste the original JSON on the left and the changed JSON on the right.
- Tick Ignore the order of items in lists if order does not matter.
- Read the list of changes, colour-coded by type.
- Copy or download the changes as JSON Patch.
Example
Comparing the two sample config versions finds 5 differences: version changed from 1.4.0 to 1.5.0, tools from 185 to 202, features[2] “text” added, owner.city “Delhi” removed, and beta: true added.
Why not a text diff?
A text diff reports changes whenever keys are reordered or the file is re-indented, which hides the real differences. JSON Diff reads both documents first and compares the data itself, so reformatted but identical documents show no differences.
Lists are compared item by item in order. If the same items appear in a different order and that does not matter, as with tags, tick the ignore-order option.
Questions people ask
Is my code or data uploaded?
No. Everything runs in your browser, so config files, queries, logs and keys stay on your device. That makes it safe to use with work data.
What is JSON Patch?
A standard list of operations, such as add, remove and replace, with paths like /owner/city, that turns one document into the other. Many libraries and APIs can apply it.
What if my JSON has an error?
The problem is shown with its line and column for whichever side is invalid.