JSON Size Analyzer

What the JSON size metrics mean

Original size is the UTF-8 byte count of the exact text pasted into the editor. Minified size parses the document and serializes it without formatting whitespace. Pretty-printed size serializes it with two-space indentation. Formatting overhead shows how many original bytes can be removed by minification and the percentage of the original input they represent.

Bytes are more useful than JavaScript character counts for HTTP payload work. ASCII characters usually occupy one UTF-8 byte, while many accented characters and emoji occupy more. That means two strings with the same visible character length can have different transfer and storage sizes.

Structure and nesting counts

The analyzer counts JSON objects, arrays, object properties, array items, primitive values, and maximum container depth. Primitive values include strings, numbers, booleans, and null. Maximum depth counts object and array containers: a root object has depth one, and an object nested inside its array has depth three.

Structural counts help explain why a payload is costly even when individual values are short. Repeated property names can dominate large arrays of similar objects. Deep nesting can make validation, mapping, rendering, and debugging more difficult. These metrics do not assign a quality score; they expose the shape so you can decide whether every field and layer is needed.

Minification versus compression

Minification removes spaces, indentation, and line breaks that are not part of string values. It does not shorten property names or change data. HTTP compression such as gzip or Brotli is a separate transport step that can reduce repeated keys and values much further. A minified byte count is therefore not a prediction of the final compressed response size.

For browser APIs, enable server compression and inspect the transferred size in developer tools. Keep readable formatting in source fixtures and logs where it helps people, then let the response pipeline minify or compress data where appropriate. Do not sacrifice clear field names solely to reduce a few uncompressed bytes without measurement.

Common uses

• Compare an API response before and after removing unused fields.
• Measure fixture and configuration files before embedding them in a bundle.
• Spot large formatting overhead in exported or generated JSON.
• Document object, array, and nesting complexity during an API review.
• Estimate whether a payload is approaching a platform or gateway limit.

Security and privacy

The JSON is parsed and measured entirely in the current tab. Cryonel does not upload the document or report. Very large files still consume memory in your browser because both parsed and serialized forms exist during analysis, so use a representative sample when a multi-megabyte document makes the tab slow.