JSON Diff
Compare two JSON documents and see what changed.
How to use
- 1 Paste the original JSON into the left box.
- 2 Paste the updated JSON into the right box.
- 3 Review the added, removed and changed entries with their paths.
- 4 Copy the diff report if you need to share it.
About JSON Diff
JSON Diff compares two JSON documents and produces a clear, path-by-path list of every difference between them.
Paste an original document on the left and an updated one on the right, and the tool walks both structures in parallel, reporting each leaf that was added, removed or changed.
Every difference is labelled with a precise path such as user.address.city or items[2].price, so you can pinpoint exactly where a value moved without scanning two walls of text by eye.
It diffs deeply and structurally rather than line by line, which means key order and whitespace do not produce false positives — only genuine value differences are reported.
Objects are compared key by key, arrays are compared by index, and a value whose type changes (for example a string becoming an array) is flagged as a change.
A running summary tallies how many fields were added, removed and changed, which is handy for reviewing config edits, API response changes, snapshot updates or migration output.
Both documents are parsed locally and an invalid one produces a specific error telling you which side failed.
Nothing is uploaded, so it is safe to compare private payloads, and the diff updates live as you edit either side.
FAQ
Does key order or formatting affect the diff?
No. The comparison is structural, so reordered keys and different whitespace do not create false differences — only real value changes are shown.
How are arrays compared?
Arrays are compared element by element by index, so a value at items[2] is matched against items[2] in the other document.
What happens if one document is invalid JSON?
You get a specific error indicating whether the left or right document failed to parse, with the parser message.