COMPARE API RESPONSES & CONFIGURATION
JSON comparison.
See exactly what changed.
Paste an original response and an updated response.
Follow aligned lines, highlighted characters, and precise field paths.
Valid JSON
Syntax checks passed. No duplicate keys found.
Syntax validation only — this does not check your API schema or business rules.How to fix:
Showing the first issue detected. Correct it and run again to check for more. Your input is never changed automatically.A PRACTICAL JSON DIFF
Find the change.
Keep the context.
Compare two API responses
- Paste the original JSON on the left and the updated JSON on the right.
- Select Compare JSON. The tool parses both documents before comparing values.
- Use Next change to move between highlighted lines, or show only changed lines.
- Switch to Change cards for the exact JSON Pointer path and before/after values.
Example: a changed sort order
Compare these two objects:
{"order":"asc","priority":1}
{"order":"desc","priority":1}The result identifies /order as changed from "asc" to "desc". The unchanged priority stays aligned for context. Select Load example above to try a larger comparison.
What counts as a difference?
Object key order is ignored; {"a":1,"b":2} matches {"b":2,"a":1}. Arrays remain ordered, so moving an item can produce multiple positional changes. This is not an ID-based record matcher. Missing fields, null, false, and empty strings are distinct values.
Duplicate keys and large numbers
If an object repeats a key, Compare uses its last occurrence and displays a warning. It does not rewrite the source. Large IDs retain their exact digits. Numeric spelling is significant: 1 and 1.0 appear as different values.
Privacy and limits
Comparison runs locally in the browser. Inputs are limited to 1 MB each and 120 nesting levels. Change cards show up to 500 differences; aligned previews support up to 12,000 combined lines with a complexity limit. For large changes, character highlighting may fall back to whole-line highlights.