Formatting isn't just about looks — dev workflows need readable diffs, while production needs smaller payloads. Match indent, line breaks, and minification to the scenario.
Development: readability first
- Use 2-space indent (common in frontend) or 4-space (some backend styles) — stay consistent as a team
- Keep array/object line breaks consistent; avoid mixing single-line and multi-line styles
- Split very large files by module instead of one giant JSON blob
Production: size first
HTTP responses and message payloads should use minified JSON: strip whitespace and newlines; combine with gzip/brotli when possible. Minification changes presentation only, not data semantics.
Validate before formatting
Syntax errors (trailing commas, single quotes, comments) block formatting. Recommended flow: paste → validate → format → copy. This toolbox supports standard JSON only, not JSON5.