JSON Compare – Structural Diff & Key Path Inspector
When an updated JSON file behaves differently from the previous version, compare the two documents to locate added keys, removed properties, changed values, or differences inside arrays. Use the reported paths to find each change, then decide whether it is expected for your data.
JSON Compare Features
Object tree traversal, key path display, key sorting, and privacy
🌳 Structural Object Traversal
Evaluates nested dictionary nodes and arrays without relying on raw line positions.
📍 JSON Path Tracing
Pinpoints exact property paths (e.g. `$.settings.executionMode`) where values differ.
🔤 Key Order Normalization
Optionally sorts object keys alphabetically to eliminate false positives caused by key order.
🔒 100% Client-Side Privacy
All JSON comparison runs locally in browser RAM. Zero payload data is transmitted to servers.
Find changed keys and values between JSON files
Comparing two formatted JSON files line by line can produce noise when spacing or key order differs. Use a structural comparison when you need to find which keys were added, removed, or changed between two data snapshots or configuration versions.
1. Load the original and revised JSON
Paste both documents or choose supported files. Make sure each input is the version you intend to compare; if either document is invalid, validate it first.
2. Review paths and values
Inspect added keys, removed keys, and modified values. A path helps locate the field in the nested structure; check the parent object and nearby values to understand the impact.
3. Confirm changes before replacing data
Pay attention to changed identifiers, settings, arrays, and fields that may be required by another application. Keep both originals until the differences are understood.
Examples of useful comparisons
- Compare an old and new API response to see which fields changed.
- Review configuration changes before using the updated settings.
- Check two exports to find new, missing, or edited records and values.
A structural difference report does not confirm that the revised data is correct or compatible with a particular application. Valid JSON can still contain an unexpected value or omit a field your workflow requires.
Frequently asked questions
Do both JSON files need to be formatted the same way?
They need to be valid JSON. Structural comparison is intended to help focus on data changes rather than superficial formatting differences.
Does a difference mean the new JSON is wrong?
No. It identifies changes; decide whether each one is expected based on the data's purpose and the receiving application's requirements.
Frequently Asked Questions
How does structural JSON comparison differ from line diffing?
Structural JSON comparison parses both payloads into object trees, normalizing key order and whitespace, so it highlights real data changes without false positives caused by key reordering.
Is my JSON payload transmitted to external servers?
No, 100% private. All object tree parsing, JSON path tracing, key order normalization, and report generation run locally inside your browser memory.
Can I compare JSON payloads with different key orders?
Yes! Keep 'Ignore Key Order' enabled to automatically sort dictionary keys alphabetically before comparing object properties.