Snowflake Pricing in 2026: What You'll Actually Pay (and When the Bill Goes Sideways)

Most teams sign up for Snowflake assuming the bill will be the bill. It rarely is. The credit model is fair — you pay for what you use — but it has a long tail of features that bill quietly, capacity contracts that lock you in before you know your usage shape, and a new layer of AI services that have been GA-ing into customer invoices over the last year. If you're trying to forecast a Snowflake bill before signing, or trying to understand one you just got, this guide is for you.

Updated 2026-05-01 with current per-edition rates, the new Snowpipe pricing model, Gen2 warehouse multipliers, Cortex AI billing, and Iceberg storage treatment.

The short version

• Snowflake bills three things separately: compute (warehouse credits, billed per second after a 60-second minimum), storage (per TB per month), and cloud services (free up to 10% of compute, billed daily after that).
• A credit costs $2.00–$6.00 depending on edition (Standard / Enterprise / Business Critical / VPS), region, and whether you're on-demand or capacity. US AWS on-demand is the cheapest. Non-US adds roughly 50%; capacity contracts cut credits by 20-30%.
• Storage is $40/TB/month on-demand for AWS US East — $23/TB on capacity. Most pricing guides cite the discounted rate without saying so.
• The bill goes sideways for predictable reasons: forgotten serverless features (materialized views, Search Optimization), full-refresh SaaS ingestion, Cortex AI line items, Time Travel storage on heavy-update tables, and oversized warehouses that should have been XS or S.
• The biggest single lever is right-sizing warehouses and tightening auto-suspend — together those have cut bills 30-50% in documented cases.
• Snowflake starts being worth reconsidering not at a specific dollar threshold, but when optimization keeps surfacing new line items, more than half your data hasn't been queried in a week, and the apparatus around Snowflake (Fivetran + dbt Cloud + a BI tool) is itself running $1,300–$2,500/mo before you touch a query.

How Snowflake actually charges you

Snowflake pricing is consumption-based and decomposes into three bills you receive on the same invoice. Most guides cover the first three. The fourth bucket — newer pricing layers added in the last 18 months — is where most stale 2024 guides get the math wrong.

1. Compute — virtual warehouses

This is where the meter actually runs. A virtual warehouse is a cluster of compute that runs your queries and transformations. Warehouses consume credits while they're running, billed per second with a 60-second minimum every time the warehouse resumes. (Snowflake docs)

A credit's dollar cost depends on edition and region (next section). The credits-per-hour cost depends on warehouse size and doubles at every step:

Size	XS	S	M	L	XL	2XL	3XL	4XL	5XL	6XL
Credits/hour	1	2	4	8	16	32	64	128	256	512

5XL and 6XL are GA on AWS and Azure, with higher tiers in preview on US Gov regions. (Source: Snowflake warehouse overview.)

2. Storage: the rate most guides quote wrong

Snowflake charges per TB per month, calculated on the daily-average volume of compressed data. The number you'll actually pay is region- and rate-class-dependent:

• AWS US East, on-demand: $40/TB/month
• AWS US East, capacity contract: $23/TB/month
• Azure / GCP regions: comparable to AWS, with non-US regions running roughly 30% higher

Most pricing guides cite "$23/TB" without specifying that this is the capacity (pre-purchase) rate, not on-demand. (CloudZero confirms both rates.) If you're not on a capacity contract, you're paying the higher number.

Compression matters here. Snowflake automatically compresses data at roughly 3:1 in typical workloads. (Keebo) Thirty TB of raw data becomes ~10 TB on the bill. This is why storage usually isn't the dominant line for most teams — even at 100 TB raw, you're paying $1,300/month on capacity, not $4,000.

3. Cloud services: the daily 10% trap

Cloud services are the layer Snowflake uses to authenticate users, plan queries, and manage metadata. They consume credits — but Snowflake rebates them up to 10% of your daily compute usage. The 10% rule is applied daily, not monthly, which means a quiet weekend with a chatty BI dashboard can blow past the threshold even if your monthly average looks fine.

