"Minify your JSON" is common API advice. It's also incomplete advice. Minification helps, but if you don't already have gzip or brotli compression on, you're solving the wrong problem first. Here's the measured truth, and when minifying matters.
What minification actually does
JSON minification strips whitespace — spaces, tabs, newlines between tokens. {"name": "Alice"} already takes the same bytes minified as not. But pretty-printed JSON:
{
"name": "Alice",
"age": 30,
"address": {
"city": "Seattle"
}
}...becomes {"name":"Alice","age":30,"address":{"city":"Seattle"}}. The savings are dramatic on indented JSON — often 20-40% of the bytes are whitespace.
Use our JSON minifier for one-off compression, or call JSON.stringify(data) with no third argument (no indentation) in JavaScript.
The measurements that matter
Take a typical API response: a 50 KB array of user records with nested address objects. Here's what compression actually saves:
| Treatment | Size | Saved vs original |
|---|---|---|
| Pretty-printed (2-space indent) | 50.0 KB | — |
| Minified | 32.1 KB | 36% |
| Pretty + gzip | 6.2 KB | 88% |
| Minified + gzip | 6.0 KB | 88% |
| Pretty + brotli | 5.1 KB | 90% |
| Minified + brotli | 5.0 KB | 90% |
Two things jump out. First, minification alone cuts ~36% — meaningful for a CDN or a phone on cellular. Second, gzip and brotli largely erase the benefit of minification: the compressor handles repeated whitespace efficiently. The difference between minified and pretty-printed after gzip is roughly 3-4%.
So when does minification actually matter?
When you don't control compression. If your CDN is misconfigured and serving JSON uncompressed (check the Content-Encoding response header), minification is your fallback. It cuts bytes on the wire by a third with one line of code.
For storage. Stored JSON usually isn't gzipped. Minifying records before they hit a database column or a S3 object adds up at scale.
For LocalStorage and IndexedDB. Browser storage is measured pre-compression. Minified JSON lets you fit more.
For inline JSON in HTML. JSON-LD in a page, server-side initial state hydration — gzip applies to the HTML response, but minified JSON still shrinks the source the browser has to parse.
When minification is the wrong fix
If your responses are slow over the network. Enable gzip or brotli first. A single nginx or Cloudfront config change cuts response sizes by 80-90%; minification on top of that adds maybe 1-2 KB. Get compression first, then revisit.
If parsing is slow. Minified JSON parses at the same speed as pretty-printed JSON — the parser strips whitespace either way. If JSON.parse is your bottleneck, the answer is structural: smaller responses, streaming parsing, or a binary format like MessagePack.
If your debug experience matters. Pretty-printed JSON in dev/staging environments is hugely easier to read in browser DevTools. Minify in production only, when whitespace genuinely costs you.
Beyond minification
If you've enabled compression and minified JSON and still need to cut bytes, the next steps cost more engineering but save more bytes:
Shorter keys. If your data is keyed {"customerAddressStreetLine1": "..."} times ten thousand rows, the keys dominate. Renaming to {"a1": "..."} with a documented schema can halve the payload. You're trading readability for size.
Pagination. Don't return ten thousand records. Return a hundred and a cursor.
Sparse responses. Omit null/default fields. {"name": "Alice"} is shorter than {"name": "Alice", "age": null, "email": null, "phone": null}. Document the omission convention.
Binary formats. When JSON is 100 MB, switch to MessagePack, CBOR, or Protobuf. They preserve JSON semantics with binary encoding — typically 30-50% smaller even before compression, and faster to parse.
Wrap-up
Minification is a quick win — one line of code, no breaking changes, a third of the bytes gone. But it's a quick win, not a fundamental fix. Turn on compression first, then minify, then if you still need more, think about pagination and structure. Most APIs that "need optimization" actually just need gzip on; gzip_types application/json; in their config.