Waiting for JSON content
Start typing on the left or load one of the sample payloads to inspect it instantly.
Instantly clean, validate, and inspect web payloads
Start typing on the left or load one of the sample payloads to inspect it instantly.
Instantly beautify JSON and transform minified payloads into clean, readable, indented output. Customize 2-space or 4-space formatting with zero data upload.
Every tool runs in your browser, so the JSON you paste never leaves your device.
Formatting, minifying, repairing, and the tree view all run on your device, so there are no uploads to wait on.
Syntax errors like unescaped quotes and trailing commas are flagged with their exact line and column.
Turning single-line API responses and escaped JSON strings back into clean, indented, readable structure.
APIs and log systems almost always send JSON as a single compact line to save bandwidth. That is efficient for machines but hard on people: a 2 KB response becomes an unbroken wall of text where you cannot tell where one object ends and the next begins. A JSON beautifier reverses that — it parses the compact string and re-prints it with line breaks and indentation so every key sits on its own line and the nesting is obvious at a glance. Paste a minified response from your browser network tab, a curl command, or a log line, and PrettyJSON beautifies it instantly in your browser.
// Minified (one line)
{"user":{"id":42,"name":"Alice","roles":["admin","dev"]}}
// Beautified (2-space indent)
{
"user": {
"id": 42,
"name": "Alice",
"roles": [
"admin",
"dev"
]
}
}A common headache is JSON that has been stored or logged as a string, so every double quote shows up with a backslash in front of it and the whole thing sits on one line. This happens when a JSON value is embedded inside another JSON field, saved to a database column, or written to a log file. Pasted in that state it is hard to read and often will not parse directly. The fix is to unescape it first — turn the escaped quotes back into real quotes — and then beautify the result so the structure is readable again. If you are pasting something full of backslash-quote sequences, that is the tell-tale sign you are looking at escaped JSON.
These terms overlap, so here is the practical difference. Beautifying and formatting do the same job — both add indentation and line breaks to make JSON readable — and people use the words interchangeably. Minifying is the opposite: it strips whitespace to make the payload as small as possible for sending over the network. A typical workflow uses both: minify JSON when you ship it, and beautify it when you need to read or debug it. PrettyJSON keeps a separate tool for each, so you can jump straight to the one you need.
Common questions and expert answers regarding this tool.
A JSON beautifier takes compact or minified JSON and adds line breaks and indentation so it is easy to read. It is the same operation as formatting. PrettyJSON beautifies in your browser, so nothing you paste is uploaded.
In practice, none — both add indentation and line breaks to make JSON readable, and the words are used interchangeably. We keep separate Formatter and Beautifier pages because people search for both, but the underlying tool is the same.
Yes. Paste a minified API response or curl output and it beautifies right away. If the JSON is escaped (a backslash before every quote, usually from a log or a database field), unescape it first, then beautify the result.