Most teams stay under the buffer. Overage typically signals one of two patterns: (1) BI tools auto-refreshing a lot of small queries, or (2) external tools polling Snowflake's metadata at high frequency.

4. The new layers (added since most pricing guides were written)

This is where most 2024-era guides get the math wrong. Three pricing surfaces have arrived or matured since the last refresh of most ranking content:

• Cortex AI services — Snowflake's hosted models (text completion, classification, summarization, embeddings, document parsing) bill per token consumed, on top of warehouse credits. Newer and larger models cost meaningfully more. Specific rates live in Snowflake's Service Consumption Table and shift over time. The proof these are landing as surprise charges: Snowflake itself ran an "AI Cost Optimization" webinar in April 2026 about Cortex Code, Cortex Analyst, Snowflake Intelligence, and Document AI line items — features that are "not experimental anymore" and showing up on invoices teams didn't budget for. (r/snowflake webinar invite)

• Snowpark Container Services — Containerized workloads run on compute pools, not virtual warehouses, with per-instance-type credit rates. CPU-XS runs at 0.06 credits/hour. GPU-L runs at 14.12. (Select.dev) That's a 235× differential between the cheapest CPU instance and the largest GPU. If you're running ML or container workloads you should price these separately.

• Gen2 warehouses — A faster-but-pricier warehouse class. Gen2 costs 1.35× the credits/hour of Gen1 on AWS, 1.25× on Azure, and is available on AWS us-west-2/eu-central-1 and Azure East US 2/West Europe (no GCP yet). Gen2 ships up to 4XL only. Snowflake claims 28-47% query speedup on TPC-DS benchmarks (Flexera) — but the credit savings are workload-dependent. One r/snowflake user halved daily costs on a long-running pipeline. Another paid 86% more for a short DBT DAG. Test on your workload before flipping the switch.

• Iceberg / external tables — Tables stored in Apache Iceberg format in S3, Azure Blob, or GCS don't incur Snowflake storage charges — storage shifts to your cloud provider's (much cheaper) rates. Snowflake still charges compute when you query them. (Espresso AI) For data queried less than once a week, this is the cheapest place to put it.

What a credit costs in 2026

Snowflake quotes credit rates in narrow ranges across editions, and the variation comes from region, on-demand vs capacity, and (in non-US regions) cloud provider markup.

Per-edition base rate (US AWS, on-demand)

Edition	Per-credit rate	When to use
Standard	$2.00	Default. Most workloads.
Enterprise	$3.00	Multi-cluster auto-scale, materialized views, advanced data masking, 90-day Time Travel.
Business Critical	$4.00	HIPAA / PCI / PHI workloads, customer-managed keys, failover for business continuity.
Virtual Private Snowflake	~$6.00	Government / regulated industries, dedicated VPC. Contact sales.

Non-US regions add roughly 50% (e.g., AWS London: Standard $2.70, Enterprise $4.00, Business Critical $5.40). Capacity contracts cut these by 20-30% on credits and ~42% on storage (Keebo), with a $25K/year minimum and 1-3 year terms.

The full $/hour matrix

This is the table most pricing guides won't give you. To find your actual hourly rate, multiply the warehouse credits/hour by the per-edition rate.

Warehouse	Standard ($2/cr)	Enterprise ($3/cr)	Business Critical ($4/cr)	VPS (~$6/cr)
XS (1 cr/hr)	$2	$3	$4	$6
S (2 cr/hr)	$4	$6	$8	$12
M (4 cr/hr)	$8	$12	$16	$24
L (8 cr/hr)	$16	$24	$32	$48
XL (16 cr/hr)	$32	$48	$64	$96
2XL (32 cr/hr)	$64	$96	$128	$192
3XL (64 cr/hr)	$128	$192	$256	$384
4XL (128 cr/hr)	$256	$384	$512	$768
5XL (256 cr/hr)	$512	$768	$1,024	$1,536
6XL (512 cr/hr)	$1,024	$1,536	$2,048	$3,072

