JSON Diff
Compare two JSON objects and list added, removed, changed keys.
Compare two JSON objects and list added, removed, changed keys. Enter your numbers and get an instant result.
Paste two JSON objects and the page reports the added, removed and changed keys between them, computed on the tool server from exactly the text pasted.
Both inputs must parse as JSON objects — dictionaries, not arrays or bare values. Anything else is refused with the reason, because the comparison walks named keys on both sides.
Formatting never appears in the report: both inputs are parsed before they are compared, so spacing, key order and indentation differences vanish and only the data differs.
How the comparison reads
Added keys exist only on the second side, removed keys only on the first, and changed keys exist on both with different values. The report is structural: it names keys and shows the differing values rather than scoring similarity.
The inputs are sent for that one request and nothing is kept. A second comparison is a second request with no memory of the first.
- Both inputs must be JSON objects
- Added, removed and changed keys reported
- Formatting and key order ignored
What it will not do
The page does not merge, patch or pretty-print: it reports the difference and leaves both inputs unchanged. Nested structures are compared by value, so a reordered array reads as changed even when it holds the same items.
A document that fails to parse is refused with the parser's message and its position, not with a partial diff of whatever parsed.
How to use the two JSON inputs
Paste the first JSON object into the first input and the second into the second input, then run. Both must parse as objects, dictionaries rather than arrays or bare values, and anything else is refused with the reason.
Read the added, removed and changed keys with the differing values shown. Both inputs are parsed before comparison, so spacing, key order and indentation vanish; a second comparison is a fresh request with no memory.
What to Expect
Best for
- Seeing what changed between two config files
- Reviewing an API response against a recorded fixture
- Checking that only the intended keys moved in a deploy
Not ideal for
- Comparing arrays of unordered items
- Merging two documents into one
- Diffing non-JSON formats such as YAML or XML
What this tool keeps
- Both inputs unchanged — the page only reports
- Your data private beyond the single request
- The same report for the same two inputs
What may need cleanup
- Reordered arrays, which read as changed
- Deeply nested paths, which you must walk by hand
- A malformed input, which must parse before it can be compared
Common errors
- Pasting arrays or bare strings and reading the refusal as a bug
- Expecting the page to write the merged document
- Reading formatting differences into a report that ignores them
Example use cases
- Diffing staging against production config
- Reviewing a webhook payload against its schema example
- Confirming a migration changed exactly the intended keys
Sample input
Two small objects sharing one key, each with one unique key and one changed value.
Sample output
One added key, one removed key and one changed key with both values, computed on the tool server.
Who this is for
- Developers reviewing configs and payloads
- QA engineers comparing fixtures
- Anyone auditing a JSON change
Frequently asked questions
What must the two inputs be?
Two JSON objects — dictionaries, not arrays or bare values. Anything else is refused with the reason, because the comparison walks named keys on both sides.
What does the diff report?
The added, removed and changed keys between the two objects, computed on the tool server from exactly the text pasted. The inputs are sent for that one request and nothing is kept.
Does it ignore formatting differences?
Yes, by construction: both inputs are parsed before they are compared, so spacing, key order and indentation never appear in the report. Only the data differs.
Build custom tools for your store
Join the SDK program to create useful ecommerce utilities for your store.