What does the JSON Size Analyzer do?

It breaks down your JSON document by size, showing exactly which keys and values consume the most bytes. The interactive treemap visualization makes it easy to spot oversized fields, redundant data, or optimization opportunities.

How is the JSON size calculated?

Size is measured in bytes of the minified (whitespace-free) JSON representation. This reflects the actual payload size when transmitted over a network, which is what matters for API performance.

How can I reduce my JSON payload size?

After identifying the largest fields, consider: removing unused fields, shortening key names for API responses, moving large binary data (images) out of JSON into separate endpoints, paginating arrays, and using GZIP compression at the server level.

What's a typical JSON response size for good performance?

For web APIs, aim to keep responses under 100KB. Mobile-first APIs should target under 50KB. Responses over 1MB should be paginated or redesigned. Use GZIP compression, which typically reduces JSON size by 70-90%.

محلل حجم JSON

خريطة شجرية تفاعلية للحجم

JSON Input

Loading editor...

Size Breakdown

Size analysis will appear here...

Find out exactly which keys make your payload heavy

Slow APIs and large databases often boil down to one or two oversized fields buried in an otherwise lean payload. A size analyzer breaks the document down by byte contribution and visualizes it as a treemap, so you can see at a glance which keys deserve attention before deciding what to trim, paginate, or move out of JSON entirely.

Use the analyzer when you need to

Diagnose a slow API response

Identify the field consuming most of the payload before you optimize, paginate, or compress.

Audit a stored document

See which keys take up the most room in a NoSQL or document-database record.

Plan a payload-shrinking effort

Prioritize the highest-impact fields to remove or compress instead of micro-optimizing small ones.

How to analyze JSON size

1
Paste the JSON document into the editor.
2
Click Analyze to break the document down by key with byte counts.
3
Hover or click the treemap to drill into the biggest contributors.

Keep going

Minify the payload

Strip whitespace as a first cheap optimization before refactoring fields.

Visualize as a graph

Switch to graph view when relationships matter more than size.

Inspect specific fields

Drill into a heavy node in tree view to decide how to slim it down.

Format before analyzing

Pretty-print the source so the labels in the analyzer match what you expect.

Common size-analysis workflows

Optimize a hot API endpoint

Identify the biggest fields and either trim, paginate, or move them out of the response body.

Audit a document database row

See which embedded subdocuments are pushing rows over storage limits.

Validate a compression strategy

Compare the breakdown before and after a refactor to confirm the savings landed where expected.

أدوات ذات صلة

ضاغط JSON

ضغط JSON بإزالة المسافات

رسم JSON

تصور هيكل JSON كرسم تفاعلي

عارض JSON

استكشاف JSON بشجرة وجدول ونص خام

منسّق JSON

تجميل JSON مع مسافات بادئة قابلة للضبط

الأسئلة الشائعة

يقسّم المستند حسب الحجم ليعرض أي مفاتيح وقيم تستهلك أكثر البايتات مع خريطة شجرية تفاعلية.

بايتات تمثيل JSON المضغوط (بلا مسافات زائدة) — يعكس حجم الحمولة على الشبكة.

أزل الحقول غير المستخدمة، قصّر أسماء المفاتيح في API، انقل البيانات الثنائية الكبيرة خارج JSON، صفِّ المصفوفات، وفعّل GZIP على الخادم.

استهدف أقل من 100 كيلوبايت للويب؛ للجوال أقل من 50 كيلوبايت. فوق 1 ميجابايت فكّر في التصفح. GZIP يقلل JSON غالباً 70–90٪.