Current documented limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| single-request uploadLarger non-chunked uploads return HTTP 413. | 100 MB | Upload API | CloudinaryAug 22, 2026 |
| chunk sizeChunking is required for files above the non-chunked ceiling. | 20 MB default; 5 MB minimum | Chunked upload | CloudinaryAug 22, 2026 |
| very large upload processingAccount maximum file size must also allow the asset. | Uploads over 20 GB require async processing | Eligible accounts | CloudinaryAug 22, 2026 |
How to apply Cloudinary limits safely
The monitored baseline covers single-request upload, chunk size, very large upload processing. Treat these as separate constraints rather than one platform-wide capacity number: a workload can fit one row and still fail another because the plan, model, endpoint, runtime, region, invocation mode, or account scope differs.
- Match the production workload to the exact scope printed beside each value and confirm it in the active Cloudinary console, configuration, or response headers.
- Measure the serialized request, token volume, duration, concurrency, storage, or connection demand at realistic percentiles, then preserve headroom for bursts and retries.
- Check every adjacent layer—client, SDK, gateway, proxy, queue, database, and downstream service—for a smaller effective limit before changing architecture.
Specific limit pages
These pages exist because the constraint has a distinct implementation or troubleshooting intent. Closely related keyword variations stay consolidated.
Cloudinary Non-Chunked Upload Limit
Cloudinary Non-Chunked Upload Limit, verified against Cloudinary's official documentation with scope, implementation impact, caveats, and a direct check.
Cloudinary Chunked Upload Limits
Cloudinary Chunked Upload Limits, verified against Cloudinary's official documentation with scope, implementation impact, caveats, and a direct check.
Cloudinary Large File Upload Behavior
Cloudinary Large File Upload Behavior, verified against Cloudinary's official documentation with scope, implementation impact, caveats, and a direct check.