THE PRACTICAL GUIDE · NORMANDIN SYSTEMS
Get more from Json Size Analyzer
Json Size Analyzer helps you inspect relative node sizes in JSON. A size view helps identify which parts of a document contribute most to its serialized weight. This is useful when the information is already available but its structure, presentation, or consistency makes it difficult to inspect. Work with a representative sample first so that you can recognize the expected result before applying the same operation to a larger document. Character counts, UTF-8 byte counts, and compressed transfer sizes are different measures. Treat the displayed metric according to the tool’s definition. Keep the original input available while reviewing the output. The important check is whether the result still has the intended values and relationships, rather than whether it merely looks neater. Look for repeated arrays, embedded blobs, and long text fields before optimizing a payload.
Guide updated October 13, 2026
How to use this tool
- Place the JSON input in the relevant editor. If the tool compares or combines documents, keep each document in its own input.
- Select the available settings for the operation you need. Look for repeated arrays, embedded blobs, and long text fields before optimizing a payload.
- Review any syntax errors before interpreting the result. A valid document with the wrong structure needs a different fix from malformed input.
- Inspect the changed portion and at least one unchanged portion. Keep a copy of the original JSON until the result has been checked in its destination.
SEE IT IN PRACTICE
A worked example
{"small":"x","large":"xxxxxxxxxx"}The large string contributes more value content than small.
Ten characters take more string content than one in this ASCII example, although property names and punctuation also contribute to serialized size.
Measure the representation you deliver
A large repeated object may dominate uncompressed JSON while compressing efficiently, whereas a shorter encoded binary field may compress poorly. Property names and structural punctuation also contribute to serialized size. Use the node view to choose what to investigate, then measure the actual encoded and compressed response if bandwidth or storage is the final concern.
Large strings versus repeated records
A payload can grow because a field contains a long string, because an array contains many records, or because each record repeats many property names. Those cases suggest different changes. Inspect the node weights to identify the source, then consider whether the application needs every field or record. Measure the real delivered payload after any change; deleting a visually large section is not the same as proving a particular bandwidth saving.
When this tool is useful
- Locate bulky API response fields while keeping the underlying structure visible.
- Compare payload structure examples with a compact, reproducible sample.
- Prioritize a data-size investigation before copying data into another application.
Tips for a better result
- Character counts, UTF-8 byte counts, and compressed transfer sizes are different measures. Treat the displayed metric according to the tool’s definition.
- Look for repeated arrays, embedded blobs, and long text fields before optimizing a payload.
- Use a small JSON example to isolate an unexpected result. Add nested objects, arrays, quoted text, and empty values only as needed to reproduce the behavior.
Frequently asked questions
Does this establish that my JSON is correct?
It checks or transforms the aspects covered by this operation. It cannot establish whether the values match your business rules, whether required records are missing, or whether the receiving application accepts the same structure.
Why do visually similar inputs behave differently?
Value types, nesting, array order, duplicate names, and invisible whitespace inside strings can carry meaning. Compare the parsed structure and exact values, rather than judging only the way the document appears on screen.
What is a useful review process?
First resolve syntax errors, then inspect the specific result this tool produces. Look for repeated arrays, embedded blobs, and long text fields before optimizing a payload. Finally, test a representative result with the application that will consume it.
What happens to the information I enter?
The utility processes your input in this browser. Some tools retain field values in browser storage or the URL; avoid entering secrets in shareable fields. Page and asset requests still go to the hosting provider. Read the privacy and offline-use notes for details.