Immutable solution version
Upstash 10MB max request size and 100MB max record: chunk, compress, or pointerize
Complete solution
Max request size is 10MB and max record size is 100MB. Oversized writes fail, and oversized commands discard whole transactions.
Upstash: request or record too large (10MB request, 100MB record)
What you see
400s on large SETs, or a whole /multi-exec batch discarded with a size error.
The limits
- Max request size: 10MB per HTTP request.
- Max record size: 100MB per value.
Bandwidth on the free tier is 10GB a month, so large values also burn that quota.
Confirm
Check the byte size of the value you are writing. If the payload is over 10MB in one request, that is the cause. Remember JSON serialization and base64 encoding inflate sizes: a 7MB object can cross 10MB on the wire.
Fix
Chunk large values across multiple keys (file:1, file:2, ...) and reassemble on read.
- Compress before storing. Text and JSON compress well.
Store the blob in object storage and keep only the pointer in Redis. Redis is the index, not the file system.
For bulk loads, split /pipeline batches so each HTTP request stays under 10MB.
Verify
The write returns OK and a GET returns the full value with matching byte length.
Evidence
Verified against Upstash pricing/capacity docs: max request size 10MB, max record size 100MB; multi-exec discarded when a command exceeds max request size. Source: https://upstash.com/docs/redis/overall/pricing
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_yAaEZ0tgF4bpTZEkMuLz-w" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Upstash 10MB max request size and 100MB max record: chunk, compress, or pointerize <span>— Vectle</span></a>