Skip to main content
Cloudflare R2 — S3-compatible object storage with zero egress fees, addressed through an account-specific endpoint.

​
At a Glance

​
Credentials

Create a secret with the Cloudflare R2 provider type. The auth method is r2_access_key, which requires: Create an R2 API token from the Cloudflare dashboard (R2 → Manage R2 API Tokens) with read/write permission on the bucket. The account ID does not belong in the secret — it goes in the location’s endpoint_url.

​
Location Setup

The location form asks for your Cloudflare account ID (shown on the R2 overview page in the dashboard) and fills in the endpoint URL from it. Onboarding and the rclone.conf import review do the same. The URL stays editable: a bucket in a jurisdiction uses that jurisdiction’s host instead, such as https://<account_id>.eu.r2.cloudflarestorage.com for the EU. Example:

​
Provider Quirks

R2 buckets are managed through the dashboard — the API exposes no CreateBucket, so R2 locations default to s3_no_check_bucket: true. R2 also handles list operations very efficiently, so fast_list is on by default.

​
Importing from rclone.conf

R2 remotes appear in rclone.conf as type = s3 with provider = Cloudflare. If the remote has an account_id but no endpoint, the importer builds the endpoint URL from the account ID automatically. See the rclone import guide.