Cloudflare R2
Step-by-step guide to connect Cloudflare R2 buckets to BucketMate for macOS with an R2 S3 API token, your account endpoint, and the right permissions.
BucketMate connects to Cloudflare R2 through the S3-compatible API endpoint for your account.
Prerequisites
- Cloudflare account
- R2 bucket
- Account ID
- R2 API token with access key ID and secret access key
Endpoint and region
Use your account-specific endpoint:
https://<account-id>.r2.cloudflarestorage.com
Set region to:
auto
Permissions
Give the token access to the buckets you want to manage. BucketMate may need permission to list buckets, list objects, read objects, write objects, and delete objects depending on the actions you use.
If the token is scoped to specific buckets and cannot list all buckets, turn off Load all buckets and enter bucket names manually.
Connection steps
- Open the Cloudflare dashboard.
- Go to R2 and create or select an API token for S3 access.
- Copy the account ID, access key ID, and secret access key.
- Open BucketMate.
- Choose Add connection.
- Select Cloudflare R2.
- Enter the endpoint
https://<account-id>.r2.cloudflarestorage.com. - Enter region
auto. - Enter the access key ID and secret access key.
- Optionally enter a Custom domain, such as
https://files.example.com, if the bucket is served through a public domain. - Use Test Connection.
- Choose Connect.
Common issues and fixes
Region must be auto
Some tools require a region value, and R2 expects auto. Fix by setting the region to auto - empty and us-east-1 are accepted aliases.
ACL headers are not supported
Requests using x-amz-acl will fail. Fix by removing ACL headers and using R2 access controls instead of S3 ACL calls.
Object Lock is not supported
Object Lock headers are not implemented. Fix by removing Object Lock headers and using provider-native retention controls if required.
Tagging headers are not supported
Requests using x-amz-tagging will fail. Fix by removing tagging headers and storing tags in metadata or your app database.
SSE-KMS is not supported
SSE-KMS headers are not implemented. Fix by using SSE-C or client-side encryption.
Direct object URLs do not open
R2 buckets are private by default. Use BucketMate's presigned share links for private objects, or configure public access and a custom domain if you want copied direct URLs to work in a browser.
BucketMate tips
- Add your public R2 domain in the Custom domain field of the connection form when you want Copy URL (custom domain) to use it. To change it later, right-click the connection and choose Edit.
- Use presigned links for private one-off sharing.
- Change files between Standard and Infrequent Access with Change storage class.... See Storage classes.
- Use manual bucket names for restricted R2 tokens.
Related guides
- Cloudflare R2 S3 endpoint setup - endpoint, keys, and
region=autofor AWS CLI, boto3, and SDKs - Cloudflare R2 pricing 2026 - storage, Class A/B operations, and free tier
- Cloudflare R2 vs AWS S3 - monthly bills compared