Compare JSON structures, not strings
You deployed a code change and your API response looks different. But scrolling through two blobs of JSON trying to spot what changed? That’s a waste of 20 minutes. Paste both documents here and the diff shows you exactly what was added (green), removed (red), or changed (yellow), with full paths like user.address.city so you can locate the affected field instantly.
Unlike a plain text diff, this tool understands JSON structure. It recursively walks both documents and compares values at every nesting level. Whitespace and formatting differences don’t trigger false positives, only actual data changes show up.
When you’ll need this
API regression testing. Hit the endpoint before and after your change, paste both responses. Anything that changed unexpectedly? You’ll see it immediately.
Config file reviews. Someone updated package.json or tsconfig.json in a PR. Diff the old and new to make sure they didn’t accidentally nuke a dependency.
Data migration validation. Transformed records from one schema to another? Compare a sample against the expected output to catch bugs.
Staging vs production. Diff environment configs to find the one setting that’s different, and probably causing the issue.
Make it easier on yourself
Format both documents first using the JSON Formatter: it won’t change the diff results, but makes the input easier to scan visually.
The path info (data.users[2].email) is directly searchable. Copy it and grep your codebase or query your database.
For generic text comparison, the Diff Checker handles any plain text.
FAQ
How are arrays handled?
Element by element, by index position. Extra elements in either array show as additions or removals.
Invalid JSON?
You’ll get an error message. Both inputs need to be valid JSON. Use the JSON Validator to find syntax issues.
Path notation?
Dot notation for object keys (user.name), bracket notation for array indices (items[0].id).
Privacy?
All client-side, your JSON never leaves your browser.