Compare JSON Objects Online
Paste two JSON objects. See what was added, removed, or changed — key by key, at every level of nesting.
🔒 100% private — runs entirely in your browseror try sample data
Paste two JSON objects. See what was added, removed, or changed — key by key, at every level of nesting.
🔒 100% private — runs entirely in your browseror try sample data
Compare JSON Objects performs a deep, semantic comparison of two JSON structures and shows you exactly which keys were added, removed, or modified at every level of nesting. Unlike a plain text diff, this tool understands JSON structure — it matches keys by name, recurses into nested objects and arrays, and provides precise path-based highlighting of every change.
JSON is the universal data interchange format. Configuration files, API payloads, database exports, feature flags, and environment settings are all stored as JSON objects. When these change — whether through a code deploy, a config update, or an API version bump — you need to know exactly what differs. Scanning raw JSON by eye is slow and unreliable, especially for deeply nested structures with hundreds of keys.
Paste any two JSON objects and get an instant, color-coded breakdown. Added keys appear in green, removed keys in red, and modified values are highlighted with both old and new values visible. The tool auto-corrects common syntax issues like trailing commas and single-quoted strings, and runs entirely in your browser so your data stays private.
// staging.json
{ "database": { "host": "db.staging.internal", "pool": { "max": 10 }, "ssl": false }, "logging": { "level": "debug" }
} // production.json
{ "database": { "host": "db.production.internal", "pool": { "max": 50 }, "ssl": true, "replication": { "enabled": true } }, "logging": { "level": "warn" }
} // Diff reveals:
// - host changed (staging → production)
// - pool.max increased (10 → 50)
// - ssl enabled
// - replication section added
// - log level changed (debug → warn)Environment config diffs catch missing keys and mismatched values before they cause production incidents. Always compare staging vs production configs before deploying.
// Before release
{ "flags": { "dark-mode": { "enabled": false, "rollout": 0 }, "new-checkout": { "enabled": true, "rollout": 50 }, "legacy-api": { "enabled": true, "sunset": null } }
} // After release
{ "flags": { "dark-mode": { "enabled": true, "rollout": 100 }, "new-checkout": { "enabled": true, "rollout": 100 }, "legacy-api": { "enabled": true, "sunset": "2026-06-01" } }
} // Diff shows:
// - dark-mode flipped on, rollout → 100%
// - new-checkout rollout → 100%
// - legacy-api sunset date setFeature flag changes often ship without code changes. Comparing flag JSON before and after a release documents exactly what was toggled.
// Exported schema as JSON (before migration)
{ "tables": { "users": { "columns": [ { "name": "id", "type": "integer", "primary": true }, { "name": "email", "type": "varchar(255)" }, { "name": "name", "type": "varchar(100)" } ], "indexes": ["idx_users_email"] } }
} // After migration
{ "tables": { "users": { "columns": [ { "name": "id", "type": "uuid", "primary": true }, { "name": "email", "type": "varchar(255)" }, { "name": "name", "type": "varchar(100)" }, { "name": "created_at", "type": "timestamp" } ], "indexes": ["idx_users_email", "idx_users_created_at"] } }
}Schema diffs show column type changes (integer to uuid), new columns, and new indexes at a glance — useful for reviewing migration scripts.
JSON objects are unordered by specification. {"a": 1, "b": 2} and {"b": 2, "a": 1} are semantically identical. This tool compares keys by name, not position, so reordering keys will not produce false differences. However, array element order does matter unless you enable "Ignore array order."
JSON distinguishes between "42" (string) and 42 (number). These are different values and will appear as a modification in the diff. This is intentional — type mismatches are a common source of bugs in APIs and configurations. Pay attention to whether values are quoted or unquoted.
In JSON, {"key": null}, {"key": ""}, and a missing key entirely are three distinct states. A key changing from null to an empty string is a modification. A key being removed entirely is a deletion. The diff tool distinguishes all three cases clearly.
Paste your JSON objects into the two input panels and click Compare. The tool performs a deep, key-by-key comparison and highlights every addition, removal, and modification with color-coded output. You can paste JSON from any source — files, API responses, browser DevTools, or clipboard.
Yes. The comparison walks the entire structure recursively, comparing nested objects, arrays, and primitive values at every level of depth. You will see the exact path to each changed value, such as database.pool.max.
Yes. JSON object keys are compared semantically regardless of their order in the source text. Two objects with the same keys and values arranged differently will be reported as equal. Array element order is respected unless you check "Ignore array order."
Yes. Everything runs in your browser using client-side JavaScript. Your JSON data is never transmitted to any server. This makes the tool safe for comparing sensitive configurations, credentials files, and internal API payloads.
The tool accepts standard JSON (RFC 8259) as well as common JavaScript-style variations like single-quoted strings, trailing commas, and unquoted keys. These are auto-corrected before comparison so you can paste directly from code editors or logs.
The tool handles JSON objects up to 5 MB in size with up to 50,000 elements. For very large files, comparison may take a moment. The 5 MB limit is a security measure to prevent browser memory issues — most real-world JSON files are well within this range.