About this tool
What it is, why it matters, and how to use it without common mistakes.
What is it?
JSON diff compares two JSON documents and highlights added, removed, and changed paths.
Why use it?
API contract changes and config drift are hard to spot by eye in large trees. A structural diff shows exactly what moved.
How it works
- Paste the left (before) and right (after) JSON.
- Run the diff and walk changed paths.
- Decide whether changes are intentional before merging.
Examples
Path-level change
Left: { "theme": "dark" }
Right: { "theme": "light" }
→ theme value changedBest practices
- Normalize key order if your serializer is unstable before comparing.
- Ignore volatile fields (timestamps) when reviewing fixtures.
Common mistakes
- Comparing pretty vs minified as if content differed.
- Ignoring array reorder semantics when order is meaningful.
FAQ
- Does order of object keys matter?
- In JSON, object key order is not significant. Arrays preserve order — reordering items is a real change.