What this estimate includes
Capacity is priced from the public on-demand class you select (standard, infrequent, archive-style where we have a SKU). Requests use the vendor’s published per-thousand or per-million rates. Retrieval and restore volume are added when the class bills them. Egress uses the same public internet-out tables as the egress calculator, including documented $0 internet out for R2.
What it does not include
- Lifecycle transition fees and early-delete penalties
- Replication to a second region
- Inventory, object-lock, or analytics add-ons
- CDN in front of the bucket (hit ratio is not modeled here — use the egress tool if origin download is the question)
- Taxes and reserved capacity discounts
How to read the ranking
If the workload is store-and-rarely-read, capacity dominates and archive classes win on paper. If it is a public download, egress usually dominates and R2’s documented zero internet-out becomes the story — but you still pay storage and Class A/B operations. Mix the two (backups that you restore in a disaster) and retrieval can exceed both.
GB vs GiB is converted explicitly. Turn free tier off if the account already consumed the monthly grant. Numbers are list prices, not a recommendation to move production tomorrow.