Compressing JSON API Responses with Gzip

JSON API Compression

JSON is the dominant data format for web APIs. Its text-based, structured nature makes it highly amenable to gzip compression, with typical reductions of 75–90%.

Why JSON Compresses Exceptionally Well

JSON has extreme redundancy:

• Key repetition: In arrays of objects, every key name repeats for every item
• Structural characters: {, }, [, ], :, ,, " are very frequent
• Value patterns: Booleans (true, false), null, repeated string values

Compression Impact by Response Size

Response Size	Gzip Compressed	Ratio
1 KB	400–500 B	50–60%
10 KB	2–3 KB	70–80%
100 KB	12–20 KB	80–88%
1 MB	80–150 KB	85–92%

Larger JSON responses compress disproportionately better because gzip’s sliding window (32 KB) can find more pattern matches.

Minification Before Compression

Removing whitespace from JSON (pretty-printed → minified) reduces raw size by 20–40% and also slightly improves gzip ratios:

Pretty JSON:   100 KB → 20 KB gzipped (80%)
Minified JSON:  65 KB → 17 KB gzipped (74%)

While the gzip percentage is lower for minified input, the absolute compressed size is still smaller.

Best Practices for API Compression

1. Always enable gzip for JSON responses (Content-Type: application/json)
2. Set a minimum size threshold (e.g., skip compression for responses under 1 KB)
3. Use level 1–4 for dynamic API responses to minimize latency
4. Consider field selection: Let clients request only needed fields to reduce payload before compression