Minified vs pretty JSON

The data is the same

Minified JSON removes unnecessary spaces and line breaks. Pretty-printed JSON adds consistent indentation and new lines. A conforming parser produces the same values from either representation because whitespace outside strings does not carry data.

// Minified
{"status":"ok","items":[1,2,3]}

// Pretty printed
{
  "status": "ok",
  "items": [
    1,
    2,
    3
  ]
}

Use pretty JSON when people need to read it

Formatted output is useful during debugging, code review, documentation, configuration editing, and API inspection. Indentation makes nested objects visible and reduces the chance of reviewing the wrong level. Two spaces per level is common, although the exact indentation width is a style choice.

Use minified JSON when bytes matter

Compact output is appropriate for network responses, embedded data, caches, and storage where humans do not edit the file directly. Removing whitespace can reduce size, especially in large, deeply nested documents. HTTP compression may reduce the practical network difference, so minification is only one part of performance work.

Minification is not encryption

Compact JSON remains plain text. Anyone who can access it can format it again in a fraction of a second. Do not use minification to hide API keys, personal data, internal URLs, or business logic.

Always parse before transforming

A safe formatter or minifier first validates the input, then serializes the parsed value. Removing spaces with a text replacement can corrupt whitespace inside string values. For example, the spaces in "LXB Hub" are real data and must remain.

The JSON formatter supports both operations locally. Use Format for readable indentation and Minify for compact output. If parsing fails, work through the common JSON errors before transforming the data.

A practical default

Keep readable JSON in source control and human-maintained examples. Generate compact JSON at a build, transport, or storage boundary when there is a measurable reason. This preserves clarity during development without requiring users to download unnecessary whitespace.