Rate limiting on managed public buckets through
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 to your bucket.
Account plan limits
|Bucket||1000 buckets per account|
|Data storage per bucket||Unlimited|
|Object metadata size||8,192 bytes|
|Object size||5 TiB per object1|
|Maximum upload size3||5 GiB2|
|Maximum upload parts||10,000|
|Maximum custom domains per bucket||50|
1The object size limit is 5 GiB less than 5 TiB, so 4.995 TiB.
2The max upload size is 5 MiB less than 5 GiB, so 4.995 GiB.
3Max 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 . The max upload size limit does not apply to subrequests.
Review the on how to use SDKs with the S3 API to upload large files.
To increase these limits, contact your Cloudflare account team.