JSON Diff
Compare two JSON documents side by side with dot-notation key paths.
Related Tools
Beautify and pretty-print JSON with configurable indentation.
Check JSON syntax against RFC 8259 with exact line/column error reporting.
Strip whitespace to produce the smallest valid JSON payload.
Browse JSON as a collapsible tree with search and path copy.
Parse JSON and get clear, actionable syntax error explanations.
Validate JSON against a JSON Schema with JSON-pointer error paths.
Documentation
What is JSON Diff?
It compares two JSON documents and highlights every addition, removal, and changed value, each with its full key path — useful for debugging API version changes or auditing config drift.
How it works
Both inputs are parsed, then walked in parallel. Any key present in one but not the other is an addition or removal; any key present in both with a different value is a change.
Best practices
Format both documents first (with the JSON Formatter) if you want to eyeball them manually alongside the diff results.
Frequently Asked Questions
How does the diff work?▾
Both documents are parsed and compared recursively, key by key. Objects are diffed by key, arrays are diffed element-by-element by index.
What do the colors mean?▾
Green marks keys present only in the modified document, red marks keys only in the original, and yellow marks keys present in both but with a different value.
What is the "key path" shown next to each difference?▾
It's the dot-notation path to that value — e.g. user.address.city — so you can locate the exact spot in a large document without scrolling through both panels.
Does array order matter?▾
Yes — arrays are compared by index, so [1,2,3] vs [3,2,1] shows differences at every index even though both contain the same numbers.
Can I diff minified JSON?▾
Yes, formatting doesn't matter — only the parsed data is compared.
Is either document uploaded anywhere?▾
No. Both documents are compared entirely in your browser.