Snowflake Billing Explained: Credits, Storage and Invoices

Snowflake billing looks simple on the sales slide: you pay for what you use. Then the first invoice arrives with credits, compute-hours, storage tiers and transfer lines on it, and finance wants to know why the number is higher than last month when "nobody used it more". This guide explains how Snowflake actually bills: what a credit costs, how warehouses consume them, the charges that run when nobody's querying, and where the invoices and usage statements live.

It's written for the people who pay the bill, not the people who write the SQL. If you're still choosing a platform, our Snowflake practice page covers where it fits.

How does Snowflake billing work?

Five rules cover most of it:

1. Compute is billed in credits. Warehouses, serverless features and AI features all consume credits at published rates.
2. The price of a credit depends on your edition, cloud and region. The same query costs more on Business Critical in Cape Town than on Standard in Virginia.
3. Warehouses only bill while running, per second, but every start or resume costs at least one minute.
4. Storage is billed per terabyte per month, and data transfer out is billed per terabyte, separately from compute.
5. On-demand accounts are invoiced monthly in arrears. Capacity customers prepay a commitment, draw it down, and get a monthly usage statement.

All prices in Snowflake's Consumption Table are in US dollars. (Source)

What does a Snowflake credit cost?

On-demand prices per credit, from the Consumption Table effective 4 November 2026:

Region	Standard	Enterprise	Business Critical	Virtual Private Snowflake
AWS US East (N. Virginia)	USD 2.00	USD 3.00	USD 4.00	USD 6.00
AWS EU (Dublin)	USD 2.60	USD 3.90	USD 5.20	USD 7.80
AWS Africa (Cape Town)	USD 2.80	USD 4.20	USD 5.60	USD 8.40

Two things to notice. First, edition is a multiplier on everything: moving from Standard to Enterprise makes every credit 50% dearer, whether or not you use the Enterprise features. Second, region matters. Running in Cape Town costs 40% more per credit than US East on the same edition.

On a capacity contract, your Order Form sets a discount that's applied to these on-demand prices, and purchased capacity can be used across all your accounts. Snowflake's AI features bill in separate AI Credits (USD 2.00 global, USD 2.20 regional on demand), and your platform credit discount doesn't apply to them. (Source)

How many credits does a warehouse use?

Warehouse size sets the burn rate. A standard (Gen 1) warehouse doubles its hourly credits with each size step:

Size	XS	S	M	L	XL	2XL	3XL	4XL
Credits per hour	1	2	4	8	16	32	64	128

The sizes continue to 256 credits an hour for 5X-Large and 512 for 6X-Large. Gen 2 warehouses use more credits per hour on the same size label: 1.35 for X-Small on AWS and Google Cloud, 1.25 on Azure, scaling the same way. They're faster for many workloads, so they can still be cheaper per job. Measure it rather than assume it. (Source)

The metering rules matter as much as the size:

• Credits are billed per second, with a 60-second minimum each time a warehouse starts or resumes.
• Resizing up also bills a minute's worth of the extra credits.
• Suspending and resuming within the first minute produces multiple one-minute charges.
• Interactive warehouses have a 60-minute minimum on each start or resume.

So an X-Small warehouse woken every few minutes by a dashboard can cost more than you'd guess from its size. (Source)

What is the cloud services charge?

Snowflake's cloud services layer handles query compilation, metadata, authentication and the rest of the plumbing. It's charged at 4.4 credits per hour of use, but there's an allowance: you pay nothing for cloud services on any day when it's 10% or less of that day's warehouse credits. The adjustment is calculated daily, and cloud services used by serverless features don't count towards it.

Most accounts never see the charge. The ones that do tend to run huge numbers of tiny queries, heavy metadata operations or lots of cloning, so the plumbing outgrows the compute. (Source)

How is Snowflake storage billed?

Storage is billed on the average terabytes stored per month, compressed. On demand, it's USD 23.00 per TB per month in AWS US East and USD 27.40 in AWS Cape Town, with lower capacity prices as your commitment grows (down to USD 13.80 and USD 16.44 respectively at the highest tier).

The surprise is historical data. Storage fees apply during both the Time Travel retention period and the Fail-safe period after it, so deleting or overwriting a large table doesn't immediately shrink the bill. For staging and scratch data, transient and temporary tables have no Fail-safe period and at most one day of Time Travel, which avoids most of that cost. (Source)

