Snowflake Pricing: Credits, Storage, and What You Actually Pay

Snowflake pricing looks simple on the surface and surprises teams in practice, because you do not buy a plan, you buy consumption. There is no per-user license and no fixed monthly fee. Instead you pay for three things that meter independently: compute, measured in credits; storage, measured per terabyte; and a handful of extra services that bill on their own. The total depends on which edition you run, how big your warehouses are, and, above all, how long they stay awake.

This guide breaks down each cost component with realistic scenarios so you can estimate what you will actually spend. All prices referenced are approximate and change, and rates vary by region and cloud provider, so always verify against the official Snowflake pricing page and the current consumption table before you budget.

How Snowflake Pricing Works: The Consumption Model

Snowflake separates storage from compute, and that separation is the foundation of the whole pricing model. Your data sits in cloud object storage and is billed by volume. When you want to query, load, or transform that data, you start a virtual warehouse, which is a cluster of compute that consumes credits for as long as it runs. Two teams can query the same data on separate warehouses without competing for resources, and each warehouse bills on its own.

There are three meters to keep in mind. Compute credits are the dominant cost for most workloads, and a credit has a dollar price that depends on your edition. Storage is a monthly fee based on the average compressed volume you hold. Additional services, including serverless features and data transfer, bill separately at their own rates. Most cost surprises come from the first meter, because a warehouse left running bills whether or not anyone is querying it.

Credits and Edition Pricing

A credit is Snowflake's unit of compute. What one credit costs in dollars is set by your edition, and the edition also decides which security and governance features you get.

Snowflake lists four editions: Standard, Enterprise, Business Critical, and Virtual Private Snowflake. Standard is the entry tier with core functionality, at roughly $2 per credit. Enterprise adds multi-cluster warehouses for concurrency, materialized views, and extended time travel, at roughly $3 per credit, a 50 percent premium over Standard. Business Critical adds stronger security and compliance controls (such as customer-managed keys and support for regulated data) at roughly $4 per credit. Virtual Private Snowflake (VPS) is a completely isolated environment for the strictest requirements, priced on request.

Snowflake does not publish per-credit dollar prices on its pricing page; it directs buyers to a consumption table and calculator. The approximate $2 / $3 / $4 figures used here are the US East AWS on-demand rates widely reported by independent pricing guides (Flexera, Revefi), so treat them as a directional baseline and confirm your own rate in the calculator.

Two points matter when reading these numbers. First, the per-credit price is a US East AWS on-demand baseline; other regions and clouds carry a premium, sometimes a large one. Second, the edition multiplies only your compute bill, not your storage bill, so moving from Standard to Enterprise raises the compute portion by 50 percent, not your whole invoice.

Warehouse Sizes and Per-Second Billing

Warehouse size sets how many credits per hour a warehouse consumes, and the scale is a simple doubling. An X-Small warehouse consumes 1 credit per hour. Small is 2, Medium is 4, Large is 8, and each step up doubles again through the larger sizes, because, as Snowflake's documentation puts it, "each increase in size to the next larger warehouse approximately doubles the computing power and the number of credits billed per full hour" (Snowflake docs). A bigger warehouse is not more expensive per unit of work; it does the same work faster by using more credits over less time, which is why right-sizing is about matching the warehouse to the query, not always choosing small.

Billing is per second, with one important floor: each time a warehouse starts or resumes, it is billed a one-minute minimum, after which "all subsequent billing is per-second as long as the warehouse runs continuously." You pay by the second for exactly the time the warehouse runs. This is the mechanism behind the single most common Snowflake overspend, which is warehouses that stay awake between queries. A Large warehouse left idle for an hour costs 8 credits, roughly $24 on Enterprise, for producing nothing. Multiply that across several warehouses and a workday and idle time becomes the biggest line on the bill.

Storage Costs

Storage is the calm part of the Snowflake bill. You pay a flat rate per terabyte based on the average volume of data you store, measured after Snowflake's automatic compression. On-demand storage runs about $23 per terabyte per month; pre-purchased capacity storage is cheaper per terabyte in exchange for an upfront commitment, and the exact rate varies by account type and region (Revefi).

Two things quietly inflate storage. Time Travel retains historical versions of your data for a configurable window (up to 90 days on Enterprise and above), and those versions count toward storage. Fail-safe keeps a further 7 days of recovery data after Time Travel expires. Snowflake charges these only for the changed rows rather than full copies, but on high-churn tables with long retention they still add up, so retention settings are worth reviewing rather than leaving at the maximum by default.

Cloud Services, Serverless, and Data Transfer

Beyond compute and storage, a few services meter separately.

Cloud services handle authentication, query planning, and metadata. Snowflake gives you a free allowance here: usage is charged only if daily cloud services consumption exceeds 10 percent of your daily virtual-warehouse usage. Most workloads stay under the threshold, but metadata-heavy patterns (frequent small queries, heavy use of INFORMATION_SCHEMA) can cross it.

Serverless features run on Snowflake-managed compute rather than your own warehouse, and each bills at its own credit rate. This includes Snowpipe for continuous loading, automatic clustering, materialized view maintenance, search optimization, and serverless tasks. They are convenient and often worth it, but they are real credits that do not show up in your warehouse usage, so they are easy to overlook when reconciling the bill.

Data transfer is mostly free within a region, but moving data out of a cloud region or to another cloud incurs egress charges billed per terabyte. Cross-region replication and data pulled to external tools are the usual sources.

Realistic Cost Scenarios

These scenarios use approximate pricing to illustrate cost structure. Your actual costs will vary based on region, edition, warehouse discipline, and negotiated rates. Verify against current pricing before budgeting.

Small team: BI and light transformation

