Limits
Rate limiting on managed public buckets through r2.dev
Managed public bucket access through an r2.dev subdomain is not intended for production usage and has a rate limit applied to it. If you exceed the rate limit, requests through your r2.dev subdomain will be temporarily throttled and you will receive a 429 Too Many Requests response. For production use cases, consider linking a custom domain to your bucket.
Account plan limits
| Feature | Limit |
|---|---|
| Bucket | 1000 buckets per account |
| Data storage per bucket | Unlimited |
| Object key length | 1,024 bytes |
| Object metadata size | 8,192 bytes |
| Object size | 5 TB per object |
| Maximum object name length | 1024 bytes |
| Maximum upload size1 | 5 GB |
| Maximum upload parts | 10,000 |
| Maximum custom domains per bucket | 50 |
1 Max upload size applies to uploading a file via one request, uploading a part of a multipart upload, or copying into a part of a multipart upload. If you have a Worker, its inbound request size is
constrained by Workers request limits. The max upload size limit does not apply to subrequests.
Review the Examples on how to use the SDKs.
Caching
Currently Cloudflare’s Tiered Cache feature is not compatible with responses from R2. These responses will act as if Tiered Cache is not configured.