Snowflake Credit Cost Calculator
What will this Snowflake warehouse actually cost per month? Pick a warehouse size, enter your price per credit and how many clusters are running, to get the credit cost, the all-in total, and every step of the arithmetic shown.
- Free with a free account
- Runs on our server in milliseconds
- Your input is not stored or logged
Create a free account to use the calculator
Members use every tool on AIDataLegends for free. It takes a name, an email and a password, and you come straight back here.
Not ready yet? The worked example below shows exactly what the tool produces.
Worked example
A Medium warehouse (4 credits/hour) at $3.00 per credit, running 10 hours a day on business days, with multi-cluster autoscaling between 1 and 3 clusters. The calculator's answer:
What this means
- This is compute credits only. The cloud services layer (query compilation, metadata, result caching) is free up to 10% of a day's compute credits and billed at the same per-credit rate beyond that — workload-dependent, so it isn't in this total. Storage is billed separately again, by the terabyte.
- The range assumes the warehouse sits at one end the whole time. Real auto-scaling usually lands somewhere in between — use the range as bounds, not a midpoint estimate.
- A warehouse resizing up or down takes effect on the next query, not retroactively, and billing jumps to the new size's rate immediately — resize for the workload you're about to run, not the one that just finished.
The breakdown
Credits/hour = clusters running × credits/hour for Medium
= 4
Cost/hour = credits/hour × price per credit = 12.00
Cost/month = cost/hour × hours/day × days/month = 2,600.40
Starting points, not an invoice: list prices vary by edition, cloud and contract, and this excludes the cloud services layer and storage. Use your own negotiated or published rates for an exact number.
How Snowflake warehouse billing works
Snowflake meters virtual warehouse compute in credits, consumed per second (60-second minimum) while the warehouse is running — not while it's suspended. Every size doubles the credit rate of the one below it:
| Size | Credits/hour |
|---|---|
| X-Small | 1 |
| Small | 2 |
| Medium | 4 |
| Large | 8 |
| X-Large | 16 |
| 2X-Large | 32 |
| 3X-Large | 64 |
| 4X-Large | 128 |
| 5X-Large | 256 |
| 6X-Large | 512 |
A multi-cluster warehouse running N clusters at once consumes N times that rate — this calculator's cluster count models exactly that. The price per credit itself depends on your edition (Standard, Enterprise, Business Critical), cloud and whether you're on on-demand or capacity pricing.
What this doesn't include
- The cloud services layer — query compilation, metadata operations and result caching — is free up to 10% of a day's compute credits and billed at the same rate beyond that. It's too workload-dependent to estimate here, so it isn't in this total.
- Storage is billed separately, by the average terabyte per month, independent of compute entirely.
- Serverless features (Snowpipe, Search Optimization, Automatic Clustering, materialized view maintenance) bill their own credits outside the warehouse you size here.
The levers that actually move this number
- AUTO_SUSPEND. A warehouse left running idle bills every second it's up, whether or not a query is executing — a short auto-suspend window (Snowflake's default is a good starting point) is the single biggest lever most accounts haven't pulled.
- Right-sizing. A warehouse resize takes effect on the next query at the new size's rate immediately — size for the query you're about to run, not the one that just finished.
- Multi-cluster + auto-scale vs. a bigger size. Bursty concurrent-query load usually calls for more clusters of a smaller size (auto-scaling) rather than one bigger, always-on warehouse; steady heavy single queries call for the reverse.
- Resource monitors cap credit spend per warehouse or account per period and can suspend warehouses automatically when a threshold is hit — useful as a backstop, not a sizing tool.
Limitations and assumptions
- The autoscaling range assumes the warehouse sits at one bound (min or max clusters) the whole time; real auto-scaling workloads usually land somewhere between, so treat the range as bounds, not an estimate.
- Cloud services credits, storage and serverless features are not included — see above.
- Prices change by edition, cloud, region and contract, and this tool has no pricing data of its own — it is pure arithmetic on the numbers you provide.