JSON diff tool for Mac: compare API responses locally

The short answer: use a local JSON diff when the payload came from an API response, support ticket, feature flag, config file, design-token export, or private test run. Compare objects or arrays locally, review added, removed, changed, and nested values, then paste only the small summary into the ticket or pull request.

TeenyTool includes JSON Diff in its Mac menu bar toolbox. It is meant for the manual review moment between "these two payloads changed" and "here is the exact difference worth discussing."

This page is not about formatting JSON. The related formatter guide is useful before the comparison. This guide is for deciding what changed between two valid JSON values.

Quick decision table

01Start by validating both sides

A diff is only useful after both inputs parse. TeenyTool's JSON Diff validates each side with Apple's JSONSerialization. If either side is invalid, the app shows the parse error instead of pretending the diff is meaningful.

The tool expects each root value to be a JSON object or array. That keeps the comparison focused on practical payloads: API responses, config objects, token files, lists, and arrays of records.

If your first issue is broken syntax, use the offline JSON formatter for Mac first. Its Pretty mode sorts object keys, while Compact preserves their input order. Once both sides parse, return here to compare values rather than formatting differences.

02Review added, removed, and changed values first

The first useful pass is the small one. Which keys were added? Which keys disappeared? Which values changed? Which nested branch contains the change?

TeenyTool's source recursively compares dictionary keys in sorted order and marks each row as added, removed, changed, unchanged, or nested. The summary header counts added, removed, and changed items so the review starts with scope before details.

Leave unchanged rows hidden unless you need context. Most payload reviews get slower when every identical key stays on screen.

03Treat arrays as their own problem

Object diffs are mostly key comparisons. Arrays are different. Order, duplicates, inserted records, removed records, and changed records can all be present in the same payload.

TeenyTool uses a longest common subsequence pass for arrays. That helps pair unchanged or matching values before marking inserted, removed, and changed rows. It will not understand your domain model, but it gives a better manual starting point than a raw line diff.

For array-heavy API responses, check the fields that identify each record: ID, slug, timestamp, type, or name. A visual JSON diff can show movement. Your domain knowledge still decides whether the movement matters.

04Keep private payloads local

API responses often include real account IDs, emails, internal feature flags, addresses, tokens, unpublished copy, customer-specific settings, or values copied from an admin screen. Those do not belong in a random browser tab just because the task feels small.

The local rule is practical: if the JSON would not belong in a public issue, compare it on your Mac. Then paste the summary, not the payload, into the place where people need to make a decision.

The broader TeenyApps hub, Mac design token QA checklist for colors and JSON, uses the same rule for token files and handoff notes.

05Know what JSON Diff does not prove

A JSON diff proves a difference. It does not prove that the new payload is valid for your API, compatible with a client, safe for a migration, or correct for a design system.

Use schema validation when the contract matters. Use tests when behavior matters. Use source control when the file belongs in a repo. Use TeenyTool when a copied payload needs a fast local manual comparison before the next step.

If the JSON holds color tokens, pair the diff with the TeenyColor guide to using an sRGB color picker for Mac design tokens. The file diff tells you what changed. The sampled UI color tells you what actually rendered.

Ten-minute JSON diff pass

1. Paste the old JSON on the left and the new JSON on the right.
2. Fix parse errors before reviewing the diff.
3. Confirm the roots are objects or arrays.
4. Review added, removed, and changed counts.
5. Open nested branches that changed.
6. Turn on unchanged rows only when you need context.
7. Check array changes against record IDs, slugs, names, or timestamps.
8. Write a short summary with the important path and value changes.

Common questions

When should I use a JSON diff tool on Mac?

Use a local JSON diff when you need to compare API responses, token files, feature flags, config changes, or copied payloads that should not be uploaded to a web tool.

Can TeenyTool compare JSON arrays?

Yes. TeenyTool's JSON Diff works with object or array roots and includes array matching logic so added, removed, and changed array values are easier to review.

Is a JSON diff the same as schema validation?

No. A JSON diff shows what changed. Schema validation proves whether the result follows a specific contract. Use both when an API or token file has strict rules.

Sources checked

• TeenyTool feature claims were checked against the local homepage and source files for the tool catalog, JSON Diff, JSON Formatter, favorites, shortcuts, JSON parsing, dictionary diffing, array matching, and unchanged-row filtering.
• Apple JSONSerialization documentation for JSON parsing behavior.
• RFC 8259 for the JSON data interchange format.