JSON Minifier

Minifying JSON is a narrower operation than minifying JavaScript or CSS. There are no comments to strip, no identifiers to shorten, and no dead code to remove. The only thing that can be removed is insignificant whitespace, meaning the indentation and line breaks between tokens. Everything else in the document is load-bearing.

Whitespace inside strings isn't whitespace

A correct minifier only touches the gaps between structural tokens. Spaces inside string values are part of the data and must be preserved exactly, as must escape sequences and the order of keys. If a minified file comes back with different string contents, the tool has a bug, because there's no legitimate optimization that would alter them.

The savings are real, until compression enters

Pretty-printed JSON with two-space indentation is commonly somewhere between fifteen and thirty percent whitespace, so the raw reduction looks impressive. The important caveat is what happens next. Indentation is extremely repetitive, and gzip and brotli are very good at repetitive input, so most of that apparent saving is something compression would have removed anyway. Over an HTTP response with compression enabled, the difference between minified and pretty JSON is often only a few percent, not the headline figure.

That doesn't make minifying pointless, it just relocates the benefit. It matters most where compression is absent or where the uncompressed size is what counts: values written to local storage, payloads measured against a message size cap on a queue or a serverless event, JSON embedded directly in an HTML document, database columns holding documents, and log lines where one record must fit a line limit.

Minification isn't compression or obfuscation

A minified document is still fully readable JSON. Anyone can format it back with one command, and nothing about it is hidden or protected. If the goal is a genuinely smaller payload, compression will beat minification by a wide margin, and if the goal is confidentiality, neither is relevant and the answer is encryption or not sending the data at all.

One habit worth adopting: keep the formatted version in source control and minify as a build step. Diffs on minified JSON collapse the entire document onto one line, which makes reviewing a one-character change effectively impossible.