JSON is everywhere — API responses, config files, log lines — and most of the time you meet it as a single unreadable wall of text. Formatting it well is the difference between spotting a bug in seconds and squinting for ten minutes.
This guide covers how to format, validate and minify JSON, and how to read the error messages when it won’t parse.
TL;DR — Paste JSON into the JSON formatter, hit Format for readable output, and read the inline error if it’s invalid. Everything runs in your browser — nothing is uploaded.
Beautify vs. minify: when to use each
Beautifying (pretty-printing) adds consistent indentation and line breaks. Use it whenever a human needs to read the JSON — debugging an API response, reviewing a config file, or committing data to a repo where diffs should be reviewable.
Minifying strips every non-essential space and newline to produce the smallest valid JSON. Use it for transport and production: API payloads, embedded config, anything where bytes on the wire matter.
The same data round-trips losslessly between the two — formatting never changes the values, only the whitespace.
How to read a JSON parse error
When JSON is invalid, the parser stops at the first problem and reports it. The usual culprits:
- Trailing comma —
{ "a": 1, }. Valid in JavaScript, illegal in JSON. - Single quotes —
{ 'a': 1 }. JSON requires double quotes on both keys and string values. - Unquoted keys —
{ a: 1 }. Every key must be a quoted string. - Missing comma between items, or a stray comma at the start.
A good formatter shows the exact reason and the position, so you can jump straight to the offending character instead of eyeballing the whole document.
Pick the right indentation
Two spaces is the most common convention and keeps nested structures compact. Four spaces reads well for shallow documents. Tabs are fine if your team standardises on them. The key is consistency — pick one and let the formatter enforce it.
Inspecting large JSON
For big documents, a flat formatted view is still hard to navigate. Switch to a tree view to collapse objects and arrays and drill into just the branch you care about. It’s the fastest way to understand the shape of an unfamiliar API response.
Do it privately
Many online JSON tools upload whatever you paste to their server. For anything containing tokens, customer data or internal structures, that’s a real risk. The JSON formatter here runs entirely in your browser — your JSON never leaves your device.