Quick answer
Redis documents single string value as 512 MB. Strings can contain binary data, but very large values affect latency, memory, replication, and persistence.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| single string valueStrings can contain binary data, but very large values affect latency, memory, replication, and persistence. | 512 MB | Redis default | RedisAug 22, 2026 |
Why does this limit matter?
A technically valid 512 MB value can block the event loop and create large network and persistence spikes.
This value is scoped to Redis default; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Measure serialized bytes and prefer chunking or object storage for large binary payloads.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- Managed services, client libraries, proxies, and commands may impose lower practical limits.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related