About the JSON Compare
Comparing JSON by eye is error-prone, especially when key ordering differs or objects are deeply nested. A semantic JSON diff parses both documents and compares them by structure and path rather than by raw text, so reordered keys are correctly treated as equal and only real differences are highlighted.
This tool walks both objects recursively and reports three kinds of change: values present only in B (added), values present only in A (removed), and values present in both but different (modified). Each difference is shown with its full path, making it easy to track down exactly what changed between two API responses, two config versions, or two snapshots of the same object.
How to use the JSON Compare
- 1Paste the original JSON into the “JSON A” editor.
- 2Paste the JSON to compare into the “JSON B” editor.
- 3Click Compare to generate the structured diff.
- 4Review additions, removals and modifications, each with its path.
Key benefits
- Semantic comparison — key order does not matter.
- Clear added / removed / modified grouping.
- Full path for every difference.
- Private and instant.
Real-world examples
Diff two API responses
Spot what changed between two calls.
Review config changes
See exactly which settings were altered.
Verify a migration
Confirm transformed data matches expectations.
Frequently asked questions
Does key order affect the result?+
No. Objects are compared by key, so reordering keys produces no differences.
How are arrays compared?+
Arrays are compared by index, so inserting an element shifts subsequent comparisons. This matches how most diff tools treat ordered lists.
Is my data uploaded?+
No — both documents are compared locally in your browser.