Analyze JSON size without leaving the browser. JSON Size Analyzer measures JSON size, depth, key counts and the heaviest nested paths — useful when you need to find which keys and nested paths are making a payload heavy between two other steps of a debugging session. Everything runs inside your browser, so the file never touches a server, which matters when the payload contains tokens, customer records or anything else you would not paste into an unknown server.
How to
Four steps, no account, nothing to install.
Add the response you want to slim down.
See which paths dominate the byte count.
Trim or paginate the heaviest branches first.
Overview
JSON is the default interchange format of the modern web. It represents data as nested objects and arrays of strings, numbers, booleans and null, and every mainstream language ships a parser for it. Its grammar is deliberately tiny — no comments, no dates, no trailing commas — which makes it fast to parse but strict about syntax.
Paste the payload — Add the response you want to slim down. Read the breakdown — See which paths dominate the byte count. Act on the biggest wins — Trim or paginate the heaviest branches first. The whole loop is designed to be repeatable: change the input, read the new result, no re-submit step in between.
The failures people hit are predictable: No comments; No native date or binary type; Strict syntax breaks on trailing commas. Each of those shows up as a specific, fixable symptom rather than a vague error, which is exactly what this tool surfaces.
API request and response bodies, Configuration files, Log records (NDJSON) — these are the contexts where JSON shows up, and this page is the fast path between "I have a blob of input" and "I understand what it contains". Keep the tab open next to your editor and your terminal.
Features
Total and per-branch byte weight
Maximum nesting depth
Largest keys and arrays ranked
Minified vs formatted comparison
Reference
| Property | Value |
|---|---|
| Format | JSON (JavaScript Object Notation) |
| Extension | .json |
| MIME type | application/json |
| Human readable | Yes |
| Typical use | API request and response bodies |
Examples
Copy the raw payload out of the network tab, drop it in here, and read the result immediately — no curl round trip, no scratch file.
Paste the snippet from the diff to confirm what it evaluates to before approving the change.
Because processing is local, real payloads with real identifiers can be inspected without violating a data-handling policy.
Benefits
FAQ
1. Paste the payload: Add the response you want to slim down. 2. Read the breakdown: See which paths dominate the byte count. 3. Act on the biggest wins: Trim or paginate the heaviest branches first.
No. Everything runs inside your browser, so the file never touches a server — safe for tokens, staging payloads and customer data.
Yes, with no account, no rate limit and no paid tier.
A lightweight, text-based format for structured data built from objects, arrays and primitives. It represents data as nested objects and arrays of strings, numbers, booleans and null, and every mainstream language ships a parser for it
No comments; No native date or binary type; Strict syntax breaks on trailing commas; Verbose for large flat tables.
Once the page has loaded, yes — the processing needs no network access.
Tools
Explore
Learn