JSON Diff

A JSON diff compares the parsed structure and data in two JSON documents. It helps developers review API responses, configuration revisions, fixtures, and saved state without treating indentation or object property order as meaningful changes.

Orbilyra reports added, removed, changed, and unchanged paths. Results use readable JSONPath-like locations such as $.settings.timeout and $.items[0]; they are a diagnostic report rather than a standardized patch format.

1. Paste the original JSON into the left editor.
2. Paste the updated JSON into the right editor.
3. Select Compare JSON or press Ctrl + Enter.
4. Review the summary and inspect each changed path.
5. Copy the text report when you need to share the result.

{
  "version": 1,
  "features": ["format", "validate"],
  "active": true
}

{
  "version": 2,
  "features": ["format", "diff"],
  "region": "eu-west-1"
}

This comparison reports a changed version, a changed array item, a removedactive property, and an added region property.

• Objects are matched by property name, so source property order is ignored.
• Arrays are compared by zero-based index because array order is significant.
• Numbers, strings, booleans, and null are compared as parsed JSON values.
• A type change, such as a number becoming a string, is reported as one changed path.
• Missing properties are distinct from properties explicitly set to null.

JSON Diff answers what changed between two valid documents. TheJSON Formatter makes one valid document readable or compact, while theJSON Validator focuses on syntax errors and document structure. Validate or repair malformed input before comparing it.

Native JSON parsing does not preserve comments, whitespace, escape spelling, duplicate object names, or original property order. Those source-text details are therefore outside this structural comparison. The tool also blocks unsafe integer literals that native JavaScript numbers could round.

Each editor accepts up to 1,000,000 UTF-16 code units. A comparison can inspect up to 20,000 value pairs and 100 nesting levels, while the visible result table is capped at 1,000 rows. These explicit limits keep malformed or unexpectedly large data from blocking the page.

• Review fields changed between two API responses.
• Compare configuration revisions before a deployment.
• Inspect expected and actual JSON in a failing test.
• Check whether a formatter-only change preserved the parsed data.