JSON compare
The JSON compare tool parses both sides, then walks the tree. You
get paths like $.user.age instead of a wall of reformatted lines.
Result kinds
- Added — path exists only in B.
- Removed — path exists only in A.
- Changed — same path, different value, same JSON type.
- Type changed — for example number vs string, or object vs array.
Key order and arrays
Object key order is ignored: {"a":1,"b":2} matches
{"b":2,"a":1}. Arrays are matched by index, so inserting at the front shifts every later
slot. That is expected for JSON, not a bug.
Filters
After a compare, you can hide kinds you do not care about and filter by path substring (for example
$.tags). Copy report uses the filtered list. Beautify / minify only change how the editors
look; they do not change structural equality.
Not this tool
-
Instagram
following.json/ followers as a username list — use the list tool. - Ordered wording in a config that is not valid JSON — text compare.
- Invalid JSON: fix the parse error under that editor; compare does not run until both sides parse.
FAQ
Does JSON compare treat key order as a change?
No for objects. Arrays still compare by index.
Can I paste Instagram following.json here?
Not to extract usernames. Use the list tool’s JSON import for that.