Paste the original JSON into the left editor and the revised JSON into the right editor. Choose object comparison to inspect changes to parsed values rather than indentation. In the example below, the property name stays the same and only its numeric value changes. Read the modified entry and its path to locate the edit in a larger document. Use the report download when you need to keep the comparison.
Leave ignore options disabled for your first comparison. Ignoring case or order deliberately changes which differences are reported, so enable an option only when your application treats those variations as equivalent. Both inputs must parse before object comparison can succeed. Text mode remains useful when you need to inspect formatting or the original serialized representation.
Left: {"count":1}
Right: {"count":2}
Object comparison: count modified, 1 → 2
JSON objects are unordered by specification, so our tool compares by key names, not position. If the same keys contain the same values in a different order, no difference is reported. This matches how JSON parsers actually work.
Yes — paste any two JSON documents and the tool highlights every difference. This is useful for comparing API responses between environments (staging vs production), before and after a code change, or across API versions.
Added keys (present in right but not left), removed keys (present in left but not right), modified values (same key, different value), and type changes (e.g., a string changed to a number). Each type is color-coded differently.
Both inputs must fit in browser memory after parsing. This comparison panel works with pasted text; it does not enforce a general 100MB file upload promise. Very large or deeply nested documents may be impractical. Compare representative sections when necessary, keeping enough surrounding structure to interpret paths. No fixed processing time is guaranteed.
Absolutely. Common uses include comparing config files between environments, verifying database migration outputs, checking API response changes after deployments, and reviewing JSON schema evolution over time.