Compare API responses
Check whether a backend response changed between environments, versions, or test runs.
Free browser tool
The JSON diff tool compares two JSON values and reports basic differences between paths, keys, array positions, and values. It is useful when checking API changes, configuration updates, webhook payloads, feature flag files, or copied examples that look similar but behave differently.
This is intentionally a practical text summary rather than a heavy visual diff. The tool validates both inputs first, then lists missing paths and changed values using readable JSON path notation. It works best for debugging small to medium JSON documents.
Compare two JSON inputs and list changed, missing, or added paths.
JSON documents can look almost identical while containing a small change that matters. A renamed key, missing field, changed boolean, reordered array, or nested value can affect an API contract, feature flag, or configuration file. The JSON Diff tool validates two inputs and reports basic differences using readable JSON paths.
This diff is intentionally practical rather than decorative. It does not try to render a full code editor comparison. Instead, it lists what changed, what only exists in A, and what only exists in B. That makes it useful for quick debugging when you need to understand why two payloads behave differently.
Arrays are compared by index, and objects are compared by key. If an array is reordered, several differences may appear even when the same values are present. For many API and config workflows, index-based comparison is still the clearest first pass because order often matters.
Check whether a backend response changed between environments, versions, or test runs.
Find differences between two JSON config files before deploying a settings update.
Compare flag payloads to see whether targeting, variants, or booleans changed unexpectedly.
Compare webhook examples from different events or providers to understand structural differences.
The diff reports that enabled changed from true to false and trial only exists in JSON B.
{
"enabled": true,
"plan": "free"
}{
"enabled": false,
"plan": "free",
"trial": true
}Both inputs must be valid JSON. Run validation first if either side fails to parse.
Arrays are compared by position. Reordered arrays can show many path changes.
Whitespace is not a JSON value. The diff compares parsed values, not indentation.
A change deep in an object appears as a path such as $.user.profile.name. Read the full path before editing.
Spot API response changes quickly.
Compare config versions without extra software.
Find changed values in nested JSON.
Readable JSON helps you understand the diff output and inspect the original payloads.
Use payloads from the same endpoint or config area so differences are meaningful.
If order should not matter, sort arrays before comparing or compare specific object keys.
A short list of changed paths is useful context for teammates reviewing a behavior change.
A practical guide to comparing JSON payloads, configs, arrays, and API responses without getting distracted by formatting.
API responses are easier to debug when you validate syntax, format payloads, inspect errors, and compare changes deliberately.
Trailing commas, bad quotes, comments, unclosed brackets, and undefined values are the JSON mistakes developers hit most often.
Yes. Both JSON documents must parse successfully before comparison.
No. It shows a clear list of changed, added, and missing paths.
Yes. Arrays are compared by index, so reordered arrays can show many changes.
The tool runs in your browser and does not require login, a database, or server-side processing.