JSON Diff — Compare Two JSON Objects

What is JSON Diff?

A JSON diff compares two JSON documents by structure rather than by text. Unlike a plain text diff — which is confused by reordered keys, different indentation, or whitespace — a structural diff parses both sides and reports exactly which values were added, removed, or changed, addressed by their path (e.g. user.address.city). This is essential for reviewing config changes, API contract drift, and snapshot test failures.

How to compare two JSON objects

1. 1Paste the original JSON on the left and the updated JSON on the right.
2. 2The tool parses both and computes a structural diff.
3. 3Review changes grouped by path: additions, deletions, and value changes are color-coded.
4. 4Use the by-path view to pinpoint exactly which nested field changed.

Use Cases

Code Examples

{ "name": "web", "replicas": 2 }

{ "name": "web", "replicas": 3, "tls": true }

~ replicas: 2 -> 3
+ tls: true

Key Concepts

Structural vs text diff

A text diff compares characters and is fooled by reordered keys or whitespace. A structural diff parses JSON first, so only real value changes are reported.

Path addressing

Each change is labeled by its location, e.g. items[2].price. This is a JSON Pointer / dot-path style that pinpoints deep changes.

Array comparison

Arrays are compared by index. Inserting an item mid-array shifts positions and can appear as many changes — a known limitation of index-based diffing.

Tips & Best Practices

• ▸Reordered object keys are treated as identical — that's the whole point of a structural diff.
• ▸Inserting an element in the middle of a large array can look like many changes because comparison is index-based.
• ▸A type change (e.g. "3" string → 3 number) is reported as a change, not equal — JSON diffs are type-aware.
• ▸For very large documents, collapse unchanged branches to focus on the deltas.