Compare two JSON documents
Paste two JSON documents, such as API responses, package.json files or configs, and see which values changed. Key order and formatting are ignored, so only real data changes show.
How to use the JSON compare tool
- Paste the first JSON on the left and the second on the right, or drop .json files on them.
- Compare as JSON is already on: both sides are formatted and their keys sorted.
- Read the added, removed and changed values in the comparison below.
- Turn Compare as JSON off to compare the raw text, formatting included.
What you see
- Differences in values, not in key order
- Formatting and indentation differences ignored
- Exact numbers, so 1.0 and 1 or long IDs are compared as written
- A clear note if either side is not valid JSON
About the JSON compare tool
Why normalise first
Two JSON documents with the same data can look completely different as text: keys in another order, different indentation, everything on one line. Comparing the raw text would flag every line. Normalising both sides first leaves only the real changes.
Typical uses
Compare an API response before and after a deploy, check what changed in package.json or a lock file, or confirm that two environment configs match.
Invalid JSON?
If one side is not valid JSON, it is compared as plain text and you're told which line is broken. Fix it with the JSON Toolkit's repair tool, then compare again.
Frequently asked questions
- Does array order matter?
- Yes. Arrays are ordered in JSON, so items that moved are shown as changes. Only the order of keys in objects is ignored.
- Can I compare minified JSON?
- Yes. Minified JSON is formatted before comparing, so you get one line per value instead of one giant changed line.
- Is my data uploaded?
- No. Both documents are compared in your browser.