Snowflake credit prices range from $2.00 per credit on Standard tier in US East to $5.40 per credit on VPS tier in EU regions, a 2.7x spread that puts edition and region choice above warehouse sizing in cost impact. Realised enterprise Capacity discounts at $1 million annual commit land at 10 to 18 percent. At $3 million commit the band moves to 18 to 28 percent. At $10 million it reaches 28 to 40 percent. This pillar covers every credit price, the four editions, Reserved Capacity bands, Cortex AI cost, and the five optimisation patterns that hit Snowflake bills harder than the negotiated discount does.
Inside This Pillar
Snowflake credit model
Snowflake bills usage in credits. A credit represents one minute of compute on an X-Small warehouse at the Standard edition price point. Larger warehouses consume credits at higher multiples (Small = 2, Medium = 4, Large = 8, X-Large = 16, 2X-Large = 32, 3X-Large = 64, 4X-Large = 128). Higher editions consume credits at the same physical rate but at a higher credit price.
The customer pays per credit consumed plus a separate storage charge. The credit price varies by edition (Standard, Enterprise, Business Critical, Virtual Private Snowflake), by cloud (AWS, Azure, GCP), and by region. Realised cost is a function of three multipliers: warehouse size, edition, and region.
The four editions
Snowflake sells four edition tiers. Edition is set at account creation but can be upgraded mid-contract.
| Edition | Per-credit price (AWS US East) | Key features included |
|---|---|---|
| Standard | $2.00 | Encryption, role-based access, Time Travel up to 1 day |
| Enterprise | $3.00 | Standard plus multi-cluster warehouses, materialized views, search optimization, dynamic data masking, Time Travel up to 90 days |
| Business Critical | $4.00 | Enterprise plus HIPAA, PCI-DSS, customer-managed keys, AWS PrivateLink and Azure Private Link, Tri-Secret Secure |
| Virtual Private Snowflake (VPS) | $5.00 to $5.40 + commit minimum | Business Critical plus dedicated metadata store, isolated tenant deployment |
Most enterprise deployments land at Business Critical. Standard is appropriate for non-production workloads. Enterprise is the default for production workloads without regulatory requirements. Business Critical is required for healthcare (HIPAA), payment data (PCI-DSS), and any workload requiring customer-managed encryption keys or Private Link connectivity. VPS is rare and typically only justified for sovereign-cloud or single-tenant regulatory requirements.
Pricing by cloud and region
Per-credit price for Enterprise edition across the most-used regions:
| Region | Standard | Enterprise | Business Critical |
|---|---|---|---|
| AWS US East (Virginia) | $2.00 | $3.00 | $4.00 |
| AWS US West (Oregon) | $2.00 | $3.00 | $4.00 |
| AWS EU (Ireland) | $2.60 | $3.90 | $5.20 |
| AWS EU (Frankfurt) | $2.70 | $4.05 | $5.40 |
| AWS AP (Sydney) | $3.10 | $4.65 | $6.20 |
| Azure East US 2 | $2.00 | $3.00 | $4.00 |
| Azure West Europe | $2.60 | $3.90 | $5.20 |
| GCP us-central1 | $2.00 | $3.00 | $4.00 |
| GCP europe-west4 | $2.60 | $3.90 | $5.20 |
The region premium for EU and APAC over US is 30 to 55 percent. For workloads that can be served from a US region (analytics workloads with no data residency obligation), the region choice alone is a 30 to 55 percent cost lever. For workloads with EU data residency obligations under GDPR or Schrems II, the EU premium is unavoidable.
Warehouse sizing economics
Warehouse size doubles credit consumption at each tier. The naive intuition is that bigger warehouses cost more. The counterintuitive truth is that bigger warehouses often cost less per query because they finish in less than half the time.
| Warehouse size | Credits per hour | Cost per hour (Enterprise, US East) | Typical query speedup vs X-Small |
|---|---|---|---|
| X-Small | 1 | $3.00 | 1.0x |
| Small | 2 | $6.00 | 1.9x |
| Medium | 4 | $12.00 | 3.7x |
| Large | 8 | $24.00 | 7.2x |
| X-Large | 16 | $48.00 | 13.5x |
| 2X-Large | 32 | $96.00 | 24x |
| 3X-Large | 64 | $192.00 | 38x (diminishing) |
| 4X-Large | 128 | $384.00 | 52x (diminishing) |
For most workloads, Medium to Large warehouses offer the best credit-per-query economics. The diminishing returns above X-Large mean that 2X-Large and above are typically a wrong choice unless the query is unusually parallelisable. Auto-suspend (set to 60 seconds in most cases) is the single largest billed-hours lever; the default 600-second auto-suspend leaks 5 to 12 percent of total credits to idle time on intermittent workloads.
The warehouse sizing trap: Most Snowflake estates run X-Large or larger because someone once needed it for a heavy query and never resized. Resizing to Medium or Large and relying on auto-scaling for peaks typically cuts credit consumption by 25 to 45 percent on BI-style workloads.
Cortex AI and ML credit cost
Snowflake Cortex bundles LLM functions, Document AI, and Cortex Analyst into Snowflake-native AI features. Cortex consumes credits per token or per request, on top of the credit cost of the warehouse running the query.
| Cortex feature | Pricing unit | Rate (Enterprise tier) |
|---|---|---|
| Cortex LLM Functions (Llama 3 70B) | Per 1M tokens | 0.79 credits in, 0.79 credits out |
| Cortex LLM Functions (Llama 3 8B) | Per 1M tokens | 0.19 credits |
| Cortex LLM Functions (Mistral Large) | Per 1M tokens | 5.10 credits in, 15.30 credits out |
| Cortex LLM Functions (Claude 3.5 Sonnet) | Per 1M tokens | 2.55 credits in, 12.75 credits out |
| Cortex Search | Per serving unit hour | 1 credit per active hour |
| Cortex Analyst | Per request | 0.067 credits per message |
| Document AI extraction | Per page | 0.0006 credits per token |
For AI-heavy Snowflake workloads, Cortex credit cost can become the dominant line item. Compare Cortex pricing against direct OpenAI, Anthropic, or Bedrock pricing using our enterprise LLM cost comparison. The Snowflake case is strongest when the prompt context lives in Snowflake tables; the case weakens when the context lives elsewhere and Cortex becomes a more expensive proxy.
Storage and data transfer
Storage is billed separately from compute. On-demand storage rates are typically $40 per TB per month on AWS, slightly higher on Azure and GCP. Capacity storage rates negotiated at $1 million commit drop to $23 per TB per month. Time Travel and Fail-safe storage are charged at the same rate but consume additional space (Time Travel: up to 90 days of changes for Enterprise edition; Fail-safe: 7 additional days, non-configurable).
Data transfer out of Snowflake is charged at $0.02 to $0.09 per GB depending on cloud and region. For replication across regions, Snowflake charges replication transfer at the same per-GB rate. Cross-region replication for disaster recovery is a frequently overlooked Snowflake line item.
Reserved Capacity bands
Snowflake Capacity contracts (committed annual spend) replace on-demand pricing with a prepaid commitment. Realised discounts in advisor-led Snowflake negotiations during 2024 to 2026:
| Annual commit (TCV) | Capacity discount range | Storage discount | Cortex discount |
|---|---|---|---|
| $250K to $1M | 5 to 12 percent | 20 to 35 percent | 0 percent |
| $1M to $3M | 10 to 18 percent | 35 to 45 percent | 0 to 10 percent |
| $3M to $10M | 18 to 28 percent | 45 to 55 percent | 10 to 20 percent |
| $10M+ | 28 to 40 percent | 55 to 65 percent | 20 to 30 percent |
Snowflake Capacity contracts run 1, 2, or 3 years. Three-year terms typically add 4 to 7 percentage points over one-year terms. Unused Capacity at year end carries forward (subject to a cap, typically 20 to 30 percent of the year's commit) into the following contract year. Year-three unused commit is forfeit on most paper. The negotiation lever is to extend carry-forward into year three and to widen the cap.
Snowflake Marketplace cost
Snowflake Marketplace is the data exchange where third-party datasets, applications, and Native Apps are sold. Marketplace charges run on top of Snowflake credits. The two cost patterns are Native Apps (apps installed into the customer Snowflake account, billed per consumption against the customer's Snowflake commit) and Data Products (datasets accessed via reader accounts, billed to the data provider's account).
Marketplace consumption is a fast-growing line item that finance teams routinely miss. Marketplace apps consume the customer's Snowflake credits but are negotiated separately by individual teams. Quarterly Marketplace audit is a standard control.
Cost optimisation patterns
Five patterns deliver most of the savings in Snowflake estates. Independent reviews typically identify 20 to 35 percent of total spend as recoverable through optimisation alone.
First, right-size warehouses. Reduce X-Large defaults to Medium or Large for routine workloads. Savings: 20 to 35 percent of compute credits.
Second, tighten auto-suspend to 60 seconds for most warehouses. Savings: 5 to 12 percent of compute credits on intermittent workloads.
Third, adopt result caching and query result reuse. Snowflake caches results for 24 hours; enabling result reuse eliminates redundant query cost. Savings: 8 to 18 percent on BI workloads.
Fourth, use Search Optimization Service and Materialized Views selectively. Both add cost but reduce query credit consumption for repetitive lookups. Net savings: 10 to 25 percent on selective workloads.
Fifth, separate dev, test, and prod into separate accounts with Standard edition for dev where the Enterprise feature set is not required. Savings: 25 to 35 percent on dev compute credits.
Contract levers
Eight commercial levers move the Snowflake contract beyond headline discount:
Carry-forward cap on unused Capacity, raise from 20 to 35 percent of commit. Carry-forward extension into year three of a multi-year term. Price-protection clause locking per-credit rates for the contract term. Termination for convenience after year one with pro-rated refund of unused Capacity. Edition flexibility (right to operate Standard, Enterprise, and Business Critical accounts simultaneously without re-quoting). Region flexibility (commit drawn against any region without surcharge). Cortex AI inclusion in the Capacity commit at a defined exchange ratio. Marketplace consumption inclusion against the commit.
For the full data platform comparison, see our Snowflake vs Databricks vs BigQuery guide, our Databricks pricing pillar, and our analytics licensing guide. For the cloud-side commit interaction, see AWS EDP negotiation and Azure MACC versus CTP. For broader cost controls, see our cloud cost optimization guide and cloud contracts guide. To engage on Snowflake negotiation, see our cloud contract negotiation service.
Snowpark and Iceberg cost
Snowpark is the Snowflake developer framework for executing Python, Java, and Scala workloads against Snowflake data. Snowpark runs on Snowflake warehouses and consumes the same credits as SQL queries, but at modestly higher per-second consumption due to the JVM and Python container overhead. For workloads previously running on Databricks or external Spark clusters, Snowpark can shift compute spend back to Snowflake while reducing the data egress and tooling sprawl that comes with multi-platform analytics.
Iceberg Tables let Snowflake read and write Apache Iceberg formatted tables on customer-managed cloud storage. The compute cost is unchanged but the storage charge moves from Snowflake Capacity storage to the customer's own S3, ADLS, or GCS bucket. For very large estates where storage is more than 30 percent of the Snowflake bill, Iceberg can reduce storage cost by 40 to 60 percent versus Snowflake-managed storage, at the cost of additional governance complexity and slightly higher query latency on first-access.
How Snowflake contracts shape spend
Snowflake contracts have three structural choices that change cost more than the headline discount. First is the on-demand to Capacity transition: on-demand pricing carries no discount but no commitment. Most enterprises move to Capacity once monthly spend exceeds $30,000. Second is the term length: one-year, two-year, and three-year terms carry incremental discount, but multi-year commitments shift carry-forward risk to the customer. Third is the deployment topology: single account with role-based isolation is cheaper to administer but exposes commit allocation across business units; multi-account with shared Capacity is more flexible but adds governance overhead.
The under-discussed contract clause is the Capacity overage rate. On-demand pricing kicks in when Capacity is fully consumed, at on-demand rates that are 5 to 18 percent higher than Capacity rates. Negotiate the overage to consume against the next year's Capacity at the Capacity rate, with a refresh credit if overage triggers an early renewal. Without this clause, customers exceeding their commit pay the on-demand premium for the remainder of the contract year.