Skip to content

Snowflake pricing explained: credits, editions and costs

Snowflake bills compute in credits, storage per terabyte and data movement per terabyte. Here is what each costs at list price, where bills grow without anyone noticing, and the controls I put in place before go-live.

Noel D'Costa beside a finance desk with a cost dashboard and printed invoices
Contents
  1. How Snowflake credits work
  2. Editions and the price per credit
  3. Storage, data transfer and the other line items
  4. Cortex AI and Snowpark Container Services
  5. Illustrative arithmetic: one warehouse, two habits
  6. On-demand vs capacity contracts
  7. The controls I set before go-live
  8. What to do next
  9. Frequently asked questions

Snowflake pricing is usage-based: you pay for compute in credits, for storage per terabyte per month, and for data moved out of a region. A credit lists at $2.00 to $3.25 on Standard edition and $4.00 to $6.50 on Business Critical, depending on cloud and region (list price, checked October 2026).

That headline number tells you very little. What you pay depends on how big your warehouses are, how long they run, which serverless features are switched on, and whether anyone is watching.

In the manufacturing and defence programmes I've worked on, the price per credit was never the problem. The problems were warehouses left running, serverless features nobody had budgeted for, and a contract sized on a guess. This guide covers the units, the list rates, the hidden cost drivers and the controls I'd put in place on day one.

Snowflake has two billing units now. Platform credits pay for virtual warehouses, Snowpark Container Services, serverless features and cloud services. AI credits pay for Cortex AI features. When an older contract says "credits", it means platform credits.

A virtual warehouse is a named block of compute. You pick a size, and the size sets the credit rate. Each step up doubles the rate. A running warehouse is billed per second, with a minimum of 60 seconds every time it starts or resumes. A suspended warehouse costs nothing.

The table below is from Snowflake's warehouse documentation and the Service Consumption Table effective 9 October 2026.

SizeCredits per hour (standard, Gen1)Credits per hour (Gen2, AWS)
X-Small11.35
Small22.7
Medium45.4
Large810.8
X-Large1621.6
2X-Large3243.2
3X-Large6486.4
4X-Large128172.8
5X-Large256n/a
6X-Large512n/a

Gen2 warehouses cost more per hour (1.25 times on Azure, 1.35 times on AWS and GCP) because they run faster. Whether they work out cheaper depends on your workload, so test before you switch. Gen2 is not available in every region and is not the default.

Two other warehouse types carry their own minimums. Interactive warehouses list at lower hourly rates (0.6 credits an hour at X-Small) but bill at least 60 minutes every time they start. Snowpark-optimised warehouses for memory-heavy Python and ML work run from 1 to 6 credits an hour at the smaller sizes, depending on the memory option.

Multi-cluster warehouses multiply the rate by the number of clusters running. A Medium warehouse allowed three clusters can burn up to 12 credits an hour. Multi-cluster is an Enterprise edition feature.

The edition you choose sets the price of every credit you burn, so it is the single biggest lever in the contract. The ranges below come from Table 2(a) of the Snowflake Service Consumption Table, on-demand list price per platform credit, checked October 2026.

EditionWhat it addsOn-demand list price per creditAWS US East (N. Virginia)
StandardCore platform, Snowpark, data sharing, Time Travel$2.00 to $3.25$2.00
EnterpriseMulti-cluster warehouses, finer governance controls, longer Time Travel, Query Acceleration$3.00 to $4.90$3.00
Business CriticalTri-Secret Secure, private connectivity, failover and failback$4.00 to $6.50$4.00
Virtual Private Snowflake (VPS)Everything in Business Critical, in an environment isolated from other accounts$6.00 to $9.75, plus an annual deployment fee$6.00

The cheapest regions are the main US regions. The most expensive are places like Zurich, Switzerland North, Hong Kong and Dammam. For a GCC or European buyer, region choice can move the bill by 30% or more before you write a single query.

For defence, this matters more. In the US government regions in the table (including AWS US Gov West 1, the DoD region and the FedRAMP High Plus regions), Standard and Enterprise are not offered. Business Critical starts at $4.80 to $5.60 a credit. If your programme has sovereignty or export-control constraints, budget for Business Critical from the start. Standard edition lacks the encryption and private connectivity controls a defence security review will ask about. I have not deployed Snowflake in a government or GCC region myself, so treat these regional figures as list-price guidance and confirm with Snowflake which services are live in your target region.

