Product overview — Object Storage • Medium

Cloudflare R2

S3-compatible object storage often evaluated to reduce egress-driven spend and support edge-adjacent workflows; fit depends on access pattern, requests, and Cloudflare alignment.

Sources linked — see verification below.

Open decision brief → Compare vs alternatives →

What it is Who it fits Next steps

Freshness & verification

Last updated 2026-02-09 Intel generated 2026-02-06 2 sources linked

Who is this best for?

This is the fastest way to decide whether Cloudflare R2 is in the right neighborhood.

Best for

Applications serving static assets, user-uploaded files, or media directly to end users where zero egress fees eliminate the largest variable cost in traditional S3-based serving architectures.
Teams that want to pair object storage with Cloudflare Workers for edge-side asset processing (image resizing, content transformation) without the latency of pulling from a cloud region.
Organizations migrating off S3 specifically to eliminate bandwidth costs — R2's S3-compatible API means most AWS SDK code works against R2 with an endpoint URL change.

Who should avoid

You require deep enterprise governance features tied to a hyperscaler ecosystem
Your workload depends on hyperscaler-native integrations across many services
You need guaranteed parity with every S3 feature and edge-case behavior

Next steps

Decision brief →

Pricing behavior, constraints, and what breaks first.

Pricing behavior →

Where the cost cliffs appear and what triggers upgrades.

Alternatives →

Common switches and why buyers pick them.

Sources & verification

Pricing and behavioral information comes from public documentation and structured research. When information is incomplete or volatile, we prefer to say so rather than guess.

Something outdated or wrong? Pricing, features, and product scope change. If you spot an error or have a source that updates this page, send us a correction. We prioritize vendor-verified updates and linkable sources.