.png)
How It Works
BigQuery charges along two primary dimensions: compute and storage. On the compute side, Google offers two pricing models. The on-demand mode bills per terabyte (TB) of data scanned by each query, which means a single poorly scoped query against a large table can generate a large unexpected charge. The capacity model uses slots, which are units of computational capacity that you reserve in advance. Teams can purchase slot reservations, called BigQuery Reservations, to get predictable pricing instead of variable per-query costs. On the storage side, BigQuery charges for active storage (tables written to recently) at a higher rate than long-term storage (tables untouched for 90 or more days).
Streaming inserts carry a separate per-row charge, while batch loads are free. Understanding which cost lever is driving your bill requires visibility into query patterns, storage tiers, and reservation utilization together. Also see Google BigQuery Committed Use Discounts guide.
Why It Matters for Cloud Cost
BigQuery spend is easy to underestimate. A single analytical workload with broad SELECT statements against unpartitioned tables can scan terabytes of data and generate charges that dwarf the underlying value of the query. Without query governance, table partitioning, and storage lifecycle policies, BigQuery costs compound quickly as data volumes grow. Teams that rely on the on-demand model without guardrails often discover large charges only after the billing period closes. Slot reservations reduce that volatility, but only when sized correctly against actual workload demand. Unused slot capacity is wasted with no refund mechanism under standard Google pricing. ClearCost reporting helps teams surface BigQuery spend alongside other GCP services, giving finance and engineering a shared view of where data costs are accumulating.
ClearCost provides visibility and showback reporting across cloud spend, helping finance and engineering teams track where GCP costs are accumulating.