For most manufacturers I'd start on Enterprise. Multi-cluster warehouses and Query Acceleration are what keep month-end reporting from queuing behind the data science team.

Storage is billed on the monthly average of compressed data. On demand it lists at $23 per TB per month in the main US regions, $24.50 in Frankfurt and $39 in AWS US Gov West 1. Capacity contracts with larger annual commitments bring it down, to $13.80 per TB at the top tier in US East.

Data transfer is free within the same cloud and region. Moving data out costs money. From AWS US East it lists at $20 per TB to another AWS region and $90 per TB to another cloud or the internet. Government regions charge more. If your ERP sits on Azure and Snowflake on AWS, every extract that leaves Snowflake back to Azure carries that cross-cloud rate. My guide to getting ERP data into Snowflake covers where to place the account.

Cloud services is the layer that handles logins, query compilation and metadata. It is billed at 4.4 credits per hour of use, but only the part above 10% of that day's warehouse credits. Most accounts never see a charge. Accounts that run huge numbers of tiny queries, or poll metadata constantly from BI tools, do.

Serverless features run on Snowflake-managed compute at one credit per compute-hour times a feature multiplier. Nothing shows in your warehouse list, which is why they surprise people. From Table 5 of the consumption table:

  1. Snowpipe: 0.0037 credits per GB loaded.
  2. Automatic clustering: 2 times compute, plus cloud services.
  3. Search Optimization Service: 2 times compute, plus cloud services.
  4. Materialized view maintenance: 2 times compute, plus cloud services.
  5. Serverless tasks: 0.9 times compute, plus cloud services.
  6. Query Acceleration: 1 times compute, billed per second when used.

Clustering and search optimisation on a fast-changing table can quietly cost more than the warehouses that query it. I review every one of them before go-live.

Cortex AI bills in AI credits, a separate unit. On demand an AI credit lists at $2.00 (global) or $2.20 (regional). Your platform credit discount does not apply to AI credits. Cortex functions charge per million tokens, with input and output often priced differently. In the consumption table, llama3.3-70b lists at 0.36 AI credits per million tokens each way, and mistral-large2 at 1.00 input and 3.00 output. Cortex Analyst bills 67 platform credits per 1,000 messages, and Cortex Search 6.3 AI credits per GB per month of indexed data.

If you run Cortex in a regional-only mode for data residency, expect the higher rate. The cross-region inference documentation explains the routing options. For defence, regional processing is usually the only acceptable setting. My piece on Snowflake Cortex AI and Snowflake Intelligence covers what these features do.

Snowpark Container Services runs your own containers on compute pools. Each node type has a credit rate. The smallest general-purpose nodes list well under 0.1 credits an hour, and GPU nodes run from about 0.5 to over 20. Nodes bill a five-minute minimum each time they start. A GPU pool left running over a weekend is the most expensive mistake I can think of on this platform.

Snowflake rarely gets expensive because of the price per credit. It gets expensive because nobody owns the warehouses.

This example is illustrative only. It uses list rates from the October 2026 consumption table: Enterprise edition, AWS US East, $3.00 per credit, storage at $23 per TB.

A Medium warehouse burns 4 credits an hour. Used for ten hours a day on 22 working days, that is 880 credits, or $2,640 a month. The same warehouse with auto-suspend switched off runs 720 hours a month. That is 2,880 credits, or $8,640. Same queries, same users, more than three times the bill.

Now add 20 TB of compressed storage: $460 a month. Storage is real money, but in the platforms I've worked on it has rarely been the line that worries a CFO. Idle compute and unwatched serverless features are.

Enterprise discounts and capacity commitments will change these numbers. The shape will not.

Snowflake sells two ways. On demand means you pay list price monthly in arrears, with no commitment. Capacity means you commit to an annual spend and get a discount on platform credits, set in your order form. Capacity can be used across all your accounts. Storage gets cheaper as your annual contract value grows. AI credits have their own tiers.

My rule: run on demand, or a small commitment, for about three months. Then size the contract from ACCOUNT_USAGE data, not from the vendor's sizing workbook. Those three months also show you how the consumption model behaves on your own workloads. An oversized commitment is money spent whether you use it or not. Read the rollover terms closely. The same discipline applies to any enterprise software deal, which I cover in my ERP contract negotiation case study.