What does data transfer cost?

Moving data within the same cloud region is free. Moving it out costs per terabyte, set by the source region:

From	Same cloud, different region	Different cloud or internet
AWS US East (N. Virginia)	USD 20 per TB	USD 90 per TB
AWS Africa (Cape Town)	USD 147 per TB	USD 154 per TB

If your BI tool, reverse-ETL jobs or data shares pull large volumes out of a Cape Town account into another region or cloud, transfer can rival compute. Keep heavy consumers in the same region as the account. (Source)

Why didn't our Snowflake bill go down?

The usual culprits, roughly in order:

• Warehouses that keep waking up. The default AUTO_SUSPEND is 600 seconds (10 minutes), and every scheduled job, dashboard refresh or tool that pings a warehouse resumes it and starts another minimum charge. Lower auto-suspend on warehouses that serve short queries. (Source)
• Serverless features. Snowpipe, clustering, materialized view maintenance, search optimisation and serverless tasks run on Snowflake-managed compute and bill whether or not your warehouses are running. (Source)
• Storage that hasn't left yet. Data you deleted is still billed through Time Travel and Fail-safe.
• An edition or region change. Same usage, higher price per credit.
• Reporting lag. Cost data in Snowsight can take up to 72 hours to appear, so last week's fix may not show in this week's numbers yet. (Source)

Set resource monitors with a credit quota on every warehouse, so a runaway job suspends the warehouse instead of running all weekend. Note that resource monitors only cover warehouses, not serverless features. (Source)

Where do I find Snowflake invoices and usage?

Everything lives in Snowsight, but who sees what depends on how you buy:

Document	Who gets it	Where
Invoice	On-demand customers	Admin » Billing » Snowflake billing tab » Invoices
Monthly usage statement	Capacity (Order Form) customers, from July 2023	Admin » Billing
Cost dashboards	Anyone with cost-management access	Admin » Cost management

To open invoices you need the GLOBALORGADMIN role in the organization account, or both ACCOUNTADMIN and ORGADMIN in an account with ORGADMIN enabled. (Source) Usage statements itemise the month in credits consumed and currency spent, which makes them the document to reconcile against your commitment. (Source)

For anything finer than a monthly total, query the views in the ACCOUNT_USAGE and ORGANIZATION_USAGE schemas. That's how you attribute spend to teams and catch a warehouse that's quietly doubled. (Source)

Is tax included, and what should South African buyers watch?

Fees don't include tax. Snowflake's terms say that where it has a legal obligation to collect tax, it invoices you for it, and you're responsible for the rest. (Source)

For South African companies, four more things:

• It's a US-dollar bill. Consumption is measured in USD. If your Order Form says you'll pay in another currency, each invoice is converted from USD at the spot rate on the last day of the invoiced period, so the rand cost moves with the exchange rate even when usage doesn't. (Source)
• Cape Town costs more. Credits, storage and egress are all priced higher in AWS Africa (Cape Town). Pay it where data residency or latency genuinely needs it, and do the maths before you assume you need it.
• Card fees. On-demand accounts paying by card can pick up cross-border and forex fees on every charge. Ask your bank, or use a card without them.
• VAT treatment. How VAT on a foreign cloud service lands in your books is a question for your accountant. Ask before the first invoice, not at year-end.

A one-page checklist for finance

• Confirm your edition, cloud and region, because together they set the price of every credit.
• Put a resource monitor with a credit quota on every warehouse.
• Set auto-suspend to a minute or two on warehouses that serve short, bursty queries.
• Use transient tables for staging and scratch data.
• Keep heavy data consumers in the same region as the account to avoid egress.
• Review serverless feature spend monthly, separately from warehouses.
• Budget the bill in USD, and agree the VAT treatment with your accountant.

Get the bill under control, then get the value

Billing is the admin. The return comes from what your data does once it's in Snowflake: reports people trust, pipelines that run on time and AI that works on your own data. Our Snowflake partner practice designs, builds and runs Snowflake platforms through our cloud data platforms service, from warehouse sizing and cost guardrails to the data pipelines that feed it.

Want a second opinion on what your Snowflake bill should look like? Book a Free AI Assessment and we'll size it with you.