JSON Diff

Compare two JSON documents by what they mean rather than how they are laid out, and get the path of every difference.

Before

After

变更

The differences appear here.

完全在您的浏览器中运行。

关于此工具

A text diff on JSON reports the wrong thing. Reindent a file or move a property to the top and it lights up as dozens of changed lines while the data is identical. This compares the documents themselves, so what comes back is a list of paths whose values genuinely differ. Objects are treated as unordered, because that is what the specification says they are. Arrays are compared by position, which is the only honest reading when the tool cannot know whether one element was inserted or every element after it was rewritten. Values count as equal when they mean the same thing, so 1 and 1.0 match and two spellings of the same string match, but two long integers have to agree digit for digit before they are called equal.

使用方法

Paste the original document on the left and the changed one on the right.
点击比较。使用交换两侧来反转比较方向。
Read the differences underneath. Each one carries the path of the value and both sides of the change.

常见问题

Why does moving a property not count as a change?

Because a JSON object is a set of name and value pairs, and the specification gives it no order. Two objects with the same properties written in a different order carry the same data, and every parser you are likely to use hands your program the same result for both. Reporting that as a difference would bury the changes that matter. Arrays are the opposite case: their order is part of the data, so it is compared.

Why is one inserted array element reported as many changes?

Because arrays are compared by position. Adding an element at the front of a list moves every element after it to a different index, and the tool reports what it measured rather than guessing that you meant an insert. A result like that is worth reading as one shift rather than many edits. Comparing by identity instead would mean knowing which field identifies an element, and that is a question only you can answer.

Are 1 and 1.0 the same value here?

Yes. They are the same number written two ways, and a diff that called them a change would be measuring the text rather than the data. The same goes for strings, where an escape and the character it stands for are the same string. The exception is integers longer than about sixteen digits: two different ones collapse onto the same floating point value, so those have to agree digit for digit before this tool calls them equal.

JSON Diff

键盘快捷键

本地数据

最近打开的文件

通过链接分享

在以下位置打开分享链接

Before

从 URL 加载

After

从 URL 加载

变更

关于此工具

使用方法