Quick answer
Cloudinary documents single-request upload as 100 MB. Larger non-chunked uploads return HTTP 413.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| single-request uploadLarger non-chunked uploads return HTTP 413. | 100 MB | Upload API | CloudinaryAug 22, 2026 |
Why does this limit matter?
A retry cannot fix a structurally oversized single upload request.
This value is scoped to Upload API; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Measure file bytes and switch to upload_large or chunked upload above 100 MB.
- 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
- Account-specific maximum file sizes can still be lower or higher by asset type and plan.
- 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