Snowflake cloud services credits: when they bill
Snowflake bills cloud services only on the days they exceed 10% of that day's warehouse credits.
When they do, it is usually a sign of many small queries, heavy metadata work or frequent logins.
Run read-only queries in your own console and paste the results. The report is worked out in your browser, with no access to your account.
What the check looks at
Credits by service and day from METERING_DAILY_HISTORY, including the daily cloud services adjustment.
Why it costs money
- Cloud services covers compilation, metadata, authentication and other work outside warehouses.
- Each day, Snowflake takes off cloud services credits up to 10% of that day's warehouse credits, in UTC. Only the rest is billed.
- Workloads with many very short queries, frequent SHOW and DESCRIBE commands, or large numbers of small files can push cloud services past the allowance.
How the tool measures it
To investigate. The report shows what this costs now and where to look. It claims no saving, because the results cannot prove one.
The report adds cloud services credits and the daily adjustment from query 1, scaled to a month, at your credit price. It shows what is billed and claims no saving, because the cause sits in the workload.
When the report raises it. Query 1 shows cloud services credits billed above the allowance.
In the sample report
The tool's sample does not raise this check, because its made-up account does not meet the condition above.
What to do
- 1Find the days with the largest billed cloud services in METERING_DAILY_HISTORY.
- 2Look for tools that run very many short queries or metadata commands, and for loads of many tiny files.
How to tell it worked. Watch CREDITS_ADJUSTMENT_CLOUD_SERVICES against CREDITS_USED_CLOUD_SERVICES by day after a change.
Trade-offs. Batching small queries or files can delay data. Weigh that against the credits.
The read-only query behind it
The same SQL the tool gives you. Each reads usage views and changes nothing.
Query 1: credits by service and average storage
-- Finitizer Snowflake Cost Check, query 1 of 5: the account bill
-- sf-cost-check-v1 (2026-11-10). Read-only: it reads Account Usage and changes nothing.
-- Credits by service for the last 30 complete UTC days, and average storage. Totals only.
-- Needs ACCOUNTADMIN, or a role with IMPORTED PRIVILEGES on the SNOWFLAKE database.
WITH w AS (
SELECT DATEADD(day, -30, DATE_TRUNC('day', CONVERT_TIMEZONE('UTC', CURRENT_TIMESTAMP()))) AS ws,
DATE_TRUNC('day', CONVERT_TIMEZONE('UTC', CURRENT_TIMESTAMP())) AS we
),
s AS (
SELECT COUNT(*) AS days,
AVG(storage_bytes) AS database_bytes,
AVG(stage_bytes) AS stage_bytes,
AVG(failsafe_bytes) AS failsafe_bytes,
AVG(hybrid_table_storage_bytes) AS hybrid_bytes
FROM snowflake.account_usage.storage_usage, w
WHERE usage_date >= w.ws::DATE AND usage_date < w.we::DATE
)
SELECT 'credits' AS row_kind,
m.service_type AS item,
SUM(m.credits_used_compute)::FLOAT AS credits_compute,
SUM(m.credits_used_cloud_services)::FLOAT AS credits_cloud_services,
SUM(m.credits_adjustment_cloud_services)::FLOAT AS credits_adjustment,
SUM(m.credits_billed)::FLOAT AS credits_billed,
COUNT(DISTINCT m.usage_date) AS days,
NULL::FLOAT AS average_bytes,
TO_VARCHAR(MIN(w.ws), 'YYYY-MM-DD') AS window_start,
TO_VARCHAR(MIN(w.we), 'YYYY-MM-DD') AS window_end,
CURRENT_REGION() AS region
FROM snowflake.account_usage.metering_daily_history m, w
WHERE m.usage_date >= w.ws::DATE AND m.usage_date < w.we::DATE
GROUP BY m.service_type
UNION ALL
SELECT 'storage', 'database', NULL, NULL, NULL, NULL, s.days, s.database_bytes::FLOAT,
TO_VARCHAR(w.ws, 'YYYY-MM-DD'), TO_VARCHAR(w.we, 'YYYY-MM-DD'), CURRENT_REGION()
FROM s, w
UNION ALL
SELECT 'storage', 'stage', NULL, NULL, NULL, NULL, s.days, s.stage_bytes::FLOAT,
TO_VARCHAR(w.ws, 'YYYY-MM-DD'), TO_VARCHAR(w.we, 'YYYY-MM-DD'), CURRENT_REGION()
FROM s, w
UNION ALL
SELECT 'storage', 'failsafe', NULL, NULL, NULL, NULL, s.days, s.failsafe_bytes::FLOAT,
TO_VARCHAR(w.ws, 'YYYY-MM-DD'), TO_VARCHAR(w.we, 'YYYY-MM-DD'), CURRENT_REGION()
FROM s, w
UNION ALL
SELECT 'storage', 'hybrid', NULL, NULL, NULL, NULL, s.days, s.hybrid_bytes::FLOAT,
TO_VARCHAR(w.ws, 'YYYY-MM-DD'), TO_VARCHAR(w.we, 'YYYY-MM-DD'), CURRENT_REGION()
FROM s, w
ORDER BY row_kind, credits_billed DESC NULLS LAST;Other checks in the report
- Snowflake auto-suspend: what idle warehouse time costsPriced
- Snowflake warehouse one size smaller: when it savesPriced
- Snowflake transient tables: cutting Fail-safe storagePriced
- Snowflake idle warehouse time: credits no query usedTo investigate
- Snowflake background services: credits outside warehousesTo investigate
- Snowflake warehouse pressure: queuing and spillingTo investigate
- Snowflake failed queries: warehouse time with no resultTo investigate
- Snowflake poor pruning: queries that read most of a tableTo investigate
- Snowflake repeated queries: the same work every hourTo investigate
- Snowflake clone-retained storage: bytes kept for clonesTo investigate
- Snowflake stage storage: files left in internal stagesTo investigate
What a credit and a terabyte cost in each region and edition: Snowflake pricing in 2026. Finitizer does this for BigQuery today. Snowflake and Redshift support is on the way.