US AWS on-demand. Azure / GCP rates are comparable to AWS in-region; non-US regions add ~50%. Capacity contracts subtract ~25%.

The headline most teams should keep in mind: a Medium warehouse on Enterprise costs $12/hour while it's running. Held warm 8 hours a day for a month (no auto-suspend gaps), you're at roughly $2,880 just on that one warehouse. If your BI tool keeps it warm or your dbt run leaves it on too long, the math tilts fast.

On-demand vs capacity — when to commit

On-demand means you pay the rates above, monthly, with no commitment. Capacity contracts are pre-purchases (1-3 years) for 20-30% off the credit rate and ~42% off storage. The minimum is $25K/year.

Two situations where capacity makes sense:

• Your monthly bill has been stable for 6+ months and you can defend the average to your CFO
• You're moving an existing workload from another warehouse and you've got real usage numbers

Two situations where it doesn't:

• You haven't run Snowflake in production for at least a quarter
• You're considering Snowflake for a use case that hasn't shipped yet (the discount looks great until your usage is half what you committed to)

If you're already in a capacity contract, the levers shift. You can't optimize your way out of unused commitment, but the seven moves below still apply to bill creep on top of the contracted floor.

5 real-world cost scenarios

Most pricing guides offer "Small / Medium / Large." That's not what teams shop for. Founders and finance leads want archetypes that match their company shape. All five below assume Standard edition, on-demand, AWS US East — multiply compute by 1.5× for Enterprise, 2× for Business Critical.

Tier	Archetype	Storage	Warehouse	Hours/day	Storage $/mo	Compute $/mo	Est. total
Hobby	5-person, single dashboard, 1 analyst	50 GB	XS	1	~$2	~$60	~$62
Startup	Series A, dbt on schedule, daily dashboards	500 GB	S	4	~$20	~$480	~$500
Growth	Series B, multi-team, near-real-time	5 TB	M	8	~$200	~$1,920	~$2,120
Mid-market	Production analytics, multi-workload	25 TB	L	12	~$1,000	~$5,760	~$6,760
Enterprise	Heavy ETL, multi-BU, multi-cluster	100 TB	XL	16	~$4,000	~$15,360	~$19,360

Worth flagging up front: if your shape lands in the Growth or Mid-market tier, you're not signing up for Snowflake on its own. You're signing up for the apparatus around it — ingestion (Fivetran or similar), transformation (dbt), a BI tool, and the people to run all of it. Definite replaces that whole assembly with one system, but more on that at the end. For now, here's the per-scenario breakdown.

Startup — Series A, daily dbt, modest reporting

A Series A team with one analyst or a stretched founder, running dbt once or twice a day, four to six dashboards, basic GA / Stripe / HubSpot integrations. Roughly 500 GB after compression. The variable that swings the bill: how aggressive is auto-suspend? Most teams at this stage have it at the default 600s (10 minutes). Tightening to 60s typically cuts compute 20-30% with no operational pain. Watch out for: Fivetran or Airbyte schedules running on a warehouse that doesn't auto-suspend cleanly between syncs.

Growth — Series B, multi-team, near-real-time

50-100 people, multiple departments hitting the same warehouse, dbt running on a schedule, a real BI tool. The variable that swings the bill: are ETL and analytics queries on the same warehouse? Running them together means analytics queries queue behind heavy ETL — your business users see a lag and complain, and you respond by upsizing the warehouse, doubling cost. Splitting workloads onto separate warehouses (M for analytics, L for batch ETL) often saves 25-40% AND speeds up dashboards. Watch out for: materialized views set up for "performance" that nobody monitors.

Mid-market — production analytics, multiple workloads

