DEVELOPER FLAGSHIP
JSON Diff
Top-level comparison only; not a semantic deep diff.
At a glance
JSON Diff — JSON Diff compares two JSON documents by meaning, not by text — so a reformatted file shows as equal, and a genuinely changed value is pinpointed with its full path.
Free for the core workflow, no account required. Parsing and transformation are performed locally in the browser from the data you enter.
About JSON Diff
JSON Diff compares two JSON documents by meaning, not by text — so a reformatted file shows as equal, and a genuinely changed value is pinpointed with its full path.
A text diff sees whitespace. A JSON diff sees structure: it parses both documents, walks them key by key, and reports what was added, removed, or changed, with the path to each difference. That distinction decides whether a deploy review takes minutes or an afternoon. Worked example — compare document A {"name":"Aisha","age":29,"city":"Multan","role":"admin"} with document B {"name":"Aisha","age":30,"city":"Multan","plan":"pro"}. The diff reports exactly three changes: changed age at $.age, from 29 to 30; removed role at $.role, which held "admin"; added plan at $.plan, with the value "pro". Name and city are untouched, so they do not appear at all. Reorder the keys in B and the diff still reports the same three changes, because JSON objects are unordered — a text diff of the same two files would flag nearly every line. Table — the four kinds of difference this tool reports: added, a key present only on the right; removed, a key present only on the left; changed, the same key with a different value, shown old then new; type changed, the same key holding a different kind of value, such as the string "30" versus the number 30. Before / after — before: two 200-line config files side by side, with the eye hunting for the one line that moved; after: a short list of three paths ($.age, $.role, $.plan) that names every difference and nothing else. Picture two trees with the same trunk: the diff walks both and marks only the branches that differ. One developer step usually leads to the next. The HTML Minifier & Formatter squeezes the bytes out of a web page’s markup — comments, indentation, and redundant spaces, while the JSON Path Explorer queries into a JSON document the way a search query finds rows in a database. The Regex Tester runs JavaScript regular expressions against your real text with live match highlighting too. Sources: ECMA-404, The JSON Data Interchange Syntax (2017); RFC 6902, JavaScript Object Notation (JSON) Patch (2013); MDN Web Docs, "JSON" (accessed November 2026). Content last reviewed: November 2026. The diff understands JSON structure, not just text: it parses both documents and compares key by key, so reformatted-but-identical JSON shows as equal while genuinely changed values are pinpointed with their full paths.
Primary objective: Compare two JSON objects and report changed, added and removed top-level properties for API and configuration review.
Privacy assurance: Parsing and transformation are performed locally in the browser from the data you enter.
How to Use JSON Diff
- Paste the original JSON on the left and the new version on the right — both must be valid JSON first.
- Run the comparison and read the change list, which is grouped into added, removed, and changed.
- For each changed key, check the old and new values and the full path (for example $.server.port) so you know exactly where it lives.
- If the list is full of reordered arrays, sort both arrays first and re-run — order changes drown out real changes.
- Copy the change list into your review note or ticket so the next person sees what moved without re-running the diff.
Key Use Cases & Applications
- Verifying that an API response matches the expected test fixture, field for field.
- Reviewing a staging config against production before a deploy goes out.
- Finding what changed in a settings file after an application update rewrote it.
- Comparing two versions of a translation file to see which strings were added or dropped.
- Verifying API responses match expected fixtures in testing.
- Reviewing config changes between staging and production.
Frequently Asked Questions
Why does the diff ignore my key reordering?
Because JSON objects are unordered by definition: {"a":1,"b":2} and {"b":2,"a":1} are the same object. The diff compares meaning, and key order carries no meaning.
How do I find a change buried ten levels deep?
Use the reported path. A change at $.server.database.pool.max tells you the exact nesting — open that path in the formatted JSON instead of scanning from the top.
What does "type changed" mean?
The key exists on both sides but holds different kinds of values — the string "30" on one side and the number 30 on the other. Code that reads the value will behave differently, so this is worth more attention than a plain value change.
Can I diff JSON against a live API response?
Yes. Paste the expected fixture on one side and the response body on the other. If the response has timestamps or random ids, ignore those keys first or the diff will be noise.
By Shehzad Hussain — owner and editor of ExpTool, based in Multan, Pakistan. He builds and tests every tool on this site himself.
Last updated: 2026-11-04