What this tool does
Find data differences without treating object key order as a change. Arrays retain positional meaning.
When to use it
Use Structural JSON comparison when you need the specific operation described here and can check the result against your own source. Keep the original and work on a copy.
Steps
- Paste the original and new JSON documents.
- Process to validate both and compare their structures.
- Review paths, difference types and before/after values.
Worked example
Input: Original {“a”:1,“b”:2}; new {“b”:2,“a”:3}.
Expected result: One changed difference at /a; b is unchanged.
Common mistakes
- 100,000 characters per document, 64 levels and up to 500 differences.
- Rejects duplicate/reserved keys and numbers that would lose precision. Does not apply patches or reorder arrays.
If an error appears, reduce the input or correct the specified field. Do not treat an unsuccessful operation as a valid result. Repeat the example with synthetic data to separate an input problem from a tool problem.
Limitations and privacy
Inputs are processed in your browser. Visiting the site downloads its resources, but the tool does not upload the document or text. Results are not automatically stored. Check downloaded files before using them in a workflow.
Do not paste production secrets on an untrusted device. Local processing does not replace validation in the destination application.
Frequently asked questions
Does this change the original?
No. Keep the source and explicitly download or copy the result you want to retain.
What should I check before using the output?
One changed difference at /a; b is unchanged. 100,000 characters per document, 64 levels and up to 500 differences.