When to Use JSON Diff

JSON Diff compares two JSON documents and highlights every difference—additions, deletions, and changes. It's essential when you need to:

• Debug API responses — Compare what your API returned yesterday vs. today to find unexpected changes
• Review configuration changes — Before deploying a config update, see exactly what's different
• Validate data transformations — Confirm your ETL pipeline produces the expected output
• Code review JSON fixtures — Quickly spot what changed in test data files

Understanding the Output

The diff view uses standard conventions:

• + Green lines — Added in the second document
• - Red lines — Removed from the first document
• Gray lines — Unchanged context

Example: Comparing API Responses

Say you're debugging why a user's profile looks different. Compare the two responses:

{
  "id": 123,
  "name": "Alice",
  "role": "admin",
  "active": true
}

{
  "id": 123,
  "name": "Alice",
  "role": "viewer",
  "active": true,
  "lastLogin": "2024-01-15"
}

The diff immediately shows: role changed from "admin" to "viewer", and lastLogin was added.

Pro Tips

• 💡 Order doesn't matter — JSON objects are unordered by spec.{"a":1,"b":2} equals {"b":2,"a":1}. Our diff normalizes this.
• 💡 Format first — For cleaner diffs, paste minified JSON and let us format it. This ensures consistent indentation.
• 💡 Use the Swap button — Quickly reverse the comparison direction if you pasted in the wrong order.

Common Questions

Why do two identical-looking objects show as different?

Usually it's whitespace or key ordering. Try clicking "Format" on both sides first. If they still differ, look for subtle type differences like "1" (string) vs 1 (number).

Can I compare JSON from URLs?

Not directly in this tool, but you can use the JSON Validator with the ?url= parameter to fetch JSON, then copy it here.

Is there a size limit?

The diff runs entirely in your browser. Files up to a few MB work fine; very large files (10MB+) may slow down the comparison.

Related Tools

• JSON Sorter — Sort keys before comparing for consistent diffs
• JSON Validator — Validate and format JSON
• JSON Schema Validator — Validate structure against a schema
• JSON Path Query — Extract specific values from JSON

Common Mistakes & Pro Tips

• Key order does not matter for objects — JSON object members are unordered, so two objects with the same keys and values are equal regardless of key order. A good diff ignores reordering of keys and only reports genuine additions, removals, or value changes. Do not treat reordered keys as a difference.
• Arrays are usually compared by index — Most structural diffs align array elements by position, so inserting one item at the front can make every later element look changed. If your arrays are really sets or keyed lists, sort them or compare by an identity field before diffing to avoid noisy, misleading results.
• Type changes are real changes — A value going from the number 1 to the string "1", or from null to 0, is reported as a change because JSON types differ. Watch for these when one side was serialized differently (for example numbers stringified by an API).
• Added vs changed vs removed — A key present only on the right is an addition, present only on the left is a removal, and present on both with different values is a change. Distinguishing these helps you read the diff: a removal plus an addition at the same path often means a value or type change, not two unrelated edits.
• Whitespace and formatting are irrelevant — The diff compares parsed JSON values, not raw text, so indentation, trailing newlines, and spacing never show up as differences. Use a text diff tool if you specifically care about formatting; use this tool to compare data.