Series C+, 100-500 people, multiple data products in production. The variable that swings the bill: workload isolation and Enterprise edition features. At this scale, multi-cluster warehouses (Enterprise) become defensible — but if you're not actually triggering multi-cluster scaling regularly, you're paying $3/credit for a feature you don't use. Watch out for: Search Optimization on tables that don't need it (10 credits/hour, 24/7).

Enterprise — heavy ETL, multi-BU, multi-cluster

Multi-region, multi-cloud, multiple business units, real data-sharing programs. Snowflake's product breadth becomes load-bearing here. The variable that swings the bill: Cortex AI usage and reader-account consumption. AI workloads can move from $0 to mid-five-figures in a quarter. Reader account compute (queries against shared data) gets billed to whichever account owns the share — make sure that's set up the way you intend.

What real teams actually pay (community benchmarks)

Synthetic scenarios are useful for math. Real spend is useful for sanity-checking. Here's what r/snowflake users reported when asked, in a November 2025 thread:

• Consultant managing 4 small electric utilities, solo admin: under $3K/mo total — about $675/mo per tenant. Proof that Snowflake at small scale, with disciplined warehouse management, can be very cheap.
• Mid-sized SaaS, 5 accounts, 20 TB, 150K capacity contract: climbed from $2K/mo to $7K/mo over 12 months. The silent climb pattern — usage growth without optimization.
• ~100 users, 10-20 TB, dynamic-table-heavy modeling: $20K/mo, dominated by ingestion and modeling, not queries.
• Five environments, 30-200 person businesses, BI-heavy: $1-2K/mo each, roughly the SMB realistic baseline.
• 10-20 TB single environment, basic BI: $1-2K/mo. Storage isn't the cost driver at this scale; warehouse hours are.

These are anonymous, anecdotal, and directional — but they're better than synthetic scenarios for stress-testing whether the number you forecast for your shape is plausible.

Hidden costs that surprise people

The pricing page doesn't list these. The bill does.

Cloud services overage. Most teams stay under the daily 10% buffer, so this is rarely the dominant problem. When it does fire, it's almost always a workload pattern: a BI tool auto-refreshing many small queries, a data app polling Snowflake metadata at high frequency, or a third-party serverless tool that decided to fan out short queries because that's how it scales. The fix is workload-side, not configuration-side.

Cortex / AI services. Snowflake's AI features (text completion, summarization, embeddings, document parsing, the Cortex Analyst NLQ layer) bill per token on top of warehouse credits. Most teams underestimate this because token math is unfamiliar. The structural validation that this is a real surprise: Snowflake's own April 2026 "AI Cost Optimization" webinar was specifically about teams seeing Cortex line items they didn't plan for. When the vendor is hosting public webinars about their own surprise charges, the runaway-bill fear isn't paranoia.

Forgotten premium features. Materialized View auto-refresh runs at 10 compute credits per hour, as does Search Optimization. Both run 24/7 once enabled. Keebo documented one staging environment racking up $44,640/month with both services left on and forgotten on tables that didn't need them (Enterprise edition pricing in a non-US region; the math is 10 cr/hr × 2 features × 24 hrs × 30 days × ~$3.10/cr). The asymmetry is brutal: you turn them on once, prove they work, and the bill keeps running until somebody finds it.

Time Travel and Failsafe storage. Time Travel retains historical versions of your tables for up to 1 day on Standard, configurable up to 90 days on Enterprise+. Failsafe is a fixed 7-day window after Time Travel ends. On heavy-update tables, Keebo notes 90-day Time Travel "can silently triple your storage costs." If you don't need point-in-time recovery for your audit profile, drop the retention to 1-7 days.

Full-refresh SaaS ingestion. This used to be the "small file overhead" problem — Snowflake's old Snowpipe model billed a per-1,000-files charge on top of compute. Snowflake moved Snowpipe to flat credit-per-GB billing in 2025 (Snowflake docs), so that specific problem is gone. The current pattern is worse: a Salesforce or HubSpot pipeline that reloads the entire opportunity table every four hours when 0.5% of the rows actually changed. One r/snowflake user reported 55% of their credits going to data loading until they switched a single Salesforce sync from full-refresh to incremental — that one change dropped 12 credits/day to 1.5.

