Changes / Warehouses & lakehouses / Snowflake
Billing model changemedium impact
Snowpipe switches to a flat 0.0037 credits per GB
Snowpipe billing switches from per-second/per-core compute plus per-1,000-files fee to a fixed 0.0037 credits per GB ingested, applied automatically.
Who’s affected
Teams on Snowflake Standard or Enterprise Edition accounts that ingest data with Snowpipe, since the billing change applies automatically. Teams that load many small files, or very large volumes, will see the biggest shift.
Not affected: Business Critical and VPS accounts, which already moved to this model on August 1, 2025. Accounts that do not use Snowpipe (COPY INTO, Snowpipe Streaming-only, or other loaders) are also unaffected.
What it costs
Snowpipe moves from per-second/per-core compute plus a per-1,000-files fee to a flat 0.0037 credits per GB ingested. Your bill now scales with data volume rather than file count or compute time, so many-small-files pipelines may get cheaper and high-volume, large-file pipelines may get more expensive.
When to act
The change took effect 2025-12-08 and is automatic, so the work is to check your current credit usage against the per-GB model and fix any budget gaps now.
Blast radius: Snowflake cost dashboards, credit budgets and chargeback reports that assume per-file or compute-based Snowpipe costs; resource monitors may trigger earlier or later than expected.
What should you do? decision tree
- you do not use Snowpipe on a Standard or Enterprise accountNothing to do; confirm no pipes exist and move on.
- you already run Business Critical or VPSYou were moved on August 1, 2025; compare your recent bills to validate the per-GB charge.
- you ingest many small files and your Snowpipe bill dropped since DecemberUpdate your budget downward and consider whether you can keep file sizes as they are.
- your Snowpipe credits rose and you ingest large volumes per GBEstimate the per-GB cost with the calculator, then evaluate batching via COPY INTO or compressing/filtering data before ingest.
- costs still exceed budget after tuningRaise it with your Snowflake account team and review alternative ingestion paths or platforms.
Options
- OptimizePull Snowpipe usage history and compute GB ingested times 0.0037 credits to compare against your pre-change bill.
- OptimizeFilter columns and drop unneeded data at the source so fewer GB hit Snowpipe.
- Re-architectMove large, scheduled loads to COPY INTO on a right-sized warehouse if that beats the per-GB rate.
- NegotiateAsk your account team about ingestion credits or commit adjustments if the new model raises your spend.
Alternatives editorial picks, not sponsored
The facts straight from the source
Facts above are extracted from the source and checked word-for-word before publishing. The guidance sections are AI-assisted analysis based only on those facts: a starting point, not legal or procurement advice. Spotted an error? Tell us.
Related changes
- SnowflakeSnowflake signs agreement to acquire Observe
Snowflake announced a signed definitive agreement to acquire Observe, an AI-powered observability vendor, pending regulatory approval.
M&A - SnowflakeSnowflake: new service users can no longer use passwords (LEGACY_SERVICE blocked)
After enforcement, new non-human users must be TYPE=SERVICE, and LEGACY_SERVICE is invalid in CREATE USER or ALTER USER.
End of support - SnowflakeSnowflake blocks password sign-in for all remaining legacy service users
Non-human users are blocked from password authentication, and existing LEGACY_SERVICE users are migrated to TYPE=SERVICE.
End of support - Microsoft FabricFabric capacity overage (preview) billed at 3x pay-as-you-go
Fabric adds an opt-in preview where capacity overage is billed at 3x the pay-as-you-go rate rather than throttled, subject to admin-set 24-hour limits.
Billing