Compare JSON files
Paste or upload two or more JSONs, choose a comparison mode, and hit Compare. Differences are grouped by file and path.
Drag & Drop | Paste JSON | Upload .json File
Drag & Drop | Paste JSON | Upload .json File
Ready to compare
Add at least two valid JSONs to enable comparison.
Overview
JSON Compare & Diff Tool — Compare JSON Files Online
Compare two or more JSON files side by side and spot structural and value differences instantly. JsonDrift's JSON diff viewer supports structural mode (keys and types only) and data mode (every value change), multiple inputs, ignore-path rules, tree and side-by-side views, merge patch export, and inline editing. Perfect for API regression testing, config audits, and debugging unexpected payload drift — all without uploading your data.
Why compare JSON?
APIs evolve, configs migrate, and caches go stale. A JSON compare tool shows exactly what changed: new keys, removed fields, type flips, and value deltas. That beats eyeballing two pretty-printed walls of text or unreliable line-based diffs that break when formatting changes.
Structural vs data comparison
Structural mode ignores value differences and reports key additions, removals, and type changes. Use it when you care about schema shape — for example verifying an API still exposes the same fields after a refactor.
Data mode compares values at every path. Use it for regression tests, golden-file review, and answering 'what changed between yesterday's deploy and today?'
Multi-document comparison
Add more than two JSON inputs and pick a base document. JsonDrift diffs every other input against the base, grouping results by file. Compare staging vs production, or three regional config variants in one session.
Features for serious debugging
- Ignore paths to skip noisy or volatile fields (timestamps, request IDs)
- Tree view with colorized nodes for nested exploration
- Side-by-side line diff for text-oriented review
- Export diff reports as Markdown for tickets
- RFC 7396 merge patch generation from differences
- JSON Schema validation per input card
- Session persistence across refreshes
Privacy-first diffing
Comparison runs entirely in the browser. Production payloads, PII-bearing API responses, and secret configs never leave your machine — unlike cloud diff services that require upload.
FAQ
Frequently asked questions
Can I compare more than two JSON files?
Yes. Add additional inputs and select which document is the comparison base.
Does formatting affect the diff?
No. JSON is parsed before comparison. Pretty-print vs minified input compares the same.
Can I ignore specific fields?
Yes. Use ignore paths (e.g. $.timestamp) to exclude volatile fields from results.
Is my JSON uploaded?
No. All comparison logic runs locally in your browser.
Continue with a related tool
All tools- JSON Patch Generator
Generate RFC 6902 JSON Patch or RFC 7396 merge patch between two JSON documents.
- JSON 3-Way Merge
Merge two edited JSON versions against a common base and resolve conflicts.
- JSON Patch Applier
Apply an RFC 6902 JSON Patch or RFC 7396 Merge Patch to a document and get the result.
- AI JSON Cleaner
Smart cleanup — remove nulls, empty strings, trim whitespace, drop empty objects.
- AI JSON Explainer
Human-readable summary of JSON structure and field meanings from naming patterns.
- AI JSON Redactor
Mask passwords, API keys, PII, and secrets before pasting JSON into an LLM.