JSON Structure Analyser
Measures a document — size, depth, node counts, type breakdown and the largest values it contains.
Loading the tool…
Processing happens locally in your browser.
What you paste or load is processed by this page and is not uploaded to a server. Nothing is stored unless you use a control that says it stores something, and you can clear anything this site has kept from the privacy page.
How to use this tool
- Paste or load the document you want to measure.
- Select Analyse.
- Read the size, maximum depth, node counts and largest values to find what is making the payload heavy.
What json analyser does
When a payload is unexpectedly slow or large, the first question is which part of it is responsible. A summary of the document — how deep it nests, how many nodes it holds, and which individual values are biggest — answers that faster than reading it.
Depth matters beyond size. Recursive parsers and schema validators have practical depth limits, and a document that nests forty levels deep will break something eventually even if it is small. The type breakdown is also a quick sanity check: a field you expected to be numeric showing up as a string across ten thousand nodes is a data quality problem worth catching early.
Frequently asked questions
Recursive parsers, schema validators and serialisers all have practical depth limits, and some databases impose one on JSON columns. A document nesting dozens of levels deep will eventually break something even when it is small.
Read the largest-values list. In most oversized payloads a small number of fields — an embedded image, a full stack trace, a duplicated lookup table — account for the majority of the bytes.
How many nodes are strings, numbers, booleans, nulls, objects and arrays. A field you expected to be numeric appearing as a string across thousands of nodes is a data quality problem worth catching before it reaches a warehouse.