The problem with raw JSON
Here is what a typical API response looks like before formatting: {"user":{"id":4891,"name":"Sarah Chen","email":"[email protected]","preferences":{"theme":"dark","notifications":{"email":true,"push":false}}}} Can you quickly tell from that whether notifications.push is enabled? Can you find the user ID? It takes real effort, and that effort is entirely avoidable. Formatted with proper indentation, the same JSON becomes an instantly readable structure where every key, value, and nesting level is obvious at a glance.
When you actually need a formatter in practice
Debugging an API integration: your API call returns unexpected data. You console.log() the response and get a minified blob. Formatting it immediately reveals whether the expected fields are present, null, missing, or nested differently than you thought.
Reviewing data migrations: before running any migration, I format a sample of both source and target data and compare them. Formatting immediately surfaces type mismatches (string where an integer is expected) and incorrect nesting levels.
Validating configuration files: any JSON config (package.json, tsconfig.json, .eslintrc) will throw cryptic errors on syntax problems. Running it through a formatter that validates while formatting surfaces these errors with precise locations.
Reading API documentation: example responses in docs are often minified or inconsistently formatted. Running them through a formatter with collapsible sections lets you navigate to just the relevant fields.
What makes a JSON formatter good or bad
Instant validation with useful errors: "Unexpected token } at position 247" is useless. "Unexpected } on line 12, expected , or ]" is immediately actionable. A good formatter points you to the exact problem.
Syntax highlighting: colour-coding keys, strings, numbers, and booleans lets your eye go directly to the right type when scanning large structures.
Collapsible nodes: for large JSON objects, collapsing sections you are not working on keeps the view manageable. Without this, a 200-line object is still hard to navigate.
Privacy: you often format sensitive data — user records, API responses with tokens, database output. A formatter that uploads JSON to a server is a privacy concern. The right implementation runs entirely in the browser, in memory, without transmitting anything.
Minify mode: sometimes you need the reverse — collapsing formatted JSON for a config value, API request body, or database field. Good formatters handle both directions.
My formatter
Mine runs entirely client-side, validates in real time, highlights syntax, supports collapsible nodes, and includes a minify mode. Nothing leaves your browser. I built it because every alternative I tried was either too slow, plastered with ads, or required uploads I was not comfortable making.