Definition:
JSON Bandwidth Inflation is the phenomenon where JSON, being a textual format, tends to be verbose, which results in increased network bandwidth usage and higher latencies. In simple terms — JSON wastes space by sending more bytes than the actual data needs, because of its human-readable, text-based nature.
JSON is designed to be readable by humans, not optimized for machines — and that readability comes at a bandwidth cost.
Simple Analogy 📦 Imagine shipping a small gift. Instead of a tight box, you use a giant cardboard box filled with bubble wrap just to label what’s inside. The gift is small, but the package is huge. JSON is the oversized box.
Why Does It Happen? JSON is a textual format, which tends to be verbose. Every response must carry:
| Overhead Type | Example |
|---|---|
| Repeated key names | “username” repeated in every object |
| No type compression | Numbers stored as plain text: “age”: 25 |
| Whitespace & formatting | Spaces, newlines, indentation |
| Redundant structure | Brackets, quotes, colons everywhere |
Example:
Imagine an API returning a list of 3 users
Option 1 — Minified JSON (remove whitespace)
[{"id":1,"username":"alice","email":"alice@email.com","age":28,"is_active":true},{"id":2,"username":"bob","email":"bob@email.com","age":34,"is_active":false}]
Option 2 — Restructured (separate keys from values)
{
"fields": ["id", "username", "email", "age", "is_active"],
"rows": [
[1, "alice", "alice@email.com", 28, true],
[2, "bob", "bob@email.com", 34, false],
[3, "carol", "carol@email.com", 22, true]
]
}
✅ Keys are declared once, not repeated per row — massive savings at scale!
Option 3 — Switch to Binary Format (Protobuf / MessagePack)
# Binary encoding — not human readable but 20–60% smaller
\x01\x05alice\x11alice@email.com\x1c\x01 ...