Formatters

Formatting tools move code between two states: expanded, with the indentation and line breaks that make structure visible to a person, and minified, with all of that stripped out to reduce bytes. Both matter, at different points in the same workflow.

Beautify while you work, minify to ship

Reach for the JSON Formatter when an API response arrives as one unreadable line, or when you need to find the syntax error in a payload — it validates as it formats, and reports where the problem is. The SQL Formatter does the same job for queries, putting each clause and join on its own line, which is usually how you spot a missing join condition. The HTML Beautifier re-indents markup so mismatched nesting becomes obvious.

Going the other way, the JSON Minifier and CSS Minifier strip whitespace and comments for production.

How much minification actually saves

Less than the raw byte difference suggests. Minifying typically removes 10 to 30 percent of a JSON document and 20 to 35 percent of a stylesheet, but gzip and Brotli already collapse repeated whitespace very efficiently, so the saving measured over a compressed HTTP response is much smaller. Minification still reduces the bytes a browser must parse, which is the more durable argument for it.

Two practical rules. Keep the readable version as your source of truth in version control and minify as a build step, because minification is effectively one-way — comments are gone and formatting cannot be meaningfully recovered. And ship a source map alongside minified assets, or your browser's dev tools will report every rule as living on line 1.