JSON Compare Tool
Compare the field differences between two JSON documents. Both sides are flattened and diffed by path, reporting missing fields, extra fields and type mismatches.
About This Tool
The JSON compare tool finds the differences between two JSON documents. Both sides are flattened into path sets and diffed by path, so differences are pinpointed to exact fields no matter how deeply nested, rather than just reporting that the objects are not equal.
Results fall into three groups: paths only present on the left, paths only present on the right, and paths present on both sides but with different types, for example the string 10 versus the number 10. This list is exactly what you need when verifying API field changes or comparing canary and stable responses.
Key Features
Path-level differences
Differences point to paths like a.b[0].c instead of whole objects.
Three result groups
Missing, extra and type mismatch are listed separately for triage.
Real type awareness
Distinguishes string, number, boolean, null, array and object so 1 and "1" are not treated as equal.
When to Use It
API change review
Compare old and new responses to confirm fields were added or removed as planned.
Environment comparison
Check structural differences between test and production responses.
Config validation
Confirm whether a configuration file is missing any keys.
How to Use It
- 1Paste the baseline JSON on the left.
- 2Paste the JSON to compare on the right.
- 3Click Compare.
- 4Review each result group and fix accordingly.
Frequently Asked Questions
Does array order affect the result?
Yes. Arrays are flattened by index, so reordering changes path correspondence, consistent with most diff tools.
Are 1 and "1" treated as equal?
No, they are reported as a type mismatch because they behave differently in real usage.
