WHAT IT DOES
Structural JSON comparison, not a line-by-line text diff.
Paste an Original and an Updated document. Both are parsed and normalized first, so reordered keys and different indentation do not register as changes. Each real divergence is reported as a side-by-side block with its JSON path, source line numbers, and one line of surrounding context.
Why use it?
Use a structural comparison to distinguish meaningful value or type changes from formatting differences when reviewing two versions of a JSON document.
How to use this tool
- Place the earlier JSON in Original and the later version in Updated.
- Choose Compare and review added, removed, and changed content.
- Check the surrounding structure before acting on a difference; a diff reports a change, not whether it is acceptable to your application.
Details and limitations
- Arrays are aligned with a bounded LCS sequence diff, so one inserted item does not mark every following item as changed.
- Nearby properties with similar names and matching value structures are paired as a renamed key rather than an unrelated add and remove.
- Red marks only removed or old content and green marks only added or new content; the opposite side is left explicitly empty.
- One or two .json files can be dropped directly onto the Original and Updated panels.