Guide · Updated 2026-07-23
How to Pretty-Print and Validate JSON
Why formatted JSON matters for debugging APIs, how minified payloads differ, and how to catch syntax errors early.
Readable JSON saves time
API responses and config files often arrive as a single line. Pretty-printing adds indentation and line breaks so nested objects are scannable. When you are comparing two payloads or hunting a wrong field name, formatting is the first step — not a luxury.
Validation is the second step. A missing comma, trailing comma in strict parsers, or unquoted key will break consumers. Catching that in a formatter before you paste into production config prevents a class of 'works on my laptop' failures.
Formatted JSON also makes code review humane. Reviewers spot accidental nulls, empty arrays, and duplicated keys faster when structure is visible.
Pretty vs minify
Pretty JSON is for humans. Minified JSON is for transport: smaller payloads, fewer bytes on the wire. Many CDNs and APIs already minify responses. Keep a pretty copy in docs and git when humans edit the file; minify only when size or a specific API contract requires it.
Never minify secrets into screenshots or tickets without redacting values. Formatting tools that run in the browser keep sensitive tokens on your machine while you inspect structure.
Some APIs return pretty JSON in development and minified in production. Do not assume whitespace differences mean semantic differences — compare parsed objects, not raw strings.
Validation and strictness
JSON allows only double-quoted strings, no comments, and no trailing commas. JavaScript object literals look similar but are not JSON; pasting `{foo: 1}` into a strict validator will fail.
Numbers must not have leading zeros (except 0.x). NaN and Infinity are not valid JSON. Dates should be ISO strings, not unquoted tokens.
Large integers beyond IEEE double precision may round-trip incorrectly in JavaScript formatters. Financial and ID fields sometimes need string encoding — validation catches syntax, not business rules.
Practical checklist
Paste the payload, format it, confirm it parses, then search for the keys you care about. If you are editing by hand, re-validate after every change. For diffs between two API responses, format both sides first so line-based diff tools highlight real field changes instead of wrapping noise.
Sort keys alphabetically only when it helps comparison, not as a permanent storage format — key order is not semantically meaningful in JSON but sorted diffs are easier to read.
When embedding JSON inside HTML or SQL, escape quotes properly. A valid JSON document can still break its host document if pasted raw.
Ready to try it? Open JSON Formatter