Compare parsed JSON structures independently of object-key order, inspect JSON Pointer differences and highlight matching source paths.
LEFT DOCUMENT
Valid JSON
RIGHT DOCUMENT
Valid JSON
TRANSFORM & CHECK
Object key order is ignored; array order matters. Paths use RFC 6901 JSON Pointer escaping (~0 for ~, ~1 for /); the empty pointer means the whole document. Added/removed containers are one structural change. Reports are bounded to 2,000 differences, with no silently truncated report.
Inputs are bounded to 200,000 UTF-8 bytes. JSON values use JavaScript numeric precision; nonfinite values and unsafe integers are rejected, and exact large numbers should be strings. JSON nesting is limited to 64 levels and 10,000 values. Output is bounded to 1 MB. Files are decoded locally as UTF-8. Nothing is uploaded to a calculation service; clipboard and downloads require an explicit action.
Enter your values locally; no inputs are uploaded.
Check validation feedback before reviewing the browser-generated result.
Review the explanation, copy supported outputs or reset the workspace.
Paste or import supported UTF-8 documents, review live validation, run the named action, then inspect and export the computed output.
JSON Diff compares parsed values and ignores object-key ordering or formatting-only differences. The existing Diff Checker compares text. Array order remains significant in this structural comparison.
Documents are processed locally in browser memory, without an external calculation-processing API or server upload. File import, clipboard and download happen only through explicit actions. Ordinary website requests may still be logged; no persistent document profile is created.
JSON Diff compares parsed values and ignores object-key ordering or formatting-only differences. The existing Diff Checker compares text. Array order remains significant in this structural comparison.
Added, removed, modified and type-changed values are reported. An added or removed container is one structural difference, while shared objects and array indexes are recursively compared.
RFC 6901 paths escape a tilde as ~0 and a slash as ~1. The empty pointer refers to the document root. Highlight path selects the exact indexed value in both source editors, or the nearest existing parent when a value is absent.
No. Arrays compare by index in their existing order. For example [1,2] versus [2,1] contains modified values rather than being considered an unordered set.
No. Left and right documents are validated independently, with the invalid side identified. Comparison is not returned until both inputs parse successfully and fit the supported depth/value and numeric limits.
Expand differences, highlight their paths, page through the list or copy/download the computed JSON report. More than two thousand differences is a controlled error, not a silently truncated report. Numbers follow JavaScript precision; unsafe integers and nonfinite values are rejected.