Snowflake Cost Calculator
Model Snowflake compute from warehouse size, query hours, auto-suspend delay and concurrency scaling — at your own contracted credit price, not a list rate you do not pay. Shows how much of the bill is idle time waiting for auto-suspend.
| Time spent executing queries8.9 hours a day of actual work | $15,585.28 |
| Time awake with nothing to do15.1 hours a day — billed at the full rate | $26,494.98 |
| Total | $42,080.26 |
What would change it
What this model assumes
- This tool does not publish a Snowflake rate card, and that is deliberate. Snowflake’s per-credit prices live in a contract-specific consumption table rather than a machine-readable feed, and almost every customer of any size pays a negotiated rate. A calculator built on list price is quietly wrong for most of its readers, so this one asks.
- Snowflake bills wakefulness, not work. Credits accrue per second while a warehouse is running, whether or not a query is executing, with a 60-second minimum each time it resumes. That is why the idle line above exists and why it is often the larger one.
- Size changes assume runtime scales inversely with compute. That is the standard Snowflake rule of thumb and it holds for scan-bound work. It is optimistic for anything serialised — a query bottlenecked on a single-threaded step will not halve.
- Compute only. Storage, cloud services above the 10% daily allowance, serverless features, Snowpipe and data transfer are not included. They are real, and they are not what a warehouse-sizing decision turns on.
- Query arrival is modelled as an average. Real traffic is bursty, and bursts suspend less often than a uniform average implies — so for spiky workloads this figure is a floor, not a ceiling.
Frequently asked questions
How is Snowflake compute billed?
By the second, for as long as a warehouse is running — not for query execution. A warehouse that resumes bills a 60-second minimum, then per second until it auto-suspends. This is why a warehouse serving 200 short queries an hour with a 10-minute auto-suspend bills a full hour for perhaps six minutes of work.
What should I set Snowflake auto-suspend to?
Sixty seconds for most warehouses, which is the minimum. The argument for a longer setting is warm cache and avoiding cold starts, and that matters for interactive BI during business hours. For ETL warehouses and anything running on a schedule, a long auto-suspend is pure idle spend — this calculator shows exactly how much.
Does a bigger Snowflake warehouse cost more?
Per hour, yes — each size up doubles credits per hour. Per query, often not, because doubling compute roughly halves runtime for scan-bound work, making the change close to cost-neutral while cutting latency. It stops being neutral when queries are bottlenecked on something that does not parallelise, or when the warehouse is idle most of the time anyway.
Why does this calculator ask for my credit price?
Because publishing one would be wrong for most readers. Snowflake per-credit prices live in a contract-specific consumption table rather than a machine-readable feed, and almost every customer of any size pays a negotiated rate. A calculator built on list price is quietly inaccurate in a way you cannot see, so this one asks instead of assuming.
What is multi-cluster warehouse scaling costing me?
Each additional cluster bills the full credits-per-hour rate for the warehouse size while it runs. A Medium warehouse scaling to three clusters costs 12 credits an hour, not 4. The concurrency factor in this calculator is the mean number of clusters running, which is what you should be measuring rather than the maximum you configured.
The same question, asked continuously against real query history.
Finitizer profiles warehouse-level idle time, finds the queries driving credit consumption, and applies the same modelling to BigQuery, Redshift and Databricks — so a multi-platform data estate gets one answer instead of four spreadsheets.