Requests vs compute
Short, light functions are request-bound, long or memory-heavy ones flip to compute-bound.
Home / Dev & AI / Cloud Cost / Google Cloud Functions Cost Calculator
Cloud Cost
Google Cloud Functions Cost Calculator
Estimate your Cloud Functions bill. Enter invocations, memory and duration, and see invocation and compute costs with the free tier applied and a growth projection.
Estimated monthly cost
$0
Request cost—
Compute cost (GB-seconds)—
GB-seconds used—
Cost per 1M invocations—
Annual estimate—
Cost as invocations grow
Projected monthly spend at 2x, 5x and 10x volume.
What the Google Cloud Functions Cost Calculator does
Google Cloud Functions runs single purpose functions in response to events or HTTP calls, with no servers to manage. Like other serverless platforms it bills on invocations plus compute, where compute is memory and CPU time measured while the function runs. The free tier covers two million invocations and 400,000 GB-seconds each month.
This Cloud Functions cost calculator computes GB-seconds from your memory and duration, applies the invocation and compute rates, and subtracts the free tier. Functions are ideal for event driven glue work, and this tool shows when that stays cheap and when high volume tips it into meaningful spend.
Heads up on pricing. The rates built into this tool are public list estimates for July 2026 and can change without notice. Providers also offer batch discounts, prompt caching and volume tiers that lower real costs, so treat the output as a planning estimate, not a quote.
The formula
GB-seconds = invocations × (duration ÷ 1000) × (memory ÷ 1024)
cost = (billable invocations ÷ 1M × $0.40) + (billable GB-seconds × $0.0000025)
cost = (billable invocations ÷ 1M × $0.40) + (billable GB-seconds × $0.0000025)
Worked example
For 5,000,000 invocations at 300 ms and 256 MB, GB-seconds is 5,000,000 × 0.3 × 0.25 = 375,000. After the free tier, invocations cost 3 × $0.40 = $1.20 and compute is nearly free, for about $1.20 a month.
Ways to lower your cloud costs
- Right size resources. Pick the smallest instance, memory or capacity that still meets your performance target.
- Commit to steady load. Reserved instances, savings plans and committed use discounts cut rates sharply for predictable workloads.
- Use serverless for spiky traffic. Scale-to-zero services mean you pay nothing while there are no requests.
- Tier cold storage. Move rarely accessed data to cheaper classes such as Glacier, Coldline or Archive.
- Cut data transfer. A CDN and keeping traffic within a single region reduce the egress charges that quietly grow with scale.
Frequently asked questions
How is Google Cloud Functions priced?
By invocations at about $0.40 per million plus compute in GB-seconds, with a free tier of 2 million invocations and 400,000 GB-seconds monthly. Enter your usage above.
What is the difference from Cloud Run?
Cloud Functions targets small event driven functions, while Cloud Run runs full containers with more control. Pricing is similar, but Cloud Run suits larger or long lived services.
Does higher memory cost more?
Yes, GB-seconds scale with memory. But more memory can shorten duration, so the net effect depends on your workload.
When are Cloud Functions most cost effective?
For low to moderate, spiky, event driven workloads where scaling to zero avoids paying for idle capacity.
Are these rates current?
They are July 2026 estimates. Confirm current pricing on the Google Cloud pricing page for your region.