JSON Minifier

Formatted JSON is typically 15–30% whitespace, and deeply nested documents are worse. The exact number for your document is shown after every conversion.

Over HTTP most of that saving disappears: gzip and brotli compress repeated indentation almost to nothing, so a minified payload is often only a few per cent smaller on the wire. Where minifying genuinely matters is anywhere the raw bytes are counted — a 2,048-character URL limit, a fixed-width column, a device with a small message budget.

Whitespace inside string values is untouched — only whitespace between tokens is removed. Key order is preserved unless you ask for sorting. Numbers are re-serialised, so 1.50 becomes 1.5 and 1e3 becomes 1000: the values are identical but the text is not, which matters if you are comparing checksums.

Stripping whitespace typically takes 10 to 20 percent off a formatted JSON file. Gzip, which every web server and every HTTP client already speaks, takes 80 to 90 percent off the same file — and it is very good at repeated whitespace specifically, so minifying first adds only a few percent to what gzip alone achieves. If the goal is a smaller response over the network, transfer compression is the whole answer and this tool is a rounding error. Where minifying does earn its place is a payload with no compression in front of it: a query string, an embedded data attribute, a size-capped log line.