Utilumo
LightDarkSystem
Guide1 min readUpdated September 1, 2026

How to compare JSON files

Short answer

To compare JSON reliably, parse both inputs first, then compare the resulting values by path. That catches real data changes and avoids noise from indentation or key spacing.

Parse before comparing

A plain text diff often highlights formatting changes that do not matter. A JSON diff should parse both inputs first, then compare objects, arrays, and values.

  1. Paste both versionsUse the old value on the left and the new value on the right.
  2. Fix parse errors firstA missing comma or trailing comma can make the whole comparison unreliable.
  3. Review pathsAdded, removed, changed, and type-changed paths show what actually changed in the parsed data.
Try it: JSON DiffCompare two JSON values locally and copy a path-by-path report.Open tool
Array moves look noisyIndex-based array comparison is predictable, but moved items can appear as changed values. Review array-heavy diffs carefully.

References

Questions

Why not use a normal text diff?

Text diffs are useful, but JSON diffs ignore indentation noise and focus on parsed data paths.

Can this compare API responses?

Yes. It is useful for API responses, config files, schema drafts, and AI-generated JSON outputs.

Does this send my data anywhere?

No. Utilumo's developer tools parse and transform input inside the browser tab. Nothing is uploaded, stored, or logged.

Keep reading

Guide1 min readHow to format (pretty-print) JSONFormat messy or minified JSON into clean, indented, readable output. Learn what pretty-printing does, how to validate, and how to minify again.Read
Explainer1 min readWhat is JSON?JSON is a lightweight, text-based format for storing and exchanging structured data. Here is how it works, its data types, and the rules that trip people up.Read