JSON Formatting, Validation and Minification: A Practical Guide
Formatting vs. minifying: opposite goals
Formatting (also called "pretty-printing") adds consistent indentation and line breaks to JSON so a human can read its structure at a glance — nested objects and arrays become visually obvious. Minifying does the reverse: it strips every unnecessary whitespace character, producing the smallest possible file size at the cost of readability.
Both operations produce functionally identical data — a JSON parser reads formatted and minified JSON exactly the same way — so the choice is purely about audience. Format JSON when a person needs to read or debug it; minify it before sending it over a network or storing it, where every byte has a small but real cost at scale.
What a validator is actually checking
A JSON validator checks that the text conforms to the JSON specification: matching brackets and braces, correctly quoted keys and string values (JSON requires double quotes, not single), no trailing commas after the last item in an object or array, and proper escaping of special characters inside strings. It is a strict syntax check, not a check of whether the data makes logical sense for whatever application will consume it.
This distinction matters because JSON that looks correct to the eye often fails validation for small reasons: a trailing comma copied from JavaScript object syntax (which tolerates it) but invalid in strict JSON, an unescaped quote inside a string, or a comment (JSON has no comment syntax, unlike JavaScript or JSON5 variants).
The most common syntax mistakes
Trailing commas are the single most frequent error, especially when JSON is hand-edited after being copied from JavaScript code. Using single quotes instead of double quotes for strings and keys is the second most common, since many programming languages accept either interchangeably. Unquoted keys (valid in JavaScript object literals, invalid in JSON) and unescaped backslashes or quotes inside string values round out the most frequent causes of a failed validation.
When to convert JSON to CSV instead
JSON's nested structure is well suited to representing hierarchical data — objects containing objects, arrays of varying length — but that same flexibility makes it awkward to open in a spreadsheet. Converting to CSV makes sense specifically when the JSON represents a flat, uniform list of records (an array of objects that all share the same keys), since CSV has no native way to represent nesting. Deeply nested or irregular JSON usually needs to be restructured before a CSV conversion produces something useful, rather than a one-to-one automatic translation.