JSON Diff Tool
Work with JSON data more effectively using this json diff tool. Validate, format, and manipulate JSON with ease.
Features
- Syntax Validation: Catch JSON errors instantly
- Pretty Printing: Format JSON for readability
- Minification: Compress JSON for production
- Path Navigation: Find and extract specific values
Example
Input:
``
// Compare two JSON objects side by side
`
Output:
`
Added: +newField
Removed: -oldField
Changed: ~modifiedField
`
Tips
Additions shown in green- Removals shown in red
- Changes highlighted for easy review
How to Use
1. Paste your JSON in the input area
2. Click process to validate and format
3. Review the results
4. Copy or download the result
Best Practices
- Always validate JSON before using in production
- Use consistent indentation (2 or 4 spaces)
- Keep keys in a consistent order
- Remove unnecessary whitespace for APIs
Comparing Two JSON Documents
Diffing JSON as text produces noise: reordered keys, changed indentation and trailing
commas all show as differences when nothing meaningful changed. A structural diff parses both
sides and compares values by path.
Array comparison is the hard part: is Change type Text diff Structural diff Key reordered Shows a change No change Whitespace Shows a change No change Value changed Shows a change Shows a change Key added Shows a change Shows an addition at a path → [b, a] two changes or a reorder? There is
no universally correct answer, which is why diff libraries let you supply a key function for
matching array elements by identity rather than position.
Numbers Are the Recurring Problem
A JSON number is an IEEE 754 double. Three consequences that bite in production:
| Value | What happens |
|---|---|
| Integers above 2⁵³ | Silently lose precision — send IDs as strings |
| Money as a float | 0.1 + 0.2 = 0.30000000000000004 |
| Leading zeros | 007 is invalid JSON; "007" is a string |
NaN and Infinity | Not valid JSON at all |
Twitter hit the first one publicly: 64-bit tweet IDs arrived in JavaScript rounded, so the
API began sending an id_str alongside every id.Keys, Order and Duplicates
Objects are formally unordered, though every JavaScript engine preserves insertion order for
string keys — with one exception: integer-like keys sort numerically and come first.
`javascript
JSON.stringify({ b: 1, 2: 2, a: 3 }); // {"2":2,"b":1,"a":3}
`
Duplicate keys are not an error in the spec, and JSON.parse keeps the last one. Two
parsers can legitimately disagree about which value wins, which has been the basis of real
request-smuggling attacks.
What a Structural Diff Reports
`json
{"id":1,"name":"Ada","role":"admin"}
`
becomes
`json
{"name":"Ada","id":1,"role":"owner"}
`
A text diff calls this three changes; a structural diff calls it one — role changed from admin to owner, and the key reordering is not a change at all.
Rules That Prevent Most JSON Bugs
| Rule | Why |
|---|---|
| No trailing commas | {"a": 1,} is invalid JSON, though JavaScript accepts it in object literals |
| Double quotes only | {'a': 1} is not JSON |
| Keys must be quoted | {a: 1} is a JavaScript object, not JSON |
| No comments | There is no comment syntax; JSON5 and JSONC are different formats |
No undefined, NaN, Infinity | JSON.stringify silently drops or nulls them |
| Numbers are IEEE 754 doubles | Integers above 2⁵³ lose precision — send them as strings |
Parsing Safely
`javascript
try {
const data = JSON.parse(text);
} catch (error) {
// The message names the character offset, which is the fastest way
// to find an unescaped quote in a large document.
console.error(error.message);
}
`
JSON.parse` throws on invalid input rather than returning null, so it always belongs in a try/catch when the source is a file, a request body or a clipboard paste.