How to Format JSON: Pretty-Print and Beautify Cleanly

What formatting does

Formatting adds structured whitespace — newlines and indentation — so nesting becomes visible. A formatter parses the JSON, confirms it is valid, and re-serializes it with consistent indentation. The data is unchanged; only its presentation improves. This is the inverse of minification, which strips that whitespace away.

{"name":"Ada","tags":["x","y"],"meta":{"active":true}}

{
  "name": "Ada",
  "tags": ["x", "y"],
  "meta": { "active": true }
}

Choosing an indentation style

• Two spaces — the most common default, compact and readable; used by most JavaScript and web tooling.
• Four spaces — more visual separation for deeply nested data, common in Python-adjacent codebases.
• Tabs — let each developer control display width and can be friendlier for accessibility.
• Pick one and apply it consistently across a project so diffs stay clean.

Sorting keys

Many formatters can alphabetically sort object keys. Sorting makes two documents directly comparable and produces stable, minimal diffs when files are regenerated — valuable for lockfiles, snapshots, and config you check into version control. The trade-off is that sorting discards the original author's intended ordering, so reserve it for machine-generated files rather than hand-curated ones where order carries meaning.

Format versus minify

Formatting and minifying are two directions of the same lossless transform. Format when you need to read, debug, review, or edit JSON. Minify when you need to ship or store it compactly. A healthy workflow keeps source files formatted and minifies only as a build or transmission step.

Formatting in code

In JavaScript, JSON.stringify(obj, null, 2) pretty-prints with two-space indentation. In Python, json.dumps(obj, indent=2) does the same, and adding sort_keys=True orders the keys. On the command line, jq . formats and colorizes JSON, and python -m json.tool is a quick built-in formatter. All of them parse first, so they reject invalid JSON instead of mangling it.

JSON.stringify(obj, null, 2); // 2-space indentation

json.dumps(obj, indent=2, sort_keys=True)

Formatting in the browser

For a quick one-off, an online formatter is faster than writing code — paste the JSON, choose your indentation, and copy the result. A client-side JSON Formatter does this entirely in your browser, so sensitive payloads never leave your machine, and it reports the exact location of any syntax error. For sustained editing rather than a single pass, a JSON Editor gives you syntax highlighting, inline validation, and format-on-demand in one place.

Why consistent formatting matters

Consistent formatting is not just cosmetic. When everyone uses the same indentation and, where appropriate, sorted keys, version-control diffs show only real changes instead of whitespace noise, code reviews get faster, and merge conflicts shrink. Standardizing formatting across a team removes a whole category of pointless churn.