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.
THE TOOLBOX / DATA & DEVELOPER UTILITIES
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.
SEMANTIC JSON DIFF GUIDE
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.
Catch silent API contract breaks when a number turns into a quoted string (5000 → "5000") or an array becomes null.
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.
Beautify payloads in JSON Formatter, validate contracts in JSON Schema Validator, generate types in JSON to TypeScript, or compare plain text in Text Diff Checker.
| Method | Ignores Key Order | Path Addressing | Best For |
|---|---|---|---|
| Semantic JSON Diff (This Tool) | Yes | RFC 6901 JSON Pointer (/a/b/0) | API v1 vs v2 audits, config drift, webhook debugging |
| RFC 6902 JSON Patch | Yes | [{"op":"replace","path":"/k","value":1}] | HTTP PATCH payloads & audit logs |
| Line-by-Line Text Diff | No | Line numbers | Source code, Markdown, prose |
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.
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.
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.
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.
No. All JSON parsing, AST comparison, path filtering, and RFC 6902 patch generation run 100% locally inside your browser tab.