Egress and reader-account consumption. Internal data transfer inside Snowflake is free, but cross-region and shared-out data trigger cloud-provider egress rates that show up on your AWS / Azure / GCP bill, not Snowflake's. And if you're sharing data with customers, the queries they run against your shares bill against your account by default — easy to miss until the volume gets real.

The Gen2 vs Standard warehouse decision. Gen2 costs 1.35× on AWS, 1.25× on Azure, runs 28-47% faster on benchmarks. Workload-dependent payoff: one r/snowflake user halved their daily warehouse cost; another paid 86% more for a short DBT DAG. Test before you flip — don't upgrade in bulk.

Seven moves to cut your Snowflake bill

These are the levers that actually move the bill, in roughly the order you should try them.

1. Right-size warehouses

Most teams default warehouses too high. In documented optimization cases, Keebo found one customer where 87% of analytical queries ran in under 2 seconds on Large or XL warehouses — right-sizing alone saved $40,000/year. Another team moved BI queries from Medium to Small; runtime increased from 20s to 24s, costs fell 50%. The pattern: pick the smallest warehouse where queries finish in acceptable time, then size up only if specific workloads need it.

2. Aggressive auto-suspend

The default is 600 seconds (10 minutes). Set it to 60 seconds in production:

ALTER WAREHOUSE my_wh SET AUTO_SUSPEND = 60;

Don't go below 30s. Snowflake's suspension polling runs every 30 seconds, so anything lower is theatrical. The real tradeoff at low values: aggressive suspend kills the warehouse cache. If your dashboards re-run the same expensive query repeatedly, the re-fetch cost can exceed the idle credits saved. Tune by workload — analytics warehouses can go aggressive, ETL warehouses doing scheduled batch can stay at the default.

3. Capacity pricing for predictable workloads

Capacity contracts cut credit costs by 20-30% and storage by ~42%. Minimum is $25K/year, 1-3 year terms. Math: if your stable monthly run-rate is $5K/month at on-demand, capacity at 25% off saves $15K/year — easily covering the minimum. If your bill is jumpy or unproven, stay on-demand.

4. Result caching for dashboards

Snowflake caches query results for 24 hours when underlying data hasn't changed — free, automatic, easy to defeat. Make sure your BI tool isn't force-refreshing or passing small parameter changes that invalidate the cache.

5. Materialized views for repeated heavy joins

A materialized view auto-refreshes at 10 credits/hour while it runs. Worth it when the underlying query (a) runs frequently enough that the savings exceed the refresh, and (b) hits tables that don't change every minute. Don't enable and forget — see the $44,640/mo example above. Audit your materialized views quarterly.

6. Separate ETL warehouses from query warehouses

Run heavy batch loads on a dedicated warehouse, dashboard queries on another. Two wins: (1) one workload doesn't block the other, so you don't upsize a warehouse to handle peak interference; (2) you can right-size each warehouse independently. Standard edition supports this — you don't need Enterprise.

7. Move cold data to Iceberg / external tables

Iceberg tables registered in Snowflake incur zero Snowflake storage charges — storage shifts to S3, Azure Blob, or GCS at cloud-provider rates (5-10× cheaper). Compute still applies when queried. Best for data queried less than once a week, audit logs, raw event data you're keeping for compliance, anything cold. Most teams overpay 5-10× on cold storage they could move with a single CREATE TABLE statement.

When Snowflake stops being worth it

So: when does Snowflake actually stop being the right answer?

When it IS the right answer

Worth saying first: Snowflake wins for plenty of teams, including small ones. A consultant running four small electric utilities on Snowflake reported under $3K/month total — solo admin, disciplined warehouse management, no analytics team. Another community comment summarized it well: "Snowflake wins in most cases against Databricks and Fabric if you look at total cost of ownership. Licenses might just be 25% of TCO; work labor is a lot more, and Snowflake requires fewer folks to manage."

