Work through the task
Compare decoded JSON values and inspect changes by path.
- Enter both complete documents; object-key formatting is not a meaningful difference.
- Read the change kind and before/after values. Array order matters, and paths escape / and ~ using JSON Pointer notation.
- Review the result before copying or downloading. Editing an input invalidates the previous result; keep an original if the transformation matters.
Example to check
{"v":1} compared with {"v":2} reports a changed value at /v.Limits and output behavior
Up to 100,000 input characters, 10,000 values and 40 data levels. Strict JSON rejects duplicate keys, trailing commas, nonfinite numbers and unsafe integers; quote large identifiers to retain their digits. Display is capped at 1,000 differences; a cap notice means further differences can exist.
Troubleshooting
Both inputs must pass the same strict JSON checks. If the display reaches 1,000 differences, narrow the documents; the cap notice means further differences can exist.
Questions
Does changing object-key order count as a change?
Object-key layout/order is not a value difference in this comparison. Array order and decoded value types do matter.
Input and privacy
Processing runs in this browser. Inputs are not saved automatically. An explicitly chosen local draft, where offered, is plaintext storage on this device. Downloaded files, clipboard contents and browser extensions have separate retention behavior.