How to compare JSON keys and values without uploading data

1. Decide whether structure or values matter

Choose Compare keys when you are validating a response contract or configuration shape. The tool represents keys as paths, so $.profile.email and $.billing.email remain distinct. Choose Compare values when you need to find primitive strings, numbers, booleans, or null values that occur in one document but not another.

2. Validate before you compare

Copy the raw JSON, not a console object that has been truncated or reformatted with non-JSON comments. The tool requires valid JSON: strings use double quotes, commas separate values, and all brackets close. If a response is sensitive, remove credentials, access tokens, email addresses, and personal data before sharing it with another person.

• Use complete JSON documents from comparable environments.
• Compare the same endpoint or configuration scope.
• Remove secrets before creating a share link or attaching an example to a ticket.

3. Treat differences as a review queue

Common paths show the stable portion of a schema. Only in A and Only in B show paths or values found exclusively on one side. For arrays, paths include an index such as $.users[0]; a reordered array can therefore look structurally similar while its values differ. Use the result to focus investigation, then return to the source documents for the surrounding context.

4. Know when you need a different kind of diff

This workflow compares membership; it does not generate a patch, preserve formatting, or match complete nested records by identity. Use a code-aware diff when you need line changes in a source file. Use a schema validator when you need formal API contract enforcement. For IDs or log lines already one-per-line, the general list tool is faster.