JSON Compare Online

What Is JSON Comparison?

JSON comparison — also called JSON diff — is the process of taking two JSON objects and identifying exactly what changed between them. Unlike plain text diffing, which compares lines, JSON diffing understands the structure of the data. It knows that { "a": 1, "b": 2 } and { "b": 2, "a": 1 } are identical, even though the key order is different.

This matters enormously in real development. API responses change between versions. Database records change after migrations. Config files diverge between environments. When something breaks, you need to know exactly what changed — not just that the JSON is different.

Common Use Cases

Understanding the Diff Results

The comparison result has four change types. Added (green) means the key exists in JSON B but not in JSON A — it was newly introduced. Removed (red) means the key existed in JSON A but is missing in JSON B — it was deleted. Changed (yellow) means the key exists in both but the value is different. Type Changed (orange) is a specific and important category — the key exists in both and even the value looks similar, but the data type is different — for example a number became a string.

Type changes are particularly valuable to detect because they often indicate bugs that are invisible to the human eye. The number 42 and the string "42" look identical when logged but behave completely differently in code — one passes a numeric validation, one does not.

How to Compare JSON Files

With this tool you can compare JSON in three ways. First, paste directly — copy the JSON text from your editor, terminal, browser dev tools, or API client and paste it into the A or B editor. Second, upload a file — click the Upload .json drop zone in either panel header and select a .json file from your computer. The file contents load into the editor instantly. You can also drag and drop a .json file directly onto either drop zone.

Once both sides are populated, click Compare JSON. The diff tree renders immediately, with changed sections auto-expanded and unchanged sections collapsed by default to keep the result focused on what matters.

Should I Format My JSON Before Comparing?

Not necessarily. This tool parses the raw JSON regardless of indentation, so minified JSON compares correctly against pretty-printed JSON. However, if your JSON has syntax errors — missing commas, trailing commas, unquoted keys — you will get a parse error. In that case, use the Format button inside each editor panel to auto-indent and validate the JSON. For more powerful formatting and repair, our JSON Formatter tool can handle more complex beautification and error diagnosis.

Deep vs Shallow JSON Comparison

A shallow comparison only checks whether top-level keys changed. A deep comparison recurses into every nested object and array. This tool performs a full deep comparison — it will find a changed string buried inside a nested object inside an array inside the root object. Every field at every depth is checked.

Arrays are compared element by element by index position. This means if you insert an element at the start of an array, every subsequent element will be marked as changed even if its content is identical — because its index position changed. This is expected behaviour for positional array comparison. If you need semantic set-based comparison for arrays, consider pre-processing the data to use keyed objects instead.

Privacy and Data Security

All comparison logic runs entirely in your browser using JavaScript. No JSON data is uploaded to any server. No data is stored, logged, or transmitted. You can verify this by using the tool while offline — it works without any network connection after the page has loaded. This makes it safe to compare sensitive data like API credentials, private user records, or internal configuration files.