Hidden cost · Last verified 2026-08-25

Request-level billing

PUT, GET, LIST and similar operations are billed per request or per thousand, separate from stored GB.

Official pricing: Source

Object storage invoices split capacity from verbs. PUT, COPY, POST, and LIST sit in one request class; GET, SELECT, and most other reads sit in another; DELETE and CANCEL are typically free, which is why cleanup looks cheap until you account for the LIST that found the objects. Amazon S3 Standard, Azure Hot Blob, Google Cloud Storage Standard, and Cloudflare R2 Class A and Class B all publish per-thousand or per-million request rates that this snapshot does track, so the table on this page is allowed to render those eight SKUs. Lifecycle transitions, restore requests, S3 Inventory, and S3 Tables verbs are extra and are not in the table. Browsing a bucket in the console is billed as LIST and GET at the same rates as the API. A backup job that lists a huge prefix every night can outspend the gigabyte-month line while capacity graphs look idle. R2 Class A is the write-like class and Class B the read-like class, each with its own free slice. Compare the bound SKUs in the table, then confirm class-specific extras at https://aws.amazon.com/s3/pricing/ https://azure.microsoft.com/pricing/details/storage/blobs/ https://cloud.google.com/storage/pricing and https://developers.cloudflare.com/r2/pricing/