Does this run entirely in my browser?

Yes. JSON.parse + recursive comparison + textual diff output — all pure JavaScript. Neither side's JSON is uploaded. Safe for production payloads, secret keys in configs, or any other sensitive content.

How is this different from the Text Diff Checker?

The Text Diff Checker compares two text blocks line-by-line — useful for diffing code or prose. The JSON Diff Checker parses both inputs as JSON and compares their STRUCTURE: reordered object keys produce no diff, pretty-printing differences are ignored, type changes are surfaced explicitly. Use line diff for code, structural diff for JSON.

Does it support deep arrays of objects?

Yes — the diff recurses into nested arrays and objects without depth limits. Arrays are compared positionally (element 0 vs element 0, etc.). For arrays where you want to match by content (e.g., 'find me the elements unique to each side regardless of position'), this tool is not the right fit — you'd need a tool that supports id-based array diffing.

What if my inputs aren't valid JSON?

The tool surfaces the parse error inline for whichever side failed. Fix the JSON (often a trailing comma, single-quoted string, or unquoted key) and the diff updates live. For pretty-printing and validating, our JSON Formatter is the sibling tool.

How are added/removed/changed counted differently from 'unchanged'?

Each primitive (leaf) value contributes one count: 'added' for keys only on the Right, 'removed' for keys only on the Left, 'changed' for keys present on both with different values, 'unchanged' for keys present on both with identical values. Whole-object additions/removals add up across all their leaf primitives.

Can I diff two JSON arrays at the top level?

Yes. Top-level arrays are diffed positionally — element 0 on Left vs element 0 on Right, etc. If lengths differ, extra elements are shown as additions or removals.

Does the tool work for very large JSON files?

Performance depends on input size and depth. Hundreds of kilobytes are fast; multi-megabyte deep-nested JSON may take a moment. For huge inputs, use a CLI tool like jd , jsondiffpatch , or diff <(jq -S . a.json) <(jq -S . b.json) which can stream and avoid loading both into browser memory.

数据格式

JSON 差异

JSON 差异，在浏览器中快速完成单项任务。

数据留在您的设备无需上传至服务器可离线使用

为什么用这个工具

JSON 差异在浏览器本地运行，适合快速处理与复制结果。

JSON 差异适用于日常高频小任务，打开即用。

默认本地处理，便于快速检查与复制结果。

如何使用

01输入或粘贴所需内容。

02查看结果并复制使用。

复制前快速检查

先确认输入格式符合你的预期。

在把结果用于文档、链接、配置或消息前快速扫一眼。

只复制你真正需要的输出。

使用场景

Review API response changes between releases

Capture a sample response before and after a backend change. Drop both in and immediately see which fields were added, removed, or changed — far faster than scanning two pretty-printed payloads side by side.

Diff config or feature-flag JSON between environments

Paste prod's feature-flag JSON on one side and staging's on the other. The structural diff surfaces every divergence without false positives from key-order or formatting differences.

Compare two snapshots of state

When debugging a state-management bug, capture the state object before and after the suspect action. The diff shows exactly which fields changed — useful for finding unexpected side effects.

Verify a JSON Patch / RFC 6902 application

Compare the original document against the post-patch result to confirm the patch did what you intended. Especially useful when the patch has many operations.

Sanity-check schema migration outputs

When migrating between schema versions, run the migration on a sample document and diff against expected output. Faster than writing assertion-by-assertion tests for ad-hoc changes.

使用技巧

01
Object diff is order-insensitive; array diff is positional
JSON objects are unordered by spec, so <code>{a:1,b:2}</code> equals <code>{b:2,a:1}</code> — no diff. JSON arrays are ordered, so <code>[1,2]</code> ≠ <code>[2,1]</code> — diff. For order-insensitive array comparison (set semantics), this tool isn't the right fit — sort both arrays first and re-diff.
02
Type changes count as 'changed'
If a value's type changes (e.g., <code>"42"</code> string to <code>42</code> number), it counts as one changed value. The diff line shows both the old and new representations so the type shift is visible.
03
Counts represent leaf-level changes
Added / removed / changed counts measure primitive (leaf) operations, not whole-subtree changes. If you delete a nested object with 5 keys, you get 5 'removed' counts, not 1. This is the granularity most useful for understanding how impactful the diff is.
04
Use the JSON Formatter first if inputs look unstructured
If your two inputs are minified or contain extraneous whitespace, paste through the JSON Formatter first. The diff itself ignores formatting, but pretty-printing first makes the diff output easier to read.

