Loading editor…

No data leaves your browser.

Indentation standards and when to beautify

Most JavaScript and web API ecosystems default to 2-space indentation in pretty JSON. Python configs and some enterprise style guides prefer 4 spaces. Tabs still appear in older codebases — SparkJSON supports all three.

Beautify when you are reading logs, reviewing diffs, or teaching. Keep minified JSON for production transport when payload size matters, then beautify locally to inspect.

2 vs 4 spaces — pick the indent your team already uses in reviews.

Minified → pretty — expand API blobs without changing values.

Validate included — broken JSON is not silently “beautified.”

Beautify vs minify — picking the right form

Pretty for humans

Use beautified JSON in tickets, PRs, and debugging sessions so nesting is obvious.

{"a":{"b":1}} → multi-line indented object

Minified for machines

Ship compact JSON on the wire; beautify only when a person needs to read it.

API body, localStorage blob, CDN fixture

Don’t hand-indent invalid JSON

Whitespace cannot fix a missing quote. Validate first, then beautify.

Frequently asked questions

Does beautifying change my data?

No. Only insignificant whitespace between tokens changes. Strings, numbers, booleans, and null stay the same.

Should I commit beautified or minified JSON?

Prefer beautified fixtures in git for readable diffs. Minify in a build step if production size is the goal.

Is beautify the same as format?

Yes in practice. SparkJSON’s Format action pretty-prints with your chosen indent and validates at the same time.