Storage for Cloudflares
Cloudflare storage products hold data for edge applications. KV is an eventually consistent key-value store for read-heavy config, R2 is S3-compatible object storage without egress fees, D1 is a serverless SQLite database, and Queues carry background messages. Each fits a different access pattern.
Stage: Developer Platform · Part of the Cloudflare roadmap · Last reviewed 19 November 2026
What to learn in Storage
- Read and write values in Workers KV and explain its consistency model
- Store and serve files from an R2 bucket through a Worker
- Run SQL queries and migrations against a D1 database
- Pick KV, R2 or D1 for a given data shape and access pattern
- Send and consume messages with Cloudflare Queues
Storage interview questions
When would you choose KV over D1?
Choose KV for read-heavy data such as configuration, feature flags or cached lookups, where eventual consistency is fine. Choose D1 when you need relational queries, joins or transactions on structured data that changes often.
What is R2 and how does it differ from S3?
R2 is Cloudflare's object storage with an S3-compatible API, so many existing tools work with it. Its notable difference is that it does not charge egress fees for reading data out, though storage and operation costs still apply.
Where Storage fits in the Cloudflare roadmap
Storage belongs to the Developer Platform stage (intermediate level), which takes about 14 hours. Build at the edge.
Other units in this stage
Back to the full Cloudflare roadmap