常见问题

这个工具会上传数据吗？

默认在浏览器本地处理。

JSON 差异

JSON 差异，在浏览器中快速完成单项任务。

数据留在您的设备无需上传至服务器可离线使用

忽略对象键顺序

左侧 JSON右侧 JSON

状态

差异生成成功

新增

删除

修改

未变

差异

{
    address: {
      city: "New York"
    + country: "US"
      zip: "10001"
  }
  - age: 30
  + age: 31
    name: "Alice"
    tags: [
      "admin"
    - "beta"
  ]
}

为什么用这个工具

JSON 差异在浏览器本地运行，适合快速处理与复制结果。

JSON 差异适用于日常高频小任务，打开即用。

默认本地处理，便于快速检查与复制结果。

如何使用

01输入或粘贴所需内容。

02查看结果并复制使用。

复制前快速检查

先确认输入格式符合你的预期。

在把结果用于文档、链接、配置或消息前快速扫一眼。

只复制你真正需要的输出。

使用场景

Review API response changes between releases

Diff config or feature-flag JSON between environments

Paste prod's feature-flag JSON on one side and staging's on the other. The structural diff surfaces every divergence without false positives from key-order or formatting differences.

Compare two snapshots of state

When debugging a state-management bug, capture the state object before and after the suspect action. The diff shows exactly which fields changed — useful for finding unexpected side effects.

Verify a JSON Patch / RFC 6902 application

Compare the original document against the post-patch result to confirm the patch did what you intended. Especially useful when the patch has many operations.

Sanity-check schema migration outputs

When migrating between schema versions, run the migration on a sample document and diff against expected output. Faster than writing assertion-by-assertion tests for ad-hoc changes.

使用技巧

01
Object diff is order-insensitive; array diff is positional
JSON objects are unordered by spec, so <code>{a:1,b:2}</code> equals <code>{b:2,a:1}</code> — no diff. JSON arrays are ordered, so <code>[1,2]</code> ≠ <code>[2,1]</code> — diff. For order-insensitive array comparison (set semantics), this tool isn't the right fit — sort both arrays first and re-diff.
02
Type changes count as 'changed'
If a value's type changes (e.g., <code>"42"</code> string to <code>42</code> number), it counts as one changed value. The diff line shows both the old and new representations so the type shift is visible.
03
Counts represent leaf-level changes
Added / removed / changed counts measure primitive (leaf) operations, not whole-subtree changes. If you delete a nested object with 5 keys, you get 5 'removed' counts, not 1. This is the granularity most useful for understanding how impactful the diff is.
04
Use the JSON Formatter first if inputs look unstructured
If your two inputs are minified or contain extraneous whitespace, paste through the JSON Formatter first. The diff itself ignores formatting, but pretty-printing first makes the diff output easier to read.

常见问题

这个工具会上传数据吗？

默认在浏览器本地处理。

JSON 差异

为什么用这个工具

如何使用

复制前快速检查

使用场景

使用技巧

常见问题

相关工具

JSON 格式化

JSON 到 typescript

文本差异检查

JSON 差异

为什么用这个工具

如何使用

复制前快速检查

使用场景

使用技巧

常见问题

相关工具

JSON 格式化

JSON 到 typescript

文本差异检查

JSON 差异

常见问题

JSON 格式化→

JSON 到 typescript→

文本差异检查→

JSON 差异

常见问题

JSON 格式化→

JSON 到 typescript→

文本差异检查→

JSON 格式化

JSON 到 typescript

文本差异检查

JSON 格式化

JSON 到 typescript

文本差异检查