Does key order matter?
No. Objects are compared by key, not by the order keys appear in the file.
Paste left and right JSON to list every added, removed, and changed path. Built for API payloads, config reviews, and snapshot tests.
JSON formatter
Run a tool to see a polished result here
Both sides are parsed, then compared as trees. You get a path-level report, not a line-by-line text diff — so key order and whitespace do not fake a change. Processing stays local.
The editor is prefilled with a small example for JSON Diff. Diff compares two JSON documents and lists structural changes by path, so you can review config or API payload drift. Replace it with your own file; the sample and your payload stay in this tab.
{
"name": "jfmt",
"version": 1,
"flags": { "dark": true }
}This dedicated JSON Diff URL matches that search intent; the homepage stays the general formatter. Diff compares two JSON documents and lists structural changes by path, so you can review config or API payload drift. Related tools on this site include beautify, validate, minify, JSON to CSV, JSON to YAML and JSON to XML — all local. JFmt runs in a Web Worker in this tab. Do not paste production secrets if you share your screen. Read errors in the output pane instead of sending production payloads to another service.
No. Objects are compared by key, not by the order keys appear in the file.
The editor is meant for typical API and config sizes. Extremely large trees may feel slow in the browser.
No. Both documents stay in memory on this device.
No. Parsing and conversion run in a Web Worker in this tab. jfmt.dev does not receive the payload.
So people searching for this operation land on a page that already selects it. Diff compares two JSON documents and lists structural changes by path, so you can review config or API payload drift.