JSON Diff and Patch Tools

3 tools · free · nothing uploaded

A text diff of two JSON files reports every reordered key as a change. These three compare the documents instead: diff to see what differs, JSON Patch for the RFC 6902 op list a Kubernetes or JSON-API endpoint expects, merge patch for the simpler RFC 7396 shape most HTTP PATCH handlers implement.

Start here

Diff Semantic compare: key order and whitespace are ignored, real changes are not. JSON Patch Generate RFC 6902 ops between two documents, or apply a patch and see the result. Merge Patch The simpler RFC 7396 semantics, which is what most HTTP PATCH endpoints implement.

Why these run in your browser

There is no server-side processing here and no upload step: the page loads, and from then on the parsing, converting and rendering happen in this tab using your machine's CPU. That has three consequences worth knowing about. Your data stays on your machine, which matters when the JSON is a production payload with real customer records in it. There is no file-size limit imposed by us, only by how much memory your browser will give the tab. And once the page has loaded, it keeps working with the network off.

The trade is that very large documents are bounded by browser memory rather than by a beefy server — somewhere past 50 MB a textarea gets sluggish, and dropping the file in is better than pasting it. The privacy page spells out what is and is not collected.