A small analytics team runs an X-Small and a Small warehouse for dashboards and dbt transformations during business hours, with auto-suspend set to 60 seconds. Rough monthly shape: a few hundred credits of compute (roughly $600 to $1,200 on Standard) plus storage for a couple of terabytes (about $50). Total: roughly $700 to $1,500 per month. The range is almost entirely about how aggressively warehouses suspend.

Mid-size platform: production ELT plus concurrent BI

A production platform runs Medium warehouses for ELT, a multi-cluster warehouse for 40 concurrent analysts, and Snowpipe for streaming ingestion, on Enterprise. Rough monthly shape: compute in the low thousands of credits (roughly $9,000 to $15,000), storage for 50 TB (about $1,150), plus serverless and egress (about $1,000). Total: roughly $11,000 to $17,000 per month. A capacity commitment typically discounts the compute portion.

Enterprise scale: multi-team, near-continuous

An enterprise runs many warehouses across engineering, analytics, and data science, several near-continuously, on Business Critical, with heavy serverless usage. Rough monthly shape: tens of thousands of credits (roughly $60,000 to $90,000), storage for 500 TB (about $11,500), plus significant serverless and transfer. Total: roughly $75,000 to $110,000 per month, before a multi-year capacity discount that at this scale typically removes a meaningful percentage.

Cost Optimization Strategies

Ranked by impact. Fix the top three before anything else.

1. Set aggressive auto-suspend. This is the highest-impact change. Configure warehouses to suspend after 60 seconds of inactivity. The idle minutes between queries are pure waste, and shrinking them cuts the compute bill more than any other single action.

2. Right-size warehouses to the workload. Bigger is not always more expensive, because it finishes faster, but an oversized warehouse on small queries burns credits with no speed benefit. Match warehouse size to query complexity, and use separate warehouses for separate workloads so one heavy job does not force everyone onto a large cluster.

3. Commit to capacity if usage is stable. If your monthly credit consumption is predictable, a capacity purchase discounts the per-credit rate. The risk is over-committing to capacity you do not use, so size the commitment to your floor, not your peak.

4. Use multi-cluster warehouses for concurrency, not size. When many users query at once, a multi-cluster warehouse (Enterprise and above) scales out and back in automatically, which is cheaper than permanently running one large warehouse to absorb peaks.

5. Watch serverless and cloud-services usage. These do not appear in warehouse metrics. Review them in the account usage views so a metadata-heavy pattern or a chatty Snowpipe does not quietly grow.

6. Tune Time Travel retention. Long retention on high-churn tables multiplies storage. Set retention to what recovery actually needs rather than leaving it at the maximum.

Hidden Costs Most Teams Miss

Idle warehouses. The one to fix first. A warehouse with auto-suspend disabled or set high bills for every minute it is awake, including overnight and weekends. This is usually the largest recoverable waste.

Serverless credits. Snowpipe, automatic clustering, materialized view maintenance, and search optimization all consume credits outside your warehouses. Teams that only monitor warehouse usage under-count their true compute cost.

Non-US and multi-cloud premiums. The familiar $2 / $3 / $4 per-credit figures are a US East AWS baseline. Running in another region or on another cloud can raise the per-credit price noticeably, so the same workload can cost more purely because of where it runs.

Cloning and Time Travel storage. Zero-copy cloning is free at creation, but as cloned and source data diverge, the changed data is stored and billed. Combined with long Time Travel windows, storage on active tables can be several times the logical data size.

Query inefficiency. Queries that scan far more data than they need run longer, and longer runtime is more credits. Poorly clustered tables and full scans on large datasets are a compute cost, not just a performance issue.

How Dawiso Helps Control Snowflake Costs

Snowflake cost control is not only about warehouse settings. It is also about knowing which data is actually used, which pipelines are redundant, and which teams are rebuilding the same transformation. That is a governance and visibility problem, and it is where Dawiso helps.

Dawiso's data catalog shows which Snowflake tables and views are actively consumed and which are orphaned. A table that has not been queried in 90 days may be produced by a pipeline that is still burning credits every night for no reader. Lineage traces those pipelines end to end, not just inside Snowflake but across dbt, ingestion, and the BI tools downstream, so you can retire the ones that lead nowhere.

The business glossary prevents duplicate work. When two teams independently build a "monthly active users" metric because neither knows the other exists, both transformations consume compute. Dawiso surfaces those overlaps so one governed definition replaces several. And because governed, well-modeled views scan less data than raw tables, teams that query the right objects run faster queries that consume fewer credits. For teams pushing further into AI, Dawiso serves that governed context to agents through the context layer for Snowflake over the Model Context Protocol, so AI reads the same trusted definitions instead of guessing.

Conclusion

Snowflake pricing is not complicated in concept: credits for compute priced by edition, a per-terabyte storage fee, and a few services that bill on their own. The complexity, and the overspending, comes from the number of levers and how easy it is to leave warehouses running. The largest savings come from three habits: aggressive auto-suspend, right-sized warehouses, and a capacity commitment sized to stable usage. For a platform comparison, see Databricks vs Snowflake, and for the other major lakehouse, see Databricks pricing.

Sources

Pricing changes often and varies by region and cloud. Always confirm current figures against the primary sources below before budgeting.

• Snowflake, Pricing Options and editions overview (editions, consumption model, calculator).
• Snowflake documentation, Understanding compute cost (per-second billing, one-minute minimum, credit doubling by size, cloud services 10% threshold).
• Snowflake documentation, Understanding storage cost (flat rate per TB, compression, Time Travel and Fail-safe).
• Flexera, Snowflake cost optimization guide (approximate per-credit and storage rates, optimization).
• Revefi, 2026 Snowflake pricing guide (per-credit rates by edition, storage, regional premiums).