format validator

JSON Diff Checker

Compare two JSON payloads locally to spot added, removed, or changed fields before API, webhook, or config changes ship.

Results

Paste input and validate locally.
Status
Ready when you validate.
Summary
Ready when you validate.
Diff preview
Ready when you validate.

How to use this validator

  1. Paste the baseline JSON into Base JSON.
  2. Paste the new or changed JSON into Compare JSON.
  3. Run the diff to parse, minify, and compare both payloads.
  4. Review the addition/deletion counts and the plus/minus preview.
  5. If the diff is noisy, prettify each payload first or reduce it to the object/array you are reviewing.

Rules & checks

Parses both JSON inputs first and stops on invalid syntax.

Minifies both payloads before comparison so formatting-only differences are ignored.

Reports additions and deletions and shows a compact diff preview with plus/minus markers.

Runs locally in your browser; pasted JSON is not uploaded, logged, or stored.

Best for quick review of modest payloads, fixtures, and config snippets rather than huge datasets.

Inputs explained

  • Base JSON

    Use this for the current production payload, expected fixture, old config, or baseline API response.

  • Compare JSON

    Use this for the new payload, actual test output, changed config, or response after a deploy.

When to use it

  • Compare API responses before and after a deploy
  • Review webhook event payload changes before updating a handler
  • Check whether staging and production JSON configs differ
  • Compare expected vs actual test fixtures while debugging
  • Spot accidental field removals before publishing docs or SDK examples

Common errors

  • Trailing commas, comments, or unquoted keys that make one side invalid JSON
  • Comparing a full response envelope on one side to a nested object on the other
  • Expecting semantic object-level moves; this tool compares minified JSON text, not schema-aware object paths
  • Large arrays that create noisy diffs when item order changes
  • Secrets or tokens pasted from config files—redact them before sharing screenshots or outputs

Limitations

  • This is a compact text diff of minified JSON, not a deep structural or schema-aware diff viewer.
  • Object key order and array order can affect the preview even when downstream systems treat values as equivalent.
  • Large payloads can be noisy and slow in a browser tab.
  • It does not validate JSON Schema contracts or business rules; pair it with schema validation and tests for release gates.

Tips

  • Validate each side with the JSON Validator if parsing fails.
  • Use JSON Prettify before manual review, then use this diff checker to confirm the actual changed values.
  • Use JSON Minify when you need the compact canonical representation that this diff compares.
  • Use JSON Schema Validator when you need to confirm the changed payload still satisfies required fields and types.
  • For large arrays, isolate one object or sort upstream first so the diff stays readable.

Examples

New API field added

  • Base: {"id":42,"name":"Ada"}
  • Compare: {"id":42,"name":"Ada","plan":"pro"}
  • Shows an addition for the new plan field.

Role changed in a nested object

  • Base: {"user":{"id":42,"role":"member"}}
  • Compare: {"user":{"id":42,"role":"admin"}}
  • Shows the removed member value and added admin value in the compact preview.

Formatting-only change ignored

  • Base: {"enabled":true}
  • Compare: { "enabled": true }
  • Minification keeps the diff focused on value changes instead of indentation.

Invalid JSON blocks comparison

  • Compare: {"name":"Ada",} -> parse error before diffing because trailing commas are not valid JSON.

Deep dive

This JSON diff checker helps developers compare two JSON payloads without uploading private data. Paste a baseline and a changed payload to see additions, deletions, and compact plus/minus output for API responses, webhooks, fixtures, and config files.

The tool parses and minifies both inputs first, so whitespace-only formatting changes do not dominate the diff. Use it for quick review, then rely on structured tests, schema validation, and code review for production-critical contract changes.

FAQs

Is this a structural JSON diff?
No. It parses and minifies both payloads, then shows a compact text diff. That keeps whitespace out of the way, but it is not a full path-by-path object diff.
Does the JSON diff checker upload my payloads?
No. Comparison runs locally in your browser. Pasted API responses, configs, and fixtures are not uploaded, logged, or stored.
Why does key or array order change the diff?
The preview compares minified JSON text. If object keys or array items are reordered, the text can change even when your application treats the data as equivalent.
Can this validate that the changed JSON still matches a schema?
No. Use the JSON Schema Validator for required fields, property types, enums, and API contract checks after you review the diff.
What should I do if the diff is too noisy?
Prettify both payloads for manual review, isolate the object or array you care about, remove volatile fields such as timestamps, or use a dedicated structural diff tool for large payloads.

Related validators

Both JSON payloads are parsed, minified, and compared in your browser. Nothing is uploaded, logged, stored, or shared.

This is a browser-local, minified text diff for quick review. Use schema-aware validation, tests, and dedicated structural diff tooling for production-critical API contracts.