Structural JSON diff
Compare two JSON documents by structure and see exactly which keys and values were added, removed or changed.
- Runs in your browser
- No upload
- Result stays on your device
Privacy & limitsRuns in your browser. Nothing is uploaded.
Input content stays in this tab; Refentra does not upload or store it. Optional aggregate action counts are sent only with your usage consent. Clear the workspace when finished.
Supported profile: JSON: 20,000 nodes, depth 64. Numbers use IEEE-754; integers must be safe and finite. Numbers must round-trip their decimal meaning. Unsafe integers, overflow, underflow or unsupported decimal precision are rejected before output.
Maximum text: 200,000 UTF-16 units; parser limits can be smaller. Worker time limit: 15 seconds (regex 1.5 seconds).
Check the input and the result
- Prepare and choose the operation
Put the original and the revised strict JSON in separate fields. The tool compares the parsed structures, not the formatting.
- Check a concrete example
Use this sample and compare the indicated result: {"a":1} → {"a":2,"b":3}: /a changed(1→2); /b added(3)
- Check the output before you reuse it
Follow each path back to its value. The order of object keys is ignored, while array positions matter.
Answers for this task
How are slashes inside keys represented?
Paths use JSON Pointer escaping: / in a key becomes ~1 and ~ becomes ~0, so /a~1b refers to the key a/b.
What should I check if the input fails?
Validate both JSON documents first. Comments, trailing commas and unsafe numbers fail before the structures are compared.
Where does this tool stop?
This reports differences in the data. It doesn't produce a guaranteed executable JSON Patch or a merge that understands your domain, and matching values can still break business rules.