JSON Diff
Compare two JSON objects and visualize differences instantly, in your browser.
What it's for
Compare JSONs instantly
Full recursive diff
Detects changes at any nesting level. Objects within objects, nested arrays, primitive values.
100% private
Comparison runs in your browser. Your API data, configs, and secrets never leave your device.
Clear color coding
Green for added, red for removed, amber for changed. Spot differences at a glance.
Instant
Diff is calculated in real time as you type. No buttons, no waiting.
How it works
Three steps, no hassle
Paste the first JSON
Paste the original JSON in the left panel. Can be a valid JSON object, array, or value.
Paste the second JSON
Paste the modified JSON in the right panel. The diff is calculated automatically and instantly.
Analyze the differences
Green: added keys. Red: removed keys. Amber: modified values. The diff is recursive and covers nested objects and arrays.
FAQ
Got questions?
Comparison is recursive, key by key. Both JSON objects are traversed simultaneously: if a key exists in the second but not the first, it is marked as added; if it exists in the first but not the second, as removed; if it exists in both but with different values, as changed. The process repeats for every level of nesting.
Green indicates keys or values added in the second JSON. Red indicates keys or values removed compared to the first. Amber (yellow-orange) indicates keys that exist in both but whose value changed. If there are no colors, both JSONs are identical.
The diff is fully recursive. If a nested object has changes in its properties, the specific modified properties are shown rather than marking the entire object as changed. This lets you pinpoint exactly which field changed in complex structures.
Arrays are compared element by element by index. If the array changed length, extra elements are marked as added or removed accordingly. If element order changed, it will be detected as a modification at each position. To compare arrays regardless of order, sort them manually before pasting.
The most common use cases are: debugging API responses (comparing expected vs actual response), reviewing configuration file changes between versions, validating that a data transformation produces the correct output, and comparing state snapshots in automated tests.
JSON diff in API development, config version control, and RFC 7396 JSON Merge Patch
In REST API development, comparing JSONs is a daily task. When debugging an integration, you need to verify that the API response matches expectations exactly. In microservice environments, a small change in payload structure can break a consumer. JSON diff lets you immediately identify which fields were added, removed, or modified between two versions of a payload.
Version control of JSON configuration files is another frequent use case. Config files like package.json, tsconfig.json, .eslintrc, or appsettings.json evolve over time. Comparing the previous version with the current one helps understand what changed in a pull request, review automatic dependency updates, or audit configuration changes in critical systems.
RFC 7396 (JSON Merge Patch) is an IETF standard that defines how to apply partial updates to JSON documents using the JSON format itself. It is the basis of the HTTP PATCH method for REST APIs. Understanding the differences between two JSONs is fundamental for generating or validating a correct JSON Merge Patch. Convertir.ai performs the diff entirely in your browser, without sending your data to any server.