Paste a line item from your invoice and find what it bills for, across the Google Cloud services covered so far.
Class A and Class B Operations
Cloud Storage bills for API calls as well as for bytes.
Class A covers writes and listing; Class B covers reads. Listing is the one that catches people: it is a Class A operation, and code that lists a bucket in a loop can generate an operations bill larger than the storage bill.
Billed: Priced per 1,000 operations, by storage class, location type and bucket namespace. On Standard, Class A (writes, lists) costs more than ten times Class B (reads); the gap narrows on colder classes, which charge more for both, and closes on Archive.
What triggers this charge
- Bucket listing calls, especially recursive listings of buckets with millions of objects, each page of results is a separate billed operation.
- Object writes. A resumable upload or rewrite through the JSON API or gRPC counts as one Class A operation however many requests it takes; each part of an XML API multipart upload is a request of its own.
- Storage class changes, including lifecycle transitions, billed as Class A at the destination class rate.
- Reads, at a lower rate but at high volume for a public asset bucket.
- Monitoring or sync tools polling bucket contents on a short interval.
How to reduce it
Stop listing to check existence
A direct metadata GET on a known object name is a Class B operation; listing the prefix to find it is Class A and returns far more data.
Use Pub/Sub notifications instead of polling
Pub/Sub notifications for Cloud Storage replace a polling loop entirely, which removes the listing charge rather than reducing it. The Pub/Sub messages bill separately, usually for far less.
List by prefix instead of walking folders
Walking a deep folder tree one level at a time sends a list request per folder. One listing with a prefix and no delimiter returns up to 1,000 objects per page however deep they sit. In hierarchical namespace buckets, recursive folder operations are billed as a Class A operation per child.
Rates
Sources and review
- Explanation reviewed:
- 1 Nov 2026, against Cloud Storage pricing and the Object Lifecycle Management docs.
- Rates verified:
- not yet. No rate is shown on this page until one is loaded from the Cloud Billing Catalog API.
Now find out how much of this you are actually paying.
Finitizer breaks your Google Cloud bill down to the SKU, shows how each one has moved since last week, and separates rate changes from usage changes, so you know whether to talk to engineering or to procurement.
See how Finitizer works