How to Format and Validate JSON

Formatting (pretty-printing) rewrites valid JSON with consistent indentation, line breaks, and spacing so humans can scan structure. It does not change the data model: object keys, array order, numbers, booleans, nulls, and strings stay the same after a correct round-trip.

Pretty print vs minify

• Pretty print — multi-line, indented; best for code review, support tickets, and learning a response shape
• Minify — single line (or minimal whitespace); smaller wire size, common in production responses and some storage

Both start from the same requirement: the input must parse. A formatter cannot invent missing braces. Validate first when paste fails; then choose the layout you need.

Open the JSON formatter, paste a minified API body, and switch between beautified and compact views. That alone catches most “looks fine in Slack” copy errors where a trailing character was clipped.

Validation means: “Does this text conform to JSON grammar?” Tools parse the string and either accept a value tree or report an error with position. Strict JSON rejects trailing commas, single-quoted strings, bare keys, comments, and undefined — habits that work in JavaScript object literals but fail in real JSON.

Core rules to remember

• Strings use double quotes only
• Keys in objects are strings
• No trailing comma after the last property or array element
• Numbers are base-10 literals (no leading zeros like 01 in strict parsers)
• Top level is usually an object or array (some parsers allow other values)

When validation fails, read the line/column or character offset. Fix the first error, re-validate, and repeat — later “errors” often vanish after the first real fix.

For payloads that embed binary as text, confirm the string content separately with a Base64 encoder decoder and the guide on how Base64 works. Validation of the outer JSON only proves the wrapper is well-formed.

These mistakes show up daily in handwritten fixtures and partially copied responses.

• Trailing commas — {"a":1,} is invalid JSON
• Single quotes — {'a':1} is not JSON
• Unquoted keys — {a:1} is a JS object, not JSON
• Comments — // and /* */ are not allowed in standard JSON
• Unescaped characters in strings — raw newlines or unescaped quotes break the string
• NaN / Infinity — not valid JSON number tokens
• Concatenated values — two root objects back-to-back without an array wrapper
• Smart quotes — Word or CMS editors replace " with curly quotes

Debug habit

If a huge file fails, isolate a smaller slice or use a tree view after a partial fix. Diff against a known-good sample from the same API version. Never “fix” production data by guessing types — check the API contract.

IDs inside JSON are often UUID strings; generate test fixtures with the UUID generator and the UUID guide when you need valid-looking keys without copying customer data.

A tree view turns nested objects and arrays into expandable nodes. You see depth, sibling counts, and which keys exist without mentally matching braces. Path navigation (JSONPath-style or simple dotted paths) jumps to data.items[2].price when support says “the third line item is wrong.”

When tree view wins

• Responses with three or more nesting levels
• Arrays of heterogeneous objects
• Config files where one mistyped key sits ten layers down
• Comparing two environments (staging vs prod shape)

Stats such as key count, max depth, and value counts give a quick smell test: an empty array where you expected hundreds of rows is visible before you write more client code.

Use the JSON tree view on large bodies instead of scrolling a single minified line. Collapse branches you do not care about and focus on the path named in the error ticket.

API debugging is a loop: capture → format → validate → interpret status and body → fix client or server → retest.

1. Copy the raw response or request body from DevTools, proxy, or logs.
2. Pretty-print so field names are readable.
3. Validate syntax; if invalid, fix truncation or proxy corruption first.
4. Check HTTP status separately — valid JSON can still be an error payload.
5. Compare required fields against the API docs or OpenAPI schema.
6. Reproduce with the smallest JSON body that still fails.

Security note

Access tokens, passwords, and PII often sit inside JSON. Prefer local or trusted tools; redact secrets before pasting into shared chats. Encoding is not protection — see password strength practices for secrets that must stay confidential, and never treat Base64 fields as encrypted.

When a field is Base64 or a compact token, decode only what you need with the Base64 tool, then return to the structured JSON for the rest of the payload.

Minify when bandwidth or storage matters and humans will not read the file on the wire: production API responses, embedded config in constrained devices, or compact logs (sometimes). Pretty-printed JSON is better for repositories that humans diff — many teams store checked-in fixtures formatted, then minify only at the edge if required.

• Minify — smaller bytes, harder to read, standard for many public APIs
• Pretty — clearer PRs and tutorials; slightly larger
• Canonicalization — separate topic (key sorting, number formatting) for signatures and hashing; simple minify is not full canonical JSON

Do not minify by hand with regex. Parse then serialize with a proper library or the online JSON minifier so Unicode escapes and nested structures stay valid.

Paste, format, validate, explore, and copy out. Everything runs in the browser so your payload stays on your machine for typical use.

1. Open the free JSON formatter and validator.
2. Paste or type your JSON into the input.
3. Run format/beautify to indent nested structures.
4. Check validation messages and jump to the reported error location.
5. Use tree view or path tools to inspect deep keys.
6. Minify when you need a compact string for an environment variable or test header.
7. Copy the cleaned result back into your client, ticket, or fixture file.

Pair with UUID generation for sample IDs and Base64 encode/decode when binary-ish fields appear inside otherwise normal JSON.