JSON Diff — compare two JSON documents

Paste an original and a new JSON document to see exactly what changed. APILens compares them structurally — key order and whitespace don't matter — and lists every added, removed and changed path. Everything runs in your browser; nothing is uploaded.

Original JSON

New JSON

Differences appear here as path-tagged lines.

JSON diff — frequently asked questions

Is this a text diff or a JSON diff?

A JSON diff. Both sides are parsed into structured values and compared by path, so reordered keys, different indentation and trailing commas do not show up as changes — unlike a character-level text diff.

Does my JSON leave my browser?

No. Comparison runs 100% client-side. Nothing is uploaded, logged or tracked — which matters when you're diffing API payloads or config that may contain secrets.

What do added, removed and changed mean?

Added = a value exists only in the new document. Removed = only in the original. Changed = the same path has a different value (or a different type) on each side.

Does it handle nested objects and arrays?

Yes. The comparison walks both trees in parallel and reports the full path of every difference — e.g. users[2].email — including array insertions and removals by index.

What if the documents are identical?

The tool reports that they are identical. Useful for confirming a refactor or a config change produced no functional difference.

Are there limits?

The free tier handles documents up to ~2 MB. For very large payloads (up to 20 MB), APILens Pro ($19 lifetime) unlocks large-file mode — it also funds this open-source project.