Paste an original and a changed JSON document. The comparison is structural, so key order and whitespace don't matter — you see exactly which values were added, removed or changed.
Original on the left, changed version on the right. Key order and whitespace are ignored.
Pyalm builds custom software, APIs and integrations for businesses in India and the UAE. We made these developer tools for our own team — use them free, and talk to us when you need something built.
A plain text diff flags every line that moved, so reordered keys or different indentation produce noise. This tool parses both documents and walks them as data, reporting only real differences — each with its full path, like $.order.items[2].price.
Check what changed between two API responses, confirm a config migration didn't drop a setting, compare staging and production feature flags, or review a webhook payload against the documented example.
📖 Read the full guide: How to Compare Two JSON Files (Without Drowning in Diff Noise)
Format, validate, minify and syntax-highlight JSON — with exact error line and column.
Send GET, POST, PUT, PATCH and DELETE requests from your browser and inspect the response.
Generate realistic test data — names, emails, phones, addresses — as JSON, CSV or SQL.
No. Objects are compared by key, so {"a":1,"b":2} and {"b":2,"a":1} are equal. Array order does matter, because in JSON arrays are ordered lists.
Index by index. If an item is inserted at the start of an array, every following index shows as changed. For arrays of records, sort both sides by an id first for the clearest result.
1 and 1.0 are the same JSON number. "1" is a string, so it is reported as a type change from string to number.
No. Both documents are parsed and compared in your browser; nothing is sent anywhere.