JSON Diff
JSON Diff
Compare JSON structures side by side and inspect additions or removals.
Live
Live update on input changes.
File input
Choose a file
Click, drop, or paste from clipboard.
More actions
Source: manual / manualCopy result exports current diff payload. Copy report details includes metadata for audits and handoff.
Workspace status
Waiting for diff rows. Edit input and run compare, or keep auto-update on.
Self-check score (heuristic): 64/100 • Needs review
Performance: 0 ms compare • live debounce 320 ms.
JSON diff rows
0rows
Preview path-level changes plus first 300 line rows below. Mobile view uses stacked cards for readability.
Path-level changes
No path-level changes match the current filter.
| Change | Left | Right |
|---|
Your input is processed locally in your browser whenever possible. We do not store your data.
Flow
- Parse both JSON payloads in strict mode or lenient normalization mode.
- Normalize both sides with stable indentation for deterministic line diff.
- Compute line diff rows with LCS and compute leaf-path changes for semantic change summary.
Example
Worked example: score field update
- 1 Left payload score is 90.
- 2 Right payload score is 92 and adds active field.
- 3 Diff output marks one removed row and added rows.
You can validate payload changes quickly before deployment.
How
- Paste left and right JSON payloads.
- Choose strict JSON or lenient normalization parse mode.
- Run compare to normalize both sides.
- Review line rows and path-level changes before copying/exporting.
Cases
- Audit API contract updates between releases.
- Compare environment configuration payloads.
- Inspect generated JSON edits before merge.
Avoid
- Using strict mode for non-JSON syntax that requires lenient normalization.
- Ignoring path-level type changes when values look similar as strings.
- Assuming object key order changes are always semantic changes without checking path summary.
FAQ
Do both inputs need valid JSON?
Yes in strict mode. Lenient mode can normalize common issues like comments, single quotes, and trailing commas.
Does this include semantic diff details?
Yes. Along with line rows, it reports path-level changes (added, removed, modified, and type-changed).
Can I use it with large API responses?
Yes, but visible line and path lists may be capped for responsive performance while export includes the computed payload.
Switch
Switch12
No match.