Guide

THE TOOLBOX / DATA & DEVELOPER UTILITIES

JSON Diff Online —
Semantic Compare & RFC 6902 Patch.

Compare two JSON payloads side-by-side ignoring key order, spot value and type mutations, match array items by ID, filter diff paths, and export RFC 6902 JSON Patches locally.

Presets:
Diff Result+2 added−1 removed~3 changed
+ ADDED /features/circuitBreaker = "strict"
- REMOVED /features/legacyWebhook (was true)
~ MODIFIED /features/retries: 3 → 5
+ ADDED /regions/2 = "us-east-1"
! TYPE CHANGED /timeoutMs (string → number): "5000" → 5000
~ MODIFIED /version: "2026.10" → "2026.11"

SEMANTIC JSON DIFF GUIDE

Comparing JSON ASTs, RFC 6901 JSON Pointers, and RFC 6902 Patches.

1. Key-Order-Agnostic AST Diff

Per RFC 8259, object key order carries no semantic meaning. This JSON diff parses both sides into abstract syntax trees so reordered keys produce zero false positives.

2. Instant Type Mutation Alerts

Catch silent API contract breaks when a number turns into a quoted string (5000 → "5000") or an array becomes null.

3. Array ID Matching & Path Filtering

Set Array ID key (e.g. id) to compare lists of user or product objects by identity rather than index, and use the search box to isolate nested paths in large payloads.

JSON Comparison Methods Matrix

MethodIgnores Key OrderPath AddressingBest For
Semantic JSON Diff (This Tool)YesRFC 6901 JSON Pointer (/a/b/0)API v1 vs v2 audits, config drift, webhook debugging
RFC 6902 JSON PatchYes[{"op":"replace","path":"/k","value":1}]HTTP PATCH payloads & audit logs
Line-by-Line Text DiffNoLine numbersSource code, Markdown, prose

Frequently Asked Questions

Why does a standard line-by-line text diff fail when comparing JSON?

Under RFC 8259 Section 4, JSON objects are unordered name/value collections. Different languages and databases (Go maps, Python dicts, PostgreSQL jsonb) emit object keys in different orders. A line-by-line text diff flags every reordered key as a deletion and addition, whereas a semantic JSON diff compares properties structurally by key name.

What is an RFC 6902 JSON Patch and how do I use it?

RFC 6902 defines a standard JSON array of atomic operations (add, remove, replace) that transform a baseline JSON document into a target JSON document. You can copy or download the patch and send it in an HTTP PATCH request with Content-Type: application/json-patch+json.

Can I compare JSON arrays ignoring element order or matching objects by ID?

Yes. Check "Ignore array order" to compare set-like arrays regardless of position, or enter a primary key such as "id" or "uuid" in "Array ID key" so reordered object lists align by identity.

How does JSON Diff catch type mismatches like "5000" vs. 5000?

The structural comparator explicitly separates type mutations (string vs. number, array vs. null) from ordinary value edits so subtle API contract breaking changes stand out immediately.

Are my API responses or config files uploaded to a server?

No. All JSON parsing, AST comparison, path filtering, and RFC 6902 patch generation run 100% locally inside your browser tab.