Find What's Making Your API Payloads Too Big
Paste a JSON response, upload a HAR file, or analyze a request. See where the bytes are going, what you can optimize, and how much bandwidth you could save.
Formatting notice: Pretty-printed indentation adds +904 B vs minified (2.13 KB).
Evaluates whitespace, redundant nulls, verbose keys, float precision, and array shapes.
Based on detected payload patterns such as excess whitespace, default/null fields, verbose keys, and unconstrained float precision.
Where Are Your Bytes Going?
Top JSON fields and nested paths consuming the most bandwidth
What Can I Fix?
Prioritized optimization actions: safe reductions vs contract revisions
Safe Optimizations
Zero contract risk — preserve exact client compatibility
Minify JSON
−904 B · 29.3%Strip indentation and newlines. Same data — this is always applied when you copy.
Review With Frontend / Backend Team
Remove redundant nulls, defaults, and precision if clients accept omission
Keep PII off the list payload
−440 B · 14.3%Looks like personal data: email_address, last_login_ip. Prefer a detail endpoint instead of repeating them on every row.
Remove null fields
−312 B · 10.1%16 null values can be omitted entirely.
Use Unix timestamps instead of ISO 8601
−166 B · 5.4%16 ISO date strings shrink by roughly 40%.
Omit false / 0 / empty-string defaults
−144 B · 4.7%8 default values can be left off if missing means the same thing.
API Contract Changes
Alters payload schema, key names, or serialization format (requires client updates)
Convert repeated objects to columnar JSON
−714 B · 23.2%results has 8 uniform items. Converting to {columns, rows} eliminates key repetition.
Don't repeat the same nested object on every row
−528 B · 17.1%preferences ×8 is identical on each item. Lift it to a default or omit it on the list.
This list is already paged — slim each row
−308 B · 10.0%Showing 8 of 128. Don't add more per-row fields; use a detail route for the rest.
Shorten repeated key names
−272 B · 8.8%email_address → email, last_login_ip → ip, preferences → prefer. Rename in the serializer — not applied automatically.
Shorten repeated keys
−247 B · 8.0%The same object shape repeats many times; key names dominate the payload. Rename in code — not applied automatically.
Approved rewrite: 0 B vs 3.01 KB original (Minify only · 0/6 contract changes ticked).
What Does This Payload Cost at Scale?
Simulate real-world traffic volume to project monthly egress bandwidth demands
Monthly Transfer Formula
Architecture Scenarios
Estimated Monthly Infrastructure Transfer Cost
Estimates for 86.11 GB monthly egress across major cloud providers
⚠️ Infrastructure Cost Disclaimer: Estimates are based on published public bandwidth transfer prices. Actual billing depends on multi-region routing, ingress/egress direction, CDN caching hit ratios, volume discounts, and commitment tiers.
Estimates, not invoices. List prices verified 2026-08-23 for US & Europe. Excludes compute, storage, seats, and enterprise discounts. CDN, serverless, and origin hosts are grouped separately as their architectures and pricing structures differ.
- Cloudflare CDN · 2026-08-23
- AWS CloudFront · 2026-08-23
- Fastly · 2026-08-23
- GCP Cloud CDN · 2026-08-23
- Azure CDN · 2026-08-23
- Vercel · 2026-08-23
- Netlify · 2026-08-23
- Azure Static Web Apps · 2026-08-23
- Supabase · 2026-08-23
- Railway · 2026-08-23
- Render · 2026-08-23
- AWS EC2 / Backend · 2026-08-23
- Azure VMs / Backend · 2026-08-23
- GCP Compute / Cloud Run · 2026-08-23
- DigitalOcean · 2026-08-23
- Hetzner Cloud · 2026-08-23
- Fly.io · 2026-08-23
Compression & Serialization Benchmark
Live browser benchmarks distinguishing measured byte sizes from mathematical estimates
Raw JSON
MeasuredUncompressed original payload received or generated
3,082 bytes on wire
Minified JSON
MeasuredWhitespace stripped, valid standard JSON
2,178 bytes on wire
Gzip (Level 6)
Calculating…Universal HTTP/1.1 & HTTP/2 compression supported by all clients
Computing stream size
Brotli (est.)
Calculating…Modern web standard with higher compression ratio for text
Computing stream size
Zstandard (est.)
Calculating…Modern high-performance compression; ideal when you control both client & server
Computing stream size
MessagePack
Calculating…Compact binary JSON equivalent eliminating string parsing overhead
Computing stream size
CBOR
Calculating…Concise Binary Object Representation standard (RFC 8949)
Computing stream size
What Happens on Real Networks?
Estimated download times for 3.01 KB on the wire, including TCP slow-start round trips
Slow 3G
Emerging markets / weak mobile signal (400 Kbps, 400ms RTT)
Fast 3G
Typical 3G connection (1.6 Mbps, 150ms RTT)
4G / LTE
Standard mobile LTE (12 Mbps, 50ms RTT)
5G / Fiber
High-speed broadband or 5G (100 Mbps, 15ms RTT)
Satellite / Starlink
Satellite link with propagation delay (25 Mbps, 220ms RTT)