Cloudflare R2 Object Storage FAQs

Question 1

How do I ensure metadata is included when listing R2 objects?

Accepted Answer

When calling the list() method, you must explicitly opt-in by including 'httpMetadata' or 'customMetadata' in the 'include' array within the options object.

Question 2

Why does Wrangler return a 403 Forbidden error during R2 operations?

Accepted Answer

Wrangler requires 'Admin Read & Write' API token permissions. Using 'Object Read & Write' permissions will fail for bucket-level operations performed by the CLI.

Question 3

Can I use custom domains with presigned URLs in Cloudflare R2?

Accepted Answer

No, presigned URLs only work with the S3 API domain (r2.cloudflarestorage.com). Custom domains should be used for serving public content, while the S3 domain handles signed access.

Question 4

Is the CORS configuration format the same for the Dashboard and CLI?

Accepted Answer

No. The Wrangler CLI requires a JSON structure with a 'rules' array, whereas the Dashboard UI uses a direct array of objects. Mixing these formats will result in configuration errors.

Question 5

What are the size limits for R2 multipart uploads?

Accepted Answer

Individual parts must be between 5MB and 100MB, and a single upload can consist of up to 10,000 parts. It is recommended to use standard put() for files under 5MB.

Cloudflare R2 Object Storage

Key Features

Use Cases

Cloudflare R2 Object Storage

Key Features

Use Cases