Cloud Storage Class Calculator

No. In Iowa, Archive stores data at $0.0012 per GiB-month against Standard's $0.020, about sixteen times less, but reading it costs more in two ways: Class B (read) operations cost $0.05 per thousand against Standard's $0.0004, 125 times as much, and every GiB read pays a $0.05 retrieval fee. For objects of a few MiB or more the retrieval fee is the larger of the two; for small objects the operation charge is. Objects deleted before 365 days also pay the rest of the minimum. How much you read decides it: on the default lake of 8 MiB objects, Archive stays cheapest up to about 8% of the data read back a month, then Coldline, Nearline and Standard take over in turn.

Class A operations write or list, inserts, updates, copies, bucket and object listings. Class B operations read, object gets and metadata reads. Class A costs more than Class B in every class except Archive, where the two cost the same. Both are charged per operation rather than per byte, so for the same data, object size decides the count: reading a terabyte held as a million small objects takes a million operations, and the same terabyte in a thousand large ones takes a thousand. In this calculator you enter the operation counts. In simple mode the average size of objects read sets how much data the reads retrieve; advanced mode takes the data retrieved directly, for metadata-heavy or partial reads.

Nearline requires 30 days, Coldline 90 and Archive 365. Deleting an object before its minimum, overwriting it, or rewriting it yourself (for example to change its class by hand) bills the remaining days at that class's rate, because a rewrite replaces the object. Changing the class with an Object Lifecycle Management rule is different: there is no early-delete charge for the change, and the days the object already spent count toward the new class's minimum. On data that turns over quickly the charge compounds: objects living 10 days in a 90-day class pay for 80 unused days every 10 days, about eight times the nominal storage cost. With soft delete on, the charge falls due when the soft-deleted copy is permanently deleted, and the soft-deleted days count toward the minimum, so they replace early-delete days rather than adding to them.

Yes. Choose the bucket location: 17 regions, three dual-regions and three multi-regions, at Google's catalog rates. Standard costs $0.020 per GiB-month in Iowa, $0.026 in the US multi-region (30% more) and $0.044 in the nam4 dual-region. Dual- and multi-region writes cost twice the regional Class A rate and pay inter-region replication per GiB of data written ($0.02 for nam4, eur4, US and EU; $0.08 for asia1 and Asia). Enter Data written per month to include it; until you do, the results say replication is not included. A lifecycle class change pays no replication.

Yes. Set the days in Standard before a lifecycle rule moves objects. Each colder class is then priced as Standard for those days and the colder class after, with no retrieval, early-delete or replication charge for the move. Each object moves once, one Class A operation at the colder class's rate. The colder class's minimum counts from creation, so the days left after the move (days from creation until deletion minus days in Standard) set the remaining obligation, and deleting before the minimum bills the days short. 0 means no rule: data is written straight into each class. The rule must move objects before they are deleted or overwritten; otherwise it is rejected and not priced. Only one rule is modeled, not a multi-stage policy. Reads are assumed to occur uniformly over the object's modeled lifetime. This does not model higher access during the initial Standard period.

This calculator compares storage classes you choose yourself and a lifecycle rule you configure; it does not evaluate Autoclass. Autoclass prices differently: every operation is charged at Standard rates, there are no retrieval or early-delete fees, and a management fee of $0.0025 per 1,000 objects is charged every 30 days for objects of 128 KiB or more (smaller objects stay in Standard and are not counted). Most class changes are free, but moving an object from Coldline or Archive back to Standard or Nearline costs one Class A operation at the Standard rate. Enabling Autoclass on an existing bucket triggers a one-time charge for early deletion of objects under their minimum, retrieval of objects not in Standard and one Class A operation per object. It cannot be combined with lifecycle rules that change or match storage class. It suits buckets with unpredictable access; when you know the pattern, choosing the class yourself is what this calculator compares.

Yes. Google keeps deleted and overwritten objects for the bucket's soft-delete retention, 7 days by default on new buckets, and bills them at the storage rate of their class. Set Soft-delete retention to your bucket's policy, or 0 if soft delete is off. Short-lived data pays the most: objects replaced every 21 days with 7-day retention store a third more on Standard. In the colder classes the soft-deleted days count toward the minimum, so they mostly replace early-delete charges rather than add to them.

Autoclass, Object Versioning (noncurrent versions bill like live objects), hierarchical namespace rates, Rapid storage, turbo replication, cross-bucket replication and any excluded replication charges are outside this model. These features can affect total costs and the appropriate storage strategy. Network transfer (egress) is not included. When moving existing data, early-delete charges on existing objects rewritten to a warmer class and soft-delete retention of rewritten objects are flagged beside the result.