For teams with multi-cluster scaling needs, advanced governance (RBAC, column-level security, Time Travel for audit), multi-cloud presence, or active data-sharing programs, Snowflake's product breadth is a real advantage. Don't switch off Snowflake to chase a cheaper number if the apparatus you'd build to replace it is bigger than the bill you're trying to cut.

Behavior patterns that say it's time to reconsider

Not a dollar threshold — a behavior pattern. Some combination of:

• The bill grew faster than analytics value. Your usage 3×'d. Your insight throughput didn't.
• Optimization keeps surfacing new line items. Every quarter brings a new "huh, I didn't budget for that": Cortex, Search Optimization, materialized view refresh, Time Travel, Snowpark.
• More than half your stored data hasn't been queried in a week. You're paying for retention you don't use.
• Your workload is mostly BI dashboards and standard ELT — but you're on Enterprise or Business Critical for capabilities you rarely trigger.
• You're hiring (or about to hire) someone whose job is to manage the bill. That person's salary is a real line item.

It's the pattern, not the dollar amount, that matters. A team at $3K/month with three of these patterns has a bigger problem than a team at $15K/month with disciplined ownership.

The total-stack reality

Here's the part no other Snowflake pricing guide will tell you: your Snowflake bill is rarely your only data bill.

A realistic 50-person SaaS company in 2026 also pays for:

