JSON Data Counter - Json Count

This is the headline number — how many items sit at the very first layer of your JSON. If your JSON is a list of users, this tells you how many users there are in total. If it is a single object, it tells you how many top-level keys it has. Think of it as the answer to "how much data do I have?"

An array is a list of items written inside square brackets [ ]. The array count tells you how many of these lists exist across your entire JSON — including ones buried deep inside other objects. This is useful when your data has multiple lists at different levels, such as a list of orders where each order also contains a list of items.

An object is a single record written inside curly braces { } that holds a set of named fields. The object count tells you how many of these records exist anywhere in your JSON. Each user profile, each order, each product — if it sits inside curly braces, it counts as one object. This is the best way to understand how many individual "things" your data describes.

A key is the label or name for a piece of data — like "name", "email", or "price". The key count adds up every single named field across all objects in your JSON. If you have 100 users each with 5 fields, your key count is 500. This helps you understand the total volume of information stored, not just the number of records.

A string is any piece of text enclosed in quotation marks — like a name, email address, city, or status label. The string count tells you how many text values appear anywhere across your JSON. Useful for understanding how much of your data is descriptive text versus numbers or flags.

A number value is any integer or decimal not wrapped in quotes — like an ID, price, age, or score. The number count totals all numeric values found across your entire JSON. This quickly shows how much of your data is quantitative, which matters when planning how to process or display it.

Nested JSON means data that lives inside other data — like a user object that contains an address object, which itself contains a city and postcode. The nested count shows how many items exist at each depth level (Level 0, Level 1, Level 2, and so on). This is the most powerful feature of the tool — it lets you see the full shape of your data, not just the surface.

Max depth is a single number that tells you how many layers deep your JSON goes at its deepest point. A flat list of users might have a depth of 1. A complex API response with nested orders, items, and metadata might reach depth 4 or 5. A higher depth means your data is more complex and requires more careful handling when reading or processing it.

Instead of manually copying JSON from an API, you can paste the API's web address (URL) directly into the tool and click Fetch. The tool retrieves the live response and runs the full count analysis on it instantly. This is ideal for developers checking how many records an endpoint returns, or for verifying that an API is sending the correct amount of data.