Loading...
Compare two JSON objects side by side. Highlights added, removed, and changed values.
Left (original)
Right (modified)
Pro tip
Reviewing JSON changes in a PR? Git AutoReview shows JSON diffs directly in your PR review with AI explanations of what changed and why it matters.
We built this because plain text diffs are terrible at JSON — they flag key reordering as a change even when nothing actually changed. This tool walks through both objects recursively, comparing every nested key and value, and only flags real differences. Reorder your keys all you want, no false positives.
We use this ourselves mostly for comparing API response versions — a backend team ships a change and you need to see exactly which fields moved, disappeared, or got new defaults. Config diffs are the second big one: two environment files, package.json before and after a dependency bump, Terraform state snapshots.
Config changes in PRs get missed constantly because reviewers skim JSON diffs — a changed timeout value or a removed feature flag hides in 200 lines of unchanged keys. A structural comparison surface those changes immediately. Git AutoReview does this automatically and explains what each change means in context.
It parses both inputs and walks every key recursively — added, removed, and changed values get highlighted. Unlike a text diff, reordering keys without changing values produces zero false positives.
Yes. Paste minified JSON in either panel — the tool parses it regardless of formatting. The diff output is always formatted for readability.
No. All comparison happens in your browser using JavaScript. Your data never leaves your machine.
Added keys, removed keys, changed values, and type changes (like string to number). Each difference shows the exact path so you know where to look.
When a PR modifies a JSON config (package.json, tsconfig, CI pipeline), comparing the before and after versions shows exactly what changed. Git AutoReview does this automatically for every PR with AI explanations.
This tool compares by key name, not by position. If you reorder keys without changing values, no differences will be shown. This is a structural comparison, not a text diff.
Yes. The comparison is fully recursive. It walks through every level of nesting and reports the exact path where differences occur, like 'config.database.port'.
Ctrl+Enter (or Cmd+Enter on Mac) to compare, Ctrl+Shift+C to copy the diff results to your clipboard.
Save the response from each API version (using curl, Postman, or browser DevTools), paste them into the left and right panels, and click Compare. The tool will show exactly which fields changed between versions.
Developer Toolkit by Git AutoReview
Free tools for developers. AI code review for teams.