• Fivetran (4 mid-volume connectors, per Fivetran's own pricing example): ~$549/mo
• dbt Cloud Starter (5-seat minimum, per dbt pricing): ~$500/mo
• A BI tool starter (Hex / Mode / Sigma / similar, 8-15 seats): $240-$1,500/mo

Total wrap-around stack before Snowflake: $1,300-$2,500/month. Add the Growth scenario's ~$2,100/month for Snowflake itself, and the all-in apparatus is $3,400-$4,600/month — before anyone's salary to operate it.

The dollar total is the easy part. Every additional vendor adds a coordination surface — versioning, contracts, ownership, the people who keep it all wired together. That's the cost teams systematically underestimate when they price the assembly. (We've made the case in detail that most teams don't actually need the Snowflake + Fivetran + dbt + Looker bundle — and the apparatus tax is why.)

See real-world TCO comparisons by company shape →

If you're trying to figure out what your specific stack costs, the stack analyzer takes a URL and gives you an instant estimate.

Honest off-ramps

1. Optimize first. The seven moves above can cut 30-50% in many cases. Most teams haven't tried them all. (For a deeper tactical guide, see our strategies to reduce Snowflake costs.) If your bill is under $5K/month and you haven't applied the first three, you don't have a Snowflake problem yet — you have a not-yet-tuned-Snowflake problem.

2. Reconsider the architecture. If optimization keeps surfacing new line items, the bill isn't a Snowflake problem — it's a "we built more apparatus than we need" problem. Read our breakdown of Snowflake alternatives for startups for how BigQuery, Redshift, and Databricks compare for warehouse-shaped problems (and the BigQuery-specific breakdown if you're already on GCP), and where the all-in-one platform path fits a different shape.

3. The Definite wedge. Definite replaces the stack-assembly problem itself: ingestion, transformation, semantic layer, dashboards, and AI in one system — one apparatus to learn and run, instead of four contracts coordinated by people. If your team needs Snowflake's specific breadth — multi-cluster, advanced governance, data sharing — Definite is not a substitute for that breadth. If your team is assembling the stack to get to "answers and metrics for a 50-person company," Definite is a different shape of the same job. The point is structural, not cheaper.

FAQ

We're a 40-person SaaS company, about $8M ARR — what should I budget for Snowflake?

Use the Startup scenario above as your floor and the Growth scenario as your ceiling: roughly $500-$2,500/month for Snowflake itself, depending on whether you have a working dbt setup and how many dashboards your business users hit daily. Add roughly $1,300-$2,500/mo for the wrap-around stack (Fivetran, dbt, BI), so all-in is $1,800-$5,000/month before headcount. The variable that decides where you land: how aggressive your auto-suspend is and whether your ETL workload runs on the same warehouse as analytics.

Should I sign a capacity contract or stay on on-demand?

Stay on on-demand for at least one full quarter of production usage before considering capacity. The 20-30% discount looks great, but only matters if your committed usage matches reality. Companies that pre-commit before they understand their workload either over-buy (locking in unused capacity) or under-buy (forfeiting the discount on overage).

What makes the difference between a $500/month Snowflake bill and a $5,000/month one?

In rough order of magnitude: warehouse size and runtime, edition, number of separate workloads (dashboards + ETL + ML each tend to want their own warehouse at scale), forgotten premium features (materialized views, Search Optimization), and Cortex AI usage.

What are the most common reasons Snowflake bills go higher than companies expect?

In observed order: (1) auto-suspend left at the default 10 minutes, (2) warehouses oversized "to be safe," (3) full-refresh SaaS ingestion eating warehouse hours, (4) materialized views or Search Optimization enabled and forgotten, (5) Cortex line items arriving without a budget line, (6) a BI tool auto-refreshing dashboards triggering cloud services overage. Storage is rarely the difference-maker until you're past 25 TB raw.

At what company size does Snowflake actually make sense vs a simpler option?

Two questions. First: do you have someone on the team who will own warehouse hygiene? If yes, Snowflake works at small scale (the consultant in our community benchmark runs four utilities for under $3K/month). If no, the bill drift will exceed the savings of the simpler option pretty quickly. Second: do you actually need the Snowflake breadth — multi-cluster scaling, advanced governance, multi-cloud, data sharing? If no, an all-in-one platform is a different (often simpler) shape of the same job.

How is the cost of Snowflake calculated?

Compute (warehouse credits × per-edition rate × runtime in seconds, with a 60-second minimum) + storage (compressed TB/month × per-region rate) + cloud services (zero up to 10% of daily compute, then billed at the same credit rate as compute). Plus per-token Cortex charges if you use AI services, and compute-pool credits for Snowpark Container Services.

What does Snowflake cost per credit?

$2.00 on Standard, $3.00 on Enterprise, $4.00 on Business Critical, ~$6.00 on Virtual Private Snowflake — all US AWS on-demand. Add ~50% in non-US regions; subtract 20-30% on capacity contracts.

How are Snowflake credits calculated?

Warehouse size (credits/hour, doubling from XS=1 to 6XL=512) × actual runtime in seconds × the per-edition rate. So a Medium warehouse on Enterprise (4 credits/hour × $3/credit = $12/hour) running 30 minutes uses 2 credits and bills $6.

What is Snowflake's pricing model?

Consumption-based across three components: compute (per-second warehouse credits), storage (per TB per month), and cloud services (free up to 10% of daily compute). On-demand or capacity contract for compute and storage; per-token billing for Cortex AI services.

Does Snowflake have hidden fees?

Not hidden so much as un-bundled. The pricing page covers compute and storage clearly. What's not on the pricing page (and where bills go sideways): Cortex AI per-token charges, Snowpark Container Services compute pools, Search Optimization and Materialized View auto-refresh, Time Travel storage on heavy-update tables, and cross-region egress that bills via your cloud provider, not Snowflake. None of these are technically hidden — they're documented — but most are layered on top of the basic three-component model and easy to miss until they show up on the bill.

How accurate is the "starts at $2 per credit" line on Snowflake's pricing page?

Accurate for Standard edition, US AWS, on-demand, base region. If any of those four conditions don't apply to you, the rate is higher: Enterprise is $3, Business Critical is $4, non-US AWS adds ~50%, and capacity contracts subtract 20-30%. The starting figure is the best-case rate, not the typical rate.