JSON Diff

Compare two JSON payloads side by side and spot changes in values, keys, arrays, and structure.

Left JSON

Paste or drop file

Right JSON

Paste or drop file
Before You Compare

Prepare the payloads first

Diff works best when both sides are already valid and readable. Clean the inputs before you compare structure or values.

Use diff in the right place

Compare API regressions after you format the JSON into a readable shape. If the comparison fails because one side is broken, validate the JSON first and then use Unexpected Token in JSON when the parser message is still unclear.

The same workflow helps with config changes and JSON-LD updates: clean the formatting, validate the syntax, then compare the payload versions side by side.

Tools

Related Tools

Move between formatting, validation, schema checks, JSONPath queries, decoding, conversion, minifying, generation, and diffing without leaving the JSON cluster.

Technical Notes

How the Diff View Works

This section explains how the diff view compares parsed JSON structures in the browser and what the highlighted changes mean.

What this tool does

The JSON Diff tool helps you compare two JSON payloads to identify additions, removals, and changed values. It parses both inputs in the browser, runs a structural comparison, and displays a human-readable diff.

This is useful for debugging API responses, tracking configuration changes, or confirming that two JSON structures are equivalent.

How JSON diff works

The tool first validates both JSON inputs. If both are valid, it uses a diffing algorithm to compare the two parsed objects recursively. The result is a structured diff that highlights the exact changes between the two payloads.

The comparison focuses on the data's structure and values, not the raw text, so formatting differences are ignored.

Common use cases

  • Comparing API responses to see what changed between calls.
  • Inspecting config files to identify accidental changes or regressions.
  • Debugging payload regressions by comparing a known-good payload with a problematic one.
  • Reviewing JSON-LD changes to ensure structured data for SEO is correct.
  • Spotting accidental schema drift between different versions of a data structure.

Privacy and browser execution

All processing happens client-side in your browser. Neither of the JSON payloads are sent to a server, which keeps your data private and the tool fast.

Support

FAQ

Guides

Related Guides

Short reference pages for the syntax issues and workflows around JSON formatting and validation.