Snowflake gives you good tools. The cost control documentation explains them. They only work if someone configures them before the first production load.

  1. Auto-suspend on every warehouse. It is on by default. Check nobody turned it off. Very short settings on bursty workloads can cost more, because each resume bills the 60-second minimum.
  2. Right-size by workload. Separate warehouses for ELT, BI and data science. Start small and size up only when query history shows spilling or queuing.
  3. Multi-cluster with limits. Set a sensible maximum cluster count. Use the Economy scaling policy where some queuing is acceptable.
  4. Resource monitors. They track warehouse credits and can suspend a warehouse at a threshold. They do not cover serverless features.
  5. Budgets. Monthly spending limits with alerts that do cover serverless features. Use custom budgets per department.
  6. Query Acceleration with a scale factor. Useful for spiky scans, but cap it. The default scale factor lets it add up to eight times the warehouse's own rate.
  7. Tagging. Object tags on warehouses and users, query tags for shared applications. Without them, nobody can say which plant, programme or function spent what.
  8. Weekly review of ACCOUNT_USAGE. WAREHOUSE_METERING_HISTORY for warehouse credits, QUERY_ATTRIBUTION_HISTORY for per-query cost, TAG_REFERENCES to join it to owners. Remember per-query cost excludes idle time, storage, serverless and AI.

The trial is a good way to learn this before you commit. Snowflake currently offers a 30-day trial with $400 in free credits. AI features are disabled until you add a card. Choose the cloud, region and edition you would actually buy, because they cannot be changed later.

Before you sign, get three numbers on one page: credits per month by workload, the edition and region price, and serverless plus AI as separate lines. If your vendor or SI cannot give you that, the estimate is a guess. If you are still choosing a platform, my Snowflake vs Databricks comparison and Databricks pricing guide use the same lens.

I help organisations size data platform contracts and set up cost governance before go-live. If that is useful, get in touch.

How much does a Snowflake credit cost?

On demand, a platform credit lists at $2.00 to $3.25 on Standard edition, $3.00 to $4.90 on Enterprise, $4.00 to $6.50 on Business Critical and $6.00 to $9.75 on Virtual Private Snowflake, depending on cloud and region (list price, checked October 2026). In AWS US East the figures are $2, $3, $4 and $6. Capacity contracts apply a negotiated discount to these rates.

Is Snowflake billed per second?

Yes. Standard virtual warehouses bill per second with a 60-second minimum each time they start or resume. Interactive warehouses have a 60-minute minimum, and Snowpark Container Services nodes a five-minute minimum. Suspended warehouses cost nothing.

How much does Snowflake storage cost per TB?

On-demand storage lists at $23 per TB per month in the main US regions, higher in some regions such as $24.50 in Frankfurt and $39 in AWS US Gov West 1. It is billed on compressed size. Capacity contracts lower the rate as your annual contract value grows.

Does Snowflake have a free trial?

Yes. Snowflake offers a 30-day trial with $400 in free credits. The trial ends when 30 days pass or the credits run out, whichever comes first. AI features are disabled until you add a credit card, and the cloud, region and edition you choose cannot be changed later.

What is the Snowflake cloud services 10% adjustment?

Cloud services usage is free up to 10% of that day's warehouse credits. Only the usage above that line is billed. Serverless features and Snowpark Container Services usage do not count towards the allowance.

Why is my Snowflake bill higher than expected?

The usual causes are warehouses that never suspend, oversized warehouses, multi-cluster with no cap, and serverless features such as automatic clustering, search optimisation and materialized views. Cortex AI usage and cross-cloud data transfer also add up. Query WAREHOUSE_METERING_HISTORY and the serverless usage views to find the source, then set budgets and resource monitors.

Noel D'Costa

Written by

Noel D'Costa

25 years across SAP and Oracle ERP programmes in aviation, government, finance, retail, and manufacturing. Finance background. I help leadership teams scope transformations honestly, recover programmes in trouble, and build systems that survive their first year in production.

Next step

Running an ERP programme right now?

If this article touched on a programme you are live in right now, a 30-minute conversation usually gets further than another week of internal analysis.