How to Format JSON Online (and Why Indentation Matters)

Minified JSON is great for machines and terrible for humans. To format JSON online, paste it into the JSON Formatter and click Format: it pretty-prints the structure with proper indentation instantly, entirely in your browser. Nothing is uploaded to a server, so it's safe to paste API keys, tokens, or internal payloads while you debug.

What "formatting" actually does

A JSON formatter (also called a pretty-printer) doesn't change your data; it re-serializes the same structure with consistent indentation and line breaks. {"id":1,"name":"Ada"} and a fully indented, multi-line version are the exact same object as far as any program is concerned. The only thing that changes is how easy it is for a human to read.

Why indentation matters more than it seems

Minified JSON is the default output of most APIs, because whitespace costs bytes over the wire. But that same compactness makes it nearly impossible to spot a missing comma, a misplaced bracket, or which value belongs to which key once a payload gets past a few dozen characters. Formatting restores the visual nesting your eyes rely on to parse structure: the same reason source code isn't written as one long line.

Indentation also makes diffs meaningful. Comparing two minified blobs shows you one giant changed line; comparing two formatted versions shows you exactly which field changed, which is why formatting a payload before diffing it (see our Text Diff Checker) is worth the extra step.

Step-by-step: formatting JSON with Code Tools Studio

1. Paste or type your JSON into the input pane.
2. Click Format to pretty-print it, or Minify to collapse it back down.
3. Use Sort Keys if you want a deterministic key order, handy before diffing two versions.
4. Use Remove Nulls to strip out null fields you don't need to look at.
5. Switch to the Tree tab to explore deeply nested structures by collapsing branches, or the Diff tab to compare two payloads side by side.
6. Export the result as JSON or a TypeScript interface from the Export menu, or copy/download it directly.

Common JSON formatting problems

If formatting fails, the input usually isn't valid JSON in the first place. The most frequent causes:

• Trailing commas: {"a": 1,} is valid in JavaScript object literals but not in JSON.
• Single quotes: JSON requires double quotes around strings and keys; {'a': 1} will fail to parse.
• Unquoted keys: {a: 1} is JavaScript shorthand, not valid JSON.
• Trailing or stray control characters: an unescaped newline inside a string value will break parsing.

The formatter reports the exact line and column of the first syntax error, so you can jump straight to the problem instead of scanning the whole payload by eye.

When to minify instead of format

Formatting is for reading; minifying is for shipping. If you're pasting JSON into a request body, a config file that's parsed by a machine, or anywhere byte size matters, minify it back down before you save or send it: the toolbar has both actions one click apart.

If you're working with a sample payload and want a schema out of it rather than just readable formatting, the JSON Schema Generator can infer one directly from your formatted example.