Local JSON comparison
Your JSON is parsed and compared in this browser without being sent to a comparison API.
Rules: Object key order is ignored. Array order and JSON value types are significant.
Ready to compare
Enter two valid JSON documents, then select Compare JSON or press Ctrl+Enter.
Comparison result
Highlighted JSON comparison
Differences are colored directly on formatted JSON with object keys ordered for comparison. Scroll either pane to move both views together.
| JSON path | Status | Original value | Changed value |
|---|
Compare JSON Structures and Values
JSON Compare parses two JSON documents and reports structural differences at precise paths such as $.settings.timeout or $.items[2].
The comparison runs locally in the browser. Object key order is ignored, while array positions, JSON value types, and primitive values are compared strictly.
Key features
- Highlighted JSON comparison View both formatted JSON documents side by side with colored lines for added, removed, changed, and type-changed values, then use each JSON path for exact navigation.
- Four difference categories The summary separates added properties or items, removed data, changed primitive values, and values whose JSON type changed.
- Structural JSON semantics Objects are compared by property name regardless of key order. Arrays are compared by index, so moving an item can produce several positional differences.
- Copyable JSON report Copy the displayed comparison as structured JSON for issue reports, code review notes, automated follow-up, or debugging records.
How to compare two JSON documents
Parse two JSON values and inspect every structural difference by path.
- Paste the original JSON Enter the baseline JSON object, array, string, number, boolean, or null value in the Original JSON field.
- Paste the changed JSON Enter the JSON version you want to verify in the Changed JSON field. Each input must be valid standard JSON and no larger than 1 MB.
- Run the structural comparison Select Compare JSON or press Ctrl+Enter. Correct any syntax error shown beneath an input before comparing again.
- Review highlighted content or copy the report Inspect colored differences directly in the synchronized JSON panes, use the path table for exact values, then copy the displayed report when you need a machine-readable record.
Usage tips
- Use standard JSON with double-quoted property names and no comments or trailing commas.
- Remember that arrays are positional: inserting an item near the start can make later indexes appear changed.
- JavaScript parses numbers beyond the safe integer range with possible precision loss; encode exact large identifiers as strings before comparing.
- When more than 1,000 differences exist, the totals still cover the full comparison but the detail table and copied report contain only the first 1,000 entries.