JSON Compare & JSON Diff Checker Online
Compare two JSON files online with a free JSON diff checker. Semantic compare ignores key order and formatting, highlighting added, removed and modified keys.
A JSON diff checker compares two JSON files by structure rather than by text, so reordered keys and different indentation are not reported as changes. Paste the original and the modified JSON into the two left panes; the right pane lists every added, removed, and modified key path.
A JSON diff compares two documents by structure rather than by line, so a reordered key or a change of indentation is not reported as a difference. JSON2X walks both trees in parallel and reports every key path that was added, removed, or changed in value, along with the old and new values. Both documents stay in the browser, which matters when you are comparing production and staging payloads.
How is a JSON diff different from a text diff?
A text diff such as git diff works on lines. Re-indent a file, sort its keys, or move an object to a different position and every affected line is reported as changed, even though the data is identical. A structural diff parses both sides first and compares values at matching key paths, so formatting and object key order are ignored entirely. What you get back is a list of semantic changes: user.address.city changed from "Berlin" to "Munich", rather than two changed lines.
How are arrays compared?
Arrays are ordered in JSON, so they are compared by index: items[2].price is matched against items[2].price. That is the correct reading of the specification, but it means inserting one element at the front of a long array reports every subsequent index as modified. When your arrays are really unordered sets of records, compare them by sorting on a stable key first, or diff the individual records that matter.
What counts as a change?
Three things. A key present in B but not A is an addition. A key present in A but not B is a removal. A key in both whose value differs โ including a change of type, such as "42" becoming 42 โ is a modification. Type changes are worth watching closely, because they are the category most likely to break a strongly typed client even when the value looks the same. If you need to enforce the shape rather than just observe it, generate a JSON Schema from the version you consider correct.
How to use the JSON Diff
Takes under a minute. Nothing is uploaded โ every step runs in this browser tab.
- Paste the original
Put the baseline document into the JSON A pane on the left โ for example last weekโs API response.
- Paste the comparison
Put the new document into the JSON B pane directly below it.
- Read the diff
The right-hand pane lists every difference grouped as added, removed, and modified, each with its full dot/bracket key path so you can find it in the source.
- Act on the changes
Copy the report into a pull request comment or an incident note, or fix the drift and re-run the comparison.
When to use it
- Spotting a breaking change between two versions of an API response
- Finding which key differs between a working and a failing configuration
- Reviewing what a migration script actually changed in an exported record
- Comparing a snapshot test fixture against live output
- Auditing environment config drift between staging and production
Step-by-step guides for this tool
Task-specific walkthroughs covering the most common ways this tool gets used.
Searches this page answers
- compare two json files online
- json compare online free
- online json diff checker
- json diff checker free
- json comparison tool
- json difference checker
- json file difference checker
- json diff viewer
- compare json differences
- semantic json compare
- json diff ignore key order
- diff json api responses
Frequently Asked Questions
How does the JSON Diff Checker work?
The tool parses both Left (Original) and Right (Modified) JSON strings into abstract syntax trees, normalizes keys, and performs a deep recursive structural comparison, highlighting added keys in green, removed keys in red, and mutated values in yellow.
What makes JSON diff different from standard text diff?
Text diffs fail when keys are reordered or formatted with different indentation. A semantic JSON diff evaluates pure data equality regardless of whitespace or key order.
Can I compare large API responses side-by-side?
Yes. You can paste raw responses or upload files directly into the left and right panels.
Is any comparison data stored on external servers?
Never. The diff comparison runs entirely in your local browser JavaScript engine.
Related Developer Tools
- Standards & references:
- JSON
Last reviewed by the JSON2X Engineering Team.