View My JSON
Skip to main content

View My JSON · compare

JSON Comparator

Staging vs production? Two API responses? Diff JSON path-by-path without juggling formatter tabs.

What a comparison reports

Left:
{ "id": 7, "plan": "free", "tags": ["a", "b"] }

Right:
{ "id": 7, "plan": "pro", "tags": ["a", "b"], "seats": 3 }

plan changed from free to pro, seats was added, and id and tags are unchanged. Reading this as a comparison, the left side is the baseline.

Why use this

  • Side-by-side comparison
  • Path-level change awareness
  • Same workspace as your JSON editor

When it helps

  • Staging vs production response shapes
  • Before/after of a config change

How to use it

  1. Open Compare in View My JSON (Pro).
  2. Paste the baseline and the new payload.
  3. Review added, removed, and changed paths.

Compare is a Pro feature

Comparing two JSON documents is part of View My JSON Pro, not the free toolkit. The free tools, including Format, Validate and the Cards, Table and Tree views, are still useful for preparing each document before you compare them: validate both so you are not diffing a parse error, and format both so you can read the results.

Key order versus array order

These two behave differently in JSON, and a good comparison respects both. Members of an object are unordered, so { "a": 1, "b": 2 } and { "b": 2, "a": 1 } represent the same data, and a comparison should not report a difference between them. Arrays are ordered, so [1, 2, 3] and [3, 2, 1] are different values. This matters when an API returns a list in a different order on each call. The data may be equivalent to you, but a comparison will correctly flag it, since position is part of the array's meaning.

Reading added, removed and changed

Differences fall into three groups. A key present only in the right-hand document was added. A key present only in the left was removed. A key present in both with a different value was changed. Decide which side is the baseline before you start, because the same pair of documents reads in reverse if you swap them. Staging against production, or before against after, are common pairings; write down which is which.

Type changes deserve extra attention. A value that goes from 5 to "5" looks nearly identical on screen but is a different type, and a consumer that expects a number may fail on the string. A change from null to a missing key is also a real difference, even though both can mean nothing here.

Preparing a fair comparison

Noise hides real differences. Timestamps, request IDs and generated tokens will differ on every call, so remove them or ignore them when you read the output. If the two documents are from different environments, check first that they were produced with the same input. And when a diff looks huge, check whether one side was minified and the other formatted; whitespace is not data, so a good comparison ignores it, but a plain line-based text diff will not.

When a comparison is not the right tool

If you only need to know whether two documents are identical, a hash or equality check in code is faster. If you need to test that a response matches a contract, a schema is a better fit than comparing against a saved sample, because samples carry values that are allowed to vary. A comparison shines when a human has to understand what changed, and in that case it pays to compare small, focused documents rather than entire database dumps.

Core viewing, formatting, and validation run in your browser — no account required for those steps. Still strip secrets before pasting into any online tool. Details: privacy policy · about.

FAQ

Is JSON compare free?

Compare is a Pro feature. Free tools still cover viewer, formatter, validator, Cards, Table, and Tree.

Related JSON tools

Guides in this cluster

More guides on the blog · Compare View My JSON with other tools