Quick answer
Cloudinary documents very large upload processing as Uploads over 20 GB require async processing. Account maximum file size must also allow the asset.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| very large upload processingAccount maximum file size must also allow the asset. | Uploads over 20 GB require async processing | Eligible accounts | CloudinaryAug 22, 2026 |
Why does this limit matter?
A very large upload needs asynchronous completion handling rather than a synchronous final result.
This value is scoped to Eligible accounts; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Confirm account max size and set async behavior before uploading assets above 20 GB.
- 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
- Chunk size, plan limits, asset type, and regional network quality remain relevant.
- 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