JSON Size Analyzer

An API response that grew from 40 KB to 300 KB rarely grew evenly: one specific field usually dragged the rest along. Paste the JSON here and you get the weight of every node in bytes, its share of the total and the full path, in the style $.data.items[0].summary. The list is sorted from heaviest to lightest, so the culprit tends to show up in the first row.

Sizes are measured on the minified form, in UTF-8 bytes, not on the text you pasted. Indentation therefore never inflates a field, and the summary still tells you how much of the payload is pure whitespace. Keep in mind that an accented letter costs two bytes and an emoji costs four, so a short label in Portuguese can outweigh an English one of the same apparent length.

The detail that usually saves the most sits in the repeated-keys block. With the key cost turned on, each node also pays for its own name, the colon and the comma separating it from the next sibling. A name such as createdAt repeated 340 times already costs around 4 KB before any value is counted, and shortening it often beats trimming the values themselves.