Warehouse size Γ active hours Γ credit price β model the compute bill.
Snowflake bills credits per second the warehouse runs, doubling per size, so auto-suspend and right-sizing are the levers. For the scan-based warehouse model instead, see the BigQuery query cost calculator.
The Snowflake Credit Cost Calculator estimates your monthly compute bill for a Snowflake virtual warehouse. It multiplies three inputs: the warehouse's credits per hour (which doubles with each size step β X-Small burns 1 credit/hour, Small 2, Medium 4, and so on), the number of active hours per month the warehouse actually runs, and your negotiated dollar price per credit. The result is the recurring compute spend that a given warehouse configuration drives, letting you compare sizes and usage patterns before committing.
The key trade-off is that a larger warehouse costs proportionally more per hour but often finishes work faster, so total credits depend on runtime, not size alone. Because Snowflake bills per second only while a warehouse is running, the biggest lever is active hours: setting a short auto-suspend timeout so idle warehouses stop consuming credits usually saves more than downsizing. Estimate before scaling up, then verify against actual usage.
Compute is metered in credits per active hour. Each warehouse size doubles the rate (X-Small = 1 credit/hr, Small = 2, Medium = 4, and so on), billed per second while running. A credit costs roughly $2β$4 depending on your edition and cloud.
Set aggressive auto-suspend (idle warehouses keep burning credits), right-size warehouses to the workload rather than defaulting large, use auto-resume so you are not paying for a warm idle cluster, and separate heavy and light workloads onto appropriately sized warehouses.
Cost at different volumes:
| Volume | Monthly | Yearly |
|---|