🔗 JSON Diff
Compare two JSON values semantically. Key-order independent. Get a list of added, removed, and changed paths.
Last updated: November 8, 2026 · By the BoltQuickTools team
Seeing what actually changed between two JSON documents
When an API response changes after a deploy, a line diff is noisy if the keys moved or the formatting differs. This page parses both sides and compares values path by path, so you get only the real differences.
Comparing two documents
- Paste the old version into Left and the new version into Right. Each panel's Sample button loads demo data. The result updates as you type.
- Read the summary chips (added, removed, changed, equal) and the path list under them.
- Tick Hide equal paths to list only differences.
- Use Copy Diff to copy the list as text, Swap Sides to reverse the comparison, and Clear to start over.
The sample data, compared
Press both Sample buttons and the summary reads +2 added, -0 removed, ~2 changed, 4 equal, with these lines:
+ address.state = "NY"
+ lastLogin = "2026-05-21"
~ age: 30 → 31
~ roles[1]: "editor" → "viewer"
= address.city = "NYC"
= address.zip = "10001"
= name = "Alice"
= roles[0] = "admin"
A + line exists only on the right, - only on the left, and ~ shows the left value and then the right value.
Two checkboxes that do less than their labels suggest
- Sort object keys changes only the order lines are listed in. Key order never affects the result, whether this box is ticked or not.
- Strict type compare has no effect in the current version. Values of different types are always reported as changed, so
{"a":1}against{"a":"1"}shows~ a: 1 → "1"with the box ticked or cleared. If you need 1 and "1" treated as equal, normalise them before comparing.
Reading results correctly
- Arrays are matched by position. Inserting one item at the front makes everything after it look changed:
[1,2,3]against[0,1,2,3]reports three changes and one addition. Sort both arrays first if order does not matter. - A side that fails to parse counts as empty. With bad JSON on the left and valid JSON on the right, you see a parse error under the left panel and also
+ (root) = ...as if everything were new. Fix the error before trusting the list. - Very long integers can look equal.
9007199254740993and9007199254740992parse to the same JavaScript number, so they appear as equal. - Paths can be ambiguous. A key literally named
a.band a nestedathenbboth print asa.b. - Only the first 200 equal lines are drawn, although the chip counts all of them. Differences are never cut off.
- Empty objects and arrays produce no line when both sides match, so two documents of
{"a":{}}show "No differences." and 0 equal.
Size, moved items and text diffs
How large can the documents be?
The code sets no limit. Everything is parsed and compared in the page, so the practical limit is your device's memory. Each side has to be parsed in full on every change, which you will notice with large files.
Can it detect a moved array item?
No. There is no matching by ID or content, so a moved item shows up as a run of changes.
When is a text diff the better choice?
When the content is not valid JSON, or when formatting and comments matter. Use Text Diff for that.
It often helps to clean up input with the JSON Formatter first. Once you know which path changed, the JSONPath Tester can pull that value from a larger document.